maemo.org - Talk - View Single Post - New stuff available for creating/editing virtual keyboards on the N900 now available

	nicolai	2012-10-23 , 08:09
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#131

Originally Posted by qwazix

It looks good. Can't you strech rows 1 and 2 to full width so that you gain even 1 pixel per key?

I must admit, I don't fully understand how the button size is
determined. There are key size attributes in the xml layout file
but the renderer shrinks the button size, depending on
the available space (width/height) and number of rows.

I created this layout by trial and error.

Originally Posted by kent_autistic

The default vkb includes some punctuations, actually the most useful punctuations - period, comma, question mark, and exclamation point. It would be good to retain at least the most commonly used punctuations. A good example would be the Maliit vkb, see how period and comma is at the bottom.

I find the maliit vkb is superior to the hildon vkb, what happens
to the project porting maliit for fremantle? Maybe we should
focus on that one instead.

Originally Posted by freemangordon

A wild idea:

Add another property to vkbrenderer class, lets name it "keys-special", which contains an array of chars. For every char in that array, create a button (from him-western-...) right to the spacebar. Treat those buttons the same way space button is treated. That way ABI will be kept, i.e. if vkbrenderer class does not expose such property, do nothing. I hope you got the idea, I can elaborate if needed.

Good idea. Where would we store this char array information?
(Assumed you meant this keys depends on the current language)
Another idea: We only add shift and backspace key to the
space bar row. That way we have more space and not this size
requirement for the shift arrow/backspace arrow icon we have now.

nicolai

Quote & Reply |

The Following 2 Users Say Thank You to nicolai For This Useful Post:
fw190, neboja