Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-06 Thread Cyriaque Dupoirieux
Hi, I think - like Ross - than Views are a very clean solution to many things. My main problem with skins is exactly what you said : * Source code may be duplicated depending on where it is used, * Granularty is complex problem which do not interest skins. The result is that w

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-05 Thread Ross Gardler
Thorsten Scherler wrote: On Sun, 2005-06-05 at 14:37 +0100, Ross Gardler wrote: Thorsten Scherler wrote: ... So I was going to ask you to write a simple How-To on creating a new contract, and then embedding it in my own site. Yeah I can understand that. Did you see whiteboard/plugins/

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-05 Thread Thorsten Scherler
On Sun, 2005-06-05 at 14:37 +0100, Ross Gardler wrote: > Thorsten Scherler wrote: > > hello devs, > > > > I just work on the i18n integration for pelt and crossed again the whys > > for using views. ;-) > > This mail makes for a pretty good piece of documentation. > :) It explains a wee bit bet

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-05 Thread Ross Gardler
Thorsten Scherler wrote: hello devs, I just work on the i18n integration for pelt and crossed again the whys for using views. ;-) This mail makes for a pretty good piece of documentation. A number of times over the last couple of weeks I have wanted to write a mail asking you to write some u

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-05 Thread Thorsten Scherler
On Sat, 2005-06-04 at 21:03 -0700, Diwaker Gupta wrote: > > Yes that would be great. :) That could be the 'last-published-net' > > contract. > > Its funny, I chose the *exact* same name even before I wrote my first mail :) > lol :) Yeah, once started working with views and contracts the naming

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-04 Thread Diwaker Gupta
> Yes that would be great. :) That could be the 'last-published-net' > contract. Its funny, I chose the *exact* same name even before I wrote my first mail :) Anyways, I'm attaching last-published-net.ft. It uses an improved version of the XSL date service (no Perl script!). In addition, if a net

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-04 Thread Thorsten Scherler
On Sat, 2005-06-04 at 19:04 -0700, Diwaker Gupta wrote: > On 6/4/05, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > > > > I had to extend the default.fv with a new line: > > > > to activate the new contract in any place of the output that I want. As > > well it is possible to place the contract a

Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-04 Thread Diwaker Gupta
On 6/4/05, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > > I had to extend the default.fv with a new line: > > to activate the new contract in any place of the output that I want. As > well it is possible to place the contract as much as I want. > > Refactoring site2xhtml.xsl has similarities o

[RT] Why using views - in comparison with "old fashion" skins - usecase i18n.

2005-06-04 Thread Thorsten Scherler
hello devs, I just work on the i18n integration for pelt and crossed again the whys for using views. ;-) The case is that the site2xhtml.xsl has a lot of repeating code. For example the "last publish"-contract can be found 2 times in the code: @@ -236,9 +241,9 @@ + |end Endtabs + -