Features/Onscreen Keyboard: Difference between revisions

(2 intermediate revisions by 2 users not shown)

Line 1:

<noinclude>~~{{TOCright}}~~

[[Category:Feature Page Incomplete]]

[[Category:Feature|~~<Feature Name>~~]]

[[Category:Feature|Onscreen Keyboard]]

</noinclude>

Line 20:

== Detailed Description ==

With OLPC announcing the XO-3 tablet, and with hardware like the [http://thejoojoo.com/ JooJoo tablet], Sugar should become better suited for touch-based, physical keyboard-less devices. The on-screen keyboard feature aims to provide one such functionality.

On-screen keyboards are also important for certain accessibility related contexts, but use cases like that are better handled by specialized software like [[Features/~~Accessibility_virtualkeyboard~~]].

On-screen keyboards are also important for certain accessibility related contexts, but use cases like that are better handled by specialized software like [[Features/Accessibility virtual keyboard]].

=== Software ===

Line 47:

==UI Design==

Following is a screenshot of fvkbd in Sugar, using an experimental Spanish layout:

[[Image:Sugar-ES-Onscreen-KBD.png]]

A screencast is also [http://dev.laptop.org/~sayamindu/sugar_vkbd_multi.ogv available].

== How To Test ==

{{:{{PAGENAME}}/Testing}}

== User Experience ==

~~''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''~~

TODO

== Dependencies ==

~~''What other packages (RPMs) depend on this package? Are there changes outside~~ the ~~developers' control on which completion of this feature depends? In other words~~, ~~does your feature depend on completion of another feature owned by someone else or that you would need~~ to ~~coordinate~~, ~~which might cause you to be unable to finish on time? Other upstream projects like Python?''~~

FVKBD is the only external dependency at the moment. It needs to support multi-lingual situations correctly.

Other dependencies may include a GTK+ module, a device icon extension to invoke the keyboard, etc.

== Contingency Plan ==

~~''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "~~None necessary, revert to previous release behaviour.~~" Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''~~

None necessary, revert to previous release behaviour.

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

None

== Release Notes ==

''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

TODO

== Comments and Discussion ==

* See [[{{TALKPAGENAME}}|discussion tab for this feature]] ~~~~

* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

@@ Line 1: / Line 1: @@
-<noinclude>{{TOCright}}
+<noinclude>
 [[Category:Feature Page Incomplete]]
-[[Category:Feature|<Feature Name>]]
+[[Category:Feature|Onscreen Keyboard]]
 </noinclude>
@@ Line 20: / Line 20: @@
 == Detailed Description ==
 With OLPC announcing the XO-3 tablet, and with hardware like the [http://thejoojoo.com/ JooJoo tablet], Sugar should become better suited for touch-based, physical keyboard-less devices. The on-screen keyboard feature aims to provide one such functionality.
-On-screen keyboards are also important for certain accessibility related contexts, but use cases like that are better handled by specialized software like [[Features/Accessibility_virtualkeyboard]].
+On-screen keyboards are also important for certain accessibility related contexts, but use cases like that are better handled by specialized software like [[Features/Accessibility virtual keyboard]].
 === Software ===
@@ Line 47: / Line 47: @@
 ==UI Design==
+Following is a screenshot of fvkbd in Sugar, using an experimental Spanish layout:
 [[Image:Sugar-ES-Onscreen-KBD.png]]
+A screencast is also [http://dev.laptop.org/~sayamindu/sugar_vkbd_multi.ogv available].
 == How To Test ==
 {{:{{PAGENAME}}/Testing}}
 == User Experience ==
-''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
+TODO
 == Dependencies ==
-''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
+FVKBD is the only external dependency at the moment. It needs to support multi-lingual situations correctly.
+Other dependencies may include a GTK+ module, a device icon extension to invoke the keyboard, etc.
 == Contingency Plan ==
-''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''
+None necessary, revert to previous release behaviour.
 == Documentation ==
-''Is there upstream documentation on this feature, or notes you have written yourself?  Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''
+None
 == Release Notes ==
-''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''
+TODO
 == Comments and Discussion ==
-* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
+* See [[{{TALKPAGENAME}}|discussion tab for this feature]]