4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

Validation is finally done, and I'm going to add the necessary logic to
dynamically add form components today. Does anyone care how I do this?

I was thinking that initially I'd make the 4.1 snapshot build availability a
little more prominent, followed by a continuous cycle of documentation/4.1
snapshot updates as more and more people start trying it out and find
issues/things they need to do what they want.

After it feels like people are more or less able to do the basic things and
not have everything blow up (there shouldn't be too much blowing up, unit
tests cover everything in the browser + server) I'd make an official
4.1release followed by more cycles/updates until we can mark it
"stable/final"
?

-- 
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.

Re: 4.1 pretty much finished now

[Norbert Sándor <de...@erinors.com>]

Currently I'm very close to a project deadline, so please don't expect 
more progress on TapDoc in the following 1-2 weeks.
After then I will convert all my running Tapestry projects to maven, so 
I will need a plugin for it too :)

Regards,
Norbi

Jesse Kuhnert wrote:
> There are no component docs for 4.1 yet, as was stated in a previous 
> email
> in this very thread.
>
> Maintaining component documentation hasn't been a very fun experience 
> thus
> far so I'm planning on trying to use TapDoc if I can. Probably need to 
> wrap
> it with a maven plugin to make it friendlier with our build.
>
> Most of the changes involved aren't centered around any one particular
> component though, it's all infrastructure and global behaviour. I'll
> probably be concentrating on providing documentation oriented around the
> current users guide, a new hivemind services section, etc...I hope 
> Norbert
> is ready for all of my user requests/needs :)
>
> On 7/2/06, James Carman <ja...@carmanconsulting.com> wrote:
>>
>> Where are the component docs for 4.1?  I don't see them on the new site.
>> I'd like to see if I can use 4.1 on my project and replace Tacos.
>>
>> -----Original Message-----
>> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
>> Sent: Sunday, July 02, 2006 11:46 AM
>> To: Tapestry development
>> Subject: Re: 4.1 pretty much finished now
>>
>> Yeah, I think so..We'll see what happens with client side validation. 
>> That
>> portion will depend on how much people have customized things there. At
>> least now the client side validates as much as the server side does. (in
>> that min/max date validate, min/max numbers validate, required clauses
>> work
>> on all fields / etc...)
>>
>> I'm sure tacos is totally fu-$%ed, but that probably won't take very 
>> long
>> to
>> fix.
>>
>> On 7/2/06, Norbert Sándor <de...@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?
>> >
>> > Thanks,
>> > Norbi
>> >
>> > Jesse Kuhnert wrote:
>> > > Validation is finally done, and I'm going to add the necessary logic
>> to
>> > > dynamically add form components today. Does anyone care how I do 
>> this?
>> > >
>> > > I was thinking that initially I'd make the 4.1 snapshot build
>> > > availability a
>> > > little more prominent, followed by a continuous cycle of
>> > > documentation/4.1
>> > > snapshot updates as more and more people start trying it out and 
>> find
>> > > issues/things they need to do what they want.
>> > >
>> > > After it feels like people are more or less able to do the basic
>> > > things and
>> > > not have everything blow up (there shouldn't be too much blowing up,
>> > unit
>> > > tests cover everything in the browser + server) I'd make an official
>> > > 4.1release followed by more cycles/updates until we can mark it
>> > > "stable/final"
>> > > ?
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > 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.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

There are no component docs for 4.1 yet, as was stated in a previous email
in this very thread.

Maintaining component documentation hasn't been a very fun experience thus
far so I'm planning on trying to use TapDoc if I can. Probably need to wrap
it with a maven plugin to make it friendlier with our build.

Most of the changes involved aren't centered around any one particular
component though, it's all infrastructure and global behaviour. I'll
probably be concentrating on providing documentation oriented around the
current users guide, a new hivemind services section, etc...I hope Norbert
is ready for all of my user requests/needs :)

