Russel Winder wrote: >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? > > To me, its as simple as: Bytecode is the often most precious commodity in J2ME programming. Lots of things are in short supply - RAM, CPU cycles, Audio channels, Network IO, Screen update speed, RecordStore space, Permission to do stuff - but in practice, the hardest limit for me is Midlet size; the amount of bytecode in the app.
To respond to this, "good" J2ME design throws out alot modern J2ME and enterprise -space styles, which emphasize lots of small fine grained classes. Thats simply not going to work well on current platforms. In some ways, you have to set the clock back 10-20 years, and rediscover methods that were once considered best practice on PCs. -Ben -- Ben Hutchison Lead Developer Playscape Games http://www.playscapegames.com ------------------------------------------------------------------------- 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
