Since I've seen it brought up in two places relevant to what I'm working on with MediaWiki:Sidebar right now I'd like to see any notes people may have on a replacement for MediaWiki:Sidebar. The consensus seams to be that we want to replace MediaWiki:Sidebar with a Special: page interface and stuff stored directly in the database instead of something in the i18n system. For now I'm thinking of calling it Special:EditNavigation/sidebar (I plan to expand our support for navigation beyond just that sidebar so that's why it's not Special:EditSidebar).
I'd like to see any comments or requirements people have of an interface/system for editing the sidebar.
One question. How is our policy on JavaScript for these kind of things right now? For something like this where users are going to want to be able to drag and reorganize things do we have to do this in a slow way that works without JS?
"DF" == Daniel Friesen lists@nadir-seen-fire.com writes:
DF> For something like this where users are going to want to be able to drag DF> and reorganize things do we have to do this in a slow way that works DF> without JS? Yes you do. You need to offer an alternate way for one to configure their many wikis via batch configuration files, as they are not going to do each one by hand in some browser.
On 11-08-22 04:56 PM, jidanni@jidanni.org wrote:
"DF" == Daniel Friesen lists@nadir-seen-fire.com writes:
DF> For something like this where users are going to want to be able to drag DF> and reorganize things do we have to do this in a slow way that works DF> without JS? Yes you do. You need to offer an alternate way for one to configure their many wikis via batch configuration files, as they are not going to do each one by hand in some browser.
That comment is fairly irrelevant to a question on whether a in-browser Special: page should function in browsers with js disabled. No-one in their right mind is going to use a Special: page user interface to batch edit a bunch of wiki's navigation.
...frankly if you're actually batch editing navigation you're doing things completely wrong. If you've got common things you want in your navigation you should be using the hooks to modify the navigation and include an extra implicit set of navigation in each wiki.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
Well whatever you do, make sure I can still use something similar to some maintenance/*.php command to update something similar to MediaWiki:Sidebar to several machines.
On Tue, Aug 23, 2011 at 11:49 AM, jidanni@jidanni.org wrote:
Well whatever you do, make sure I can still use something similar to some maintenance/*.php command to update something similar to MediaWiki:Sidebar to several machines.
Can still use? AFAIK we have no maintenance script to do that currently....
On Tue, Aug 23, 2011 at 12:07 PM, K. Peachey p858snake@gmail.com wrote:
Can still use? AFAIK we have no maintenance script to do that currently....
He probably exports and imports MediaWiki:Sidebar
On 23.08.2011, 6:07 K. wrote:
On Tue, Aug 23, 2011 at 11:49 AM, jidanni@jidanni.org wrote:
Well whatever you do, make sure I can still use something similar to some maintenance/*.php command to update something similar to MediaWiki:Sidebar to several machines.
Can still use? AFAIK we have no maintenance script to do that currently....
php edit.php MediaWiki:Sidebar
jidanni@jidanni.org (2011-08-23 01:56):
"DF" == Daniel Friesenlists@nadir-seen-fire.com writes: DF> For something like this where users are going to want to be able to drag DF> and reorganize things do we have to do this in a slow way that works DF> without JS?
Yes you do. You need to offer an alternate way for one to configure their many wikis via batch configuration files, as they are not going to do each one by hand in some browser.
You could probably add JSON input. This could be achived by adding a textarea input to which one could simply copy&paste some data and which would normally be changed with JS. So when JS would be available you could simply hide the input.
I'd like to see any comments or requirements people have of an interface/system for editing the sidebar.
* Show in which languages each menu item is available and allow one to quickly add more language versions. * Show current user language by default and allow to view other version (e.g. in tooltip). * Move items or branches (whole submenu) up or down and between branches. * Allow users to compose their own menu and save it in their preferences. * Allow adding JS calls to each item (preferably with a fallback page - when JS is not available). * Ability to change position of special menus (e.g. languages and toolbox). * Each submenu should have "defaults to visible" true/false attribute (e.g. languages are visible by default when no cookie is set). * Each menu item should have a changeable id attribute e.g. "p-lang" for language menu. This should probably only be available in some advanced mode (as changing id would break some existing scripts). * Ability to add/change access keys for items (also probably in advanced mode).
Cheers, Nux.
wikitech-l@lists.wikimedia.org