On 7/2/06, James Carman <ja...@carmanconsulting.com> wrote:
>
> Where are the component docs for 4.1?  I don't see them on the new site.
> I'd like to see if I can use 4.1 on my project and replace Tacos.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Sunday, July 02, 2006 11:46 AM
> To: Tapestry development
> Subject: Re: 4.1 pretty much finished now
>
> Yeah, I think so..We'll see what happens with client side validation. That
> portion will depend on how much people have customized things there. At
> least now the client side validates as much as the server side does. (in
> that min/max date validate, min/max numbers validate, required clauses
> work
> on all fields / etc...)
>
> I'm sure tacos is totally fu-$%ed, but that probably won't take very long
> to
> fix.
>
> On 7/2/06, Norbert Sándor <de...@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?
> >
> > Thanks,
> > Norbi
> >
> > Jesse Kuhnert wrote:
> > > Validation is finally done, and I'm going to add the necessary logic
> to
> > > dynamically add form components today. Does anyone care how I do this?
> > >
> > > I was thinking that initially I'd make the 4.1 snapshot build
> > > availability a
> > > little more prominent, followed by a continuous cycle of
> > > documentation/4.1
> > > snapshot updates as more and more people start trying it out and find
> > > issues/things they need to do what they want.
> > >
> > > After it feels like people are more or less able to do the basic
> > > things and
> > > not have everything blow up (there shouldn't be too much blowing up,
> > unit
> > > tests cover everything in the browser + server) I'd make an official
> > > 4.1release followed by more cycles/updates until we can mark it
> > > "stable/final"
> > > ?
> > >
> >
> > ---------------------------------------------------------------------
> > 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.
>
>
>
> ---------------------------------------------------------------------
> 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.

RE: 4.1 pretty much finished now

[James Carman <ja...@carmanconsulting.com>]

Where are the component docs for 4.1?  I don't see them on the new site.
I'd like to see if I can use 4.1 on my project and replace Tacos.  

-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com] 
Sent: Sunday, July 02, 2006 11:46 AM
To: Tapestry development
Subject: Re: 4.1 pretty much finished now

Yeah, I think so..We'll see what happens with client side validation. That
portion will depend on how much people have customized things there. At
least now the client side validates as much as the server side does. (in
that min/max date validate, min/max numbers validate, required clauses work
on all fields / etc...)

I'm sure tacos is totally fu-$%ed, but that probably won't take very long to
fix.

On 7/2/06, Norbert Sándor <de...@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?
>
> Thanks,
> Norbi
>
> Jesse Kuhnert wrote:
> > Validation is finally done, and I'm going to add the necessary logic to
> > dynamically add form components today. Does anyone care how I do this?
> >
> > I was thinking that initially I'd make the 4.1 snapshot build
> > availability a
> > little more prominent, followed by a continuous cycle of
> > documentation/4.1
> > snapshot updates as more and more people start trying it out and find
> > issues/things they need to do what they want.
> >
> > After it feels like people are more or less able to do the basic
> > things and
> > not have everything blow up (there shouldn't be too much blowing up,
> unit
> > tests cover everything in the browser + server) I'd make an official
> > 4.1release followed by more cycles/updates until we can mark it
> > "stable/final"
> > ?
> >
>
> ---------------------------------------------------------------------
> 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.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

Yeah, I think so..We'll see what happens with client side validation. That
portion will depend on how much people have customized things there. At
least now the client side validates as much as the server side does. (in
that min/max date validate, min/max numbers validate, required clauses work
on all fields / etc...)

I'm sure tacos is totally fu-$%ed, but that probably won't take very long to
fix.

On 7/2/06, Norbert Sándor <de...@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?
>
> Thanks,
> Norbi
>
> Jesse Kuhnert wrote:
> > Validation is finally done, and I'm going to add the necessary logic to
> > dynamically add form components today. Does anyone care how I do this?
> >
> > I was thinking that initially I'd make the 4.1 snapshot build
> > availability a
> > little more prominent, followed by a continuous cycle of
> > documentation/4.1
> > snapshot updates as more and more people start trying it out and find
> > issues/things they need to do what they want.
> >
> > After it feels like people are more or less able to do the basic
> > things and
> > not have everything blow up (there shouldn't be too much blowing up,
> unit
> > tests cover everything in the browser + server) I'd make an official
> > 4.1release followed by more cycles/updates until we can mark it
> > "stable/final"
> > ?
> >
>
> ---------------------------------------------------------------------
> 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.

