DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 7 of 7

Thread: XSLT for web interface, what's your opinion

  1. #1
    andy Guest

    XSLT for web interface, what's your opinion


    I think XSLT is great for transforming xml to whatever, but is it really good
    for building web application front ends? With ASP.NET making front end development
    a breeze, why even consider XSLT for anything beyond transforming xml to
    static content (html)?

    What are your thoughts

  2. #2
    Michael Gautier Guest

    Re: XSLT for web interface, what's your opinion

    I had the exact same thought as you did (off and on over the past 2 years)
    and here is what I concluded:

    When using ASP.NET, use ASP.NET fully: It is just too rich and deterministic
    to do anything outside of the server controls. Of course you have the Xml
    Control where you can 'target' the placement of Xsl's. Perhaps the answer
    here relies on how much Xml you use in the application. You can move
    granularly from the robust, highly functional and debuggable framework to
    the general processing facilities in Xsl as needed.




    "andy" <adeanjs@hotmail.com> wrote in message
    news:3dad728a$1@tnews.web.devx.com...
    >
    > I think XSLT is great for transforming xml to whatever, but is it really

    good
    > for building web application front ends? With ASP.NET making front end

    development
    > a breeze, why even consider XSLT for anything beyond transforming xml to
    > static content (html)?
    >
    > What are your thoughts




  3. #3
    Joe Shawfield Guest

    Re: XSLT for web interface, what's your opinion


    I think that for sites that are constantly being updated or sites that make
    heavy use of "portal-like" sections are a perfect fit. I think the XSL transformations
    really just replace some procedural code that would do the same thing. With
    XSL however, it is easer to maintain... ie no recompile. XSL is more natural
    for looping through stuff and wraping it in other stuff like HTML.




    "andy" <adeanjs@hotmail.com> wrote:
    >
    >I think XSLT is great for transforming xml to whatever, but is it really

    good
    >for building web application front ends? With ASP.NET making front end

    development
    >a breeze, why even consider XSLT for anything beyond transforming xml to
    >static content (html)?
    >
    >What are your thoughts



  4. #4
    Dorothy Hoskins Guest

    Re: XSLT for web interface, what's your opinion


    "Joe Shawfield" <joe@shawfield.com> wrote:
    >XSL however, it is easer to maintain... ie no recompile. XSL is more natural
    >for looping through stuff and wraping it in other stuff like HTML.


    What i like about XSL is being able to modify the look of the ouput HTML
    in conjunction with CSS. I use XSL for sort/order and other data-manipulation
    type effects, and CSS for styling the output fonts, colors, etc. Also in
    some cases, you can develop XSL/CSS independently of the database backend,
    just agree on the XML structure of the output. Then you can develop web look
    and feel while someone else develops the database connection, query strings,
    etc. This made it very fast to create (and modify the visual representation
    as needed) a client-side XSL transform of the XML returned from a db query
    to an Oracle DB, for example.

    BTW, Kurt Cagle has an interesting chapter on modular XSL development in
    Porfessional XSL from WROX Press, check that out.

    I don't do .Net, just XML/XSL. My 2 cents for what it's worth.
    Dorothy

  5. #5
    MarkN Guest

    Re: XSLT for web interface, what's your opinion


    I think they should be used wisely. I haven't personally done a lot with
    XS*, but I am finishing up doing some things on a project that uses it alot
    along with a mixture of asp and html. Comparing what a was done there with
    an OO UI - I would rather deal with the issues of applets or something like
    that for business GUIs or use ASP.Net or Echo (for Java).

    It probably is fine for just displaying 'data' but still introduces issues
    if one needs to externalize labels, etc. A good tool and framework (I think
    someone mention this) will go along way to alleviate most of these issues.



    "andy" <adeanjs@hotmail.com> wrote:
    >
    >I think XSLT is great for transforming xml to whatever, but is it really

    good
    >for building web application front ends? With ASP.NET making front end

    development
    >a breeze, why even consider XSLT for anything beyond transforming xml to
    >static content (html)?
    >
    >What are your thoughts



  6. #6
    al butler Guest

    Re: XSLT for web interface, what's your opinion




    Dorothy hit it right on the nose and not many have got it.
    I have 2 apps out in the real world based on XML-XSL, with IE as the
    calling device.

    The best thing about XSLT is that you can farm out portions of the
    interface to other developers WITHOUT the need of a server, just simply
    give them the XML, the look and feel of what needs to be done and a good
    XML tool like XMLSpy or eXelon Stylus Studio.

    And upkeep is great. You got a bug, fix it in the stylesheet and drop it
    in the directory where it belongs.

    al


    "andy" <adeanjs@hotmail.com> wrote:
    >
    >I think XSLT is great for transforming xml to whatever, but is it really

    good
    >for building web application front ends? With ASP.NET making front end

    development
    >a breeze, why even consider XSLT for anything beyond transforming xml to
    >static content (html)?
    >
    >What are your thoughts



  7. #7
    Andrew \(BTClick\) Guest

    Re: XSLT for web interface, what's your opinion

    The two key points I think are:

    1) using XSLT allows a clean division of labour between developers and
    designers (as already
    mentioned by dorothy)
    2) XSLT is portable, as it adheres to publically defined standards. If i
    write an XSLT sheet i know
    i can use it in ASP/PHP/ASP.NET etc. - all i need to change for each
    development environment
    is the call to the transform function (MSXML/Sablotron etc.)... this is
    very useful when porting
    web applications between different platforms.

    "andy" <adeanjs@hotmail.com> wrote in message
    news:3dad728a$1@tnews.web.devx.com...
    >
    > I think XSLT is great for transforming xml to whatever, but is it really

    good
    > for building web application front ends? With ASP.NET making front end

    development
    > a breeze, why even consider XSLT for anything beyond transforming xml to
    > static content (html)?
    >
    > What are your thoughts




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center