27
edits
| Line 58: | Line 58: | ||
**** Checkboxes are not a problem. The tree has built-in support for them starting with Gecko 1.8 (treecol type="checkbox"), the images are missing in the default theme however (at least Firefox, SeaMonkey has them). Text boxes on the other hand require quite a few hacks (Adblock Plus 0.7 has inline editing in its preferences dialog - it works). Generally, editable trees have been discussed quite a few times already, maybe we will finally see them in Gecko 1.9. But still - I don't think it will be possible to display a textbox for every single row of the tree at the same time, this would be a waste of memory. All that I expect is an editor for one row once the editing mode has been activated. [Wladimir Palant] | **** Checkboxes are not a problem. The tree has built-in support for them starting with Gecko 1.8 (treecol type="checkbox"), the images are missing in the default theme however (at least Firefox, SeaMonkey has them). Text boxes on the other hand require quite a few hacks (Adblock Plus 0.7 has inline editing in its preferences dialog - it works). Generally, editable trees have been discussed quite a few times already, maybe we will finally see them in Gecko 1.9. But still - I don't think it will be possible to display a textbox for every single row of the tree at the same time, this would be a waste of memory. All that I expect is an editor for one row once the editing mode has been activated. [Wladimir Palant] | ||
** Overall I guess I would say that working from the current UI, but changing to a treeview, allowing options to be more easily edited, and adding descriptions of all the items (visible at top/bottom for whatever item is selected) would go a long way toward addressing the shortcomings of about:config. Perhaps a few buttons (for adding/deleting an option, or editing one? maybe this is a better replacement for doubleclick than the textfield idea) at top would be good too. | ** Overall I guess I would say that working from the current UI, but changing to a treeview, allowing options to be more easily edited, and adding descriptions of all the items (visible at top/bottom for whatever item is selected) would go a long way toward addressing the shortcomings of about:config. Perhaps a few buttons (for adding/deleting an option, or editing one? maybe this is a better replacement for doubleclick than the textfield idea) at top would be good too. | ||
* I don't think descriptions/human readable names or categorization are viable ideas, both require more effort then can be justified here (as has been noted in mozilla.dev.apps.firefox several times). And "beginners helper widgets" are a non-feature - whoever goes to about:config is an advanced user by definition. Improvements on a lower scale might still be fine, especially better editing of preferences. Search should be the usual find bar, no need to reinvent the UI here. Optional presentation as a tree might also be useful, especially if you don't create useless containers containing only one pref. Possible issues: a container in the tree might be a pref itself, sorting is problematic. [Wladimir Palant] | |||
==== Gerv's Thoughts ==== | ==== Gerv's Thoughts ==== | ||
edits