Last modified: 2014-08-26 03:40:07 UTC
As it is now you got the choice between nasty JavaScript-hacks and editing EditPage.php for changing the toolbar-buttons. It would be better if they were accessible through a WM specialpage.
Probably you mean same thing as bug 11732.
That does not appear to be so. bug 11732 talks about different toolbar-buttons for different languages, I just want the buttons more accessible for changes and modifications in general.
I.e. if you want to change the standard -- (two hyphens) before the signatures created by the current signature button to say, a — (em dash), you have to hack includes/EditPage.php, you can't change it in a page like [[Mediawiki:EditButtons]].
Yes, thats correct. I belive a Mediawiki-specialpage would be better than having to edit the EditPage.php or doing javascript hacks.
JS Hacks? What are you talking about. Last time I checked the methods for adding buttons to the toolbar were clean JS functions. There is nothing wrong with that. The buttons use JS to add things into the text box, so there's nothing wrong with using JS to add new buttons. MW makes JS readily available for the site, and also for individual users. Making use of things like [[MediaWiki:EditButtons]] would only help sites, it doesn't help an individual user at all.
The problem is modifying button that at defined in includes/EditPage.php. If i am not very wrong, that is where the singature-button-js is located.
I have made this little hack to do the requested modifications (the "nasty" js-hack): http://no.wikipedia.org/w/index.php?title=MediaWiki:Monobook.js&diff=next&oldid=3849958 Given that the editbuttons are localized, I think it would be somewhat difficult to do a entirely dynamic configuration of the buttons, but it shouldn't be too difficult to make the image, open, close and key-parameters also a part of the Message-files (ie. localized). This way it would be possible to edit the contents in the MediaWiki-namespace and get rid of awkward js-hacks in the global js-files (as now introduced in nowiki).
*** Bug 14808 has been marked as a duplicate of this bug. ***