VE is too heavyweight, it even implements categories. this should be split out, and added differently to the wiki page, so a dedicated, easy to implement category editor like hotcat is possible.
editing categories with ve currently is not only a terrible software architecture, but also terrible user experience. hotcat: 1 click to remove a category. VE: (minimum) 4 clicks and 15 seconds waiting time to start the visual elephant. not acceptable.
Version: unspecified
Severity: enhancement
(In reply to comment #0)
VE is too heavyweight, it even implements categories. this should be split out,
and added differently to the wiki page, so a dedicated, easy to implement
category editor like hotcat is possible.
I don't consider bug reports with "easy to implement"/"heavy-weight" buzzwords particularly helpful if you want to convince developers that there might actually be a real problem. Could you stick to technical aspects, also in your own interest, and elaborate a bit on why it "is possible"? Thanks!
I'll leave it to the developers to explain the potential advantages to have category editing as part of VE. Or not. :)
hehe - probably better. i saw your cv here: http://home.arcor.de/ak-47/cv.html and i am quite impressed. and it states "corresponding Open Source community with its own culture and demands". i guess language like "easy to implement"/"heavy weight" is cultural. i could have said "implemented by one person in X days of work, and activated X times worldwide, and used X times per day, and X bug reports in X years" to illustrate "easy" for hotcat. but it costs quite some time to fill out all these Xes. and i could point to the 85% against vote on the german wikipedia for VE, and calculate the man years or $$ invested to implement it until now, to illustrate "heavy weight" or "difficult". but - i understand you _very_ well, and i like like you slim bugzillas with as many closed tickets as possible. it does not serve anybody if we have tickets hanging around for years.
As I mentioned before, this is a terribly out-of-scope idea. HotCat-like functionality should (and currently is) be developed in a separate extension (right now it's happening in Extension:InlineCategorizer).
just to add one piece of information concerning hotcat, a dicussion on wikitech-l about "why it is not an extension" or "why it is not included in core":
and here the main problem:
tyler, you solved this now?
just for the record, i agree 100% with tyler, that it category editing should be a separate thing with reachable from an edit link. if it is called VE, or within VE project, or completely separate, in core, or an extenstion, is not too important imo. the hotcat discussion mentioned above was, beside editing a paragraph opens the whole page, the driver to file bug52380.
"Currently solving" would be a better description. ;) Here's the patch:
https://gerrit.wikimedia.org/r/76858
Everything except changing multiple categories at once and some other slight functionality nuances are working.
So this won't be done in VE, see patch in comment 5 which moves this to a separate extension ([[mw:Extension:InlineCategorizer]]). Closing as WONTFIX for VE itself.
Rupert: That would have to happen after deploying and starting to use that new extension, which would be another ticket to file at that time.
The original request in this bug report is WONTFIX though, hence restoring state.
i am terribly sorry that i mixed up a project "visual editor" with a budget with the software "visual editor" while entering the title. changed the title to match the contents. previous:
"VE should implement categories like hotcat does it"
this ticket says "split out the functionality". currently we have hotcat, and its working. in future there is inlinecategorizer, and it will work. this means, there is a better way for categories now and then. so the code should go out of VE _now_.
It will not go out of VE now as there is no functionality *ready* yet that would replace it. Both Hotcat and Inlinecategorizer are "not there (yet)".
You might want to create a new enhancement request "Deploy InlineCategorizer" after talking to the extension maintainer and finding out about plans, and then talk to VE maintainers (e.g. on https://en.wikipedia.org/wiki/Wikipedia:VE/F , mailing list or via IRC) how to inherit that functionality and make sure that VE deals properly with it, before filing a separate ticket.
Please leave this specific request as RESOLVED WONTFIX for the time being.