From: Andreas A. <a.a...@th...> - 2001-08-15 15:06:54
|
Hi Alex, > I like this syntax because it allows non-programmer users to define pages > and embed modules without worrying about php syntax - they use > familiar tags > to call in modules that programmers provide. 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? > 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. BTW: How far are you with the Query/Entity Manager stuff? Andi |