Hi Shane (that sounds weird),<br><br>The reason I decided to make two separate projects was because the API should provide an application interface only (which should be - in a perfect world - compatible with all implementations of GEM). The idea is that you could download the gemapi project and use it to develop applications for DR GEM, OpenGEM, Atari GEM, GEMix, whatever. The restriction being that the API only covered VDI and AES calls - OS specific stuff would be up to the developer. I also considered adding a third set of calls to the API for common operations that are not supported by the existing GEM interface - like common access to configuration files (like the Windows xxxProfileString() functions) - this would require a POSIX based OS (or compatibility library) though.<br>
<br>The 'gemix' project was purely an implementation of VDI, AES and the Desktop for Linux. It would contribute code to the API project (as a binding that could be used) but the API project would not depend on it.<br>
<br>I think the two projects are aiming for different goals - the first (gemapi) is aiming for a common API for all GEM implementations. The second is an implementation of the GEM API for a new platform.<br><br>I've looked at the Seasip site before (I originally came across it because I was making a port of Manic Miner - my favourite game on my first computer, the ZX Spectrum - and he had some details of map formats etc). Once again it seems Intel/DOS specific. Other sites I've come across seem Atari/TOS specific. It would be nice to have a generic GEM interface that could be used by all source (and would ease porting between the various implementations).<br>
<br>Regards,<br>ShaneG<br><br><div class="gmail_quote">On Mon, Nov 9, 2009 at 9:48 PM, Shane Martin Coughlan <span dir="ltr"><<a href="mailto:shane@shaneland.co.uk">shane@shaneland.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Shane<br>
<div class="im"><br>
> Anyway - as I have stated previously I have created the 'gemapi' and<br>
> 'gemix' projects on SourceForge. I'm happy to hand over control of the<br>
> 'gemapi' project to those with more of a history (and more experience)<br>
> with GEM. I intend to continue with the 'gemix' project as a 'GEM<br>
> like' (at the very least) implementation of the GEM API for the Linux<br>
> kernel (initially, ideally it should work on any POSIX compliant<br>
> system that someone can provide a VDI implementation for). SourceForge<br>
> does provide for webspace as well so maybe the 'gemapi' project would<br>
> be a reasonable place for a documentation Wiki and other developer<br>
> style information?<br>
<br>
</div>Could the two projects be combined into one codebase that is not<br>
platform dependent, allows backward compatibility (when running on x86)<br>
and potentially also allows Atari platform tools to work?<br>
<br>
I think a starting point for you is probably to have a chat with John.<br>
He has done a lot of the work to modernize GEM. His site is here:<br>
<a href="http://www.seasip.info/Gem/index.html" target="_blank">http://www.seasip.info/Gem/index.html</a><br>
<br>
Regards<br>
<font color="#888888"><br>
Shane<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
gem-dev mailing list<br>
<a href="mailto:gem-dev@simpits.org">gem-dev@simpits.org</a><br>
<a href="http://www.simpits.org/mailman/listinfo/gem-dev" target="_blank">http://www.simpits.org/mailman/listinfo/gem-dev</a><br>
</div></div></blockquote></div><br>