Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 0.9.9
-
Fix Version/s: 1.7
-
Component/s: utilities
-
Labels:None
Description
Let the user maintain a persistent list of passages and searches, which they can rename.
Attachments
Activity
More thoughts that I put in an email to a BD user:
Our next major release "Elephant" will feature all kinds of memory. Some key features are:
1) Bookmarks - The ability to save a view of a book. This may be a single verse, a collection of verses, a chapter, a dictionary entry, a commentary selection.... The Bookmark will also retain the View settings when the Bookmark is created.
2) Automatic Bookmark - The ability to automatically save the Bookmarks for every book that is being viewed when the program closes.
3) Historical Bookmarks - The use of Bookmarks in "Forward" and "Backward" navigation. Currently the program only remembers what verses are being viewed.
4) Applied Bookmarks - The ability to apply a Bookmark pertaining to one Bible version to another.
5) Annotated Bookmarks - The ability to save notes for a Bookmark. Other SWORD programs use "Personal Commentary" This will be our primary mechanism instead of Personal Commentary.
It is likely that this will replace Save and Save All.
This won't save the physical layout, but only the content layout and its order. Saving the physical layout will come later.
This can use the save/open verse list feature, but it needs to be fixed. Save All, should be changed to create a BookMark set.
It should store the state of the Bible View. This should include:
1) the books that are selected and their order.
2) Their selection (e.g. passage lookup or search request for Bibles; BCV for commentaries, displayed entry for "dictionaries") [Probably should save both lookup and search request so that if the index is dropped the restore will still work and so that the search does not have to be done again.
3) The state of the View Menu at save.
4) The font spec currently in effect. (This may not be necessary)
In order to have this work with current lists, there should be a version number.
Also, the directory that they are currently saved in is ~user. It should probably be a bookmark subdirectory of $JSWORD_HOME.
There should be Bookmarks list which the user can access and maintain (delete, rename).
This should dovetail with History, allowing the user to save any history element as a Bookmark.
The user should be able to specify that BibleDesktop automatically saves all Bible Views as a BookMark set, using that to restore the application on startup.
The user should be able to specify that a BookMark set is used to start BibleDesktop each time it starts.