Hi, Here go my comments on the keyboard navigation patches. I like them, and would like to commit it probably in the next version (kbd3). Note: we use to work heavily on patches and commit only after they're stable or polished. All this with a view to keep a relatively stable CVS source tree to work with. This is different to the usual model, but it has its rewards. With regard to the keyboard navigation patch, it probably can be polished better when on CVS, so here my remarks to make the next version into the sources. On Fri, 24 Oct 2003, Frank de Lange wrote:
Sebastian Geerken wrote:
I would at least leave the traditional line, for reasons of consistence. Perhaps the link may be also highlighted, in a lighter color than the background color (and lightgray for white etc., look at Dw_style_color_create, which is used for shaded colors for borders)? This would make it unconfusable with text selections.
I have tried using tile and stipple fill patterns for focus highlight, this did not give useable results. Next on the line is color, with a (stippled/dashed) frame around the link.
This is a good idea. Having the spaces inside links highlighted and the whole kbd. nav. current link in a distinctive pattern or color. One thing I noticed between kbd1 and kbd2 is that sometimes the latter makes odd jumps when using UP and DOWN keys. For instance with "gtk-types.html" page from GTK+'s manual. The "directional" navigation of links feels very handy and intuitive. One thing that can be improved is when the current link is outside the screen not to jump to it upon a key press but to find the most appropriate one within the displayed area. This would allow for a smooth keyboard navigation by integrating with the scrolling keys. Sincerely Jorge.-