> > Because the Gimp was not originally designed as a server, it does
> > not follow some conventions that are necessary for such a mode. This
> > includes the issue of managing shared resources among different
> > threads of execution. A few of the resources that are not
> > 'thread-safe' include
> My solution is not yet implemented. But a lot of what needs to be done
> is in GIMP 2.0 already. There's really no good reason not to use GIMP
> 2.0.
I would love to. I tried to install the rpm for fedora core 1 but it didn't
work. I also tried to compile it but I've very busy now. I will try ag
Hi,
Oscar Picasso <[EMAIL PROTECTED]> writes:
> I use the script-fu-server and came across this remark at
> http://people.westminstercollege.edu/students/d-b1649/linux/gimp_server.html
>
>
>
> Adding a Queue
>
> Because the Gimp was not originally designed as a server, it does
> not follow so
Hi,
I use the script-fu-server and came across this remark at
http://people.westminstercollege.edu/students/d-b1649/linux/gimp_server.html
Adding a Queue
Because the Gimp was not originally designed as a server, it does not follow
some conventions that are necessary for such a mode. This inclu
