Just reading the overview of Cobalt makes me wonder whether it is a good time to port to PPC. If one needs to change that much, might as well picking up a new platform.
Alex,
What, to you, seems to be "that much"? Why would updating to the Protein API (which is even optional for running on Cobalt devices) seem so overwhelming? As Ben pointed out, there's really not that much:
At 6:44 AM -0600 3/2/04, Ben Combee wrote:
Some minor things change -- you don't have card numbers anymore, you use different typedefs. Some major things change -- you need to support update-based windows, you can't hack into system internals.
Is removing unused card number parameters and doing a search/replace for UInt32 -> uint32_t so onerous that you think porting to PPC is easier?
Again, as Ben says:
At 6:44 AM -0600 3/2/04, Ben Combee wrote:
I'd urge you to read just the first few chapters of the "Porting Apps to Cobalt" PDF that's in the Cobalt docs.
After that, I for one would be interested in hearing what difficulties you see facing, and why you feel they're so insurmountable.
-- Keith Rollin -- Development Tools engineer
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