Re: 4.1 pretty much finished now

[Mark Reynolds <ma...@gmail.com>]

Perfect explanation. Thanks!

On 7/3/06, Jesse Kuhnert <jk...@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 <ma...@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 <jk...@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 <jk...@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 <km...@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.
>
>

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

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 <ma...@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 <jk...@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 <jk...@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 <km...@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.

Re: 4.1 pretty much finished now

[Mark Reynolds <ma...@gmail.com>]

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.0 to
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 <jk...@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 <jk...@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 <km...@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.
>
>

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

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 <jk...@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 <km...@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.

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

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 <km...@servprise.com> wrote:
>
> On Sun, 02 Jul 2006 11:38:12 -0400, Norbert Sándor <de...@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.

Re: 4.1 pretty much finished now

[Kevin Menard <km...@servprise.com>]

On Sun, 02 Jul 2006 11:38:12 -0400, Norbert Sándor <de...@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

Re: 4.1 pretty much finished now

[Norbert Sándor <de...@erinors.com>]

How compatible are the 4.0 and 4.1 versions?
Can I just replace the 4.0 jars with the 4.1 ones?

Thanks,
Norbi

Jesse Kuhnert wrote:
> Validation is finally done, and I'm going to add the necessary logic to
> dynamically add form components today. Does anyone care how I do this?
>
> I was thinking that initially I'd make the 4.1 snapshot build 
> availability a
> little more prominent, followed by a continuous cycle of 
> documentation/4.1
> snapshot updates as more and more people start trying it out and find
> issues/things they need to do what they want.
>
> After it feels like people are more or less able to do the basic 
> things and
> not have everything blow up (there shouldn't be too much blowing up, unit
> tests cover everything in the browser + server) I'd make an official
> 4.1release followed by more cycles/updates until we can mark it
> "stable/final"
> ?
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

Yeah, I wouldn't want to call it stable yet. (Even though it's probably more
stable than any other ajax related tapestry functionality I've seen to date,
there may be more API changes to go through still).

On 7/2/06, KE Gan <kh...@gmail.com> wrote:
>
> Alright !!
>
> BTW, this is an "release candidate" kind of version, am I right ? Not a
> stable-ready-for-production right ?
>
> ~KEGan
>
>
> On 7/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah, that's what I'm going to be working on alongside of the continuous
> > release cycle when people start using it..
> >
> > I don't normally like to toot my own horn, but this release kind of
> kicks
> > ass if I do say so myself. And I do.. ;)
> >
> > On 7/2/06, KE Gan <kh...@gmail.com> wrote:
> > >
> > > Hi Jesse,
> > >
> > > THANKS !!  I am really looking forward for 4.1 (especially on Dojo
> > part).
> > > Hope there is enough documentation on the new stuffs, so we could
> start
> > > exploring :)
> > >
> > > ~KEGan
> > >
> > >
> > > On 7/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > > >
> > > > Validation is finally done, and I'm going to add the necessary logic
> > to
> > > > dynamically add form components today. Does anyone care how I do
> this?
> > > >
> > > > I was thinking that initially I'd make the 4.1 snapshot build
> > > availability
> > > > a
> > > > little more prominent, followed by a continuous cycle of
> > > documentation/4.1
> > > > snapshot updates as more and more people start trying it out and
> find
> > > > issues/things they need to do what they want.
> > > >
> > > > After it feels like people are more or less able to do the basic
> > things
> > > > and
> > > > not have everything blow up (there shouldn't be too much blowing up,
> > > unit
> > > > tests cover everything in the browser + server) I'd make an official
> > > > 4.1release followed by more cycles/updates until we can mark it
> > > > "stable/final"
> > > > ?
> > > >
> > > > --
> > > > 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.

