tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Reynolds" <mark.reynolds.n...@gmail.com>
Subject Re: 4.1 pretty much finished now
Date Mon, 03 Jul 2006 19:35:31 GMT
Perfect explanation. Thanks!

On 7/3/06, Jesse Kuhnert <jkuhnert@gmail.com> wrote:
>
> I should probably add a new documentation page to the site today to
> address
> these questions. I've been getting enough of them that it will be easier
> for
> me to just do it once. I'll do this later today.
>
> The gist of it is that this release replaces all of the "infrastructure"
> work tacos does, but not necessarily the components themselves. (Except
> maybe the Autocomplete/DatePicker).
>
> For instance, the "AjaxEventSubmit" component has now been replaced with
> the
> @EventListener annotation. They both do the same thing (more or less),
> with
> the EventListener being much more usable and friendly than the former.
> (imho).
>
> I haven't added "effects" or the "AjaxDirectLink" sort of functionality
> yet
> either.
>
> If people wanted a wholesale replacement of tacos it may be best to stick
> with tacos for the time being. It's unclear when a 4.1 compatible version
> of
> it would be available, but unless people are looking for very specific
> "drop
> in" components they may not need to wait.
>
> On 7/3/06, Mark Reynolds <mark.reynolds.name@gmail.com> wrote:
> >
> > Jesse,
> >
> > I am interested in jumping on the bleeding edge. Can you give us a quick
> > idea of what new or modified functionality we will get in going from
> 4.0to
> > 4.1 at this point (I know it incorporates Dojo and makes some
> > infrastructure
> > changes to better support AJAX, but that is a little vague).
> >
> > Also, you mentioned "I'm sure tacos is totally fu-$%ed, but that
> probably
> > won't take very long to fix." So does that mean if we want to start
> > playing
> > around with tacos, we should stay with 4.0 until there is a new snapshot
> > of
> > tacos for 4.1? Or is there tacos-like functionality in 4.1?
> >
> > Thanks for any clarification you can provide.
> >
> > -- Mark R
> >
> > On 7/2/06, Jesse Kuhnert <jkuhnert@gmail.com> wrote:
> > >
> > > Ok. 4.1 is "out" now. At least in snapshot form. With no
> > > documentation...heh.. So, it's out for the few bleeding edge type
> people
> > > at
> > > least.
> > >
> > > I'll be updating documentation more and more indefinitely, saving
> > > component
> > > docs until something gets figured out with tapdoc.
> > >
> > > On 7/2/06, Jesse Kuhnert <jkuhnert@gmail.com> wrote:
> > > >
> > > > Yeah, you were unlucky in timing, sorry about that. The event stuff
> > (aka
> > > > implementing form state management on client side) is in subversion
> > head
> > > now
> > > > so what you were trying to do would probably work great now.
> > > >
> > > > I have a few unit tests to fix before deploying a new snapshot but
> > will
> > > do
> > > > it one at some point today. (not because it's broken, just new
> > > unexpected
> > > > easymock method calls)
> > > >
> > > >
> > > > On 7/2/06, Kevin Menard <kmenard@servprise.com> wrote:
> > > > >
> > > > > On Sun, 02 Jul 2006 11:38:12 -0400, Norbert Sándor <
> > > > > developer@erinors.com>
> > > > > wrote:
> > > > >
> > > > > > How compatible are the 4.0 and 4.1 versions?
> > > > > > Can I just replace the 4.0 jars with the 4.1 ones?
> > > > >
> > > > > I gave 4.1 a whirl and ultimately had to go back to 4.0.2 for the
> > time
> > > > > being.  The form event stuff still needs some TLC.  Additionally,
> > note
> > > > > that a lot of things (all?) that were deprecated in 4.0 are
> removed
> > in
> > > > > 4.1.  So, if you still use the Visit object, for example, that's
> no
> > > > > longer
> > > > > there.
> > > > >
> > > > > All in all, it's not a bad upgrade, but I don't think it's as
> simple
> > > as
> > > > > dropping in the new JARs.
> > > > >
> > > > > --
> > > > > Kevin
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tacos/Tapestry, team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind.
> > > >
> > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tacos/Tapestry, team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind.
> > >
> > >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message