Skip to main content

1.4 feedback

14 replies [Last post]
Anonymous

Hi All,

We are looking for feedback on release 1.4 of LWUIT for internal
promotion within Oracle, we might try to form a more organized survey
for a later date but right now we want to get general abstract impressions.
Have you updated to 1.4, if not when do you plan to do this? What
features of 1.4 do you like? Which features are you using? Where do you
see LWUIT going for the next version? What would you like to see in LWUIT?
Feel free to rant and provide abstract thoughts/context.

Thanks

[att1.html]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jayshil
Offline
Joined: 2010-08-13
Points: 0

Hi Chen,

I finally was able to upgrade from 1.3 to 1.4. The first thing is, it doesnt crashes the previous version, though i had a problem i doubt it was LWUIT related in the first place.

Also, it was very nice to see the long awaited HTMLBrowser component. But as you have said, you guys dont intend to make it a full fledge browser i doubt how useful it can be for apps which are planning to replace the phone's browser to the LWUIT one. And i tested the Qrir's implementation, it seemed very raw to say the least. I suppose the idea behind that was to have XHTML local files to be displayed in the apps which is indeed nice.

Apart from this what i would like to see is first three command screens for s40 series, the users are never gonna be comfortable with the application changing to multiple commands. Add functionality to add command related to components. For eg. in a textfield a clear command, and if we have 3 commands for s40 series than have check, open, commands for components like checkbox, list and all.

Also i would like to see a tree field component being added, if its already there (please ignore, since i have just started off using LWUIT so not sure of all the functionality)

Apart, from that everything else is just superb, keep up the good work, its very refreshing to see such kind of development for J2ME in terms of themes, font and all. Kudos for such a great library.

pnkanchi
Offline
Joined: 2006-06-09
Points: 0

Hi All,

Why do we need to have different jar files, like for Blackberry?
Is it possible to pass some constant value in the Display.init method and respective classes are initialized?

Thanks,
pnkanchi

bjcoredev
Offline
Joined: 2008-06-13
Points: 0

Hi

My application 's code uses intensively TabbedPane class and i've sub-classed TabbedPane class for regrouping all my common code.
All is working like a charm
What was a (bad) surprise to me when i saw that the TabbedPane class is now depreciated in LWUIT 1.4 and replaced by the Tabs class
I see chen's post (http://lwuit.blogspot.com/2010/08/opening-new-tab-in-lwuit.html)

. The Tabs class is final -> no subclass allowed
. you now have to press fire to actually switch a tab -> not very user friendly (for my app)

I ask my self why depreciate (and in the future remove) TabbePane class.
Why TabbedPane and Tabs could'nt be two different classes for different uses.

PS: I have successfully migrated from 1.3 to 1.4 LWUIT release.

vprise
Offline
Joined: 2003-11-07
Points: 0

First you should probably open a separate thread to discuss issues rather than reply to an existing thread...

Tabs is not a part of 1.4 but will replace TabbedPane for the next version of LWUIT. Its superior to tabbed pane in almost every way and answers all of the very long standing open issues in the issue tracker related to tabbed pane (and adds lots of cool new features).

Making it final was a mistake that's rectified, Chen also added the ability to track tab focus change and provide tab switching similar to the old experience. Personally I think the new approach is better since it doesn't force you to go through intermediate tabs when looking for something specific.

If you are still unhappy about this remember that LWUIT is open source and the fact that we remove something from the core only means we no longer support it... You can take the code for the tabbed pane (which is just a standard LWUIT component) and use it pretty much as is with future versions of LWUIT. If you change it you need to publish changes to that class (to comply with the LGPL license) but other than that go crazy...

ngosti2000
Offline
Joined: 2006-09-16
Points: 0

Hi,
Am currently using 1.4 but having issues with the table where i cant scroll once i load data from a database through network.

I like the fact that with 1.4 one does not get the null pointer exception when calling Table.setModel() method which needed lot of theatrics.

One feature i would like to see is use of simple Graphs like pie chart,barchart and series Charts.Most companies want to display data on their phone and one way of doing this in a summarised form is use of Graphs.

Overall LWUIT is just the Bomb

zimba
Offline
Joined: 2010-03-15
Points: 0

