Blake, Thanks for your response. I agree with you, my statements may have been strong, but I do think this is an interesting subject. I am currently VERY READY to migrate an app we wrote in C with CodeWarrior to anything else. We agree on the benefits of C, but I think my other comments on High Level Languages are somewhat correct, and being in business to make money, and develop quickly, I think it would be the best use of programming resources to go that way, IF AND ONLY IF, they provide the expected results.
That is my quest now, which is why I posted my comments. I appreciate your comments, as I agree fully with the approach you took and realize, no matter what development platform we may choose, it will still have to have device/OS specific code segments. I hope you are right that much more than 20% of the code will be common, as that is when development resources would be used efficiently to make multiple platform development cost effective. So, I take it your vote for this job is C++. I also see that David Martin believes that APPFORGE also could be a candidate, but David doesn't use APPFORGE. John Blackman suggested Satellite Forms. I was looking at NSBasic as well. I heard of a company in France who has a dev system that supports something like 4 dozen platforms. I also feel that it is not only important that these dev systems be able to do the job, but it is important that the companies that produce them are legitimately willing to support their product. There needs to be a future in these companies or what is the point of using them, if they are not going to "keep their systems up to date with the latest features of their target systems". I feel very comfortable with CodeWarrior and PILRC, as obviously lots of developers use them. The French company got really bad reviews on this forum in the past for support and documentation. The others get mixed reviews. Anybody have any other suggestions, or is this all that is worth looking at in today's dev system market? -------------------------------------------------------------------- Gary Gorsline Easy Business Software ========================== End of Message ========================== ----- Original Message ----- From: "Blake Winton" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Thursday, December 26, 2002 2:45 PM Subject: RE: Windows CE on J2me Need Help > > It really requires two completely separate sets of code to > > provide the appropriate user interface in your system. > > Maybe 10% to 20% of your code could be common between the > > platforms, but then there is the endian issues, so it > > really isn't worth trying to have a common code set, in my > > opinion. > > Speaking as a developer who works at a company that develops > applications for the Palm and PocketPC, my opinion differs > from yours to a great degree. Far more than 10 or 20 percent > of our code is common to the two platforms, and the fact that > the business logic runs on two separate platforms helps us > narrow down bugs very quickly. (If it's in both, it's a > common-code bug. If it's only in Palm, then we only have to > look through the Palm stuff. Ditto for PocketPC.) We've > separated our code out into Models, Views, and Controllers, > and the only platform-specific code we have are in the sub- > classes of the various Views. (So, we'll have a FooView, > and a PalmFooView, and a WinceFooView, and recently even a > Win32FooView.) > > Having said this, we are doing all of our Palm development > in C++. It makes for larger applications than I might like, > but our clients seem to think that the benefits of having a > product for both of the major handheld systems out there is > more than worth the slightly larger size. > > > So, is Java the answer? > > I've worked with Java on the Palm (back when it was the KVM), > and I don't think Java is the answer yet. Maybe when the > new processors are more common it will be feasible. On my > Palm Vx I could get the demos working, but as soon as I tried > to write something a little more complicated than them, I hit > barriers that I couldn't get around. > > Later > Blake. > > > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
