Skip to main content

Expose platform methods?

6 replies [Last post]
asumma66061
Offline
Joined: 2007-04-12

LWUIT seems to have made great strides forward in being able to detect what device it is running on (e.g. being able to 'know" what keycodes to look for).

Any thoughts on exposing methods so we can leverage that knowledge in our apps?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
asumma66061
Offline
Joined: 2007-04-12

I read over http://lwuit.blogspot.com/2008/07/lwuit-porting-and-device-issues.html and it has many good points. But I still think that the more information developers can be armed with about the device or operator we are dealing with the more flexibility we will have in dealing with the JME environment.

asumma66061
Offline
Joined: 2007-04-12

Sorry if I wasn't clear. I'm less interested in knowing what keycodes map to what (as long as they just work) - and more interested in less preprocessing for manufacturer specific code (bug work arounds, requirements, etc).

I understand the process for determining the softkey values and understand why you don't want to expose it. However the information is very valuable and not widely available. Maybe what I am looking for is more for the LWUIT extension project (non-ui focused)?

Thanks for the great work.

Qunhuan Mei

Hi LWUIT team,

Current design/implementation of transition always involves the whole page when transits from form A to B or vice versa.

For our application, a page always has a logo (image) on top and a menu bar at the bottom. When transition happens, the logo and menu bar moves too no matter they change or not.

Is it possible to refine the design/implementation of transition to make only the content part moves, while keeping the top (e.g. a logo) and bottom (e.g. menu bar)? (Our designer said if a transition always moves the whole page, including the unchanged part, he would “bin” the use of transition, since he could not bear the view that the same top logo and bottom menu bar has to be replaced every time – “it is just not acceptable”!). If we look at iPhone’s implementation, the transition only happens to those changed part. For the unchanged part, either top or bottom or both, they stay unmoved.

What do you think?

Thanks,

Qunhuan

Shai Almog

Hi Qunhuan,
please see Container.replace(...). Not all transitions work with this
but slide/fade should work as expected.

Thanks.

> Hi LWUIT team,
>
> Current design/implementation of transition always involves the
> whole page when transits from form A to B or vice versa.
>
> For our application, a page always has a logo (image) on top and a
> menu bar at the bottom. When transition happens, the logo and menu
> bar moves too no matter they change or not.
>
> Is it possible to refine the design/implementation of transition to
> make only the content part moves, while keeping the top (e.g. a
> logo) and bottom (e.g. menu bar)? (Our designer said if a
> transition always moves the whole page, including the unchanged
> part, he would “bin” the use of transition, since he could not bear
> the view that the same top logo and bottom menu bar has to be
> replaced every time – “it is just not acceptable”!). If we look at
> iPhone’s implementation, the transition only happens to those
> changed part. For the unchanged part, either top or bottom or both,
> they stay unmoved.
>
> What do you think?
>
> Thanks,
>
> Qunhuan

Shai Almog
http://lwuit.blogspot.com/

[att1.html]

Qunhuan Mei

Thanks Shai,

It looks this may achieve what we want to achieve and will let you know if there are problems.

Cheers,

Qunhuan

From: Shai.Almog@Sun.COM [mailto:Shai.Almog@Sun.COM]
Sent: 23 July 2008 14:12
To: users@lwuit.dev.java.net
Subject: Re: Partial page transition, instead of whole page.

Hi Qunhuan,
please see Container.replace(...). Not all transitions work with this but slide/fade should work as expected.

Thanks.

Hi LWUIT team,

Current design/implementation of transition always involves the whole page when transits from form A to B or vice versa.

For our application, a page always has a logo (image) on top and a menu bar at the bottom. When transition happens, the logo and menu bar moves too no matter they change or not.

Is it possible to refine the design/implementation of transition to make only the content part moves, while keeping the top (e.g. a logo) and bottom (e.g. menu bar)? (Our designer said if a transition always moves the whole page, including the unchanged part, he would "bin" the use of transition, since he could not bear the view that the same top logo and bottom menu bar has to be replaced every time - "it is just not acceptable"!). If we look at iPhone's implementation, the transition only happens to those changed part. For the unchanged part, either top or bottom or both, they stay unmoved.

What do you think?

Thanks,

Qunhuan

Shai Almog
http://lwuit.blogspot.com/

[att1.html]

Shai Almog

Hi,
We expose the ability to set the keyCodes for soft buttons/back and
clear but we don't expose the detection code or the end result we
keep for reasons of encapsulation.

I don't think we will ever expose them officially but if you want to
access this information just create a class in the com.sun.lwuit
package and access the static variables of Form:
Form.leftSK, Form.rightSK, Form.backSK, Form.clearSK

Theoretically these might change for a future release but there are
no plans for that at this time.

Thanks.
Shai.

> LWUIT seems to have made great strides forward in being able to
> detect what device it is running on (e.g. being able to 'know" what
> keycodes to look for).
>
> Any thoughts on exposing methods so we can leverage that knowledge
> in our apps?
> [Message sent by forum member 'asumma66061' (asumma66061)]
>
> http://forums.java.net/jive/thread.jspa?messageID=287762
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
> For additional commands, e-mail: users-help@lwuit.dev.java.net
>

Shai Almog
http://lwuit.blogspot.com/

[att1.html]