> On Oct 21, 2014, at 3:05 PM, James HK wrote:
>
> The Foreground and Chameleon skin both have dedicated advantages over
> the Vector skin.
I couldn’t agree more with the above statement and I’m excited about this
conversation. I think Semantic MediaWiki adopting a new skin with a modern look
On Oct 21, 2014, at 12:21 PM, Tom Hutchison wrote:
> The biggest weakness both will share, will an update cause backward
> compatibility issues.
As you all think through this skin change I do think it’s worth highlighting
this issue. The traditional idea in MediaWiki of a user choosing their o
On 10/21/2014 3:05:36 PM, "James HK"
wrote:
>Hi,
>
>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
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 Fo
FWIW, I'd see responsiveness as a nice bonus. From the first mail I did not
get the impression that it was a hard requirement.
Regarding the result formats being displayed in a mobile friendly way, I'd
see that as the result format's task. In fact, in particular the examples
on the help pages shou
-- Forwarded Message --
From: "Tom Hutchison"
To: "Markus Krötzsch"
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"
> wrote:
>
>>Hi,
>>
>>On 21.10.2014 03:51, James HK w
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 Bootstr
thanks for the response James, that clears a lot of things up.
I'm aware of coupling issues and wouldn't suggest creating any
dependencies. What I'm trying to say is offering a developed skin could be
a good advantage for users to enhance their sites too. Sites that use SMW
are also part of the pr
Hi,
> I understand SMW is no longer trying to fit into the Wikimedia universe,
> but it still honours the MW approach of edits and source being human
> parseable and benefits from ongoing MW enhancements. And using the same
> skin as Wikipedia immediately lets people know they are on a (real) wiki
Hi all,
Maybe I am running with this, but it would benefit the community to make
these efforts generally reusable.
I understand SMW is no longer trying to fit into the Wikimedia universe,
but it still honours the MW approach of edits and source being human
parseable and benefits from ongoing MW e
On 20.10.2014 09:05, Krabina Bernhard wrote:
> Hi,
>
> regardless of the skin used, I think it's worthwile to have a look at some
> sites we should aim to match regarding their appearance, e. g.
>
> http://www.drupal.org/
> https://wordpress.org/
> http://www.joomla.org/
> https://www.atlassian.co
Hi,
regardless of the skin used, I think it's worthwile to have a look at some
sites we should aim to match regarding their appearance, e. g.
http://www.drupal.org/
https://wordpress.org/
http://www.joomla.org/
https://www.atlassian.com/
cheers,
Bernhard
- Am 17. Okt 2014 um 11:58 schrieb
Could you try
composer require --prefer-dist mediawiki/chameleon-skin "~1.0"
Apparently composer uses download from git by default for development
versions (which are the only available versions of Chameleon right
now).
On 17 October 2014 20:56, Cavila wrote:
> Hi Stephan,
>
> It's step #5, whi
Hi.
On 17 October 2014 16:40, Cavila wrote:
> Would like to try it out, but there's a bug in the installation process (the
> git file from Git cannot be cloned using Composer).
Is that the actual error message (Google did not find it)? And
following the instructions on [1] at what point exactly
One more thing worth considering: The Bootstrap framework is not
designed to support as extensive a range of browsers as Vector. [1]
"Bootstrap is built to work best in the latest desktop and mobile
browsers, meaning older browsers might display differently styled,
though fully functional, renderin
+1 for chameleon
Bernhard
--
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 mobi
Well, I plan to maintain the skin for a while yet, not least because I
use it myself.
I want to finally release a version 1.0 this weekend. Should have done
that a long time ago, but always put it off. There is one major issue
left that I want to fix before, which is the un-responsiveness of the
n
Hi,
Good idea. Chameleon is great (also because of the nice Bootstrap
styling that becomes available on all pages). I am using it right now to
build a site (to be published soon).
A big advantage with Chameleon is that most customizations happen in CSS
or by inserting HTML into the page throug
18 matches
Mail list logo