Hi,
Thanks for the effort in bringing out the new version. I've upgraded to 1.4 from 1.3; and so far, nothing is broken :) We aren't using the html components, but going forward, they'll be a critical feature.

Overall, LWUIT has been great to use. Would love to see these:

1. a better blackberry integration - the port included in the new version is a great step, jst that some of our screens are breaking on some BB models - maybe prob is in our code; yet to check.

2. would be really helpful if a working android port is also included along with BB port - rather than having to fish it out of the repository and make some tweaks...

3. Some demo / sample code for media components - camera, video and audio player.

4. Location based API support demo

Thanks again for the great platform - it is especially a boon for resource constrained start-ups where creating multiple builds for different platforms is not possible. Hoping to see it staying relevant on newly introduced handsets !

-zimba.

thorsten_s
Offline
Joined: 2008-08-15
Points: 0

I use a recent SVN revision, so I probably have the 1.4 features available. I really love your move for the LWUIT4IO package. Since I have something equivalent of my own I did not yet get to switch, but I probably will at some point. It certainly is helpful for folks who start a new project, targeting more than one platform.

And thanks for your move to extract the MenuBar from the Form class. It was really important to make adaption of the menu more easy, given the variety of platforms out there. Reading the issue tracker I see that there might be more to come. Looking forward to it.

The XHTML component is also very nice for integrated documentation. Makes me want to throw my own XML dialect away that I use currently :)
I read that the XHTML component processes "XHTML Mobile Profile 1.0". If you happen to have any links to tools/editors that help to craft pages in that very XHTML profile you might want to add a link or two to the documentation somewhere.

dmitry_belov
Offline
Joined: 2009-03-16
Points: 0

Without Mutli-Line textfields our app would not be possible.

shankar_vn
Offline
Joined: 2009-11-03
Points: 0

> Without Mutli-Line textfields our app would not be
> possible.

It is available in 1.4. Re check.

dmitry_belov
Offline
Joined: 2009-03-16
Points: 0

What are you talking about? What I wrote implicitly states that they are available and that without them it would not be possible to implement my app. Reading comprehension...

Klemens

Hi,

I'd be really happy if LWUIT could support the 9-patch graphics that
Android uses. I can achieve the same effect with image borders, but it's
a tedious work to always cut out the sub-images using Photoshop.

It's really hard to make a LWUIT app visually appealing and
state-of-the-art without image borders.

BlackBerry support would really need some more attention. It may be good
for simple use cases but you might run into troubles if you are about to
develop a production-ready app for a customer that has exact
requirements and wants a typical BlackBerry look and feel.

Klemens

On 02.09.2010 09:18, Chen Fishbein wrote:
> Hi All,
>
> We are looking for feedback on release 1.4 of LWUIT for internal
> promotion within Oracle, we might try to form a more organized survey
> for a later date but right now we want to get general abstract impressions.
> Have you updated to 1.4, if not when do you plan to do this? What
> features of 1.4 do you like? Which features are you using? Where do you
> see LWUIT going for the next version? What would you like to see in LWUIT?
> Feel free to rant and provide abstract thoughts/context.
>
> Thanks
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net

Mixa

Hi Chen,

I haven't updated to 1.4 yet, but probably will do it within 1-2
months. Since I haven't seen anything important for me in new features
list (I already used HTML browser from SVN head, as for LWUIT4IO - it
needs time to take this concept), so I'll probably migrate to 1.4 just
to be on top of LWUIT development, if migration to from 1.3 to 1.4
will be smart enough (from 1.2 to 1.3 some phones went out of LWUIT
compatibility list)

As for new features, I would vote for some kind of screen definition
language, in XML or other format - I would prefer BIT Scheme
http://www.iro.umontreal.ca/~dube/, a light-wight Scheme
implementation for microcontrollers, it should be within 30k of java
byte code (I have a java port of BIT Scheme, but haven't used it in
any project - I would be happy to contribute it). So it could be used
as a script engine for applications, for LWUIT screen definition
subsystem as well.

