Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
When I started working on a attribute template language (ATL)
proposal, it was obvious to me that it should be attribute name
driven. So why did I end up proposing a content driven one? While the
attribute driven is atractive for very simple exampl
> Le 7 déc. 04, à 18:54, Sylvain Wallez a écrit :
> > ...(hearing Stefano coming behind me, ready to shout "FS!!!" in my
> > ears...)
>
> Nahh...his detector exploded yesterday, don't worry.
>
> > ...Now going back to the annotated-HTML-to-XSL compiler that we
> > (Anyware) wrote many years ago
Le 7 déc. 04, à 18:54, Sylvain Wallez a écrit :
...(hearing Stefano coming behind me, ready to shout "FS!!!" in my
ears...)
Nahh...his detector exploded yesterday, don't worry.
...Now going back to the annotated-HTML-to-XSL compiler that we
(Anyware) wrote many years ago, it allows to mix both sy
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
We also need:
- some script compiler directives i.e. for cache control (as in JXTG)
> Seem reasonable, sugest some mechanism.
if we
want the directive to remove element at which it
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
We also need:
- some script compiler directives i.e. for cache control (as in JXTG)
> Seem reasonable, sugest some mechanism.
if we
want the directive to remove element at which it was declare. Or we
co
Daniel Fagerstrom wrote:
When I started working on a attribute template language (ATL)
proposal, it was obvious to me that it should be attribute name
driven. So why did I end up proposing a content driven one? While the
attribute driven is atractive for very simple examples it IMO very
soon b
Vadim Gritsenko wrote:
Daniel Fagerstrom wrote:
Here, I just want to comment that I find way more intuitive and user
friendly following constructs:
if()
--
example:
and
for conditions.
My example should have been:
and I'm ok with
if people want it.
Concerning attribute name v.s. a
Vadim Gritsenko wrote:
for(var=,begin=,end=,step=)
---
Is it necessary? Current jxtg does not have it (IIRC).
it does.
--
Leszek Gawron [EMAIL PROTECTED]
Project ManagerMobileBo
Daniel Fagerstrom wrote:
Just a reminder; before you guys start implementing one or another template
language, could we have [VOTE] for one of the variants, have [PROPOSAL], or at
least [SUMMARY]? :)
Here, I just want to comment that I find way more intuitive and user friendly
following constr
On Dec 5, 2004, at 11:59 AM, Stefano Mazzocchi wrote:
Glen Ezkovich wrote:
On Dec 5, 2004, at 10:02 AM, Daniel Fagerstrom wrote:
Your alarm might have been desensitized by our continuos stream of
FS ;) Actually it would be boring if you were easy to predict.
I really think that it makes sense to
Glen Ezkovich wrote:
On Dec 5, 2004, at 10:02 AM, Daniel Fagerstrom wrote:
Your alarm might have been desensitized by our continuos stream of FS
;) Actually it would be boring if you were easy to predict.
I really think that it makes sense to have two different syntaxes,
one that uses elements a
Daniel Fagerstrom wrote:
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
I like this idea very much. It would be a shame if the quirks of
Dreamweaver should force everyone to use an awkward syntax.
The attribute driven synatax is new to me so I don't know if I find
it awkward or not, I'll need
Leszek Gawron wrote:
Reinhard Poetz wrote:
But the Dreamweaver usecase is a valid one (It was me who started a
discussion about this in May after attenting a Tapestry seminar at a
conference) and so we should support it.
Now, having them cohexist in the page smells like FS, though ;-)
Can't agr
On Dec 5, 2004, at 10:02 AM, Daniel Fagerstrom wrote:
Your alarm might have been desensitized by our continuos stream of FS
;) Actually it would be boring if you were easy to predict.
I really think that it makes sense to have two different syntaxes,
one that uses elements and another one that u
On Dec 5, 2004, at 8:04 AM, Leszek Gawron wrote:
Fine by me. The only concern is the performance here. Macro would have
to be played, output recorded and after that omitTag invoked. I'd
rather do it otherwise.
As is usually, my advice is that unless you know what the performance
hit will be in a
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
We also need:
- some script compiler directives i.e. for cache control (as in JXTG)
> Seem reasonable, sugest some mechanism.
if we
want the directive to remove element at which it was declare. Or we
could pass processing instr
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
I like this idea very much. It would be a shame if the quirks of
Dreamweaver should force everyone to use an awkward syntax.
The attribute driven synatax is new to me so I don't know if I find it
awkward or not, I'll need to see some larger example
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
macro(,,...,)
---
example:
${item}
We also need an evalBody as in JXTG. And maybe we should have a
possibilty to give a name space to the macro name.
We also need:
- some scr
Leszek Gawron wrote:
Reinhard Poetz wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
But the Dreamweaver usecase is a valid one (It was me who started a
discussion about this in May after attenting a Tapestry seminar at a
conference) and so we should support it.
Now, having them cohexist in the
Reinhard Poetz wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
But the Dreamweaver usecase is a valid one (It was me who started a
discussion about this in May after attenting a Tapestry seminar at a
conference) and so we should support it.
Now, having them cohexist in the page smells like FS,
Leszek Gawron wrote:
Reinhard Poetz wrote:
But the Dreamweaver usecase is a valid one (It was me who started a
discussion about this in May after attenting a Tapestry seminar at a
conference) and so we should support it.
Now, having them cohexist in the page smells like FS, though ;-)
Can't agr
Roy G. Biv wrote:
Any prohibition on (non-HTML) namespaced tags would imply to me that
arbitrary namespaced attributes would be a no-no in Dreamweaver as
well. Stefano, as I haven't ever used Dreamweaver for more than ten
minutes, is this limitation a rendering issue or data entry issue? I
qu
Reinhard Poetz wrote:
But the Dreamweaver usecase is a valid one (It was me who started a
discussion about this in May after attenting a Tapestry seminar at a
conference) and so we should support it.
Now, having them cohexist in the page smells like FS, though ;-)
Can't agree more.
What would y
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
I like this idea very much. It would be a shame if the quirks of
Dreamweaver should force everyone to use an awkward syntax.
The attribute driven synatax is new to me so I don't know if I find it
awkward or not, I'll need to see some larger exampl
On Dec 4, 2004, at 11:40 PM, Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
Stefano's focus seem to be on HTML.
For the record: my focus is on having a template language for cocoon
that is as powerful as XSP but avoids all the problems.
Then it won't be as powerful ;-) The power is not needed.
Roy G. Biv wrote:
Stefano Mazzocchi wrote:
For the record: my focus is on having a template language for cocoon
that is as powerful as XSP but avoids all the problems.
Is that realistic? I can see logicsheets, but XSP was arbitrary Java
code. I find it hard to believe that *anything* will be a
Stefano Mazzocchi wrote:
For the record: my focus is on having a template language for cocoon
that is as powerful as XSP but avoids all the problems.
Is that realistic? I can see logicsheets, but XSP was arbitrary Java
code. I find it hard to believe that *anything* will be as
powerful/flexibl
Daniel Fagerstrom wrote:
Stefano's focus seem to be on HTML.
For the record: my focus is on having a template language for cocoon
that is as powerful as XSP but avoids all the problems.
Also, I think that XHTML markup offers the best possible usecase of how
that template language should work.
A
Daniel Fagerstrom wrote:
I like this idea very much. It would be a shame if the quirks of
Dreamweaver should force everyone to use an awkward syntax.
The attribute driven synatax is new to me so I don't know if I find it
awkward or not, I'll need to see some larger examples. Anyway, we have a
use
Roy G. Biv wrote:
Daniel Fagerstrom wrote:
I as well. In addition, I think that the optimum template language
would be as close to the appearance of the output document as possible.
(Yet another reason I don't personally care for explicit forEach, if and
chose elements; they make it harder to
Roy G. Biv wrote:
2. Namespaced tag or attribute: may not be compatible with Dreamweaver
(strikes me as a serious limitation that needs to be addressed by the
Dreamweaver developers IMHO), but can guarantee well-formedness.
Nevermind. Forget I said this. Dreamweaver supports namespaced attribut
Daniel Fagerstrom wrote:
Stefano Mazzocchi wrote:
All I ask from a template language:
1) something that HTML designers can edit with Dreamweaver
2) something that doesn't use namespaced tags to identify dynamic
scopes (clashes with #1)
3) something that doesn't use the name taglib
That's prett
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
macro(,,...,)
---
example:
${item}
We also need an evalBody as in JXTG. And maybe we should have a
possibilty to give a name space to the macro name.
We also need:
- some script compiler directives i.
Jonas Ekstedt wrote:
On Sat, 4 Dec 2004, Daniel Fagerstrom wrote:
snip...
if()
--
example:
Your cart is empty
How would you implement choose/when?
I woudn't, don't think it works that well with Dreamweaver and such
things. You can use a number of if instead. I would also assume that
t
Jonas Ekstedt wrote:
Several directives
--
So, how do we handle multiple directives for one element? We could
handle the TAL example above like:
Ex Text
Isn't there a risk that attribute templates become unreadable?
That is quite true: the attribute value could become lengthy.
Daniel Fagerstrom wrote:
macro(,,...,)
---
example:
${item}
We also need an evalBody as in JXTG. And maybe we should have a
possibilty to give a name space to the macro name.
We also need:
- some script compiler directives i.e. for cache control
On Sat, 4 Dec 2004, Daniel Fagerstrom wrote:
snip...
>
> if()
> --
>
> example:
>
>
>Your cart is empty
>
>
How would you implement choose/when?
snip...
>
> Several directives
> --
>
> So, how do we handle multiple directives for one element? We could
> handle the T
37 matches
Mail list logo
