hartti | 14 June, 2007 18:33
The MIDP3 expert group has been been thinking about removing (deprecating) the PauseApp method call from the MIDlet life-cycle methods. Sean Sheedy (from the MIDP3 expert group) has written a lengthy article about pauseApp and how the EG wants to remove fragmentation by requiring that the implementations never call it (Note: this is the current behavior on Nokia devices).
C. Enrique Ortiz has written a response for this, stating that he is against of deprecating pauseApp and he justifying his stand well. There is also quite active discussion around this on KVM interest mailing list. If you have an option on this please email to the expert group or leave your comments in Sean Sheedy's post.
Personally I think pauseApp is not required (I am likely biased because of getting used to the Nokia implementations :-), but there should be also more granular methods to let the MIDlet know what kind of interruptions are coming from the system (not just always calling hideNotify without no indication if it is a phone call, user, another application etc. which is taking the foreground).
Java |
Next |
Previous |
Comments (3) |
Trackbacks (0)
njzk2 | 15/06/2007, 11:19
hartti | 15/06/2007, 17:50
Simon, you have a valid point. Hopefully the EG makes sure the specification defines this behavior (whatever it will be) in enough detail so that the implementations do not have room to fragment (in this regard)
Re: PauseApp and MIDP3 - the expert group is looking for your input
eortiz | 15/06/2007, 01:49
I've added to my entry, a survey to capture the opinions of the dev community to take to the MIDP3 EG:
http://www.cenriqueortiz.com/weblog/JavaME%2C+J2ME/2007/06/14/MIDP3-Proposal-to-remove-the-MIDlet-pauseApp-lifecycle-method.html
ceo