You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Massimo Lusetti <ml...@gmail.com> on 2006/02/02 15:34:42 UTC
Fwd: Components IDS (was: Tapestry 4.1 AJAX support)
Sorry i mean to send this to the dev list
---------- Forwarded message ----------
From: Massimo Lusetti <ml...@gmail.com>
Date: Feb 2, 2006 12:46 PM
Subject: Components IDS (was: Tapestry 4.1 AJAX support)
To: Tapestry users <ta...@jakarta.apache.org>
I take this portion of Jesse's mail just to put on plate an idea or
simply a feeling I've always had since i migrated from
BarracudaMVC/XMLC to Tapestry
[quote]
-) Component Ids / Form Component Ids - Howard seems to be addressing these
already with some new ideas. It's an incredibly hard problem to solve and I
don't envy him for it, but it's also one huge stumbling block for anything
client js related. I could go on and on in this section, but I think
everyone knows what we are talking about.
[/quote]
Why not approaching to this problem the way XMLC, i mean, using the
DOM structure of the HTML template?
I'll admit I'm not so deep in the tapestry code to fully understand
the whole but i would like to know if any of the developers have taken
this into account, especially now that the rewind phase is in
consideration to be removed.
I'm throwing the stone... and probably I've already asked this
question in the past so please forgive me :)
--
Massimo
http://meridio.blogspot.com
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Components IDS (was: Tapestry 4.1 AJAX support)
Posted by Massimo Lusetti <ml...@gmail.com>.
On 2/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> I have to admit that I don't know what XMLC is, can you give a very brief
> summary ?
Well, XMLC works taking an HTML template file and then generating a
java file containing all the methods to access the tag marked by the
id attrbute, the java objects are mapped with the DOM api, then use
the a DOM writer to write output to the client.
Then in BarracudaMVC (the tool similar to Tapestry) you get some sort
of components (they choose to back up the HTML tags) for you to use
directly or a BTemplate object (which they call pull-MVC) that's used
to parse a DOM as a template and then pull data from a Model and put
them in the DOM, this all driven by directive in a separate file
(something similar in concept to what .page are)
The key here is that all is driven by the DOM tree which use the id of
XHTML/HTML, XML, VoiceXML, WML, CHTML tag element to bind them to
"java"
One (big?) downside note is that to be able to parse the markup
template it should validate against DOM...
I wish to elaborate more with your input.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Components IDS (was: Tapestry 4.1 AJAX support)
Posted by Jesse Kuhnert <jk...@gmail.com>.
I have to admit that I don't know what XMLC is, can you give a very brief
summary ?
On 2/2/06, Massimo Lusetti <ml...@gmail.com> wrote:
>
> Sorry i mean to send this to the dev list
>
>
> ---------- Forwarded message ----------
> From: Massimo Lusetti <ml...@gmail.com>
> Date: Feb 2, 2006 12:46 PM
> Subject: Components IDS (was: Tapestry 4.1 AJAX support)
> To: Tapestry users <ta...@jakarta.apache.org>
>
>
> I take this portion of Jesse's mail just to put on plate an idea or
> simply a feeling I've always had since i migrated from
> BarracudaMVC/XMLC to Tapestry
>
> [quote]
> -) Component Ids / Form Component Ids - Howard seems to be addressing
> these
> already with some new ideas. It's an incredibly hard problem to solve and
> I
> don't envy him for it, but it's also one huge stumbling block for anything
> client js related. I could go on and on in this section, but I think
> everyone knows what we are talking about.
> [/quote]
>
> Why not approaching to this problem the way XMLC, i mean, using the
> DOM structure of the HTML template?
>
> I'll admit I'm not so deep in the tapestry code to fully understand
> the whole but i would like to know if any of the developers have taken
> this into account, especially now that the rewind phase is in
> consideration to be removed.
> I'm throwing the stone... and probably I've already asked this
> question in the past so please forgive me :)
>
> --
> Massimo
> http://meridio.blogspot.com
>
>
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>