Hi,
Gert Cuykens <[EMAIL PROTECTED]> writes:
> can you explain why modules API is more limited please ?
You didn't really understand the purpose of modules if you are still
asking this. Well, I don't know how to explain it any better. Perhaps
you should have a look at the code.
Sven
_
On Thu, 09 Dec 2004 00:47:58 +0100, Sven Neumann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Gert Cuykens <[EMAIL PROTECTED]> writes:
>
> > why does gimp have modules ? why not make only plugins ?
>
> They serve completely different purposes. Modules are ways to add
> alternative implementations of cor
Hi,
Gert Cuykens <[EMAIL PROTECTED]> writes:
> why does gimp have modules ? why not make only plugins ?
They serve completely different purposes. Modules are ways to add
alternative implementations of core functionality. At the moment there
are three kind of module interfaces that can be impleme
Gert Cuykens ([EMAIL PROTECTED]) wrote:
> why does gimp have modules ? why not make only plugins ?
Because modules have a tighter integration with the GIMP and can
e.g. provide additional color selectors embedded in the Gimp-GUI
or invoke actions.
Their API is more limited but plugins *have* to b
On Wed, 08 Dec 2004 23:44:35 +0100, Sven Neumann <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> Gert Cuykens <[EMAIL PROTECTED]> writes:
>
> > what is the difference between a module and a plugin ?
>
> A plug-in runs as it's own process and can use the full libgimp API.
> A module is some piece of c
Hi,
Gert Cuykens <[EMAIL PROTECTED]> writes:
> what is the difference between a module and a plugin ?
A plug-in runs as it's own process and can use the full libgimp API.
A module is some piece of code loaded at run-rime by the gimp
process. It has to implement a certain set of methods and can o
