I understand that book would be valuable addition to Tapestry, but I would
also prefer you to spend your time doing the coding, and if I may add, not
so much on new features (like Spring Web Flow), but more on improving
already present ideas since there are many places for improvement. One thing
that comes to my mind is - various ways of passing parameters between pages
(for example for search form criteria etc..), Javascript support that you
mentioned, etc... These things are pretty much needed in every web app out
there.
I just converted my first T4 app to T5, and although it was generaly better
experience, I have found few places where things became harder that it was
before, for eg - no properly working submit button context, no easy option
to turn of sorting in grids, and similar bits and pieces...
Regards,
Vjeran
----- Original Message -----
From: "Howard" <hls...@gmail.com>
To: <users@tapestry.apache.org>
Sent: Saturday, November 07, 2009 7:11 PM
Subject: [Tapestry Central] Next Steps for Tapestry
I've been consciously letting Tapestry 5.1 sit and stabilize for a
while ... a time that's stretched a few months longer than I initially
intended.
This is due to a number of factors: my return to independent
consulting, my desire to write a definitive Tapestry 5 book, and
preparations for many trips and speaking engagements.
All of these factors have worked on each other: I've been improving and
extending my Tapestry Workshop training materials which can be quite
time consuming. I've also (over the last several months) been on the
road several times, talking about Tapestry or doing Tapestry training.
I do want to write a book on Tapestry but if I start writing 5.2 code,
I know I'll be sucked right in ... lots of code (that darn Spring Web
Flow integration for sure this time) and bug fixes.
In addition, I've had an embarassment of riches: two main clients, one
regular part time, and the other requesting (but not always getting)
all my remaining time. I also have additional clients and training
engagements waiting in the wings. I simply have a lot of draws on my
time.
As usual, working on real-world projects lets me experience the "rough
edges" of Tapestry and fills me with ideas on how to address those in
the next release ... often by splitting up Tapestry services into
smaller, more easily overridden chunks and carefully moving internal
services out into the public APIs.
Finally, I've been very pleased by the fact that as I've stepped back
temporarily from my normal stream of commits, the other Tapestry
developers have stepped in and filled the gap. There's been quite a bit
of activity especially from Igor that I've barely had a chance to keep
up on.
So the question is: do I wait and see if time opens up in Q1 to
actually start on a T5 book ... or do I jump into 5.2 coding and leave
books to others? It's much, much easier to write code than to write a
book ... a book is a large amount of concentrated effort. It's very
hard to accomplish anything on a book using an hour here or an evening
there ... whereas Tapestry's code base lends itself to that kind of
effort quite nicely.
--
Posted By Howard to Tapestry Central at 11/07/2009 10:11:00 AM
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.53/2486 - Release Date: 11/07/09
07:38:00
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
