On 08/12/10 16:31, Trevor Parscal wrote:
> I warned that I would defend XSL with vigor :)
Magnus wrote a wiki to XML converter a few years ago and I hacked up a
small XSLT to convert its output to XHTML:
http://svn.wikimedia.org/viewvc/mediawiki/trunk/parsers/wiki2xml/php/
Look at test.xml & xh
* Trevor Parscal [Wed, 08 Dec 2010 07:31:33
-0800]:
> On 12/7/10 10:46 PM, Dmitriy Sintsov wrote:
> > * Ashar Voultoiz [Tue, 07 Dec 2010 19:19:53
> +0100]:
> >> On 06/12/10 16:57, Trevor Parscal wrote:
> >>> I personally think XSL is awesome, and would defend it with
> >>> vigor.
> >> I love XSL
On 12/7/10 10:46 PM, Dmitriy Sintsov wrote:
> * Ashar Voultoiz [Tue, 07 Dec 2010 19:19:53 +0100]:
>> On 06/12/10 16:57, Trevor Parscal wrote:
>>> I personally think XSL is awesome, and would defend it with
>>> vigor.
>> I love XSL too. Probably the easiest way to render an XML data file.
>>
> It's
On 10-12-07 04:32 PM, Platonides wrote:
> Daniel Friesen wrote:
>
>> On 10-12-07 08:18 AM, Bryan Tong Minh wrote:
>>
>
>
>>> I was first like wtf as well, but on the other hand this way skin
>>> building would be much more accesibles for non-programmer mediawiki
>>> us
* Ashar Voultoiz [Tue, 07 Dec 2010 19:19:53 +0100]:
> On 06/12/10 16:57, Trevor Parscal wrote:
> > I personally think XSL is awesome, and would defend it with
> > vigor.
>
> I love XSL too. Probably the easiest way to render an XML data file.
>
It's easy only when XSL style sheet already exists. E
Daniel Friesen wrote:
> On 10-12-07 08:18 AM, Bryan Tong Minh wrote:
>> I was first like wtf as well, but on the other hand this way skin
>> building would be much more accesibles for non-programmer mediawiki
>> users. Regular wiki users do know wikitext, as opposed to PHP. I'm not
>>
On 10-12-07 10:19 AM, Ashar Voultoiz wrote:
> On 06/12/10 16:57, Trevor Parscal wrote:
>
>> I personally think XSL is awesome, and would defend it with
>> vigor.
>>
> I love XSL too. Probably the easiest way to render an XML data file.
>
> Another approach could be inspired by ruby on rai
On Tue, Dec 7, 2010 at 9:46 AM, Paul Houle wrote:
> I18N is essential if you need to cover multiple linguistic zones.
> If you don't, I18N can increase the cost of making simple changes by a
> factor of 3 to 5.
Not for us, in my experience. The developers just write the stuff
purely in Engl
On 06/12/10 16:57, Trevor Parscal wrote:
> I personally think XSL is awesome, and would defend it with
> vigor.
I love XSL too. Probably the easiest way to render an XML data file.
Another approach could be inspired by ruby on rails way. You define a
general application layout using HTML with s
On 10-12-07 08:18 AM, Bryan Tong Minh wrote:
> On Tue, Dec 7, 2010 at 5:12 PM, Trevor Parscal wrote:
>
>> Oh please no!
>>
>> - Trevor
>>
>> On 12/7/10 7:26 AM, Platonides wrote:
>>
>>> Daniel Friesen wrote:
>>>
PHP ->XSL doesn't quite feel like much of an improvement in
On Tue, Dec 7, 2010 at 5:12 PM, Trevor Parscal wrote:
> Oh please no!
>
> - Trevor
>
> On 12/7/10 7:26 AM, Platonides wrote:
>> Daniel Friesen wrote:
>>> PHP -> XSL doesn't quite feel like much of an improvement in terms of
>>> cutting down on the verbose redundant code boilerplate required to
>>
Oh please no!
- Trevor
On 12/7/10 7:26 AM, Platonides wrote:
> Daniel Friesen wrote:
>> PHP -> XSL doesn't quite feel like much of an improvement in terms of
>> cutting down on the verbose redundant code boilerplate required to
>> insert something.
>> ie: doesn't look much better than> $this->t
Bryan Tong Minh wrote:
> On Tue, Dec 7, 2010 at 4:26 PM, Platonides wrote:
>> Daniel Friesen wrote:
>>> PHP -> XSL doesn't quite feel like much of an improvement in terms of
>>> cutting down on the verbose redundant code boilerplate required to
>>> insert something.
>>> ie: doesn't look much bett
On Tue, Dec 7, 2010 at 4:26 PM, Platonides wrote:
> Daniel Friesen wrote:
>> PHP -> XSL doesn't quite feel like much of an improvement in terms of
>> cutting down on the verbose redundant code boilerplate required to
>> insert something.
>> ie: doesn't look much better than > $this->text("title")
Daniel Friesen wrote:
> PHP -> XSL doesn't quite feel like much of an improvement in terms of
> cutting down on the verbose redundant code boilerplate required to
> insert something.
> ie: doesn't look much better than $this->text("title") ?>, as opposed to {$title|escape:html}.
This seems an
On 12/7/2010 2:23 AM, Daniel Friesen wrote:
> One thing our skin system "does" have is an extensive linker and system
> for building tooltips and accesskeys for things using our i18n system.
> And calls to the message system from skins are all over the place:
> tagline, jumpto, and basically ever
skin->tooltipAndAccesskey( 'search-go' ); ?> />
One thing our skin system "does" have is an extensive linker and system
for building tooltips and accesskeys for things using our i18n system.
And calls to the message system from skins are all over the place:
tagline, jumpto, and basically ever
* Daniel Friesen [Mon, 06 Dec 2010 08:13:04
-0800]:
> PHP -> XSL doesn't quite feel like much of an improvement in terms of
> cutting down on the verbose redundant code boilerplate required to
> insert something.
> ie: doesn't look much better than $this->text("title") ?>, as opposed to {$title
Fair enough, but when I've pushed for using PHP as a template language,
even with a clever wrapper that would make injected data escaped by
default (so unescaping was obvious and could be more easily scrutinized
for XSS) I have been met with about equal resistance.
The state of things is that u
PHP -> XSL doesn't quite feel like much of an improvement in terms of
cutting down on the verbose redundant code boilerplate required to
insert something.
ie: doesn't look much better than text("title") ?>, as opposed to {$title|escape:html}.
And I'm not sure how XSL handles html vs. text, we ha
Have you considered using something like say XSL? If a skin was a
combination of a set of CSS/JS/image files plus an XSL file which took
XML data (which would be the page content and various user interface
elements) then you could avoid using a whole new template system. PHP 5
has an XSL 1.0 li
Perhaps I should commit what I have so far even though it's not quite
ready for use yet.
It's enough to do this so far:
http://testwiki.new.wiki-tools.com/index.php?title=Main_Page&useskin=testskin
((this runs off that ported monobook template I put in the pastie))
Right now I'm using smarty's
This is a really awesome project, I'm sure we can figure out a way for
Vector and Monobook to be able to use the same arrays.
Let me know if you want some help.
- Trevor
On 12/2/10 6:30 PM, Daniel Friesen wrote:
> On 10-12-02 04:52 PM, Platonides wrote:
>> Aryeh Gregor wrote:
>>
>>> On Thu, Dec
2010/12/2 Paul Houle
>
> Of all the code I've seen, the Mediawiki code seems to be one of
> the most difficult code bases to make simple changes in.
I'm absolutely not a programmer (probably my profile is much more similar
to someone
"who should never be allowed anywhere near a computer")
On 10-12-02 04:52 PM, Platonides wrote:
> Aryeh Gregor wrote:
>
>> On Thu, Dec 2, 2010 at 5:17 PM, Paul Houle wrote:
>>
>>> Of all the code I've seen, the Mediawiki code seems to be one of
>>> the most difficult code bases to make simple changes in. When I had to
>>> change the te
On 12/2/10 10:35 AM, Trevor Parscal wrote:
> +1
>
> Cheap hallway testing is so incredibly useful that I dedicated my time
> in Berlin last year to giving a crash course in it. I am not sure it was
> effective in inspiring or educating people on how to do this, but
> everyone is welcome to revisit
Aryeh Gregor wrote:
> On Thu, Dec 2, 2010 at 5:17 PM, Paul Houle wrote:
>> Of all the code I've seen, the Mediawiki code seems to be one of
>> the most difficult code bases to make simple changes in. When I had to
>> change the template of a mediawiki once, the easiest answer I found was
>>
Neil Kandalgaonkar wrote:
>
> Like, there's a thread over on Commons Village Pump right now about how
> to change certain strings that are hardcoded into the upload process.
> Apparently this kind of bug lasts for years rather than five minutes,
> just because the people who are most exercised
On Thu, Dec 2, 2010 at 5:17 PM, Paul Houle wrote:
> Of all the code I've seen, the Mediawiki code seems to be one of
> the most difficult code bases to make simple changes in. When I had to
> change the template of a mediawiki once, the easiest answer I found was
> to put a proxy server in
On 12/2/2010 2:48 PM, Neil Kandalgaonkar wrote:
> Like, there's a thread over on Commons Village Pump right now about how
> to change certain strings that are hardcoded into the upload process.
> Apparently this kind of bug lasts for years rather than five minutes,
> just because the people who a
On 12/2/10 11:05 AM, Arthur Richards wrote:
> As a predominantly back-end developer, it's become clear to me over the
> last few years that usability is not just a front-end concern. 'Users'
> don't necessarily only interact with the 'front end'. Particularly in
> an open-source paradigm, 'users
I'd like to +1 all of this, particularly Trevor's thoughts on
developer-testing APIs - or software that is otherwise meant to be
extended/used by other developers.
As a predominantly back-end developer, it's become clear to me over the
last few years that usability is not just a front-end conce
+1
Cheap hallway testing is so incredibly useful that I dedicated my time
in Berlin last year to giving a crash course in it. I am not sure it was
effective in inspiring or educating people on how to do this, but
everyone is welcome to revisit the slides here:
http://wikitech.wikimedia.org/ind
Hi there -- I don't post much here, but I was the programmer on the
Multimedia Usability Project, which primarily focused on making uploads
easier. The outside funding for that project just ended, so I think it's
a good time to talk about what (if anything) we will do in the future
along these
34 matches
Mail list logo
