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 M. Lewis Ship" <hl...@attbi.com> on 2003/03/07 15:50:11 UTC

[DISCUSS] 2.4 TODO

I'm hoping that 2.4-alpha-4 will be the last alpha for 2.4.  Given how
ambitious 2.4 is, it probably deserves a very long beta.  I have noticed
that downloads for 2.4 vastly outdistance 2.3 downloads.

Anyway, some ideas I'm still kicking around for 2.4 (in no particular order)
1) Fix up IMonitor to be useful in its newly repurposed job: hooks into
transaction systems.
2) JSP taglib that can call into Tapestry, using page and external service.
3) Investigate performance w.r.t. Luis Neve's observations (I've put some
buffering in place that may already help with this).
4) Nightly builds, integrated with Maven.
5) Neil Clayton's Tutorial
6) Replace Developer's Guide with User's Guide
7) 90% code coverage in test suite
8) David Solis' WML components
9) Use 2.4 features in Component Reference
10) Build web-site documentation (and Component Reference) from XML (but not
DocBook!)
11) Improvements to Script specification and processing
12) Handle locale change properly, somehow.
13) Make use of FileUpload
http://jakarta.apache.org/commons/fileupload/index.html

I think that 1, 2, 7, and 8 need to be completed to exit alpha.

I think that 3, 5, 6 and 9 need to be completed to exit beta.

The others are nice to have but not critical.

I'd like to take a crack at #2 soon; I think it will take a little work on
ApplicationServlet, IEngine and IRequestCycle to make it work.

I'd love it if #4 could come about, but don't have any cycles to spare.

What have I missed?

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



Re: [DISCUSS] 2.4 TODO

Posted by Richard Lewis-Shell <rl...@mac.com>.
> What have I missed?

I hope to commit the SubmitLink component into 2.4

R


RE: [DISCUSS] 2.4 TODO

Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
> 
> I'm hoping that 2.4-alpha-4 will be the last alpha for 2.4.  
> Given how ambitious 2.4 is, it probably deserves a very long 
> beta.  I have noticed that downloads for 2.4 vastly 
> outdistance 2.3 downloads.
> 
> Anyway, some ideas I'm still kicking around for 2.4 (in no 
> particular order)
> 1) Fix up IMonitor to be useful in its newly repurposed job: 
> hooks into transaction systems.
> 2) JSP taglib that can call into Tapestry, using page and 
> external service.
> 3) Investigate performance w.r.t. Luis Neve's observations 
> (I've put some buffering in place that may already help with this).
> 4) Nightly builds, integrated with Maven.
> 5) Neil Clayton's Tutorial
> 6) Replace Developer's Guide with User's Guide
> 7) 90% code coverage in test suite
> 8) David Solis' WML components
> 9) Use 2.4 features in Component Reference
> 10) Build web-site documentation (and Component Reference) 
> from XML (but not
> DocBook!)
> 11) Improvements to Script specification and processing
> 12) Handle locale change properly, somehow.
> 13) Make use of FileUpload 
> http://jakarta.apache.org/commons/fileupload/> index.html
> 
> I 
> think that 1, 2, 7, and 8 need to be completed 
> to exit alpha.

Just have #7 (Code Coverage) left to go.

> 
> I think that 3, 5, 6 and 9 need to be completed to exit beta.

David Solis has made a head start on #9 (Component Reference).

> 
> The others are nice to have but not critical.

I'm working on getting Tapestry to build using Gump.  That's part of our
acceptance as a full Jakarta project.