I hope this isn't considered too far off topic... In a Java SE context, Most people try to separate out data objects and listener objects often with anonymous classes and Mediator pattern. All the Java ME software I have seen to date seems to put all the listener activity in the same class, and object, as the application.
I am guessing this is to minimize the number of classes and objects? Is this considered good Java ME style? Another thing I have noticed is two definite trends with respect to startApp and pauseApp. Some people try to maximize the amount of work done in the constructor of an application class and minimize the work done in the start and pause methods. Others seem to put as little as possible in the constructor and everything in the start and pause methods seemingly causing a lot more resource activity to start and stop an application. It is probably that I haven't read enough books on Java ME (they are in the mail), so far I have done all my Java ME stuff from the manuals, so I probably haven't picked up the idioms. Is one of these two approaches `The Right Way' ? (For resources that remain from creation to destruction, of course.) Thanks. -- Russel. ==================================================== Dr Russel Winder +44 20 7585 2200 41 Buckmaster Road +44 7770 465 077 London SW11 1EN, UK [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
