On Jul 2, 2012, at 5:17 AM, A Kobame wrote: > Hi folks, > > I'm wondering that here is any preferred/recommentd component > distribution method? >
Display components tend to be site and application specific; I've never figured out a way to package them generically. I think the best thing to do for now is publish components, or entire example Mason/Poet sites, on github and let people pick out what they need. > The second question is about the html-template separation. > > E.g. What is the best way having an separate directory, e.g. > /templates, where one can put some _poet-specific_ site-templates, > together with template-specific methods, css, js and etc.. and the > "main" execution flow only fill the template as one of last actions - > probably from /Base.mc. > > How to implement for example: > http://example.com/some/component?template=print > > e.g. in the "normal" execution flow the site will use some "default" > template, but when get the arg "template=print" (or any other > "template-name") will search the "/templates" for the requested > template (like "print") and will use/fill that one... > > I understand than this is too application specific, and some apps > simply doesn't need this, but would be nice have some hints, what is > the right way to do this tasks like this. Is the "right way" using > subrequests here with "$m->visit" ? Any other hints? Yes, I think $m->visit is the right way to do this. Jon ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
