Re: extended support for DOCDECL

> Regarding J2ME - well, it is true, that J2ME should keep the code
> as small as possible, but unfortunately people do confuse J2ME and MIDP.
> 
> The MIDP platfrorm is extremely small, where every bit counts, and the
> API set is very restricted. But J2ME also covers the PDAs, where
> foundation profile (FP), personal basis profile (PBP) and personal profile (PP)
> take place. Those API sets are much more wide, and capabilities of target
> platforms are much more generous rather than what MIDP targets.
> 
> Those developers who want to deploy to that PP enabled platforms,
> would very much like to use more enabled APIs. IMHO, overrestricting
> APIs to keep them small enough for MIDP may and will make those APIs
> obsolete with time, when MIDP is finally replaced with PP (when a phone
> reaches the today's PDAs capabilities), or just because developers
> who write for PDAs will not use them.

Hi Pawel,

are you sure MIDP will become obsolete earlier DTDs? :-)

At the time PP replaces MIDP on phones, J2SE will probably have
replaced PP on PDAs. So following your argumentation, we would
not need to care about J2ME at all :-)

While I agree that J2ME is something more general than MIDP, MIDP
is definitely a part of J2ME. Targenting at CLDC/MIDP helps to avoid
bloated APIs, and to make sure J2ME is covered completely.

Best,
Stefan


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/2U_rlB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/