> Trinidad view about how to develop components is that if we have some code > that could be in renderer we have to put in the renderer. But the practice > says that there are some situations when we need to write custom code on > component class.
you can override things, by providing a template, which is a first class java file > > In tomahawk 1.2.x, the 80% of the components use template files to add > custom code to use forceId, visibleOnUserRole, implements additional facets, > define constants used on the renderer, or override > processXXXXXX(FacesContext context) methods (and tomahawk is full of > components created by users!). > > Actually, the only code that breaks the templates is when you want to define > restoreState and saveState methods. In that case you have to use abstract in Trinidad, we delegate that; > class or exclude the class for component generator, use the generator, > generate some code and put this on the real component class. > > Not have code completion and other features on the IDE is a low price for we > have with templates. > > regards > > Leonardo Uribe > > > > > > > > > > > > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
