![](https://secure.gravatar.com/avatar/516640127f084752aaf5f23c7119f1be.jpg?s=120&d=mm&r=g)
On Fri, 2013-04-26 at 18:22 +0400, Alexandre Prokoudine wrote:
I have a feeling that it would involve enhancing the extensions architecture. There's a bunch of things we cannot do yet, like registering extensions in arbitrary menus.
I'm not sure if this is the _best_ solution. Although of course I think the functionality should be available, just not used as a 'toxic workaround' for a more structured extensions system. For example, an import/export to/from the internet extension would be really good to have as a 'type' of extension which provides data specific for that kind of job.
So what type of extensions are there? Generators, filters, openers, meta-data-inizers, importers, exporters and templators?
I think we'll have a good grasp on this when it's possible to safely kick OCAL out of the codebase and into an extension without loosing any functionality.
Martin,