I doubt OOUI will use the same classes, but being styled identically would
be nice. I'm working on a way to generate OOUI compatible output from PHP,
so that the same classes actually can be used, and ideally the server-side
widgets I'm working on could be used as the way MWUI generates widgets.
It's important to identify that the core principal behind OOUI's design is
abstraction, so widgets in OOUI will not, and need not, have semantic HTML
output which can be styled using generic CSS targeted at such. It turns out
that even in modern browsers, using HTML5 and CSS3, that it is not possible
to achieve cross browser compatible styling on many semantic elements that
have been around since the dark ages, like fieldset, legend, button, or
input. OOUI also uses abstraction for events for similar reasons - but I
digress. The point is, we really look forward to having output of certain
(simple) OOUI compatible widgets from PHP, because it supports out approach
to abstraction, even in a non-JS environment.
I'm on vacation until the 13th, so I might not check back until then. When
I return, I will be working again on my PHP library, and we should talk
about how we can eventually merge all this stuff together.
- Trevor
On Thu, May 8, 2014 at 9:15 AM, Pau Giner <pginer(a)wikimedia.org> wrote:
Hi Gilles,
I'll add some details about Agora: Some of the Agora classes are already
available as part of mediawiki.ui (such as buttons and button groups we
discussed for Media Viewer), and progress details for upcoming UI
components are available in this Trello board:
https://trello.com/b/EXtVTJxJ/mediawiki-ui
I don't know the technical details on why OOUI components such as buttons
are not using those classes, or which are the plans for doing so, but I
would love the current duplication to be solved for the benefit of
consistency and time.
Pau
On Thu, May 8, 2014 at 5:19 PM, Gilles Dubuc <gilles(a)wikimedia.org> wrote:
Towards the end of developing features in Media
Viewer, Pau asked us to
correct a lot of the layout that was provided by the OOUI defaults. In fact
I know there are still some elements that aren't styled the way Pau wants
them to be, that we couldn't improve due to lack of time.
I think I recall that this happened because OOUI doesn't implement Agora
styles yet, which I understand to be the standard look as defined by the
Design team. Is that correct? Or were the styling issues specific to Pau's
design for Media Viewer?
Since we're embarking on Upload Wizard work, the fact that we will use
OOUI for it or not will soon be debated, and I'd like to clarify if we're
likely to have to do that sort of patching on top of existing CSS again in
order to comply to unified styling.
If there is a plan to make OOUI CSS comply to the unified styling, what's
the status of that? Is anyone actively working on it?
https://www.mediawiki.org/wiki/UX_standardization seems to list it as a
TODO, but there's no timeline nor references about who's taking on that
task.
_______________________________________________
Multimedia mailing list
Multimedia(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/multimedia
--
Pau Giner
Interaction Designer
Wikimedia Foundation
_______________________________________________
Design mailing list
Design(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design