I'd suggest that instead of hacking a resource whose format and existance
are subject to change, you could simply put a resource of your own into
your app. Perhaps more work in the short term, but perfect reliability and
control in the medium and long term. Your single resource's size might be
smaller than that of the code to parse N different varieties of the rom
resource.
In some ways this is like folks who are trying to do incredibly complex
hacks to get the built-in UI objects to do something they weren't made for,
instead of writing their own. There's a point where it is much better to
roll your own, and just accept the up-front investment.
What if your app sells 100 or 1000 times more than you think it will, and
you've got that number of customers demanding you fix your app because an
assumption broke? :-( Worth another hour of work today to avoid that,
probably.
I'm not trying to lecture, if that's the tone that comes across - I'm
suggesting this in all seriousness.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
