* John Beppu <[EMAIL PROTECTED]> [020309 11:20]:
> [ date ] 2002/03/04 | Monday | 01:07 PM
> [ author ] Sven Neumann <[EMAIL PROTECTED]>
> > > with Gimp 1.2.3, and I read it can in fact be made to act like a
> > > server, startedwithout the GUI, passing it commands with the
> > > 'gimp-remote' program (which incidentally seems absent from my
> > > installation).
> > The only thing gimp-remote can do is to tell a running gimp to open a
> > specific file.
> I wrote a script called gimp-request which does what you (vio)
> thought gimp-remote would do. An interesting twist is that it
> lets you preprocess the Scheme code with Perl. I noticed you
> were a Python guy, but you might find the implementation to be
> interesting anyway.
Thanks for your message. You can be sure that I will have a look, and your
preprocessor sound intriguing.
> Instead of trying to bring the GIMP to the Web like you're proposing,
> I'm trying to make the GIMP and the Unix command line work together the
> way a Unix programmer expects to be able to.
On my front, after some intense work this week, I managed to embed a python
web server inside a Gimp module. In fact, I call it a Proxy server, because
all it does is listen to a port, then execute all data POSTed to it by some
web client, and return the result back to the client. That data this proxy
server receives from the client is hopefully 'only' Gimp scripts (python-based).
Because it is a HUGE security hole into the system hosting the Gimp: a skilled
python programmer can run any python script he/she wants remotely and
anonymously, so potentially do a lot of damage on the host. It's a dirty little
hack. Still, it does execute Gimp commands (python-only) as I wanted,
and I guess I like to live dangerously.
Gimp-developer mailing list