On 3/16/07, Nils Bruin <[EMAIL PROTECTED]> wrote: > If lots of options get added then menus are unavoidable, but currently > I don't think the options presented in the notebook take up real > estate that would otherwise get good use. Avoiding drop-down menus has > the advantage that all options are immediately visible. Having to > first drop down the menu does add another layer of indirection.
I am not going to ever add a drop-down menu on the top of the SAGE Notebook screen. Instead, we will rethink, eliminate, or move some of the existing buttons in the upper right (there are too many already). > For the help: From experience (my university uses them quite a bit), I > find that multi-level CSS drop down menus are a rather mixed blessing. > The problem: Path of the pointing device becomes important in addition > to the position of the click. Try navigating one a few levels deep > using an oversensitive trackpad on a laptop. Does anybody know how > accessibility tools can make sense of drop down menus? I very much agree. > I think good search access would provide a much better interface to > the help than a drop-down hierarchical contents list. Even just a > search tool that produces a page with the lines from the index that > match a given substring would be very useful. I find I never access > computer algebra system help via contents lists, but always via search > or index. I fully agree. I have some ideas for implementing full text search for the notebook, which I'll implement soon. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
