Frontends:FeatureList - Revision history

Refdoc: /* User resources */

2018-01-10T15:17:11Z

‎User resources

2018-01-10T15:14:54Z

‎User resources

2018-01-08T07:52:45Z

2014-09-02T18:27:49Z

‎Module support: <ref>Not yet supported by the SWORD API.</ref>

2014-09-02T18:25:23Z

‎Module support: * [http://en.wikipedia.org/wiki/Qere_and_Ketiv Ketiv & Qere] support for the Masoretic text

2014-09-02T18:23:12Z

‎Module support: * Alternative readings (display primary, secondary or both)

2012-08-18T14:23:42Z

‎General UI features: * Per module assignment of speech synthesis voices, or none.

2012-02-03T18:01:31Z

‎Workflow

2012-02-03T17:57:48Z

‎Running

2012-02-03T17:56:49Z

‎Managing modules

@@ Line 85: / Line 85: @@
 Users should also be able to manage (create, edit, save) verse lists, possibly with comments on each verse.
-Users should be able to manage bookmarks in a tree list. These bookmarks should be so that they could be shared between different frontends. A [[Frontend:Bookmarks Standard|Standard for bookmarks]] is under discussion.
+Users should be able to manage bookmarks in a tree list. These bookmarks should be so that they could be shared between different frontends. A [[Frontends:Bookmarks Standard|Standard for bookmarks]] is under discussion.
 User generated material should be for that user alone (on a multi-user OS), unless specified by the author for viewing by all users.

@@ Line 85: / Line 85: @@
 Users should also be able to manage (create, edit, save) verse lists, possibly with comments on each verse.
-Users should be able to manage bookmarks in a tree list. These bookmarks should be so that they could be shared between different frontends. A [[Frontend:BookmarksStandard|Standard for bookmarks]] is under discussion.
+Users should be able to manage bookmarks in a tree list. These bookmarks should be so that they could be shared between different frontends. A [[Frontend:Bookmarks Standard|Standard for bookmarks]] is under discussion.
 User generated material should be for that user alone (on a multi-user OS), unless specified by the author for viewing by all users.

← Older revision		Revision as of 07:52, 8 January 2018
Line 1:		Line 1:
−	~~This page is oriented to the SWORD API, but the ideal features listed could apply equally as well to the JSword API.~~
−
−	~~==Ideal Full Featured SWORD Front-end==~~
−	What makes an ideal front-end is dependent upon the platform and the targeted audience. A hand-held, such as a PDA or phone, or an application targeted to children, probably would not be full featured.

	===Cross-platform===		===Cross-platform===

@@ Line 71: / Line 71: @@
 * Ruby markup for (e.g.) Japanese modules
 * Alternative readings (display primary, secondary or both)
-* [http://en.wikipedia.org/wiki/Qere_and_Ketiv Ketiv & Qere] support for the Masoretic text
+* [http://en.wikipedia.org/wiki/Qere_and_Ketiv Ketiv & Qere] support for the Masoretic text<ref>Not yet supported by the SWORD API.</ref>
 Other general support requirements:

@@ Line 71: / Line 71: @@
 * Ruby markup for (e.g.) Japanese modules
 * Alternative readings (display primary, secondary or both)
 Other general support requirements:

@@ Line 49: / Line 49: @@
 * Resolution independence, adaptable to both low and high resolution and small/large screens.
 * Speech synthesis to read text content of selection or whole chapter.
 * Optional continuous scrolling text with synchronized audio.
 * [http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&cat_id=RenderingGraphite Graphite] rendering (either by direct employment of the API or via a toolkit, such as Pango, that employs it)

@@ Line 33: / Line 33: @@
 * Removal of unwanted features.
 * Plug in of new or alternate features. E.g. whiteboard collaboration, Facebook integration.
 ===General UI features===

@@ Line 170: / Line 170: @@
 ====Running====
 * Be able to be run from within a front-end and standalone.
-* Make newly installed modules immediately seen by front-ends without restarting.
+* Make newly installed modules immediately seen by front-ends without restarting [low priority].
 ====Presentation====

@@ Line 149: / Line 149: @@
 * Predefine the CrossWire download site.
 * Allow the user to downloaded and install zips (via the remote installer).
-* Allow local installation of modules (e.g. from a CD).
+* Allow local installation of modules (e.g. from a CD or phone SD card).
 * Install modules by drag'n'drop to the front-end application (e.g. local zip file).
 * Work over a proxy.