|
Replies:
19
-
Last Post:
Apr 27, 2009 2:19 AM
by: technolgia
|
|
|
|
|
|
|
Touchscreen Support
Posted:
Feb 18, 2009 2:34 PM
|
|
|
Hi there,
I thought LWUIT supports touchscreen devices by default. One of our customers complains that he doesn't get the focus of TextField to enter his password on a HTC Diamond. Normally, touching the TextField should work.
Can someone shed some light on that?
Thanks in advance.
Stephan
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 18, 2009 7:31 PM
in response to: bardubitzki
|
|
|
My problem of touch screen is about List Scrolling Bar.
It doesn't work as my imagine.
I touch the bar and pull down, it doesn't work.
But I touch the blank of the bar and pull up, the scrolling bar go down.
It is weird.
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 18, 2009 10:47 PM
in response to: fisher55
|
|
|
Sorry stephan, no idea about the HTC touch issue.
to fisher: To scroll a list you actually touch the component itself and drag its contents into the direction of choice. This means that the user does not have to try to aim for those small scrollbars. If you still try to 'move the scrollbar' then it might look weird because it looks like the directions are reversed. Note that the scrollbar is actually not a component itself.
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 19, 2009 3:25 AM
in response to: thorsten_s
|
|
|
Thx for your answer
But actually it always goto another page if user touch the component of the List.
I think user habits is to click scroll bar directly instead of click the List itself
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 19, 2009 5:42 AM
in response to: fisher55
|
|
|
|
|
In the current version only touching the selected element will
produce an action event. LWUIT is targeted at finger based touch UI's.
> Thx for your answer
>
> But actually it always goto another page if user touch the
> component of the List.
> I think user habits is to click scroll bar directly instead of
> click the List itself
> [Message sent by forum member 'fisher55' (fisher55)]
>
> http://forums.java.net/jive/thread.jspa?messageID=332869
>
> ---------------------------------------------------------------------
> 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/
https://lwuit.dev.java.net/faq.html
[att1.html]
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 19, 2009 12:05 AM
in response to: bardubitzki
|
|
|
|
|
Hi,
midp doesn't have the functionality to popup a virtual keyboard.
There is no such API call which we can invoke to provide that behavior.
If the user clicks the T9 softbutton he will get the native textbox
which should work as expected, alternatively you can use the text
area which will have the same behavior.
> Hi there,
>
> I thought LWUIT supports touchscreen devices by default. One of our
> customers complains that he doesn't get the focus of TextField to
> enter his password on a HTC Diamond. Normally, touching the
> TextField should work.
>
> Can someone shed some light on that?
>
> Thanks in advance.
>
> Stephan
> [Message sent by forum member 'bardubitzki' (bardubitzki)]
>
> http://forums.java.net/jive/thread.jspa?messageID=332764
>
> ---------------------------------------------------------------------
> 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/
https://lwuit.dev.java.net/faq.html
[att1.html]
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 19, 2009 8:46 AM
in response to: Shai Almog
|
|
|
Hi Shai,
the problem is that the customer doesn't come to the input mode and
therefore doesn't see the T9 soft button.
You guys had LWUIT demo running on a HTC Touch, how is the TextField
behavior on this device?
In the first place our customer couldn't start our LWUIT based
application at all, but other HTC user could. It came down to the fact
that the Esmertec JVM was the problem. Now, with the newest Version
(Esmertec Jbed Build ID: 20081016.3.1) our app starts fine, but he has
that TextField input problem.
We tend to blame the JVM for the ongoing problems and advised the
customer to download phoneMe Advanced(dual stack) from here:
http://www.cs.kuleuven.be/~davy/phoneme/index.php?q=node/10
but it seems that there is lack of understanding how to set this as the
JVM to use. Do you or Terrence have any information on that? (We don't
have any access to Windows Mobile devices)
Thanks.
Stephan
Shai Almog wrote:
> Hi,
> midp doesn't have the functionality to popup a virtual keyboard. There
> is no such API call which we can invoke to provide that behavior.
> If the user clicks the T9 softbutton he will get the native textbox
> which should work as expected, alternatively you can use the text area
> which will have the same behavior.
>
>> Hi there,
>>
>> I thought LWUIT supports touchscreen devices by default. One of our
>> customers complains that he doesn't get the focus of TextField to
>> enter his password on a HTC Diamond. Normally, touching the TextField
>> should work.
>>
>> Can someone shed some light on that?
>>
>> Thanks in advance.
>>
>> Stephan
>> [Message sent by forum member 'bardubitzki' (bardubitzki)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=332764
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>> <mailto:users-unsubscribe@lwuit.dev.java.net>
>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>> <mailto:users-help@lwuit.dev.java.net>
>>
>
> Shai Almog
> http://lwuit.blogspot.com/
> https://lwuit.dev.java.net/faq.html
>
> --------------------------------
>
>
> Spam/Virus scanning by CanIt Pro
>
> For more information see http://www.kgbinternet.com/SpamFilter.htm
>
> To control your spam filter, log in at http://filter.kgbinternet.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 19, 2009 9:42 AM
in response to: Stephan Bardubi...
|
|
|
|
|
Hi,
touching the text field should start the input mode to replace the
softkeys. This works on most devices, however some HTC native VM's
have a problem with showing the softbutton area so that might be the
thing tripping this off.
Maybe Terrence can help you with the PhoneME questions, our WinMo
devices came preinstalled so I wouldn't know. It might be best to ask
for PhoneME questions in the PhoneME forum where you can probably
find the real experts on this subject.
There is another alternative that I can't discuss much due to NDA,
but I don't think they will mind if I say that LWUIT seems to work
with this alternative. Their site explains the general idea: http://
innaworks.com/
> Hi Shai,
>
> the problem is that the customer doesn't come to the input mode and
> therefore doesn't see the T9 soft button.
>
> You guys had LWUIT demo running on a HTC Touch, how is the
> TextField behavior on this device?
>
> In the first place our customer couldn't start our LWUIT based
> application at all, but other HTC user could. It came down to the
> fact that the Esmertec JVM was the problem. Now, with the newest
> Version (Esmertec Jbed Build ID: 20081016.3.1) our app starts fine,
> but he has that TextField input problem.
>
> We tend to blame the JVM for the ongoing problems and advised the
> customer to download phoneMe Advanced(dual stack) from here:
>
> http://www.cs.kuleuven.be/~davy/phoneme/index.php?q=node/10
>
> but it seems that there is lack of understanding how to set this as
> the JVM to use. Do you or Terrence have any information on that?
> (We don't have any access to Windows Mobile devices)
>
> Thanks.
> Stephan
>
>
> Shai Almog wrote:
>> Hi,
>> midp doesn't have the functionality to popup a virtual keyboard.
>> There is no such API call which we can invoke to provide that
>> behavior. If the user clicks the T9 softbutton he will get the
>> native textbox which should work as expected, alternatively you
>> can use the text area which will have the same behavior.
>>
>>> Hi there,
>>>
>>> I thought LWUIT supports touchscreen devices by default. One of
>>> our customers complains that he doesn't get the focus of
>>> TextField to enter his password on a HTC Diamond. Normally,
>>> touching the TextField should work.
>>>
>>> Can someone shed some light on that?
>>>
>>> Thanks in advance.
>>>
>>> Stephan
>>> [Message sent by forum member 'bardubitzki' (bardubitzki)]
>>>
>>> http://forums.java.net/jive/thread.jspa?messageID=332764
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>>> <mailto:users-unsubscribe@lwuit.dev.java.net>
>>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>>> <mailto:users-help@lwuit.dev.java.net>
>>>
>>
>> Shai Almog
>> http://lwuit.blogspot.com/
>> https://lwuit.dev.java.net/faq.html
>>
>> --------------------------------
>>
>>
>> Spam/Virus scanning by CanIt Pro
>>
>> For more information see http://www.kgbinternet.com/SpamFilter.htm
>>
>> To control your spam filter, log in at http://filter.kgbinternet.com
>>
>
>
> ---------------------------------------------------------------------
> 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/
https://lwuit.dev.java.net/faq.html
[att1.html]
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 24, 2009 6:56 AM
in response to: Shai Almog
|
|
|
|
|
Sorry for the delayed reply.
I just tried this on an HTC Touch with an older version (9 months) of
phoneME Advanced for Windows Mobile installed and the latest LWUIT demo.
In the LWUIT demo If I touch an input field I get an input dialog box
which allows me to enter text. But it doesn't look like the native
the input method and I cannot bring up the on-screen keyboard - I think
this is a limitation of the phoneME Advanced version I've installed.
For more information I suggest to post your question to the phoneME
Advanced forum http://forums.java.net/jive/forum.jspa?forumID=100 as
Shai suggested.
Best,
-- Terrence
Shai Almog wrote:
> Hi,
> touching the text field should start the input mode to replace the
> softkeys. This works on most devices, however some HTC native VM's have
> a problem with showing the softbutton area so that might be the thing
> tripping this off.
>
> Maybe Terrence can help you with the PhoneME questions, our WinMo
> devices came preinstalled so I wouldn't know. It might be best to ask
> for PhoneME questions in the PhoneME forum where you can probably find
> the real experts on this subject.
>
> There is another alternative that I can't discuss much due to NDA, but I
> don't think they will mind if I say that LWUIT seems to work with this
> alternative. Their site explains the general idea: http://innaworks.com/
>
>> Hi Shai,
>>
>> the problem is that the customer doesn't come to the input mode and
>> therefore doesn't see the T9 soft button.
>>
>> You guys had LWUIT demo running on a HTC Touch, how is the TextField
>> behavior on this device?
>>
>> In the first place our customer couldn't start our LWUIT based
>> application at all, but other HTC user could. It came down to the fact
>> that the Esmertec JVM was the problem. Now, with the newest Version
>> (Esmertec Jbed Build ID: 20081016.3.1) our app starts fine, but he has
>> that TextField input problem.
>>
>> We tend to blame the JVM for the ongoing problems and advised the
>> customer to download phoneMe Advanced(dual stack) from here:
>>
>> http://www.cs.kuleuven.be/~davy/phoneme/index.php?q=node/10
>>
>> but it seems that there is lack of understanding how to set this as
>> the JVM to use. Do you or Terrence have any information on that? (We
>> don't have any access to Windows Mobile devices)
>>
>> Thanks.
>> Stephan
>>
>>
>> Shai Almog wrote:
>>> Hi,
>>> midp doesn't have the functionality to popup a virtual keyboard.
>>> There is no such API call which we can invoke to provide that
>>> behavior. If the user clicks the T9 softbutton he will get the native
>>> textbox which should work as expected, alternatively you can use the
>>> text area which will have the same behavior.
>>>
>>>> Hi there,
>>>>
>>>> I thought LWUIT supports touchscreen devices by default. One of our
>>>> customers complains that he doesn't get the focus of TextField to
>>>> enter his password on a HTC Diamond. Normally, touching the
>>>> TextField should work.
>>>>
>>>> Can someone shed some light on that?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Stephan
>>>> [Message sent by forum member 'bardubitzki' (bardubitzki)]
>>>>
>>>> http://forums.java.net/jive/thread.jspa?messageID=332764
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>>>> <mailto:users-unsubscribe@lwuit.dev.java.net>
>>>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>>>> <mailto:users-help@lwuit.dev.java.net>
>>>>
>>>
>>> Shai Almog
>>> http://lwuit.blogspot.com/
>>> https://lwuit.dev.java.net/faq.html
>>>
>>> --------------------------------
>>>
>>>
>>> Spam/Virus scanning by CanIt Pro
>>>
>>> For more information see http://www.kgbinternet.com/SpamFilter.htm
>>>
>>> To control your spam filter, log in at http://filter.kgbinternet.com
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>> <mailto:users-unsubscribe@lwuit.dev.java.net>
>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>> <mailto:users-help@lwuit.dev.java.net>
>>
>
> Shai Almog
> http://lwuit.blogspot.com/
> https://lwuit.dev.java.net/faq.html
>
--
Terrence Barr
Senior Technologist and Community Ambassador
Java Mobile & Embedded Community
Phone: +49 711 720 98185
Yahoo: terrencebarr, AIM: terrencebarr123
http://www.mobileandembedded.org
http://www.sun.com
Registered Office:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
NOTICE: This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy all copies of the original
message.
[terrence_barr.vcf]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 25, 2009 7:57 PM
in response to: Terrence Barr -...
|
|
|
Not only HTC, but also other touch screen cell-phone
Such as MotoA1200.
I tested TextArea in MotoA1200, it can't pop up the native cellphone input menu.
But this kind of phone don't have keyboard.
So I don't know how do deal with that...
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 25, 2009 8:14 PM
in response to: fisher55
|
|
|
I have the bad feeling that this can be a show stopper for LWUIT on
touchscreen devices.
At least it seems not to be a problem on S60 based touchscreen devices.
lwuit-users@mobileandembedded.org wrote:
> Not only HTC, but also other touch screen cell-phone
> Such as MotoA1200.
>
> I tested TextArea in MotoA1200, it can't pop up the native cellphone input menu.
> But this kind of phone don't have keyboard.
> So I don't know how do deal with that...
> [Message sent by forum member 'fisher55' (fisher55)]
>
> http://forums.java.net/jive/thread.jspa?messageID=333916
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
> For additional commands, e-mail: users-help@lwuit.dev.java.net
>
>
> --------------------------------
> Spam/Virus scanning by CanIt Pro
>
> For more information see
> http://www.kgbinternet.com/SpamFilter.htm
>
> To control your spam filter, log in at
> http://filter.kgbinternet.com
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 25, 2009 8:53 PM
in response to: Stephan Bardubi...
|
|
|
|
|
For what it's worth, when I touch an LWUIT textarea on my moto e680i
(touchscreen device without a keypad; circa 2005) it /does/ bring up the
native input component appropriately. At that point, the user can choose
from various keyboards or handwriting recognition input methods.
So, this sounds like a KVM issue to me and probably more of a showstopper
for the device in question than for LWUIT specifically. I think (for
obvious reasons) many manufacturers are rushing sub-par touch devices to
market, buyer beware!
On Wed, Feb 25, 2009 at 11:14 PM, Stephan Bardubitzki <
stephan@bardubitzki.com> wrote:
> I have the bad feeling that this can be a show stopper for LWUIT on
> touchscreen devices.
>
> At least it seems not to be a problem on S60 based touchscreen devices.
>
>
>
> lwuit-users@mobileandembedded.org wrote:
>
>> Not only HTC, but also other touch screen cell-phone
>> Such as MotoA1200.
>>
>> I tested TextArea in MotoA1200, it can't pop up the native cellphone input
>> menu.
>> But this kind of phone don't have keyboard.
>> So I don't know how do deal with that...
>> [Message sent by forum member 'fisher55' (fisher55)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=333916
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>>
>>
>> --------------------------------
>> Spam/Virus scanning by CanIt Pro
>>
>> For more information see
>> http://www.kgbinternet.com/SpamFilter.htm
>>
>> To control your spam filter, log in at
>> http://filter.kgbinternet.com
>>
>>
>>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
> For additional commands, e-mail: users-help@lwuit.dev.java.net
>
>
[att1.html]
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 25, 2009 8:59 PM
in response to: signal3
|
|
|
|
|
Do KVM provider need a certificate for their product from SUN? Why there is
so many different behavior on different phone? or there are too many non
mandatory options in the KVM specification?
On Thu, Feb 26, 2009 at 12:53 PM, signal3 <signal3@gmail.com> wrote:
> For what it's worth, when I touch an LWUIT textarea on my moto e680i
> (touchscreen device without a keypad; circa 2005) it /does/ bring up the
> native input component appropriately. At that point, the user can choose
> from various keyboards or handwriting recognition input methods.
>
> So, this sounds like a KVM issue to me and probably more of a showstopper
> for the device in question than for LWUIT specifically. I think (for
> obvious reasons) many manufacturers are rushing sub-par touch devices to
> market, buyer beware!
>
>
> On Wed, Feb 25, 2009 at 11:14 PM, Stephan Bardubitzki stephan@bardubitzki.com> wrote:
>
>> I have the bad feeling that this can be a show stopper for LWUIT on
>> touchscreen devices.
>>
>> At least it seems not to be a problem on S60 based touchscreen devices.
>>
>>
>>
>> lwuit-users@mobileandembedded.org wrote:
>>
>>> Not only HTC, but also other touch screen cell-phone
>>> Such as MotoA1200.
>>>
>>> I tested TextArea in MotoA1200, it can't pop up the native cellphone
>>> input menu.
>>> But this kind of phone don't have keyboard.
>>> So I don't know how do deal with that...
>>> [Message sent by forum member 'fisher55' (fisher55)]
>>>
>>> http://forums.java.net/jive/thread.jspa?messageID=333916
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>>>
>>>
>>> --------------------------------
>>> Spam/Virus scanning by CanIt Pro
>>>
>>> For more information see
>>> http://www.kgbinternet.com/SpamFilter.htm
>>>
>>> To control your spam filter, log in at
>>> http://filter.kgbinternet.com
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
>> For additional commands, e-mail: users-help@lwuit.dev.java.net
>>
>>
>
[att1.html]
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Feb 25, 2009 11:03 PM
in response to: anson ho
|
|
|
|
|
On Wed, Feb 25, 2009 at 11:59 PM, anson ho <hotszkin@gmail.com> wrote:
> Do KVM provider need a certificate for their product from SUN? Why there is
> so many different behavior on different phone? or there are too many non
> mandatory options in the KVM specification?
>
>
Lol, well... I slightly feel like I'm feeding a troll here, but I'll offer
you my view of the world anyway. And believe me, if you're trolling, I hope
to feed you so much as to burst! 
First of all, I don't work for Sun and I'm not a lawyer so take my
statements at face value only; I'm just another perl hacker.
Does the KVM provider need a certificate? I don't think so... as I
understand it, the vendor needs to co-operate with Sun, pay them a fee, and
have their VM subjected to tests *only* if they want to use the coffee cup
logo. Otherwise, they're free to do what they want (e.g. Android Dalvik)...
although it may be a good indicator, it doesn't mean the VM will be bad or
non-compliant. It just means they didn't make the extra effort to "win the
hearts and minds" of their users, basically it's a marketing decision that
the vendor makes. There are other ways to "win the hearts and minds" of
users. Obviously, I would expect caveat emptor to apply.
Why are there so many different behaviors on the world's myriad of phones?
Simply because it's a big world, and... not all vendors/developers create
products of equal quality. Remember, quality is a subjective and
philosophical notion so what someone thinks is good another may think is
bad. Personally I think that "variety is the spice of life" and I don't see
this as being a bad(tm) thing. Ultimately, the "invisible hand of the
market" should determine what is good over time, but... in the short term,
the market acts more like a popularity contest than an objective measure of
"good". Right now, the market likes touchscreen phones but they're still
fledgling... If demand for them persists I'd expect the KVMs to get much
better, much sooner. Hey, the KVM on my e680i isn't all that bad and it's
almost 5 years old.
Are there too many non-mandatory options in the specification? Again, it
depends on how you define "too many". However, the intention and spirit of
the specifications is to be rigid where they need to be; flexible where they
are allowed. My opinion is that the specifications do a rather good job of
balancing the two... allowing vendors to optimize and customize things where
they can while at the same time insuring a high level of compatibility
between competing products. If you want a more concrete example consider
the fix I needed to put into one of my projects here:
http://battlephone.cvs.sourceforge.net/viewvc/battlephone/battlephone/src/ShotSprite.java?r1=1.1&r2=1.2
Without going into extreme detail, the bug in my software was caused by the
fact that I didn't consider the return value of the RayIntersection. The
specification deliberately states that the RayIntersection may remain
unmodified if nothing was intersected. My code was relying on some valid
intersection being returned no matter what. Now, many phones *did* actually
give me a valid value. However, those KVMs could be considered
"unoptimized" by returing a modified RayIntersection. Those phones did a
whole lot of work (pick is a computationaly expenive opertation) just to
figure out that nothing had been intersected. On some of the more optimized
KVMs, they (presumably) didn't do the computations since they were probably
implementing a more efficient means of picking (selection buffer maybe).
The bottom line became... what's better, a fast function call or an easy to
use function call? The JSR-184 specification allows both... and it's the
software engineer's job to accomodate both. I could very easily blame
myself for not having the will to implement my own code to determine
orientation. That's a lot of math for a simpleton like me! So I took the
easy way out and decided to lean on the library. But, I used the library in
an unexpected way, and I got expected results... serves me right! Are the
manufacturers to blame? The specification to blame? No... I'm to blame.
Anyway, it's easy to get frustrated by this stuff, but the alternative is
certainly more bleak. Consider it a lesser of two evils... in one case we
could have a perfectly rigid specification (in which the Java-ME platform
would degenerate into a product) or we could allow flexibility where it is
needed to insure that Java-ME remains a competitive platform. This way
different products can deliver the benefits that their intended users demand
(instead of what an arbitrary vendor may dictate). It's very important IMHO
to understand the differences between a platform and a product. Java-ME &
its configurations aren't really tangible products, they're platform
specifications. This is where many unnamed vendors blur the lines; often
leaving their adopties to shoulder the pain further down the line. Shame on
them!
I guess it boils down to a matter of faith, judgement, and expectations. Do
you have faith in manufacturers to deliver quality KVM implementations as
the industry moves forward? In your experience and judgement, do you think
the existing KVMs are so radically different that you can't produce a piece
of software which will do its job on a large number of disparate devices?
Do you really expect that an application with fantastically demanding
requirements will execute the same way on everything from a pre-paid
give-away to a $1000+ top of the line device?
Remember, the configuration specifications aren't something that any
individual corporation came up with. They're created by coalitions of
corporations, coalitions of people just like you and me. They stand to
benefit everyone. So, I think if you step back and take a sober look at it
all, you'll see that the state of affairs is in no way as bad as it seems
sometimes.
Just do some sensitivity analysis in your head... how many devices do you
think a well thought out small-mid size J2ME project (say 50k-250k lines)
will run on sucessfully? 10? 1000? 1e6? 100*1e6? 1e9? Now consider the
alternatives. I'm telling you all this so you can make up your /own/ mind
about what's better... for yourself... as a developer.
EOM/NRN
[att1.html]
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Apr 5, 2009 10:39 PM
in response to: Shai Almog
|
|
|
Hi,
The display of text in the T9 mode appears very small. Is it possible to increase the size of the font in the T9 mode form.
Thanks,
Regards
Norton.
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Apr 6, 2009 8:14 AM
in response to: technolgia
|
|
|
Hi,
Change the Font of the SoftButton style.
Regards,
Chen
lwuit-users@mobileandembedded.org wrote:
> Hi,
>
> The display of text in the T9 mode appears very small. Is it possible to increase the size of the font in the T9 mode form.
>
> Thanks,
> Regards
> Norton.
> [Message sent by forum member 'technolgia' (technolgia)]
>
> http://forums.java.net/jive/thread.jspa?messageID=340701
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
> For additional commands, e-mail: users-help@lwuit.dev.java.net
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Apr 6, 2009 9:21 AM
in response to: Chen Fishbein
|
|
|
Hi Chen,
I meant the size of the text we type in the T9 form not the soft button font.
Thanks,
Regards
Norton.
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Apr 23, 2009 9:37 AM
in response to: technolgia
|
|
|
Hi,
This is not in LWUIT's control since the text in the native text box is
handled by the MIDP implementation in a way that can't be customized.
> Hi Chen,
>
> I meant the size of the text we type in the T9 form not the soft button font.
>
> Thanks,
> Regards
> Norton.
> [Message sent by forum member 'technolgia' (technolgia)]
>
> http://forums.java.net/jive/thread.jspa?messageID=340793
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
> For additional commands, e-mail: users-help@lwuit.dev.java.net
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Apr 23, 2009 9:39 AM
in response to: technolgia
|
|
|
Hi,
This is not in LWUIT's control since the text in the native text box is
handled by the MIDP implementation in a way that can't be customized.
> Hi Chen,
>
> I meant the size of the text we type in the T9 form not the soft button font.
>
> Thanks,
> Regards
> Norton.
> [Message sent by forum member 'technolgia' (technolgia)]
>
> http://forums.java.net/jive/thread.jspa?messageID=340793
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
> For additional commands, e-mail: users-help@lwuit.dev.java.net
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Touchscreen Support
Posted:
Apr 27, 2009 2:19 AM
in response to: Shai Almog
|
|
|
Thank you..
|
|
|
|
|
java.net RSS