As for HTML browser, it would be good to use "thin client" approach,
similar to Opera Mini - with HTML pages parsed on server side,
transformed to simplified format for better rendering on client
(Webkit could be used on server side, it is used for that in Bolt
browser). For pages representation I would use Scheme byte code (BIT
Scheme works so), and also it probably could allow JavaScript
transformation (it is not supported in Opera Mini). Well, even without
HTML to Scheme transformation, it would be cool anyway to load pages /
applications (as Scheme byte code) into an LWUIT app at runtime.
Something like that was made in Widsets Nokia platform (now
abandoned).

FYI Scheme is used in Google AppInventor project
(http://appinventor.googlelabs.com/about/), with Kawa - Scheme
implementation in JVM.

Regards,
Mike

On Thu, Sep 2, 2010 at 11:18 AM, Chen Fishbein wrote:
> Hi All,
>
> We are looking for feedback on release 1.4 of LWUIT for internal promotion
> within Oracle, we might try to form a more organized survey for a later date
> but right now we want to get general abstract impressions.
> Have you updated to 1.4, if not when do you plan to do this? What features
> of 1.4 do you like? Which features are you using? Where do you see LWUIT
> going for the next version? What would you like to see in LWUIT?
> Feel free to rant and provide abstract thoughts/context.
>
> Thanks
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net

Mixa

And I forgot to say that it would be good to make a proper Ant script
to build LWUIT from command line, outside Netbeans (that one,
auto-generated by Netbeans, doesn't work without Netbeans installed
AFAIK). Or for Maven. Unit tests would be good too, but I'm not used
to write them myself ))

Mike

On Thu, Sep 2, 2010 at 1:31 PM, Mixa wrote:
> Hi Chen,
>
> I haven't updated to 1.4 yet, but probably will do it within 1-2
> months. Since I haven't seen anything important for me in new features
> list (I already used HTML browser from SVN head, as for LWUIT4IO - it
> needs time to take this concept), so I'll probably migrate to 1.4 just
> to be on top of LWUIT development, if migration to from 1.3 to 1.4
> will be smart enough (from 1.2 to 1.3 some phones went out of LWUIT
> compatibility list)
>
> As for new features, I would vote for some kind of screen definition
> language, in XML or other format - I would prefer BIT Scheme
> http://www.iro.umontreal.ca/~dube/, a light-wight Scheme
> implementation for microcontrollers, it should be within 30k of java
> byte code (I have a java port of BIT Scheme, but haven't used it in
> any project - I would be happy to contribute it). So it could be used
> as a script engine for applications, for LWUIT screen definition
> subsystem as well.
>
> As for HTML browser, it would be good to use "thin client" approach,
> similar to Opera Mini - with HTML pages parsed on server side,
> transformed to simplified format for better rendering on client
> (Webkit could be used on server side, it is used for that in Bolt
> browser). For pages representation I would use Scheme byte code (BIT
> Scheme works so), and also it probably could allow JavaScript
> transformation (it is not supported in Opera Mini). Well, even without
> HTML to Scheme transformation, it would be cool anyway to load pages /
> applications (as Scheme byte code) into an LWUIT app at runtime.
> Something like that was made in Widsets Nokia platform (now
> abandoned).
>
> FYI Scheme is used in Google AppInventor project
> (http://appinventor.googlelabs.com/about/), with Kawa - Scheme
> implementation in JVM.
>
> Regards,
> Mike
>
> On Thu, Sep 2, 2010 at 11:18 AM, Chen Fishbein wrote:
>> Hi All,
>>
>> We are looking for feedback on release 1.4 of LWUIT for internal promotion
>> within Oracle, we might try to form a more organized survey for a later date
>> but right now we want to get general abstract impressions.
>> Have you updated to 1.4, if not when do you plan to do this? What features
>> of 1.4 do you like? Which features are you using? Where do you see LWUIT
>> going for the next version? What would you like to see in LWUIT?
>> Feel free to rant and provide abstract thoughts/context.
>>
>> Thanks
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net

ghady_rayess
Offline
Joined: 2009-01-09
Points: 0

1- To have support for Bitmap Arabic font ([b]important[/b])

2- Enhance the touch scroll effect. At the moment, there is a bit of lag between the finger touch scroll and the actual scroll of the list. Also, sometimes the application misses scroll gestures if done fast, while native applications handle them correctly.