From: alex b. <en...@tu...> - 2001-08-15 17:36:37
|
> Cool. This ebedding syntax will also be availabel for the layouts and > masters templates, I guess? So that acutally a "real" template system (xslt, > smarty etc) is only required in the modules itself 'caus in layouts/ and > masters/ are only module outputs embedded that are translated to php calls > ($Page->output[...]) on compile time? Here's the trick: that syntax is available from _anywhere_. You can put it in masters, layouts, module templates, includes, whatever! :) > > Why is this worthwhile? > > > > It means you can forego using layouts and module lists if you > > don't need the advanced features page offers (load/init ordering, etc) - > and > > it's obviously convenient for embedding modules _anywhere_ (yes, you could > > embed one module's output in another module's output!) > Groovy. > > > I'm sure there will be questions on this, fire away! > I think this feauture is nice to have but might be a bit confusing. > Especially if one embedds html markup in the xml page definition like shown > above. I think this breaks xml conformance. But as I said, nice to have. > Especially for small "just-presentation" pages. In this case I'm not so concerned with xml conformance, if you were big on that you could make sure your page defs used xhtml, and validated as xml... that would be fine. then again it would also be fine if they didn't within <markup> > BTW: How far are you with the Query/Entity Manager stuff? I expect there to be a bit of delay integrating that stuff, it could be as long as a month before the first revs are in the system. I've been focusing on other things for my business recently, so I don't have the kind of time I would like to devote to r2. But it will all happen... best, _alex |