Vadim Gritsenko wrote:
for(var=name,begin=expr,end=expr,step=expr)
---
Is it necessary? Current jxtg does not have it (IIRC).
it does.
--
Leszek Gawron [EMAIL PROTECTED]
Project Manager
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
On Dec 4, 2004, at 10:52 PM, Stefano Mazzocchi wrote:
Glen,
I don't think we are talking about very different things.
I know.
I *completely* agree with you that the power of pipelines and SoC is
exactly that: change one file and make all the others adjust. Damn,
there wouldn't be a cocoon if
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
Stefano Mazzocchi wrote:
snip/
Still, CSS is not enough because is not able to change the layout of
things and, even worse, sometimes the style dictates the markup
(example: if you want to use stuff like rounded boxes).
OT
For rounded corners at tabs you can use :before and :after pseudo
Daniel Fagerstrom wrote:
Stefano Mazzocchi wrote:
snip/
Still, CSS is not enough because is not able to change the layout of
things and, even worse, sometimes the style dictates the markup
(example: if you want to use stuff like rounded boxes).
OT
For rounded corners at tabs you can use :before
Roy G. Biv wrote:
Daniel Fagerstrom wrote:
Stefano Mazzocchi wrote:
snip/
Still, CSS is not enough because is not able to change the layout of
things and, even worse, sometimes the style dictates the markup
(example: if you want to use stuff like rounded boxes).
OT
For rounded corners at tabs
Daniel Fagerstrom wrote:
Stefano Mazzocchi wrote:
snip/
Still, CSS is not enough because is not able to change the layout of
things and, even worse, sometimes the style dictates the markup
(example: if you want to use stuff like rounded boxes).
OT
For rounded corners at tabs you can use :before
Le 3 déc. 04, à 22:35, Christian Stocker a écrit :
On 3.12.2004 21:50 Uhr, 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)
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 pretty much all you have to
Antonio Gallardo wrote:
On Vie, 3 de Diciembre de 2004, 15:35, Tony Collen dijo:
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)
Bertrand Delacretaz wrote:
snip/
I think we need
a) data templates (for a lack of a better word), to generate XML out
of data (what JXTG does now),
and
b) presentation templates downstream to convert the XML to HTML or
other presentation markup (currently covered by XSLT, far from ideal)
- oo
Le 4 déc. 04, à 14:14, Daniel Fagerstrom a écrit :
Bertrand Delacretaz wrote:
...b) presentation templates downstream to convert the XML to HTML
or other presentation markup (currently covered by XSLT, far from
ideal)
...For b), being dreamweaver-compatible would be a big plus, allowing
less
On Sab, 4 de Diciembre de 2004, 6:58, Daniel Fagerstrom dijo:
Antonio Gallardo wrote:
On Vie, 3 de Diciembre de 2004, 15:35, Tony Collen dijo:
Stefano Mazzocchi wrote:
All I ask from a template language:
1) something that HTML designers can edit with Dreamweaver
2) something that doesn't
Le 4 déc. 04, à 16:56, Antonio Gallardo a écrit :
...I think is better to extend what we have instead of defining a new
language. We need to consolidate things while I understand is good to
have
a new research areas. So in anycase the JXTG refactoring is a must...
I'd say keeping JXTG alive is a
On Sab, 4 de Diciembre de 2004, 10:03, Bertrand Delacretaz dijo:
Le 4 déc. 04, à 16:56, Antonio Gallardo a écrit :
...I think is better to extend what we have instead of defining a new
language. We need to consolidate things while I understand is good to
have
a new research areas. So in
Bertrand Delacretaz wrote:
Le 4 déc. 04, à 14:14, Daniel Fagerstrom a écrit :
Bertrand Delacretaz wrote:
...b) presentation templates downstream to convert the XML to HTML
or other presentation markup (currently covered by XSLT, far from ideal)
...For b), being dreamweaver-compatible would be a
On Sat, 4 Dec 2004, Antonio Gallardo wrote:
snip...
I agree. Anyway, we (in Cocoon) have a current user base using JXTG that
we cannot forget. If is necesary, I can do that. Some months ago, I spend
a week understanding how the JXTG works. While I don't consider myself an
expert. I thing we
On Sat, 4 Dec 2004, Daniel Fagerstrom wrote:
snip...
if(test)
--
example:
div do=if(count(cart/item) == 0)
Your cart is empty
div
How would you implement choose/when?
snip...
Several directives
--
So, how do we handle multiple directives for one
Daniel Fagerstrom wrote:
macro(name,param-name,...,param-name)
---
example:
table do=macro(mytable,list,td-class)
tr do=forEach($list)
td class=${$class}${item}/td
/tr
/table
We also need an evalBody as in JXTG. And maybe we should have a
possibilty
On Sat, Dec 04, 2004 at 09:37:10AM +0100, Bertrand Delacretaz wrote:
For b), being dreamweaver-compatible would be a big plus, allowing less
technical people to create templates themselves. Using Dreamweaver or
not, that's not the point: DW-compatibility also means that the
templating
Le 4 déc. 04, à 18:56, Stefano Mazzocchi a écrit :
Bertrand Delacretaz wrote:
...I think we need
a) data templates (for a lack of a better word), to generate XML
out of data (what JXTG does now),
and
b) presentation templates downstream to convert the XML to HTML or
other presentation markup
Jonas Ekstedt wrote:
Several directives
--
So, how do we handle multiple directives for one element? We could
handle the TAL example above like:
p
do=let(x=/a/long/path/from/the/root;if(x);content(x/txt);attributes(class=x/class)
Ex Text
/p
Isn't there a risk that attribute
Bertrand Delacretaz wrote:
Le 4 déc. 04, à 16:56, Antonio Gallardo a écrit :
...I think is better to extend what we have instead of defining a new
language. We need to consolidate things while I understand is good to
have
a new research areas. So in anycase the JXTG refactoring is a must...
I'd
On Sunday 05 December 2004 02:00, Tim Larson wrote:
Perhaps I am not the only person on this list that has never
used DreamWeaver...
DreamWeaver is loved by many page designers as it manages the various
resources and on-page placements well (seen from the eye of the designer).
The concept is
Tim Larson wrote:
On Sat, Dec 04, 2004 at 09:37:10AM +0100, Bertrand Delacretaz wrote:
For b), being dreamweaver-compatible would be a big plus, allowing less
technical people to create templates themselves. Using Dreamweaver or
not, that's not the point: DW-compatibility also means that the
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
On Dec 3, 2004, at 3:33 PM, Ralph Goers wrote:
Glen Ezkovich said:
On Dec 3, 2004, at 2:50 PM, Stefano Mazzocchi wrote:
All I ask from a template language:
1) something that HTML designers can edit with Dreamweaver
Why? I really don't want HTML designers touching my templates. I want
them to work
Daniel Fagerstrom wrote:
And it might make a big difference, from the users point of view, by
making it possible to use a single tool for the whole presentation
pipeline, and making presentation templates way easier than raw XSLT,
which is a major stumbling block for many people.
We might want
Stefano Mazzocchi wrote:
What we need is a template language. Period. Something that converts
data *structures* into SAX events. Whether you use it for data or
presentation or whatever else, it's up to you.
Once again, it looks like I should have just read all the comments
before replying
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
Roy G. Biv wrote:
Daniel Fagerstrom wrote:
snip/
You're right no need to optimize until we know if it is needed. AFAICS
the only reasonable way of accessing the XML input is things like
XPath that in general need access to the complete XML-tree. And in
that case we can reuse XSLT processor
Glen Ezkovich wrote:
On Dec 3, 2004, at 3:33 PM, Ralph Goers wrote:
Glen Ezkovich said:
On Dec 3, 2004, at 2:50 PM, Stefano Mazzocchi wrote:
All I ask from a template language:
1) something that HTML designers can edit with Dreamweaver
Why? I really don't want HTML designers touching my
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 pretty much all you have to do to make me happy.
--
On Dec 3, 2004, at 2:50 PM, Stefano Mazzocchi wrote:
All I ask from a template language:
1) something that HTML designers can edit with Dreamweaver
Why? I really don't want HTML designers touching my templates. I want
them to work withe the data received from my generator and transform
that
What's the closest equivalent to what you have in mind :)
-- dims
On Fri, 03 Dec 2004 15:50:30 -0500, Stefano Mazzocchi
[EMAIL PROTECTED] 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
Glen Ezkovich said:
On Dec 3, 2004, at 2:50 PM, Stefano Mazzocchi wrote:
All I ask from a template language:
1) something that HTML designers can edit with Dreamweaver
Why? I really don't want HTML designers touching my templates. I want
them to work withe the data received from my
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 pretty much all you have to
On 3.12.2004 21:50 Uhr, 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
On Vie, 3 de Diciembre de 2004, 15:35, Tony Collen dijo:
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
Antonio Gallardo wrote:
On Vie, 3 de Diciembre de 2004, 15:35, Tony Collen dijo:
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
On Vie, 3 de Diciembre de 2004, 16:44, Upayavira dijo:
That might help in the short term. But there's something special that
happens in Cocoon - it has happened with flow, then CForms, but hasn't
happened with JXTemplate. When everyone rounds on a technology, and
thoroughly backs it. And that
42 matches
Mail list logo
