[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What problem are you trying to solve (was Re: [xsl

Subject: Re: What problem are you trying to solve (was Re: why no indent here)
From: Wolfgang Laun <wolfgang.laun@xxxxxxxxx>
Date: Tue, 13 Dec 2011 07:41:39 +0100
Re:  What problem are you trying to solve (was Re: [xsl
Hi Wendell,

my question was triggered by what I saw and (thought that I) understood
about the Tamara blog effort, the way the XML input is produced. I have
no experience with Symphony or anything similar, but I feel that
it's maintainability and adaptability for multiple backends via
varied XSLT transformations isn't necessary in this case. What else?
Was our user needlessly goaded into using this tool chain?

(Yes, learning a new tool with some relatively simple project is a good
idea, but I don't think that this applies in this case.)

Actually, I  had it on the tip of my fingers to suggest he just write this
thing in HTML, with a sprinkle of CSS, and all his worries soon be over.

Thanks
Wolfgang

On 12/12/2011, Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> wrote:
> Wolfgang,
>
> On 12/12/2011 4:08 AM, Wolfgang Laun wrote:
>> (I'd like to hear some opions from the Wizards on this list: Is it
>> worth doing all this if you can write it in HTML, add a nice CSS and
>> that's it? The "content" isn't going to need much maintenance - at
>> least I can't see it in *this* app. And consider what you have to
>> master either way.)
>
> I dare say it's impossible to answer the question in the general case.
> Generally, there are specific considerations that come into play.
>
> But yeah: if you can solve your problem in CSS and there's no reason to
> do otherwise ... then there's no reason to do otherwise. :-)
>
> Reasons to do otherwise might include because you think it's fun, or you
> are deliberately investing effort in learning.
>
> Yet I agree, if you mean to suggest it's easy to waste effort on
> solutions to problems you don't really have, or which could be dealt
> with much more easily if you defined them differently (as, for example,
> a display problem not a transformation problem).
>
> Cheers,
> Wendell
>
> ======================================================================
> Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
> Mulberry Technologies, Inc.                http://www.mulberrytech.com
> 17 West Jefferson Street                    Direct Phone: 301/315-9635
> Suite 207                                          Phone: 301/315-9631
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
>    Mulberry Technologies: A Consultancy Specializing in SGML and XML
> ======================================================================

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.