Update

So here we go... I have been spending alot of time this weekend researching and thinking about the code aspect like the use of the SysAppLaunch function used to pass control between function calls (using the ScrAppLaunchCode launch code). If anyone wants to know the speed of the SysAppLaunch try changing the time in the prefs app and quickly tap the find silk button and count the number of seconds it takes for the find dialog to show. This is going through every application's PilotMain even if it returns straight away on most apps. I have also made sure that this method is compatible with PalmOS Cobalt. The object component API has now numbered sub components and I am getting closer to the end of the perspective design and naming the functions. Once the function naming of the core (the object component) is done I can start coding the data sub component (hopefully). Screens is moving along and is showing more and more opportunity as time goes by. I have decided that by releasing the final release (demos will only be for PalmOS) on both PalmOS and PocketPC at once will allow Screens to get more users and because the changes are minimal, there is no 'cost' for the porting. The only problem is that code written for PalmOS wont work on PocketPC and visa versa. I might think about using java since it's platform-independent and all it needs to do anyway is call the Screens API. However drivers or any software which uses API's outside of Screens should be natively coded. If I could get the java idea to work it would allow the core to be natively coded and most of the other apps to be java compiled.