Hi Emmanuel, I think with your hints and Geert's I can manage to achieve my goal.
While I agree with you that, usually, we start with some sketches made by web designers and then "instrument" them to add dynamic contents, I think in the life cycle of a product there will have surely loop back. I mean that some pages already used and instrumented will have to be modified by a web designer. In the case, it is handy if he can work directly with the real pages and make his changes with the minimal impact on the dynamic content. We had also a situation where the site was made entirely by programmers at the first step using semantic XHTML only (no presentation) and the web designer worked them after to give them a look. Regards Jean-Marie eokyere wrote: > > Jean-Marie, > > I have always thought that designers supply statics, and then from > statics templates are defined; at least this is the way I've worked > with most people. > > In any case, I find the output from blocks to be only a minor > annoyance, if at all. If the content within those blocks are large and > sort of put off our previews, you can use include (i) tags within the > blocks and move the fragments into a separate file (instead of > inlining them) if that helps. > > cheers, > Emmanuel > > On 1/14/07, Jean-Marie Galliot <[EMAIL PROTECTED]> wrote: >> >> Hi Geert, >> >> One of the thing which appealed to me in Rife was the fact that I hate >> the >> jsp tag-soup. >> >> I wanted to have a templating system which allow web designer to >> visualize >> pages in their editor and browser without being obliged to start the >> server. >> >> Tapestry and Wicket also offered this kind of "non intrusive" >> instrumentation of web pages. >> >> I thought it was also the case for Rife as I saw at a first glance that >> the >> tags (at least the first version of them) was HTML-Comment like. >> >> But, I realize that when I define two or three blocks as alternative >> values >> for a "value" tag, those three blocks appear if I open a browser and try >> to >> pre-visualize the page. >> >> Is there a way to prevent some of them to appear in the browser? >> >> Do you think that coding them as <r:b> instead of <!--B> is a sound and >> safe >> solution to that problem? >> >> Beside that I would say that I love the templating system which allow to >> really keep presentation and business logic separate. >> >> Thanks >> >> Jean-Marie >> -- >> View this message in context: >> http://www.nabble.com/templates-viewed-in-a-browser-tf3010833.html#a8362163 >> Sent from the RIFE - users mailing list archive at Nabble.com. >> >> _______________________________________________ >> Rife-users mailing list >> [email protected] >> http://lists.uwyn.com/mailman/listinfo/rife-users >> > > > -- > blog -- http://eokyere.blogspot.com > RIFE Framework -- http://rifers.org > RIFE Training -- http://rifers.org/training > > Mohandas Gandhi - "You must be the change you wish to see in the world." > _______________________________________________ > Rife-users mailing list > [email protected] > http://lists.uwyn.com/mailman/listinfo/rife-users > > -- View this message in context: http://www.nabble.com/templates-viewed-in-a-browser-tf3010833.html#a8376326 Sent from the RIFE - users mailing list archive at Nabble.com. _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
