I will clean up the preference structure to remove obsolete fields.
This means that the preference ID will change and it will not be possible to upgrade to version 1.9 and later if you are using version
1.1 or older without losing the preference settings; I doubt this will
be a problem considering that 1.1 was released in 2001 ;-)
I assume you will add upgrade code for going from 1.8 to 1.9.
I'd also like to do something about the per-document settings. Today,
it is only the Font & Layout settings that can be stored for a
document, but there are other settings that also could be of interest,
e.g. alignment, force default text colours, enable underline tags,
word lookup, and screen depth (the device's default depth results in
faster rendering, but you might want to use a different setting for
documents with many images). The screen depth is stored, but (as far as I can tell) never restored...
The screen depth is stored so as to invalidate the paragraph height metadata if the document is loaded at a different depth from the one it was last loaded it. The paragraph height metadata becomes invalid when the depth changes, because which images get displayed can depend on the depth on some units.
Don't know how to handle these "global" and "local" preference settings, yet. Some "local" options are mixed with options that only makes sense "globally" and we also have to make it easy to store the settings...
Yes. And the other complication is that the font options can be EITHER global or local, depending on a pref switch.
Actually, the preference forms could need a bit of work, too. Some options seems a bit misplaced, e.g. why is the Alignment setting not included in the Font & Layout?
It certainly should be there.
> Still, the Font & Layout settings
should probably be moved to the preferences (and be split into two different forms; one for font and another one for layout).
Right. And I assume orientation is "layout".
I am glad you are taking on this task. It needs doing.
While updating the prefs, maybe you want to uniformize the hard key handling with the keyboard form by removing all the hard key entries from the prefs and throwing them into the keyboard database?
Alex
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: www.georgetown.edu/faculty/ap85
--------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
