Re: [QT*] unpredictive keyboard
On Mon, 27 Apr 2009 10:39:07 +0200
Franky Van Liedekerke wrote:
> I understand the concern, but when you type in a sentence (or multiple
> sentences) and you need punctuation characters, you're gonna need a
> lot of sliding ... so I would bring the most used keyboards under 3
> buttons as well. I'll try it, and if it clutters too much, I'll remove
> it again. I can always leave the code in, and just disable it in the
> layout.conf file ...
> For the buttons, any suggestions? I can take any html code ... see
> http://cityofstrife.net/hexcodes.html. For uppercase/lowercase, I'll
> use an "fat arrow" up/down (x21E7 and x21E9), but what to use for
> letter symbol, special char symbol and cipher symbol?
> In the letters keyboards, I'll add: up/down, special char, ciphers
> In the special char keyboard, I'll add: letters (lowercase), ciphers
> In the ciphers keyboard, I'll add: letters (lowercase), special chars
>
> Franky
Hmmm ... I changed keyboard.cpp to look like this (never mind I
could've used a case structure):
+++ qtmoko/src/plugins/inputmethods/predictivekeyboard/keyboard.cpp
2009-04-27 22:21:27.0 +0200 @@ -1577,6 +1577,16 @@
clear();
} else if(c == QChar(0x2190)) {// backspace key
doBackspace();
+} else if(c == QChar(0x21E7)) {// uppercase
+setBoardCaps(true);
+} else if(c == QChar(0x21E9)) {// lowercase
+setBoardCaps(false);
+} else if(c == QChar(0x2213)) {// Other
+setBoardByType(Other);
+} else if(c == QChar(0x2205)) {// Numeric
+setBoardByType(Numeric);
+} else if(c == QChar(0x2200)) {// Words
+setBoardByType(Words);
} else {
And then I changed etc/default/Trolltech/PredictiveKeyboardLayout.conf
to use these characters, but it seems that "\x" notation is only
interpreted correctly in the "Others" keyboard, on the other keyboards,
the symbols don't show as expected (empty spaces are used instead).
Any hint is appreciated ...
Franky
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
This is great - and might be what's needed to convince me to move from my
now-ancient QTE 4.4.3 to the latest and greatest!
Thanks to everyone for all the hard work on this - it's clear that Nokia
desupporting QTE was the best thing that could happen to the FR.
Warren
On Mon, Apr 27, 2009 at 4:39 AM, Franky Van Liedekerke
wrote:
> On Sun, Apr 26, 2009 at 10:22 PM, leona...@lilik.it
> wrote:
> >>> I've already build a new image with this (not online yet, since I'm
> >>> setting it up on a new space). A visual hint for prediciveness would
> >>> be nice, but I leave that up to you :-)
> >>
> >> btw, I also added code for a backspace key. I *know* that you can slide
> >> to the left for backspace, but if you want to delete an entire
> >> sentence (or just 10 letters), this becomes ridiculous. Therefore: the
> >> backspace key is to be found in the same group as the return key.
> >> I've updated the current image with it.
> >
> > you can select the text you want to cancel and leftslide, but it's very
> > unconfortable.
>
> true, even more because there's no visual feedback for selection (I
> think, or I never succeeded into selecting naything yet)
>
> >> Now just some buttons to quickly go from letters to ciphers and to the
> >> sentence-characters (".","?", etc...). Instead of always needing to
> >> slide up and down ... There's place for at least 3 extra signs on the
> >> letters screen, I would use them for "uppercase" (and in the uppercase
> >> version: "lowercase"), "numbers" and "sentence-characters". This would
> >> work more reliable and quicker than the basic sliding ...
> >
> > we could use the other three diagonals. I think it's better then filling
> > the keyboard with more buttons, or it will end up like matchbox keyboard.
>
> I understand the concern, but when you type in a sentence (or multiple
> sentences) and you need punctuation characters, you're gonna need a
> lot of sliding ... so I would bring the most used keyboards under 3
> buttons as well. I'll try it, and if it clutters too much, I'll remove
> it again. I can always leave the code in, and just disable it in the
> layout.conf file ...
> For the buttons, any suggestions? I can take any html code ... see
> http://cityofstrife.net/hexcodes.html. For uppercase/lowercase, I'll
> use an "fat arrow" up/down (x21E7 and x21E9), but what to use for
> letter symbol, special char symbol and cipher symbol?
> In the letters keyboards, I'll add: up/down, special char, ciphers
> In the special char keyboard, I'll add: letters (lowercase), ciphers
> In the ciphers keyboard, I'll add: letters (lowercase), special chars
>
> Franky
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, Apr 26, 2009 at 10:22 PM, leona...@lilik.it wrote:
>>> I've already build a new image with this (not online yet, since I'm
>>> setting it up on a new space). A visual hint for prediciveness would
>>> be nice, but I leave that up to you :-)
>>
>> btw, I also added code for a backspace key. I *know* that you can slide
>> to the left for backspace, but if you want to delete an entire
>> sentence (or just 10 letters), this becomes ridiculous. Therefore: the
>> backspace key is to be found in the same group as the return key.
>> I've updated the current image with it.
>
> you can select the text you want to cancel and leftslide, but it's very
> unconfortable.
true, even more because there's no visual feedback for selection (I
think, or I never succeeded into selecting naything yet)
>> Now just some buttons to quickly go from letters to ciphers and to the
>> sentence-characters (".","?", etc...). Instead of always needing to
>> slide up and down ... There's place for at least 3 extra signs on the
>> letters screen, I would use them for "uppercase" (and in the uppercase
>> version: "lowercase"), "numbers" and "sentence-characters". This would
>> work more reliable and quicker than the basic sliding ...
>
> we could use the other three diagonals. I think it's better then filling
> the keyboard with more buttons, or it will end up like matchbox keyboard.
I understand the concern, but when you type in a sentence (or multiple
sentences) and you need punctuation characters, you're gonna need a
lot of sliding ... so I would bring the most used keyboards under 3
buttons as well. I'll try it, and if it clutters too much, I'll remove
it again. I can always leave the code in, and just disable it in the
layout.conf file ...
For the buttons, any suggestions? I can take any html code ... see
http://cityofstrife.net/hexcodes.html. For uppercase/lowercase, I'll
use an "fat arrow" up/down (x21E7 and x21E9), but what to use for
letter symbol, special char symbol and cipher symbol?
In the letters keyboards, I'll add: up/down, special char, ciphers
In the special char keyboard, I'll add: letters (lowercase), ciphers
In the ciphers keyboard, I'll add: letters (lowercase), special chars
Franky
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
Roland wrote: > Hello Leonardo and Franky, > > I haven't tried out your changes yet but they sound very useful. I would > also prefer the three switching buttons suggested by Franky. I think when > putting them e.g. at the far right, they wouldn't really fill up the space > too much or make the other keys too small. if you try the patch you'll notice the keyboard is quite larger now... > Another idea: Wouldn't it be possible to toggle the predictability of the > keyboard through an option in the context (options) menu? By putting a > checkmark in front you would also have a visual information about the state. > I think this should be possible because when changing to the undocked > keyboard the option "Change input Method" changes into a submenu. That was my first attempt, but it seems that that menu has nothing to deal with the keyboard itself. It just sends basic signals like create/destroy to the widget and sets up the next one. Anyway, toggling/untoggling predictability is not something you do that often I guess, and it works ok with the diagonal slide. I'm having harder time in showing some graphics on the keyboard to have a feedback from that action. ciao, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: [QT*] unpredictive keyboard
Hello Leonardo and Franky, I haven't tried out your changes yet but they sound very useful. I would also prefer the three switching buttons suggested by Franky. I think when putting them e.g. at the far right, they wouldn't really fill up the space too much or make the other keys too small. Another idea: Wouldn't it be possible to toggle the predictability of the keyboard through an option in the context (options) menu? By putting a checkmark in front you would also have a visual information about the state. I think this should be possible because when changing to the undocked keyboard the option "Change input Method" changes into a submenu. Roland ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
>> I've already build a new image with this (not online yet, since I'm
>> setting it up on a new space). A visual hint for prediciveness would
>> be nice, but I leave that up to you :-)
>
> btw, I also added code for a backspace key. I *know* that you can slide
> to the left for backspace, but if you want to delete an entire
> sentence (or just 10 letters), this becomes ridiculous. Therefore: the
> backspace key is to be found in the same group as the return key.
> I've updated the current image with it.
you can select the text you want to cancel and leftslide, but it's very
unconfortable.
> Now just some buttons to quickly go from letters to ciphers and to the
> sentence-characters (".","?", etc...). Instead of always needing to
> slide up and down ... There's place for at least 3 extra signs on the
> letters screen, I would use them for "uppercase" (and in the uppercase
> version: "lowercase"), "numbers" and "sentence-characters". This would
> work more reliable and quicker than the basic sliding ...
we could use the other three diagonals. I think it's better then filling
the keyboard with more buttons, or it will end up like matchbox keyboard.
ciao,
leonardo.
--
http://leonardo.lilik.it
Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 15:15:07 +0200
Franky Van Liedekerke wrote:
> On Sun, 26 Apr 2009 11:36:26 +0200
> Franky Van Liedekerke wrote:
>
> > never mind ... wrong copy, ok now :-)
> > Although I still believe no dictionaries should be updated when in
> > non-predictive mode. I would also like not to have to click on a
> > word before being able to enter a space and continue to the next
> > word, so default accept would be nice as well in unpredictive
> > mode ... Probably KeyboardWidget::acceptWord() and
> > OptionsWindow::acceptWord() can benefit from you changes :-)
>
> Hi Leonardo,
>
> I've changed your patch a bit:
>
> - no more dictionary updates for non-predictive keyboard
> - disabled the animation for non-predictive keyboard (where the
> selected word was "pulled" into the correct place, it is nice but a
> bit overkill and too slow).
>
> Please check it out, I provided a .so file here:
> http://www.e-dynamics.be/openmoko/libqpredictivekeyboard.so
> For the changes:
> http://github.com/liedekef/qtmoko/commit/f818d487e3552e9b9832a9f5942ddfc3a2330031
>
> I've already build a new image with this (not online yet, since I'm
> setting it up on a new space). A visual hint for prediciveness would
> be nice, but I leave that up to you :-)
btw, I also added code for a backspace key. I *know* that you can slide
to the left for backspace, but if you want to delete an entire
sentence (or just 10 letters), this becomes ridiculous. Therefore: the
backspace key is to be found in the same group as the return key.
I've updated the current image with it.
Now just some buttons to quickly go from letters to ciphers and to the
sentence-characters (".","?", etc...). Instead of always needing to
slide up and down ... There's place for at least 3 extra signs on the
letters screen, I would use them for "uppercase" (and in the uppercase
version: "lowercase"), "numbers" and "sentence-characters". This would
work more reliable and quicker than the basic sliding ...
Franky
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 20:22:52 +0200 "leona...@lilik.it" wrote: > I didn't have time to check your patch. Anyway you cannot avoid a way > to "accept" a word. If you slide right, you put a whitespace, if you > click on the bar you accept the word and you have a free whitespace. > I've noticed also that while you wait for the animation to end, you > can type new letters, so you don't waste time. Hmmm ... I didn't notice that before, and it works :-) > > > > I've already build a new image with this (not online yet, since I'm > > setting it up on a new space). A visual hint for prediciveness > > would be nice, but I leave that up to you :-) > > I've checked it quickly, it doesn't seem really easy, I should get > more ocnfident with Qt. I hope I will have time to make it visible. > Is it better something like a "p" on a corner or a very short popup > saying "unpredictive"? well, I prefer something visible all the time, since the keyboard maintains it's state across usage > > And a question: wouldn't it be more logical to add a space by > > default after each word? It was like that once I believe ... > > that's what it does. When you accept the word you have a whitespace > added. I know now :-) > > Also, the capitalization is not working that good, maybe that can be > > off as well, or maybe that can be another option (left-bottom=> > > right-up stroke + visual confirmation). > > capitalization doesn't work really ok. Well, it just doesn't work > actually. Well, it works, but it takes the first word you type as beginning of a sentence (and thus capitalizes it), even if you correct a sentence and restart in the middle ... > Something I've noticed that could be improved is that if you type a > single letter and you want to accept it it's quite hard to touch with > your finger the letter, since it's quite little. I guess this is > inherited from the predictive keyboard. It would be better to make the > whole bar reactive instead of the single letter. true, but sliding to the right accepts the word as well ... Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
Franky Van Liedekerke wrote: > On Sun, 26 Apr 2009 11:36:26 +0200 > Franky Van Liedekerke wrote: > Hi Franky, >> never mind ... wrong copy, ok now :-) >> Although I still believe no dictionaries should be updated when in >> non-predictive mode. I would also like not to have to click on a word >> before being able to enter a space and continue to the next word, so >> default accept would be nice as well in unpredictive mode ... I didn't have time to check your patch. Anyway you cannot avoid a way to "accept" a word. If you slide right, you put a whitespace, if you click on the bar you accept the word and you have a free whitespace. I've noticed also that while you wait for the animation to end, you can type new letters, so you don't waste time. >> Probably KeyboardWidget::acceptWord() and OptionsWindow::acceptWord() >> can benefit from you changes :-) > > - no more dictionary updates for non-predictive keyboard > - disabled the animation for non-predictive keyboard (where the > selected word was "pulled" into the correct place, it is nice but a > bit overkill and too slow). that's better! > > Please check it out, I provided a .so file here: > http://www.e-dynamics.be/openmoko/libqpredictivekeyboard.so thanks, the university server seems to be lazy today. tomorrow I hope it will be fixed. > For the changes: > http://github.com/liedekef/qtmoko/commit/f818d487e3552e9b9832a9f5942ddfc3a2330031 > > I've already build a new image with this (not online yet, since I'm > setting it up on a new space). A visual hint for prediciveness would be > nice, but I leave that up to you :-) I've checked it quickly, it doesn't seem really easy, I should get more ocnfident with Qt. I hope I will have time to make it visible. Is it better something like a "p" on a corner or a very short popup saying "unpredictive"? > > And a question: wouldn't it be more logical to add a space by default > after each word? It was like that once I believe ... that's what it does. When you accept the word you have a whitespace added. > Also, the capitalization is not working that good, maybe that can be > off as well, or maybe that can be another option (left-bottom=> > right-up stroke + visual confirmation). capitalization doesn't work really ok. Well, it just doesn't work actually. Something I've noticed that could be improved is that if you type a single letter and you want to accept it it's quite hard to touch with your finger the letter, since it's quite little. I guess this is inherited from the predictive keyboard. It would be better to make the whole bar reactive instead of the single letter. ciao, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 11:36:26 +0200 Franky Van Liedekerke wrote: > never mind ... wrong copy, ok now :-) > Although I still believe no dictionaries should be updated when in > non-predictive mode. I would also like not to have to click on a word > before being able to enter a space and continue to the next word, so > default accept would be nice as well in unpredictive mode ... > Probably KeyboardWidget::acceptWord() and OptionsWindow::acceptWord() > can benefit from you changes :-) Hi Leonardo, I've changed your patch a bit: - no more dictionary updates for non-predictive keyboard - disabled the animation for non-predictive keyboard (where the selected word was "pulled" into the correct place, it is nice but a bit overkill and too slow). Please check it out, I provided a .so file here: http://www.e-dynamics.be/openmoko/libqpredictivekeyboard.so For the changes: http://github.com/liedekef/qtmoko/commit/f818d487e3552e9b9832a9f5942ddfc3a2330031 I've already build a new image with this (not online yet, since I'm setting it up on a new space). A visual hint for prediciveness would be nice, but I leave that up to you :-) And a question: wouldn't it be more logical to add a space by default after each word? It was like that once I believe ... Also, the capitalization is not working that good, maybe that can be off as well, or maybe that can be another option (left-bottom=> right-up stroke + visual confirmation). Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 11:16:28 +0200 Franky Van Liedekerke wrote: > On Sun, 26 Apr 2009 02:15:00 +0200 > "leona...@lilik.it" wrote: > > > Hi list, > > > > I've changed strategy on the unpredictive > > qtopia/qtextended/qtextendedimproved keyboard. > > Instead of patching the matchbox keyboard I've changed the original > > qtopia keyboard. I've stretched it a little to make it larger and > > higher and i made it unpredictable. I added another gesture: if you > > slide from bottom-right along the diagonal to up-left you can toggle > > prediction. > > > > here you can find the binary and the patch. > > http://leonardo.lilik.it/wordpress/2009/04/26/qtextended-keyboard-made-unpredictive/ > > > > the patch is on Franky's git tree but I guess it works with any Qt* > > since the keyboard doesn't seem changed at all. The binary is for > > the qt-extended-improved I'm using.. > > > > two improvements are possible: > > - give a visual feedback when toggling prediction on/off > > - well, there are three more diagonal gestures that could be used > > if you have ideas. > > Hi Leonardo, > > it seems prediction is still being used ... I'm a dutch speaker, and > it seems that when I enter the word "van", it predicts it to > "een" (because that word is in my personal prediction dictionary, from > before the changes). > If prediction is off, you should disable the use of any personal > dictionaries as well, as well as disabling saving to a dictionary. > never mind ... wrong copy, ok now :-) Although I still believe no dictionaries should be updated when in non-predictive mode. I would also like not to have to click on a word before being able to enter a space and continue to the next word, so default accept would be nice as well in unpredictive mode ... Probably KeyboardWidget::acceptWord() and OptionsWindow::acceptWord() can benefit from you changes :-) Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 02:15:00 +0200 "leona...@lilik.it" wrote: > Hi list, > > I've changed strategy on the unpredictive > qtopia/qtextended/qtextendedimproved keyboard. > Instead of patching the matchbox keyboard I've changed the original > qtopia keyboard. I've stretched it a little to make it larger and > higher and i made it unpredictable. I added another gesture: if you > slide from bottom-right along the diagonal to up-left you can toggle > prediction. > > here you can find the binary and the patch. > http://leonardo.lilik.it/wordpress/2009/04/26/qtextended-keyboard-made-unpredictive/ > > the patch is on Franky's git tree but I guess it works with any Qt* > since the keyboard doesn't seem changed at all. The binary is for the > qt-extended-improved I'm using.. > > two improvements are possible: > - give a visual feedback when toggling prediction on/off > - well, there are three more diagonal gestures that could be used if > you have ideas. Hi Leonardo, it seems prediction is still being used ... I'm a dutch speaker, and it seems that when I enter the word "van", it predicts it to "een" (because that word is in my personal prediction dictionary, from before the changes). If prediction is off, you should disable the use of any personal dictionaries as well, as well as disabling saving to a dictionary. Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 02:15:00 +0200 "leona...@lilik.it" wrote: > Hi list, > > I've changed strategy on the unpredictive > qtopia/qtextended/qtextendedimproved keyboard. > Instead of patching the matchbox keyboard I've changed the original > qtopia keyboard. I've stretched it a little to make it larger and > higher and i made it unpredictable. I added another gesture: if you > slide from bottom-right along the diagonal to up-left you can toggle > prediction. > Hi Leonardo, your patch is in my git now and I'm recompiling as we speak, thanks again! Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
On Sun, 26 Apr 2009 02:15:00 +0200 "leona...@lilik.it" wrote: > Hi list, > > I've changed strategy on the unpredictive > qtopia/qtextended/qtextendedimproved keyboard. > Instead of patching the matchbox keyboard I've changed the original > qtopia keyboard. I've stretched it a little to make it larger and > higher and i made it unpredictable. I added another gesture: if you > slide from bottom-right along the diagonal to up-left you can toggle > prediction. > > here you can find the binary and the patch. > http://leonardo.lilik.it/wordpress/2009/04/26/qtextended-keyboard-made-unpredictive/ > > the patch is on Franky's git tree but I guess it works with any Qt* > since the keyboard doesn't seem changed at all. The binary is for the > qt-extended-improved I'm using.. > > two improvements are possible: > - give a visual feedback when toggling prediction on/off > - well, there are three more diagonal gestures that could be used if > you have ideas. > > now matchbox seems quite useless. > > feedbacks are most welcome. > > ciao, > leonardo. Hi Leonardo, thanks alrady! Btw: your patch (diff) is reversed :-) Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QT*] unpredictive keyboard
leona...@lilik.it escribió: > Hi list, > > I've changed strategy on the unpredictive > qtopia/qtextended/qtextendedimproved keyboard. > Instead of patching the matchbox keyboard I've changed the original > qtopia keyboard. I've stretched it a little to make it larger and higher > and i made it unpredictable. I added another gesture: if you slide from > bottom-right along the diagonal to up-left you can toggle prediction. > > here you can find the binary and the patch. > http://leonardo.lilik.it/wordpress/2009/04/26/qtextended-keyboard-made-unpredictive/ > > the patch is on Franky's git tree but I guess it works with any Qt* > since the keyboard doesn't seem changed at all. The binary is for the > qt-extended-improved I'm using.. > > two improvements are possible: > - give a visual feedback when toggling prediction on/off > - well, there are three more diagonal gestures that could be used if > you have ideas. > > now matchbox seems quite useless. > > feedbacks are most welcome. > > ciao, > leonardo. > Well, I just get a network timeout. Maybe the server is down? Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QT*] unpredictive keyboard
Hi list, I've changed strategy on the unpredictive qtopia/qtextended/qtextendedimproved keyboard. Instead of patching the matchbox keyboard I've changed the original qtopia keyboard. I've stretched it a little to make it larger and higher and i made it unpredictable. I added another gesture: if you slide from bottom-right along the diagonal to up-left you can toggle prediction. here you can find the binary and the patch. http://leonardo.lilik.it/wordpress/2009/04/26/qtextended-keyboard-made-unpredictive/ the patch is on Franky's git tree but I guess it works with any Qt* since the keyboard doesn't seem changed at all. The binary is for the qt-extended-improved I'm using.. two improvements are possible: - give a visual feedback when toggling prediction on/off - well, there are three more diagonal gestures that could be used if you have ideas. now matchbox seems quite useless. feedbacks are most welcome. ciao, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
