With a well-designed set of transformation, you won't have to update
every one of your stylesheets for a single attribute change. For
instance, I use the xsl:copy tag to simply copy as-is any element that
I'm not interested in doing something with in a particular stylesheet.
On Thursday, Decemb
Steven Noels dijo:
> Kasper Nielsen wrote:
>
>> For a short synopsis at school I'm looking for points to areas where
>> cocoon and stacking an endlessly number of XSL transformers on top of
>> each other falls short. You know stuff like how difficult it is adding
>> a new attribute to an XML elemen
On Thu, 12 Dec 2002, Alex McLintock wrote:
> Why did you chuckle? As a member of the London perl mongers group (I drink
> with them and waffle on the mailing list) I know a large number of people
> happy to work with Mason.
Well, I know exactly nothing about Mason itself, but perhaps the title of
At 16:02 12/12/02, Tony Collen wrote:
On a side note, I chuckled to myself when I saw this book in the store:
http://www.oreilly.com/catalog/perlhtmlmason/
I think it helped me appreciated what Cocoon does just a little bit more
:)
Why did you chuckle? As a member of the London perl mongers g
On a side note, I chuckled to myself when I saw this book in the store:
http://www.oreilly.com/catalog/perlhtmlmason/
I think it helped me appreciated what Cocoon does just a little bit more
:)
Tony
Tony Collen -- [EMAIL PROTECTED]
College of Liberal Arts University of Minnesota, Minneapo
PROTECTED]]
Sent: Thursday, December 12, 2002 7:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Why cocoon sucks
- Original Message -
From: "Chris Faulkner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 12, 2002 12:56 PM
Subject: Re: Why cocoon sucks
I agree with Chris. In every language you can create a mess.
Two rules of advice for Kasper on programming:
1) Be a lazy coder. Think first how you can write as few lines of code as
possible. Not only will you have effecient code, you'll have code that you
can maintain.
2) Stop using copy & p
Kasper Nielsen wrote:
For a short synopsis at school I'm looking for points to areas where cocoon
and stacking an endlessly number of XSL transformers on top of each other
falls short. You know stuff like how difficult it is adding a new attribute
to an XML element, and make sure it's copied alon
- Original Message -
From: "Chris Faulkner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 12, 2002 12:56 PM
Subject: Re: Why cocoon sucks
>
> >
> >For a short synopsis at school I'm looking for points to areas where
coc
>
>For a short synopsis at school I'm looking for points to areas where cocoon
>and stacking an endlessly number of XSL transformers on top of each other
>falls short. You know stuff like how difficult it is adding a new attribute
>to an XML element, and make sure it's copied along in all your 200
Okay this is a question not a statement!
For a short synopsis at school I'm looking for points to areas where cocoon
and stacking an endlessly number of XSL transformers on top of each other
falls short. You know stuff like how difficult it is adding a new attribute
to an XML element, and make s
11 matches
Mail list logo
