On Mon, 28 Jun 2010 18:31:35 -0300, Christophe Cordenier
<[email protected]> wrote:
Hi,
Hi!
Will the documentation continue to be generated from xdoc and apt files,
or will it be fully maintained via confluence ?
I don't know, but I guess the Confluence option would be the better one.
Actually this WE, i have started to think on what should be the plan for
a reference guide and how to organize chapters. We have a lot of
starters for new comers but in my opinion with User guides, we miss to
many existing and interesting informations because of the lack of a
structured TOC.
Nice!
This thought has lead me to this simple (and sorry if it sounds stupid)
question : What is Tapestry 5 ?
In fact, tapestry-core corresponds to the module we use to build Web
applications, then 'core' Tapestry is Web application development. After
that i made a quick overview of modules present on trunk to get familiar
with fresh developments, here is the list :
I think that the documentation should have two main entry points: one for
tapestry-core, another for tapestry-ioc. Under tapestry-ioc would be found
the documentation for tapestry-upload, tapestry-beanvalidator and
tapestry-webflow, i.e, anything that is related directly to web
development. Everything else would be part of the documentation of
Tapestry-IoC, including pointers to third-party packages.
My conclusion is that Tapestry is really so much more than a Web
Framework and the IOC is central.
Agreed. But, when you say Tapestry, the first idea that comes to the mind
of almost anyone is the web framework, so we should be careful about that
and be very emphatic about Tapestry-IoC not being dependent on
Tapestry-core. I've seen at least one person doing this mistake.
Should i address IOC first and then talk about web application
development as any other part of the documentation ?
I don't think so, for the reasons I stated above.
Should i emphasize on the Web development and make it central, and give a
plan for every contribution ?
I think we could keep Web development as central, but raise the visibility
of Tapestry-IoC inside the documentation. For example, in the first page,
give a description of tapestry-core first and then talk about tapestry-ioc.
Anyway i would be pleased to contribute to the documentation effort for
my first contribution as committer, so suggestions are very welcome.
Cool! :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
