|Dear JSR360 experts,|
We have checked back with people using CLDC8 and received feedback that EventListener and EventObject
are used by several APIs. ME-EP is using them as well as some other internal projects.
Since they only introduce very low additional footprint and help to align future with JavaSE we think
it is better to retain them in the spec.
On 30.05.2013, at 14:43, Werner Keil wrote:
The actual UI sure is, after all there should be devices with a far restricted or no UI supported by MEEP.
If you mean the EventObject or EventListener, that's a trickier part, first it is not AWT as such, but java.util, and the concept of non-visual or server-side events are all over the place, also find them e.g. in a slightly different form with CDI (unfortunately that may be a bit too heavy, otherwise such events could be great for ME, too<347.gif>) so "distributed" events between devices or inside a single device have nothing to do with AWT, JavaFX or any other UI.
However, the question I raised yesterday, that the stakeholders for those event items should be identified and asked could help find out, if these two are needed in CLDC.
Werner Keil | JCP Executive Committee Member | Eclipse UOMo Lead, Babel Language Champion | Java Godfather
Twitter @wernerkeil | @JSR354 | #EclipseUOMo | #Java_Social | #OpenDDR
* Eclipse DemoCamps Kepler 2013: June 19-28 2013, Germany, Denmark, Austria. Werner Keil, UOMo Lead, Mærsk DevOps Build Manager will present "Triple-E’class DevOps with Hudson, Maven, Kokki, Multiconf & PyDev", "M4M 2 the Rescue of M2M"
On Thu, May 30, 2013 at 12:31 AM, Thiago Galbiatti Vespa <
User Interface is beyond of the scope of this JSR. Don't you agree?