One more thought: I tried to make our framework reasonably pluggable. If
you just use the form dispatching mechanisms, the overhead isn't great.
There is overhead, but it's not prohibitive.
If you drag in the templated collection classes (I have an associative
array and a vector), you're going to get some code bloat, just by the
nature of templating. If you use the String class (optional), you're going
to get more framework overhead. If you use the database reference-counted
record classes, you're going to get more overhead. If you include
stream-based TCP/IP classes, .... etc.
Our last two Palm projects were both written using our framework. The first
involved TCP/IP communication between a wireless Symbol SPT 1740 and a Java
port listener which talked to a SQL database. The second is closer to a
standard Palm app, but involves database interactions, etc.
The first was running on devices that were dedicated to our application,
and we didn't worry too much about code bloat; it was quite a large Palm
app, but considering what it did, it wasn't absurdly large (145k or so, I
think). This is large by Palm standards, but for the use, it was quite
acceptable.
I think everything we included can be of some use; the question is how much
overhead you're prepared to eat, at what point segmenting starts becoming
an issue, etc. The flexibility is there; for those who can afford the extra
overhead, they'll get quicker development time and a safer coding
environment. For those who can't, they may not want to use every library
we've provided.
Regards,
Ben Flaumenhaft
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
