Sorry i mean to send this to the dev list
---------- Forwarded message ---------- From: Massimo Lusetti <[EMAIL PROTECTED]> Date: Feb 2, 2006 12:46 PM Subject: Components IDS (was: Tapestry 4.1 AJAX support) To: Tapestry users <[email protected]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
