- Original Message -
From: "Hunsberger, Peter" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 22, 2002 4:47 PM
Subject: RE: XSP Best Practise Question
> > As you've noted a lot of examples, and suggested solutions to problems
> As you've noted a lot of examples, and suggested solutions to problems
posted
> to this list, use an alternate approach: the generators present data to
the
> pipeline which uses Transformers and Actions to do often complex
operations.
> The data itself is often wrapped in a page markup language
>The XSP below mixes content and presentation, and if it
>contained sections it would be even worse, mixing content, logic and
>presentation.
On this point specifically, I'd consider it a best practice to have *all* logic
moved into a logicsheet so that you're left only with your own custom t
kham
> -Original Message-
> From: Michael Edge [mailto:[EMAIL PROTECTED]]
> Sent: 22 August 2002 10:20
> To: [EMAIL PROTECTED]
> Subject: XSP Best Practise Question
>
>
>
> Hi All
>
> I have a question regarding the use and purpose of XSP. I believe that XSP
Michael,
The _main_ reason that the example XSP operates in this manner
is, quite simply, *because* it's example. The best method _is_
as you describe, but that would add extra overhead to the example
which would hide what the example is actually trying to show.
J.
===
Hi All
I have a question regarding the use and purpose of XSP. I believe that XSP is an
attempt to separate content/logic from presentation, and I believe it's possible to
use it in this way. However, in many of the samples (such as results-dept.xsp below,
found in the tutorial) XSP is used
