Hello , RvM taglib:
RvM gave a great presentation about what is possible with the 2.4 servlet api his goals where to use a few simple tags, use jstl and the EL as much as possible. (only 3 tags !!). He also discussed the MVC approach. I missed that part of in the presentation of the presentation tags. If the data is to be fetched by the controller the tags should be even more simple jaco's simpletags http://www.dynasol.com/simpletags/1.1.2/ should be sufficient (and even better) because there is not logic in them. and is't possible to create things like a html table/calender. I think the presentation was great , but the examples not realistic. The mmbase taglibs make use of the hierarchy of the tags , thats on the the great powers of the taglib. <list> <related> <related> </related> </list> </list> This makes is easy to cut and past code around (no need to declare variables) other examples where false to <mm:node> <mm:field name="bla"/> </mm:node> can also be written as <mm:node id="test"/> <mm:field node-"test" field="title"/> but that is almost never used because it requires to define a test variable. jtsp:forEach tags: the forEach tag can be useful. but when people start using it they will need the exact functions that are in the mmbase taglib -know the size of the list -know if the list is not empty -know if this is the first / last element those simple functions are not provided by the jstl (maybe the flow taglibs are for that purpose). We also discussed if it was not possible to create an other taglib next to the presentation taglib. This taglib would be the data taglib, and could be used as dataprovider for the presentation taglib. Still having a controller is a good thing for stuff like authorization and for global functions _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
