Hi Jesse, sorry to press on more on this, even more while you're so commited
to turning this Alpha to a Beta candidate! ;-)
I have just arrived after 2 months without internet access and my, things
have evolved! :-D
I'm simply marveled with the EventListener... it's a must have for my Ajax
(dojo) intense web application I'm building.
I have build a component lib that basicly encapsulates several Tacos
components and a few new of my own as the base fot the UI of this
application.
I'm eager to start using the T4.1 ASAP, mainly because of the EventListener
annotation, but my question is, will the old Tacos lib work in T4.1?
Can we have a working hybrid of T4.0 + Tacos / T4.1 app? I could refactor
and/or reimplement my component lib on-demand as the new features would
arrive and new functionallity was added if this is possible but with the
majoraty of the code unchanged and all my components working, yes?
Must confess I haven't read throught the full T4.1 docs yet, mainlly I have
read several posts here on the matter and a few links to the docs, but I was
looking to a GOD NO, it is not possible, or, it could work with a few
changes kind of push down the right direction.
Thanks and keep up the good work!
On 8/3/06, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Oh what a familiar theme we weave
I wasn't very happy with the way we had to do certain things in tacos the
first time around, so I'm trying as much as possible to not let myself
apply tacos to Tapestry as much as possible.
That being said, I have added a few key services which tacos could very
easily use to replace the core functionality aspects of things.
Generally speaking I tried to make the tacos components act/look as much
like their Tapestry counterparts to help ease the learning curve when
going
from Tapestry - Tacos, so I think the same will be true when going from
Tacos - Tapestry.
AjaxEventSubmit is a very powerful/nice component, but I've always
considered it an abomination in terms of design. I'm much happier with
@EventListener.
I'm still not sure I like the idea of the standard parameter set
updateComponents/effects/etc but we'll see. Maybe there really isn't
going
to be a clear and victorious winner for these things.
Like I said in a previous posting though, I've only laid down the internal
support necessary to do these things so far. ..Now is more the time for
component developers/users of tacos to start thinking about how they've
been
doing things so far and what might make things feel/seem more intuitive.
I think EventListener is really the only official new thing that I'm
happy
with the design of. (leaving out effects/what to update/etc on purpose)
Either way the end result can't be too radical(for T4 at least ;) ). It
should hopefully be based on existing concepts/tasks that every day
Tapestry
users go through with simple extensions of those concepts where it makes
sense. (and with minimal effort/typing..I hate typing)
On 8/2/06, Karthik N [EMAIL PROTECTED] wrote:
I'm also very keen to know the answer to this.
Considering that Tap 4.1 is round-the-corner, we're wondering whether
to
go ahead and use Tacos in our projects, and be able to refactor then
with
minimal effort when they become a part of Tapestry 4.1? Also any Tacos
components that might get deprecated?
Essentially we want to make our applications 4.1 friendly ...
Any pointers/answers would be of most help! Thanks!!
On 8/2/06, Murthy Parthasarathi [EMAIL PROTECTED] wrote:
Hi All.
If I have a Tapestry 4.0 application, that uses Tacos, what
will
be
the effort involved in moving this app to Tapestry 4.1? Are Tacos
components going to be available as-is, or will there be a lot of
changes needed to the existing components?
i.e. Should we limit ourselves from not using Tacos in 4.1?
Cheers
Murthy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Thanks, Karthik
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
--
Pedro Viegas
