Internally the T3 uses a different mechanism to support its collapsible/dynamic input 
area. I don't know what the end delivery mechanism will be, but from what I understand 
there will be a set of prc's from them that will create a compatibility layer for the 
platform DIA API  on the T3. For the T3 simulator there will be a similar set of dll's 
to do the same. Once the PRCs or DLLs are installed, you should be able to use the 
platform API and everything will work fine.

As for the overall story, the first platform implementation of the DIA API is OS 5.3.  
However, Garmin and Tapwave running on OS 5.2 have implemented, with our support, a 
compatible DIA API. And, as mentioned, the Palm Inc device will be compatible once the 
compatibility layer is put on there. As a developer you ought not think of OS version 
but rather check to see if the PinMgr feature is set.

The Sony API is, of course, different. But it is less different then you might 
suspect. The enabling of the DIA is done on an app by app basis on their API versus a 
form by form basis on the platform API, but the process of resizing and re-laying out 
the forms is the same. There is a sample code int he KB (article 507) that shows how 
to write an application that will work on both Sony and the platform API. Actually, 
many applications probably can use the utility functions in that sample which abstract 
the differences between the two APIs as is. I have tested the sample in attached to 
article 507 on OS 4 Sony, OS 5 Sony (tall and landscape), garmin, OS 5.3, tapwave and 
the Palm Inc device. But please do submit any feedback you have or any bug you may 
find with it to the feedback form available from the knowledge base article page (yes 
we do read them :)

As for future compatibility of the PinMgr API, 68K applications that use the platform 
API will continue to work in OS 6 through PACE. The native window manager is 
fundamentally different then in OS 5 (it has to be to better support the multithreaded 
UI in 6) such that native apps will use a slightly different API. But like I said, 68K 
apps can and should still use the same API as they would for OS 5.

BTW: The sample does not handle the status bar at the moment, but I will try and add 
that in the near future. It should be pretty easy to do so on your own.

-Ezekiel Sanborn de Asis
PalmSource Developer Support





--
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to