A big +1. On 02/11/2012, at 12:57 PM, Rural Hunter wrote:
> δΊ 2012/11/2 1:31, Thiago H de Paula Figueiredo ει: >> On Thu, 01 Nov 2012 13:38:05 -0200, Rural Hunter <ruralhun...@gmail.com> >> wrote: >> >>> yes, thanks guys. I know I can get it from service-status or source code. I >>> have already had a rough read of both. But if there is a doc to briefly >>> describe all those services and how to utilize them, it will be very >>> helpful and save a lot of time at least for beginners. >> >> Tapestry has a large number of services and many of them are supposed to be >> used only inside Tapestry itself (the ones in packages named 'internal', so >> documenting all of them in a detailed manner would be a waste of time. > Yes, that's correct. I just want a list for those are intended to be used by > common users. There is no need to document internal services. If someone > needs to know the internal thing, it's better to read the source. I raised > this question because I have seen many developers use Tapestry but only focus > on those UI comps. They understand there is IOC service in Tapestry and some > of them are able to create their own IOC services. But most of them don't > know how to use the power of builtin services. When I read some Tapestry > blogs such as Taha's, I always have this feeling: wow, there is such a > service and it can be used like this! I think at least we should have a doc > for those most useful services. If it costs too much time to describe each > service in detail, a short brief intro and putting the links of some > developers' blogs about how to use it should be fine. >> >>> Regarding the current IOC docs, I have read almost all of them and I think >>> I have understood this part. but I still need to get into source to see >>> what the service does and other things I want to know. for example, if it >>> implements any of Gang Of Four Design Patterns etc. >> >> Many of them use Chain of Command, others use Command (the Tapestry >> rendering in the end is just executing RenderCommand's, which is an >> interface), Decorator is supported by Tapestry-IoC itself, etc. >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
