Fl_Browser instead of Fl_Tree for <select> list box.

Discussion:
http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-December/009604.html
http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-December/009609.html

Fl_Tree didn't handle the 18000-item list in
https://bugzilla.redhat.com/query.cgi?format=advanced so well,
plus it's relatively heavy, plus we've found bugs in it on occasion
because it's newer than Fl_Browser. Fl_Browser is naturally
closer to what we use than Fl_Tree is in its ordinary default
usage.

Why didn't I use Fl_Browser initially when going to fltk-1.3?
Documentation made it sound like fltk1 and fltk2's browsers were
quite different despite having the same name (I think the APIs
were rather dissimilar, although I don't feel it's worth my time
to verify that right now), and I believe I had the impression that
Fl_Browser was going to be too limited in some ways.

1 files changed, 3 insertions, 5 deletions

diff --git a/dw/fltkui.hh b/dw/fltkui.hh
index 46bb5c39..29448384 100644
--- a/dw/fltkui.hh
+++ b/dw/fltkui.hh
@@ -505,15 +505,13 @@ class FltkListResource:
 protected:
    Fl_Widget *createNewWidget (core::Allocation *allocation);
    void setWidgetStyle (Fl_Widget *widget, core::style::Style *style);
-
-   int getNumberOfItems () {return itemsSelected.size();};
+   int getNumberOfItems();
    int getMaxItemWidth ();
-
 private:
    static void widgetCallback (Fl_Widget *widget, void *data);
    void *newItem (const char *str, bool enabled, bool selected);
-   void *currParent;
-   lout::misc::SimpleVector <bool> itemsSelected;
+   int currDepth;
+   int colWidths[4];
    int showRows;
    ListResource::SelectionMode mode;
 public: