I guess so, although I'd probably want a lawyer to take a good look just in
case one of you guys implements something that would add value to Rev.
However, if it's GPL it's just another good reason for you to go with a
plugin architecture.
I know it sounds like a newbie question but anyway,
jbv wrote:
could someone be kind enough to explain to me briefly how does
this plugin arch. work in Rev ?
Basically it's just a menu built dynamically to provide quick access to
stack files in a Plugins folder. Rev builds its menu at startup, but my
own plugins menu works so fast being built
Richard,
jbv wrote:
could someone be kind enough to explain to me briefly how does
this plugin arch. work in Rev ?
Basically it's just a menu built dynamically to provide quick access to
stack files in a Plugins folder. Rev builds its menu at startup, but my
own plugins menu works so
jbv wrote:
One last question : could we also drop standalones into that Plugins
folder ? I don't see any specific reason to do that right now, I'm just
wondering if that would be feasable...
H... an interesting idea. If we come up with a reason to do it, it
shouldm't be hard to do.
--
I'm very strongly opposed to hierarchical menus except where
absolutely necessary, as they're simply more physically
diffcult to use (lose the use of your dominant arm for a few
months and accessibility issues become very clear g). I'm
envisioning this Plug-Ins menu being a simple
