Quote:Original post by Thygrrr
b) as I suspected, resource strings have the potential to account for several KB of memory (although ascii usually packs quite well). I'll try to use loops and generated resource names and well-structured programming to avoid as much overhead here, while also improving code legibility.
Data-driven design will be your saviour. ::thumbs up::
Quote:
c) I don't think I'll exceed the 5 class limit for a while, mostly, it'll be the MIDlet, the Canvas, and up to one or two game objects.
Consider trying to make one of those 'game object' classes the really big one instead of the MIDlet or Canvas. Those two are the first that you need to get anything up on the screen at all, so you want them to load quickly (i.e. be small).
Quote:
d) try to get around having to build my projects using JBuilder (which is a clunky process, at best), and work with shell scripts and makefiles to actually package the application. This is particularly useful for the slide show project I've been assigned to, because with tools like Imagemagick, you can pretty much automate the process of resizing/cropping all the images, putting them into various .jars depending on the target platform (e.g. Nokia Series 60, Siemens C 55).
Don't deny yourself access to more powerful scripting languages, either. There are some things better done in .bat (.sh, etc.) and others better done in .py (or .pl). [smile]
