I'll check Teenee, for what I see it looks very good... thanks a lot for the people
who gave the link!
Jose Manuel Guerra Chapa wrote:
> This sound great, thanks a lot for your comments, but don't you think that this
>framework the developers have to make, is like reinventing a different wheel for each
>developer? and by the time someone shares some code snippets, no one understands
>because he is using his own framework... it'll be harder for someone else to maintain
>your code because he is not familiar with your framework...
>
> so does no one would like this PFCs developed by Palm? am I the only one?
> I personaly don't like it much using libs if they are not from the source... but
>that's just my opinion...
>
> [EMAIL PROTECTED] wrote:
>
> > I just recently finished a project written in C++ for the palm. It wasn't that
>difficult, but here are a few of the observations I have:
> >
> > 1)You can't create mulitple definitions for a function. If I want to methods to
>call a function, each with a different set of args, Codewarrior won't compile. It
>complains that the function has been redefined.
> >
> > 2)Destructors don't seem to work at all.
> >
> > As for the request response loop. It was actually pretty simple to get around
>once I created the basic Form class. I was able to pipe all of the general requests
>to the base class and handle anything else I wanted to in the sub-class. This is
>essentially what Microsoft has done with MFC. I had to tweak the main request
>response loop so it wouldn't care which class was currently being displayed, but once
>that worked, everything else fell into place.
> >
> > I think the only thing palm is missing for the OO'ness is the PFC. That's
>something palm developers themselves could start writing themselves. Eventually, you
>have a nice set of classes that run and create all the stuff you need to build an app
>quickly.
> >
> > Brian McClung
> > Sigma Automation
> > [EMAIL PROTECTED]