Re: 4.1 pretty much finished now

[KE Gan <kh...@gmail.com>]

Alright !!

BTW, this is an "release candidate" kind of version, am I right ? Not a
stable-ready-for-production right ?

~KEGan


On 7/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Yeah, that's what I'm going to be working on alongside of the continuous
> release cycle when people start using it..
>
> I don't normally like to toot my own horn, but this release kind of kicks
> ass if I do say so myself. And I do.. ;)
>
> On 7/2/06, KE Gan <kh...@gmail.com> wrote:
> >
> > Hi Jesse,
> >
> > THANKS !!  I am really looking forward for 4.1 (especially on Dojo
> part).
> > Hope there is enough documentation on the new stuffs, so we could start
> > exploring :)
> >
> > ~KEGan
> >
> >
> > On 7/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > >
> > > Validation is finally done, and I'm going to add the necessary logic
> to
> > > dynamically add form components today. Does anyone care how I do this?
> > >
> > > I was thinking that initially I'd make the 4.1 snapshot build
> > availability
> > > a
> > > little more prominent, followed by a continuous cycle of
> > documentation/4.1
> > > snapshot updates as more and more people start trying it out and find
> > > issues/things they need to do what they want.
> > >
> > > After it feels like people are more or less able to do the basic
> things
> > > and
> > > not have everything blow up (there shouldn't be too much blowing up,
> > unit
> > > tests cover everything in the browser + server) I'd make an official
> > > 4.1release followed by more cycles/updates until we can mark it
> > > "stable/final"
> > > ?
> > >
> > > --
> > > 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.
>
>

Re: 4.1 pretty much finished now

[Jesse Kuhnert <jk...@gmail.com>]

Yeah, that's what I'm going to be working on alongside of the continuous
release cycle when people start using it..

I don't normally like to toot my own horn, but this release kind of kicks
ass if I do say so myself. And I do.. ;)

On 7/2/06, KE Gan <kh...@gmail.com> wrote:
>
> Hi Jesse,
>
> THANKS !!  I am really looking forward for 4.1 (especially on Dojo part).
> Hope there is enough documentation on the new stuffs, so we could start
> exploring :)
>
> ~KEGan
>
>
> On 7/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Validation is finally done, and I'm going to add the necessary logic to
> > dynamically add form components today. Does anyone care how I do this?
> >
> > I was thinking that initially I'd make the 4.1 snapshot build
> availability
> > a
> > little more prominent, followed by a continuous cycle of
> documentation/4.1
> > snapshot updates as more and more people start trying it out and find
> > issues/things they need to do what they want.
> >
> > After it feels like people are more or less able to do the basic things
> > and
> > not have everything blow up (there shouldn't be too much blowing up,
> unit
> > tests cover everything in the browser + server) I'd make an official
> > 4.1release followed by more cycles/updates until we can mark it
> > "stable/final"
> > ?
> >
> > --
> > 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.

Re: 4.1 pretty much finished now

[KE Gan <kh...@gmail.com>]

Hi Jesse,

THANKS !!  I am really looking forward for 4.1 (especially on Dojo part).
Hope there is enough documentation on the new stuffs, so we could start
exploring :)

~KEGan


On 7/2/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Validation is finally done, and I'm going to add the necessary logic to
> dynamically add form components today. Does anyone care how I do this?
>
> I was thinking that initially I'd make the 4.1 snapshot build availability
> a
> little more prominent, followed by a continuous cycle of documentation/4.1
> snapshot updates as more and more people start trying it out and find
> issues/things they need to do what they want.
>
> After it feels like people are more or less able to do the basic things
> and
> not have everything blow up (there shouldn't be too much blowing up, unit
> tests cover everything in the browser + server) I'd make an official
> 4.1release followed by more cycles/updates until we can mark it
> "stable/final"
> ?
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.
>
>