If you would like to be kept up to date with Dasher development news, join the Dasher Yahoo Group. If you decide you'd like to hear special announcements only, you can join the same group, and then modify your membership settings at the discussion group website.
Click to subscribe to dasher-text-entry using your browser
| Browse the discussion group. | Post message: | dasher-text-entry@yahoogroups.com |
| Subscribe: | dasher-text-entry-subscribe@yahoogroups.com |
| Unsubscribe: | dasher-text-entry-unsubscribe@yahoogroups.com |
| List owner: | dasher-text-entry-owner@yahoogroups.com |
We have a Dasher project wiki for discussing Dasher development.
When reporting bugs, please be sure to give the precise version of Dasher you are using, and complete information about how to reproduce the bug.
[Our bug tracker is located at bugzilla. (view all)]
CVS access is provided to let you get hold of the latest source code. To access it, type:
cvs -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome login
and press enter at the prompt. Now run
cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co dasher
and the CVS tree will be downloaded.
The Dasher code consists of two main sections - a platform independent core, and a platform dependent interface. The core has been written with portability in mind and so should build on most platforms with a modern C++ compiler. Note that Dasher currently requires the Expat XML parsing library to read alphabet definition files - for embedded platforms, it may be desirable to replace the AlphIO functionality with simpler code rather than port or include Expat.
The platform dependent interface code is responsible for passing user input to the Dasher core and displaying the Dasher canvas and outputting text. Documentation for how the interface should communicate with the core may be found here.
If none of the above routes satisfies your needs, please send an email.