On 7 March 2012 09:49, Pedro Melo <m...@simplicidade.org> wrote: >> #1 is hard to do because Mason is supposed to be content-type agnostic - >> usable for HTML generation but also other kinds of content generation.
The default filter is defined in the interpreter instance. If you need to use Mason to generate any type of content, you can perfectly have different interpreters with different default filters. Anything wrong with that? If users really insist on having the same Mason interpreter to render different types of contents, maybe the default filter should be a property of the component? Define it in Base.mc for your HTML generating component directory .. job done. -- Jerome Eteve. http://sigstp.blogspot.com/ http://twitter.com/jeteve ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
