Date: Thu, 09 May 1996 22:30:56 -0700 From: "Amancio Hasty Jr." <hasty@rah.star-gate.com> To: "Eric L. Hernes" <erich@lodgenet.com> Cc: multimedia@FreeBSD.org Subject: Re: tcl interface to GIMP? Message-ID: <199605100530.WAA00918@rah.star-gate.com> In-Reply-To: Your message of "Thu, 09 May 1996 15:08:36 CDT." <199605092008.PAA22122@jake.lodgenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
For starters o we should create the plug-ins as shared loadable modules that will eliminate the shared memory requirement. o Perhaps investigate using X11R6's XIE for storing images and manipulating them in the X server. o tcl interface plus a tk interface so we can create user friendly filters which can be modified at run time. The tcl/tk interface would just invoke actions on gimp The guild and perl approach is fine however you really want to have also a graphical interface to the scripting language. The origins of GIMP are in Lisp so it does not surprise me that its authors have chosen guild. Regards, Amancio > > Yesterday I looked through the gimp-list archives and it looks like > those guys want to use guile for the extension language. I'd much > prefer tcl, lisp is about the most un-intuitive language in the world > even more so than assembler ;-). > > They want the same functionality that you do, they just appear > to be mis-directed. I'd like to get gimp to spit out frames in > batch style so that I can roll them into an mpeg. I built one > with the whirl filter, but it's clumsy. > > Or were you thinking of writing a tcl program to call the plug-in > directly? I believe that the plug-ins use a shared-memory and pipe > protocol. I don't think that it'd be too tough to hack up a perl > interface to that, but it'd be hackery. > > BTW, I'm not trying to dig up a big language war here, just a few > observations... > > eric. > > "Amancio Hasty Jr." writes: > > > > > >Anyone upto writing a tcl interface for GIMP? > > > >The reason that I am thinking is to be able to write meta filters so > >with one single command we could create cut out text or customizable > >filters . For instance , a given filter could be presented with a set > >of options which could be easily modified at run-time. If we do this > >we will have one hell of an image processing program. The latest > >version of tcl supports sockets connection and it should be > >"a piece of cacke" to create a routine to listen and handle > >the socket communications. > > > >There is other stuff like converting GIMP to use XIE instead of > >shared memory which will make the program more user friendly at the > >system level. > > > >http://www.xcf.berkeley.edu/~gimp/ > > > > Tnks, > > Amancio > > > > > > > > -- > erich@lodgenet.com > http://rrnet.com/~erich erich@rrnet.com > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605100530.WAA00918>