Last modified: 2013-11-06 15:50:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58241, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56241 - Getting rid of wikibase.ui (the "old ui")
Getting rid of wikibase.ui (the "old ui")
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Wikidata bugs
: javascript
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-28 13:20 UTC by Daniel A. R. Werner
Modified: 2013-11-06 15:50 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Daniel A. R. Werner 2013-10-28 13:20:18 UTC
The old ui (see https://meta.wikimedia.org/w/index.php?title=Wikidata/Notes/JavaScript_ui_implementation/old_ui) should be refactored to share as much code as possible with the new, jQuery.wikibase based repository user interface implementation.

This means that we have to get rid of all the code in wikibase.ui and instead re-implement it as jQuery widgets, sharing code with other jQuery.wikibase widgets or making use of jQuery.valueview.

This task should probably be further divided into more fain grained sub-tasks. The actual implementation of the old ui as part of the new ui should be carefully discussed as there are different possible approaches and "new ui" related bugs that might better be taken care of first.
Comment 1 Lydia Pintscher 2013-11-05 21:55:33 UTC
I'm going to close this as this is on our radar anyway and I don't think it is useful to keep this around - just cluttering up the bugtracker at the moment.
Comment 2 Daniel A. R. Werner 2013-11-06 02:59:21 UTC
When it comes to the actual refactoring, this should ideally serve as tracking bug since this is too big for just one item. There has been no real commitment to this in the past besides the toolbar refactoring which has happened months ago already.

Also, some development note on meta is currently referring to this one, so it also serves as documentation for people outside the team who do not share any team internal radar ;)
Furthermore, this could be the place to discuss how exactly the refactoring should be done or at least offer a link to further development notes regarding the details after the team has discussed them.
Comment 3 Lydia Pintscher 2013-11-06 07:19:09 UTC
Let's please keep this closed. A bug is not a place for proper refactoring discussion.
We will need a tracking bug for this later but we will split this up in a meeting as needed and then create the necessary bugs. It will not be this one.
Comment 4 Daniel A. R. Werner 2013-11-06 15:50:23 UTC
The Bug could still be a place to accumulate thoughts for the actual discussion (whenever that's going to happen...). At least that's one of the reasons for being able to drop messages on the bug's thread.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links