Difference between revisions of "Development/Plans/EmbeddedGlom"

From Glom
Jump to: navigation, search
(Embedded Glom)
Line 1: Line 1:
 
Glom already [http://bugzilla.gnome.org/show_bug.cgi?id=441854 runs on Maemo] (The Nokia 800 and 810 Internet Tablets), though it is only an initial port. Some  more work is needed:
 
Glom already [http://bugzilla.gnome.org/show_bug.cgi?id=441854 runs on Maemo] (The Nokia 800 and 810 Internet Tablets), though it is only an initial port. Some  more work is needed:
  
* Use hildon widgets such as the time and date widgets (needs modifications to hildon to allow them to be empty).
+
* Use hildon widgets such as the time and date widgets (needs modifications to hildon to allow them to be empty, though these should probably be in GTK+ anyway).
 
* Allow the Glom developer to specify smaller alternative layouts.
 
* Allow the Glom developer to specify smaller alternative layouts.
* Handle loss of network connections more gracefully, and offer a network connection (using libconic) when neeeded.
+
* Handle loss of network connections more gracefully, and offer a network connection (using libconic) when needed.
* Offer a simple replication system to handle data input (and maybe modification) when the handheld does not have a network connection.
+
* Offer a simple replication system to handle:
 +
  - Updating read-only tables from the server.
 +
  - Data input (and maybe modification) when the handheld does not have a network connection. We should probably avoid replication that would ever require admin intervention to resolve conflicts during replication, or at least make it very clear when that could be required.

Revision as of 06:12, 6 November 2007

Glom already runs on Maemo (The Nokia 800 and 810 Internet Tablets), though it is only an initial port. Some more work is needed:

  • Use hildon widgets such as the time and date widgets (needs modifications to hildon to allow them to be empty, though these should probably be in GTK+ anyway).
  • Allow the Glom developer to specify smaller alternative layouts.
  • Handle loss of network connections more gracefully, and offer a network connection (using libconic) when needed.
  • Offer a simple replication system to handle:
 - Updating read-only tables from the server.
 - Data input (and maybe modification) when the handheld does not have a network connection. We should probably avoid replication that would ever require admin intervention to resolve conflicts during replication, or at least make it very clear when that could be required.