Fabien Costantini wrote:
> I do complain :-)
> This was made on purpose and we even (briefly) discussed about this,
> this was made to follow the API order in the sources.
I can say I've been through this with my commercial software,
and I have to say alphabetical is the way to go for reference
manuals. Tutorials, on the other hand, are best managed with
groupings.
It's really confusing to users quickly trying to find something
in a large list if it's not alphabetical. Only a few users think
to use the browser's built-in find function, so they just scroll
back+forth searching.. painful to watch. (I've had to do a lot of
shoulder surfing watching users use my own software and docs.)
I came around to the user's view myself when I was a user
of 3D software that had giant API references (maya, shake..),
and definitely appreciated the index being alphabetical,
and really hated, hated, when it was 'in some other kind
of order' that was hard to discern the logic behind it,
and quickly decided it was just 'a random mess' and resorted
to scrolling around or browser-searching. Who has the time
to figure out what the documenter was thinking.
For sure Fl_Browser was not really in any kind of order;
like methods were/are a bit all over the place. And I imagine
even if we fixed it up, it would degrade over time as new code
was added, cause when coding, one's not always thinking about
documentation order implications..
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
