El sáb, 12-11-2005 a las 11:52 +0000, Ross Gardler escribió: > Ferdinand Soethe wrote: > > I'd like to create a new class of plugins termed 'bypass plugins' for > > functionalities where the SSP ideas of Forrest are either not needed, > > not provided at the moment or not useful alltogether. > > > > By definition a bypass-plugin will simply provide a way of > > transforming one non-Forrest format into another non-Forrest format > > including all the needed resources. > > My gut instinct is to be -1 on accepting any such plugins in Forrest, my > reasons are inline. However, please continue to discuss, it may be that > you can sway me by making me understand your arguments. ... > > If you are not providing XDoc what transformations do you get from Forrest? > ... > The problem with accepting plugins that do not conform to our TR is that > we dilute that TR and provide examples of the *wrong* way of doing > things. Forrest is about multiple input formats and multiple output > formats. If we provide plugins that bypass this then we are nothing more > than a transformation engine and therefore overkill. ... > Thinking of the s5 plugin which was the inspiration for smart slides. It > allows content to be generated from any accepted input format in > Forrest. That is why it is powerful. > > With your new schema we can convert from whatever input format to your > new schema and leverage the full power of Slidy from any input format. ...
-1 for bypass plugins, above reasoning shows why. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
