Hi, >>I have done a lot of work on the Foreground Skin[0] over the past year. >>Some may know it is already used on WikiApiary[1] using SMW as well >>many other wikis using SMW or not. Foreground uses Foundation instead >>of Bootstrap, here is a good comparison[2]. Each framework has their
The Foreground and Chameleon skin both have dedicated advantages over the Vector skin. The Chameleon skin and its required Bootstrap extension deploy unit tests [0] (I admit I sweet talked Stephan a bit to make it happen) so we are able to run tests over the MW life-cycle to see whether functionality is broken for a recent MW version. The current MW skin infrastructure can not standalone and therefore requires the usage of a specific interface in order to harmonize with MW hence the unit tests to verify that the interface is working as expected. [0] https://travis-ci.org/wikimedia/mediawiki-skins-chameleon Cheers On 10/22/14, Tom Hutchison <t...@hutch4.us> wrote: > > > ------ Forwarded Message ------ > From: "Tom Hutchison" <t...@hutch4.us> > To: "Markus Krötzsch" <mar...@semantic-mediawiki.org> > Sent: 10/21/2014 12:02:10 PM > Subject: Re[2]: [Semediawiki-user] [SMW-devel] smw.org to replace the > "old" Vector skin? > >>On 10/21/2014 3:49:08 AM, "Markus Krötzsch" >><mar...@semantic-mediawiki.org> wrote: >> >>>Hi, >>> >>>On 21.10.2014 03:51, James HK wrote: >>>... >>>> >>>> PS: As far as I understand, the user of smw.org would be able to >>>> switch to the "old" Vector skin as registered user. >>>> >>> >>>Let me come back to this, since this is also important for planning >>>the >>>transition. The key question is: >>> >>> Can we use Bootstrap components independent of Chameleon? >>> >>>To make the in-page content fully responsive, we will need to use a >>>grid >>>framework like the one in Bootstrap. Many other nice components exist >>>(tabs, carousels, etc.). If it is possible to use these with Vector as >>>well as with Chameleon, then the transition is much easier and we >>>could >>>offer both skins alongside each other. >>Of course anything is possible, the question to answer, is it >>practical? There would be a need to add Bootstrap CSS and/or JS to the >>Vector skin. >> >>What is at odds is the design aspect of the page content. "Mobile >>first" is the new catch phrase of today. Vector isn't "mobile first" so >>the two skins will always be at odds with each other from day one. >>Bootstrap 3 is mobile first as compared to Bootstrap 2. There will be a >>need to strike a balance, how far do you take the actual content(wiki >>markup) layout for each skin? DIV containers will have to become the >>norm for wrapping pieces of page content if you want to take advantage >>of mobile responsiveness. Even MW MobileFrontend has this, mf >>selectors. >> >>There is also the issues of MW's core using tables for some of its >>output. SpecialPages isn't to bad since it is 2 columns. Category pages >>are a different story because they output in a 3 column table. Another >>consideration is the HTML sanitizer in MW core. Frameworks require some >>sanitized HTML tags and IMHO MW is behind because the sanitizer is >>stripping out valid, safe HTML5 tags. >> >>I have done a lot of work on the Foreground Skin[0] over the past year. >>Some may know it is already used on WikiApiary[1] using SMW as well >>many other wikis using SMW or not. Foreground uses Foundation instead >>of Bootstrap, here is a good comparison[2]. Each framework has their >>strengths and weaknesses. The biggest weakness both will share, will an >>update cause backward compatibility issues. >> >>Just my thoughts. >> >>Tom >> >> >>[0] https://github.com/thingles/foreground >>[1] https://wikiapiary.com/wiki/Main_Page >>[2] http://responsive.vermilion.com/compare.php > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Semediawiki-devel mailing list > Semediawiki-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
