Derick Rethans wrote: > On Tue, 24 Jun 2008, Kore Nordmann wrote: > > On Mon, 2008-06-23 at 16:50 +0200, James Pic wrote: > > > Output Filters > > > ============== > > > 2) Should this filters be pluggable in the view-manager? > > > > no > > > > IF we support output filters, they must be pluggable. Hardcoded filters > > are imho a no-go. > > Sure, but the thing is *where* they are pluggable I think here. James, > can you clarify?
I though that we could use a list of filter objects in the view-manager constructor. Because the view-manager wraps around the view-handlers, it could either be fed into the view-handler, either be used at the view manager level. > > > > View-manager > > > ============ > > > > > > 0) Should the view-manager implement the same routing system as the > > > router? > > > > How could that work? I don't think the view routing will be URL based in > > most cases, but "just" based on the provided view structures. Not sure > > if some basic general implementation is useful here... > > In the discussion document we list different views: template, php and > json. The view-manager should be free to use the input and output objects to figure which view-handler to use? Regards, James -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
