Bug #1933
openXBL 2d Dropdown: various improvements
0%
Description
In order of priority, most urgent to least urgent:
1) rethink how enumerations get populated at runtime - currently done in
javascript, and this is so slow (for large lists like species in the pisco app)
that firefox pops up a dialog asking if user wants to terminate JS process.
Other possibilities include:
- optimizing the existing javascript code (NOTE - maybe the bottleneck is the
alphabetical reordering? is this done in JS? if so, can we do it in the rules
instead?)
- getting menuitems from a call to a java Command in the backend
2) make scrollbox arrows bigger and easier to hit - need to inherit from and
override default XUL arrowscrollbox to do this (see how default XUL menuitem was
overridden in a similar fashion, in the
jalama/chrome/content/widgets/enumeration_bindings.xml file)
3) reordering of entries on 2d popup screen - for example:
- most recently used at top, with separator line?
- alphabetical (current scheme)
- cluster species groups together
- species in the same spatial zone are grouped together
- other arbitrary grouping to accomodate individual preferences
Related issues
Updated by Matthew Brooke almost 20 years ago
0.5) Look at using 2 lines on each menuitem to display string, because long
strings (eg pisco species names) get cropped and are hard to tell apart
Updated by Matthew Brooke almost 20 years ago
Update to items (1) and (3)
- now have alphabetizing done in Java code - XSElementDeclarationWrapper, and
not in XBL. This paves the way for orderign schemes to be configurable in rules
(see item 3).
Now populates a little quicker, but still prompts to say javascript is slowing
down rendering. Prime suspect is actual creation of new menuitems (cloning and
adding), so need a way around that (see item 1)
Updated by Matthew Brooke almost 20 years ago
done item 0.5) (using multiple lines on each menuitem to display string, because
long strings (eg pisco species names) get cropped and are hard to tell apart)
Updated by Matthew Brooke over 19 years ago
Summary of what's left to do, and one added todo for color coding:
................................................................................
1) rethink how enumerations get populated at runtime - currently done in
javascript, and this is so slow (for large lists like species in the pisco app)
that firefox pops up a dialog asking if user wants to terminate JS process.
Prime suspect is actual creation of new menuitems (cloning and
adding); possibilities include:
- optimizing the existing javascript code (alphabetizing already done in Java
code - XSElementDeclarationWrapper, and not in XBL)
- getting menuitems from a call to a java Command in the backend
Now populates a little quicker, but still prompts to say javascript is slowing
down rendering. Prime suspect is actual creation of new menuitems (cloning and
adding), so need a way around that (see item 1)
................................................................................
2) make scrollbox arrows bigger and easier to hit - need to inherit from and
override default XUL arrowscrollbox to do this (see how default XUL menuitem was
overridden in a similar fashion, in the
jalama/chrome/content/widgets/enumeration_bindings.xml file)
................................................................................
3) reordering of entries on 2d popup screen - for example:
a) cluster species groups together, or species in the same spatial zone are
grouped together
b) other arbitrary grouping to accomodate individual preferences
c) most recently used at top, with separator line?
................................................................................
4) (NEW) color-code boxes in 2-d menu to group items (for example, invertibrates
blue, kelps brown, seagrass green etc). This might be easier if dataset has a
separate species table that has some classification data in it, or if dataset
has a taxonomy section filled in