Hi Jason,
Thanks for all the info. Knowing that you have already tried the custom
classloader route saves me beating my head against that.
I'm sure that the reason they have limited GUI components was to handle
size restrictions on the 503s, but to prevent extendibility? Well seems
to me the only reason can be that they want to make it difficult for
different GUIs to be presented, i.e. they want a TextBox to always have
the same functionality that they have decided so as not to confuse the
users.
CHEERS> SAM
Jason Pollard wrote:
>
>
>>Well it won't work on any phones at the moment as far as I can see cos I
>>can't have a com.nttdocomo.ui.Gauge class cos I'm forbidden to create
>>something in that package.
>>
>>
>>
>I think I went thru this same thing about a year and a half ago. After giving
>up on making my own components, I got help from this list in trying to
>implement a custom classloader, which I was going to use to download new UI
>classes over the network. That can't be done either, in case you were
>wondering. :-(
>
>I think they must have done this to reduce the complexity of the
>API/Implementations, as well as reduce the size of iAppli code. Even just to
>paint a basic button, you need 4 lines, background color fill, and text, which
>you could do only if you could paint on the Display. Yeah, sometimes it seems
>they went out of their way to make things difficult for developers. My guess
>is that J2ME isn't long for this world, and that we'll have a standard J2SE JVM
>on most devices within 3 years that would maybe have a limited UI toolkit.
>
>
Received on Thu Sep 18 05:29:24 2003