> The great thing I like when writing pages with RIFE tags is that I can > define a common "structure.html" file with V to mark regions on the > page. Then, in my other pages, I just include the common > "structure.html" and define the content of those V-marked regions with > BV tags.
Not exactly a RIFE's unique features, thou. The same thing can be achieved using something like Sitemesh. Sure, it's nice that we can do this with RIFE, but this is not one of it's unique strengths. The "selling points" of RIFE's templating engine are, in my opinion: * Complete absence of logic * Simplicity And to tell you the truth, even these are a hard sell. The complete lack of logic in RIFE's template is very nice from a design point of view, but it takes some time to get used to. Things like iteration, that you take for granted in other template languages, have to be done in java code in RIFE. While this actually gives the programmer an exciting opportunity to do complex data transformations and other operations *inside* the iteration (something hard to achieve in other template languages), it also makes the common case (simple iteration over a bunch of ready-to-display objects) somewhat harder. -- Marcus _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
