I am not a specialist but I can help a little bit:
Jeffrey Siegel wrote:
1. Will CW source code be easily portable to PODS if I have to move there?
Not very "easy", take some time depending of the size/complex is your
project, but there is good points: in your case your project is a C not
a C++ so this is a good point, also every time we can see a lot of
questions here about people migrating CW->PODS so you have a lot of
resources to research and a lot of people to ask how-to.
The big points in migrating CW->PODS would be :
1) migrating the resources,
2) adaptating the multisegment stuff
3) creating your makefike
...did I forget any?
So consider taking 1 or 2 weeks to complete migrate your code depending
on the size of it, but no risk of a "impossible mission"
2. Does CW have all of the SDK definitions for all of the newer devices
released in the last year (Treo 650, LifeDrive, etc)? If not, is it easy to
find and add them?
did you mean that you plan to design using any of the specifics for
these device? Sorry I never did it but I *think* that is not difficulty
as CW is very customizable (xml stuff). In case of integrating
simulators, and debuggers I already integrated lifedrive, Treos and
Cobalt Simulator with no problem, but sorry never tried specific
plugedin SDK stuff.
3. Are there any debugging differences between CW and PODS? Can I simulate
different devices in both environments (Garmin, m515, LifeDrive, etc.)?
in CW you can (from Palm III to Cobalt) and I think that in PODS is ok also.
Franco
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
