Craig Thrall wrote:
> > * It overall bloats the code.
>
> How so? For example, wrapping some of the Palm string functionality will
> greatly reduce the LOC you have to write (see the Palm Foundation Classes
> project at SourceForge for a poor example - it's mine, so I say such things
> :) - of such a class). The reuse OO frameworks support will greatly pay off
> in the long run.
I think this person was talking from a pessimistic point of view whereby the
foundation was poorly designed. If it isn't properly
delineated you may find yourself using only a fraction of each class that you include,
which means your code will be bloated.
This is common in Windows programming, since you can easily include libraries for only
a subset of what they offer, and there are
few ill effects since the target computers, generally, have enough horsepower to run
the app anyways. On something as light as a
palm the code needs to be tight to do a proper job.
That being said, I'm certainly not against a framework, and personally feel that a
well-designed one could easily speed up the
development time (or in the very least help with the coherency of the code). I can,
however, see how a poorly designed framework
(or the poor use of one) can contribute to code bloat.
Sam
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
