Add specialised plugins

[GoogleCodeExporter]

Other suggestion: allow for specialised plugins. For example, the full
screen viewer could be a plugin, and jBrout could allow for calling a
specialised plugin before editing or after editing. 

Actually, these wouldn't be plugins in the same sense as the current jBrout
plugins: they wouldn't appear in the contextual menus, and maybe they would
have to be called using a special syntax (for example, the full screen
plugin could take a list of files). But this would allow to customize
jBrout. The user would start with a simple plugin-free jBrout and would be
able to expand jBrout if he so wishes. Why would I want a plugin after
calling an external editor? Because I'd like jBrout to store automatically
in the image what tools were used to correct the it. I understand I may be
the only one who would want this. But by allowing to call user-defined
software in several key points, jBrout could be customized without laying
the burden on the original developers ;-)

Original issue reported on code.google.com by davito...@gmail.com on 15 Jul 2009 at 2:13

[GoogleCodeExporter]

Many features are specific and therefore not interesting for everybody. This 
plugin
approach would allow to have a modular jBrout. This could let people implement 
very
specific plugins. (issues 93 and 73 for example)

Original comment by tbenita on 15 Jul 2009 at 3:25

[GoogleCodeExporter]

Original comment by matej.c...@gmail.com on 12 Aug 2013 at 10:45

• Added labels: Component-jbrout, Priority-Low, Type-Enhancement