Actually, I almost agree with all the thoughts here, especially about defining Web application development as central, but i have another question : What is a reference guide ?
In my humble opinion, it should not stand for a user guide, or articles, or community wikis and so on... It's all about referencing the API in a human readable format, i.e. 'How to implement a AppModule class?' we have the ServiceBinder, build, contribute, decorate, advise methods, symbols, @SubModule, services overrides... This will not be 'How to override the ApplicationState service so i can benefit from my companies SSO system ?' or anything else This is why i think that getting started with tapestry-ioc is maybe more natural for a technical documentation as it is the heart and soul of Tapestry. 2010/6/29 Tom van Dijk <[email protected]> > Actually, I'm still busy learning Tapestry and I started with the IoC. Why > should it not be a starting point? I think it's essential to understand that > piece first. > > > Igor Drobiazko schreef: > > First of all Tapestry is a web framework and that is the reason why >> developers start using it.Tapestry IoC is the heart and sole of Tapestry >> but >> it should not be the starting point for beginners. Tapestry IoC is not the >> reason why developer start using Tapestry. In most cases they even do not >> know about IoC concepts but relealize the strength during learning. >> >> >> >> On Tue, Jun 29, 2010 at 5:31 AM, Christophe Cordenier < >> [email protected]> wrote: >> >> >> >>> Hi, >>> >>> I would like to contribute to the great documentation effort started by >>> Ulrich and Robin as designer. I have seen all the work done to migrate >>> the >>> existing documentation to confluence and macro to identify deprecated >>> documentation. >>> >>> Will the documentation continue to be generated from xdoc and apt files, >>> or >>> will it be fully maintained via confluence ? >>> >>> 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. >>> >>> 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 : >>> >>> we have the most popular and most used : >>> - tapestry-ioc >>> - tapestry-spring >>> - tapestry-upload >>> - tapestry-hibernate and hibernate-core >>> - tapestry-test >>> >>> but also >>> >>> - tapestry-func >>> - tapestry-beanvalidator >>> - tapestry-jmx >>> - tapestry-webflow >>> >>> + all the existing third party libraries... >>> >>> My conclusion is that Tapestry is really so much more than a Web >>> Framework >>> and the IOC is central. >>> >>> So to design the plan, >>> >>> Should i address IOC first and then talk about web application >>> development >>> as any other part of the documentation ? >>> >>> or >>> >>> Should i emphasize on the Web development and make it central, and give a >>> plan for every contribution ? >>> >>> Anyway i would be pleased to contribute to the documentation effort for >>> my >>> first contribution as committer, so suggestions are very welcome. >>> >>> -- >>> Regards, >>> Christophe Cordenier. >>> >>> Committer on Apache Tapestry 5 >>> Co-Creator of wooki @wookicentral.com >>> >>> >>> >> >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Regards, Christophe Cordenier. Developer of wooki @wookicentral.com
