You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2007/10/21 21:03:34 UTC
5.0.6 ready soon
Folks,
I'm going to be cranking out the 5.0.6 release today ... please try to hold
off commits for a little bit. Once the binaries are up on people.apache.org,
we can go forward with a vote on releasing 5.0.6.
For me, 5.0.6 represents a transition point from alpha towards a more mature
state for the code. I hope that from here on, it will be filling gaps with
a *minimal* disruption to existing APIs.
The only major new features I personally want to pursue between now and
final is a) Ajax (and that's a biggie) and b) Spring Web Flow integration.
I also have some ideas for improving performance, but I don't know that
those are necessary yet.
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
Re: 5.0.6 ready soon
Posted by Fernando Padilla <fe...@alum.mit.edu>.
nice. :)
Well. Have you been able to take a look at TAPESTRY-1600?
What can I do to get that included? Is it acceptable as is? What else
would people like to see? :) :)
Howard Lewis Ship wrote:
> I was talking about new features.
>
> Bug fixes, especially those with patches and tests, will certainly go in.
>
> On 10/21/07, Fernando Padilla <fe...@alum.mit.edu> wrote:
>> WAIT.
>>
>> What about proper support for XML and XML Namespaces???
>>
>> Like the JIRA TAPESTRY-1600, adds basic Namespace support, with backward
>> compatibility. Maybe we should discuss that before 5.0.6 goes out, or I
>> can definitely imagine such changes being harder for us to include..
>> since they might seem like "big" changes, even though they are backward
>> compatible.
>>
>> And I am starting to play with adding a simple
>> MarkupWriterFactory.newMarkupWriter( ContenType type ) method, allowing
>> us to properly support XML output (to pick between DefaultMarkupModel
>> and XMLMarkupModel). Would a change like that be unwelcome for 5.0.7?
>>
>>
>>
>>
>> Howard Lewis Ship wrote:
>>> Folks,
>>>
>>> I'm going to be cranking out the 5.0.6 release today ... please try to
>> hold
>>> off commits for a little bit. Once the binaries are up on
>> people.apache.org,
>>> we can go forward with a vote on releasing 5.0.6.
>>>
>>> For me, 5.0.6 represents a transition point from alpha towards a more
>> mature
>>> state for the code. I hope that from here on, it will be filling gaps
>> with
>>> a *minimal* disruption to existing APIs.
>>>
>>> The only major new features I personally want to pursue between now and
>>> final is a) Ajax (and that's a biggie) and b) Spring Web Flow
>> integration.
>>> I also have some ideas for improving performance, but I don't know that
>>> those are necessary yet.
>>>
>> ---------------------------------------------------------------------
>> 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: 5.0.6 ready soon
Posted by Howard Lewis Ship <hl...@gmail.com>.
I was talking about new features.
Bug fixes, especially those with patches and tests, will certainly go in.
On 10/21/07, Fernando Padilla <fe...@alum.mit.edu> wrote:
>
> WAIT.
>
> What about proper support for XML and XML Namespaces???
>
> Like the JIRA TAPESTRY-1600, adds basic Namespace support, with backward
> compatibility. Maybe we should discuss that before 5.0.6 goes out, or I
> can definitely imagine such changes being harder for us to include..
> since they might seem like "big" changes, even though they are backward
> compatible.
>
> And I am starting to play with adding a simple
> MarkupWriterFactory.newMarkupWriter( ContenType type ) method, allowing
> us to properly support XML output (to pick between DefaultMarkupModel
> and XMLMarkupModel). Would a change like that be unwelcome for 5.0.7?
>
>
>
>
> Howard Lewis Ship wrote:
> > Folks,
> >
> > I'm going to be cranking out the 5.0.6 release today ... please try to
> hold
> > off commits for a little bit. Once the binaries are up on
> people.apache.org,
> > we can go forward with a vote on releasing 5.0.6.
> >
> > For me, 5.0.6 represents a transition point from alpha towards a more
> mature
> > state for the code. I hope that from here on, it will be filling gaps
> with
> > a *minimal* disruption to existing APIs.
> >
> > The only major new features I personally want to pursue between now and
> > final is a) Ajax (and that's a biggie) and b) Spring Web Flow
> integration.
> >
> > I also have some ideas for improving performance, but I don't know that
> > those are necessary yet.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
Re: 5.0.6 ready soon
Posted by Fernando Padilla <fe...@alum.mit.edu>.
WAIT.
What about proper support for XML and XML Namespaces???
Like the JIRA TAPESTRY-1600, adds basic Namespace support, with backward
compatibility. Maybe we should discuss that before 5.0.6 goes out, or I
can definitely imagine such changes being harder for us to include..
since they might seem like "big" changes, even though they are backward
compatible.
And I am starting to play with adding a simple
MarkupWriterFactory.newMarkupWriter( ContenType type ) method, allowing
us to properly support XML output (to pick between DefaultMarkupModel
and XMLMarkupModel). Would a change like that be unwelcome for 5.0.7?
Howard Lewis Ship wrote:
> Folks,
>
> I'm going to be cranking out the 5.0.6 release today ... please try to hold
> off commits for a little bit. Once the binaries are up on people.apache.org,
> we can go forward with a vote on releasing 5.0.6.
>
> For me, 5.0.6 represents a transition point from alpha towards a more mature
> state for the code. I hope that from here on, it will be filling gaps with
> a *minimal* disruption to existing APIs.
>
> The only major new features I personally want to pursue between now and
> final is a) Ajax (and that's a biggie) and b) Spring Web Flow integration.
>
> I also have some ideas for improving performance, but I don't know that
> those are necessary yet.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: 5.0.6 ready soon
Posted by Dan Adams <da...@ifactory.com>.
That actually does help although it would be nice if I could talk about
implementation approach before working on it for the ones that aren't
clear. I don't have a ton of time to spend on this (which I'm sure you
can all relate to) so I'm try to not spending my time implementing
something that will get thrown out. For things I'm really unsure about I
guess I'll just use a branch and for other stuff I'll take my best stab
at it.
On Mon, 2007-10-22 at 08:51 -0400, Jesse Kuhnert wrote:
> I don't know how things have been working in the T5 code base, but
> for me personally some of these tickets would be a little hard to say
> "sounds good" or whatever to as they could go either way depending on
> how you implement them.
>
> So...If I were looking for feedback I'd probably just go ahead and
> implement one at a time and be sure to point out the changes and ask
> for feedback immediately after.
>
> If the changes are large or have a big impact on the system that may
> have any largish impact on people using T5 from snapshot builds then
> it might be good to do it in a quick branch and ask for feedback after
> that.
>
> Just my thoughts. I usually start tuning out and become less useful
> on helping people with design on projects once the overall stuff
> sounds good and end up asking them to just do it and critique
> afterwards...On smaller stuff at least. It's a lot easier/efficient
> for the person doing the critiquing that way.
>
> Hope that makes sense..
>
> On 10/21/07, Dan Adams <da...@ifactory.com> wrote:
> > I would very much like to see the API stabilize. I've had more time lately to work on both our internal stuff that relies on t5 and t5 itself which has been great. I think that most of the change I would like to see/make are improvements/enhancements rather than changes to the existing API. The ones I've got right now that are blocking my stuff are (in rough order of severity):
> >
> > TAPESTRY-1653: Coercion from Hibernate entity -> String and back
> > TAPESTRY-1842: Allow coercions to handle multiple or non-concrete types (related to 1653)
> > TAPESTRY-1839: Include SymbolSource when looking up component messages
> > TAPESTRY-1645: Getting the current Grid instance from the environment
> > TAPESTRY-1835: Indicating if a field is required
> > TAPESTRY-1647: Need to be able to render elements before and after form labels
> > TAPESTRY-1617: Change GridPager to Pager and make it more general
> > TAPESTRY-1643: @Mixin should accept parameters
> > TAPESTRY-1635: Support for optional validator constraints (related to 1839)
> >
> > I have no problem working on these but for a lot of them I just need better feedback on design decisions; I don't want to plow ahead on something based on a bunch of assumptions, create something in my library that depends on it, and then have to go back and change it all (such as 1839 for instance).
> >
> >
> > ----- Original Message -----
> > From: "Howard Lewis Ship" <hl...@gmail.com>
> > To: "Tapestry development" <de...@tapestry.apache.org>
> > Sent: Sunday, October 21, 2007 3:03:34 PM (GMT-0500) America/New_York
> > Subject: 5.0.6 ready soon
> >
> > Folks,
> >
> > I'm going to be cranking out the 5.0.6 release today ... please try to hold
> > off commits for a little bit. Once the binaries are up on people.apache.org,
> > we can go forward with a vote on releasing 5.0.6.
> >
> > For me, 5.0.6 represents a transition point from alpha towards a more mature
> > state for the code. I hope that from here on, it will be filling gaps with
> > a *minimal* disruption to existing APIs.
> >
> > The only major new features I personally want to pursue between now and
> > final is a) Ajax (and that's a biggie) and b) Spring Web Flow integration.
> >
> > I also have some ideas for improving performance, but I don't know that
> > those are necessary yet.
> >
> > --
> > Howard M. Lewis Ship
> > Partner and Senior Architect at Feature50
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
--
Dan Adams
Senior Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: 5.0.6 ready soon
Posted by Jesse Kuhnert <jk...@gmail.com>.
I don't know how things have been working in the T5 code base, but
for me personally some of these tickets would be a little hard to say
"sounds good" or whatever to as they could go either way depending on
how you implement them.
So...If I were looking for feedback I'd probably just go ahead and
implement one at a time and be sure to point out the changes and ask
for feedback immediately after.
If the changes are large or have a big impact on the system that may
have any largish impact on people using T5 from snapshot builds then
it might be good to do it in a quick branch and ask for feedback after
that.
Just my thoughts. I usually start tuning out and become less useful
on helping people with design on projects once the overall stuff
sounds good and end up asking them to just do it and critique
afterwards...On smaller stuff at least. It's a lot easier/efficient
for the person doing the critiquing that way.
Hope that makes sense..
On 10/21/07, Dan Adams <da...@ifactory.com> wrote:
> I would very much like to see the API stabilize. I've had more time lately to work on both our internal stuff that relies on t5 and t5 itself which has been great. I think that most of the change I would like to see/make are improvements/enhancements rather than changes to the existing API. The ones I've got right now that are blocking my stuff are (in rough order of severity):
>
> TAPESTRY-1653: Coercion from Hibernate entity -> String and back
> TAPESTRY-1842: Allow coercions to handle multiple or non-concrete types (related to 1653)
> TAPESTRY-1839: Include SymbolSource when looking up component messages
> TAPESTRY-1645: Getting the current Grid instance from the environment
> TAPESTRY-1835: Indicating if a field is required
> TAPESTRY-1647: Need to be able to render elements before and after form labels
> TAPESTRY-1617: Change GridPager to Pager and make it more general
> TAPESTRY-1643: @Mixin should accept parameters
> TAPESTRY-1635: Support for optional validator constraints (related to 1839)
>
> I have no problem working on these but for a lot of them I just need better feedback on design decisions; I don't want to plow ahead on something based on a bunch of assumptions, create something in my library that depends on it, and then have to go back and change it all (such as 1839 for instance).
>
>
> ----- Original Message -----
> From: "Howard Lewis Ship" <hl...@gmail.com>
> To: "Tapestry development" <de...@tapestry.apache.org>
> Sent: Sunday, October 21, 2007 3:03:34 PM (GMT-0500) America/New_York
> Subject: 5.0.6 ready soon
>
> Folks,
>
> I'm going to be cranking out the 5.0.6 release today ... please try to hold
> off commits for a little bit. Once the binaries are up on people.apache.org,
> we can go forward with a vote on releasing 5.0.6.
>
> For me, 5.0.6 represents a transition point from alpha towards a more mature
> state for the code. I hope that from here on, it will be filling gaps with
> a *minimal* disruption to existing APIs.
>
> The only major new features I personally want to pursue between now and
> final is a) Ajax (and that's a biggie) and b) Spring Web Flow integration.
>
> I also have some ideas for improving performance, but I don't know that
> those are necessary yet.
>
> --
> Howard M. Lewis Ship
> Partner and Senior Architect at Feature50
>
> Creator Apache Tapestry and Apache HiveMind
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: 5.0.6 ready soon
Posted by Dan Adams <da...@ifactory.com>.
I would very much like to see the API stabilize. I've had more time lately to work on both our internal stuff that relies on t5 and t5 itself which has been great. I think that most of the change I would like to see/make are improvements/enhancements rather than changes to the existing API. The ones I've got right now that are blocking my stuff are (in rough order of severity):
TAPESTRY-1653: Coercion from Hibernate entity -> String and back
TAPESTRY-1842: Allow coercions to handle multiple or non-concrete types (related to 1653)
TAPESTRY-1839: Include SymbolSource when looking up component messages
TAPESTRY-1645: Getting the current Grid instance from the environment
TAPESTRY-1835: Indicating if a field is required
TAPESTRY-1647: Need to be able to render elements before and after form labels
TAPESTRY-1617: Change GridPager to Pager and make it more general
TAPESTRY-1643: @Mixin should accept parameters
TAPESTRY-1635: Support for optional validator constraints (related to 1839)
I have no problem working on these but for a lot of them I just need better feedback on design decisions; I don't want to plow ahead on something based on a bunch of assumptions, create something in my library that depends on it, and then have to go back and change it all (such as 1839 for instance).
----- Original Message -----
From: "Howard Lewis Ship" <hl...@gmail.com>
To: "Tapestry development" <de...@tapestry.apache.org>
Sent: Sunday, October 21, 2007 3:03:34 PM (GMT-0500) America/New_York
Subject: 5.0.6 ready soon
Folks,
I'm going to be cranking out the 5.0.6 release today ... please try to hold
off commits for a little bit. Once the binaries are up on people.apache.org,
we can go forward with a vote on releasing 5.0.6.
For me, 5.0.6 represents a transition point from alpha towards a more mature
state for the code. I hope that from here on, it will be filling gaps with
a *minimal* disruption to existing APIs.
The only major new features I personally want to pursue between now and
final is a) Ajax (and that's a biggie) and b) Spring Web Flow integration.
I also have some ideas for improving performance, but I don't know that
those are necessary yet.
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org