Re: [Gimp-developer] Re: whishes for Gimp
On Sunday 21 November 2004 09:29, Juhana Sadeharju wrote: From:Alan Horkan [EMAIL PROTECTED] Sven's point still stands though, adding more tools to the default toolbox is not a great idea. I agree completely, because I did not suggest that. We still need a system which allows us to add as many tools as needed to the tool pucket --- a tool plugin system (or extended existing plugin system) would help. You can hide non-default tools as deep in the system if you wish, but users should be able to have the tool they want and need. It just does not make sense to keep a user in doing things more complicated way only because somebody wants keep the tool number down to minimum or wants avoid alternative tools (being too similar to existing tools). Could existing plugin system be expanded so that the plugins may create the control objects as overlays to the image windows? One idea that is one of the pre-requisites for plugable tools is a way for plug-ins to receive pointer actions and coordinates. I have openned bug 140165 to track such idea and help develop it, hopefully over the next development cycle. ( http://bugzilla.gnome.org/show_bug.cgi?id=140165 ) We should refine the idea of a plug api for a tool to register itself as such, and possibly to make itself visible or not in the main toolbox. JS -- Juhana ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] open thumbnail and raw files
Hi, In most raw files the thumbnail exists as an embedded jpeg. I know how to read it to memory, but need advice on how to load it into gimp (i.e. create a valid image ID for it). Option a) Perhaps such functionality already exists - but I did not find it? Option b) Go through the file system - write a temporary file and load it via a PDB call. Option c) Use some jpeg library (say libjpeg) to read it. (b) is the probably the simplest, but I am not happy about going to the file system and all the issues it brings. On the other hand (c) is quite complicated. Can someone make a suggestion? Thanks, Joseph Sven Neumann wrote: Hi, a while ago Joseph Heled [EMAIL PROTECTED] wrote: The gimp Open Image dialog contains preview thumbnail. To generate them, gimp calls the plugin to generate them. Now, for raw digital camera files (.nef, .crw ...) this is a very expensive operation - and obviously one would love to use the prepared/pre-stored thumbnail which exists in the file. From what I could see, there is no way I (the plugin author) can detect if the call is for a thumbnail or not. Note that I have just added the missing API for plug-ins and also implemented the core functionality. What's missing now is some more plug-ins using this feature. See also http://bugzilla.gnome.org/show_bug.cgi?id=158190 http://bugzilla.gnome.org/show_bug.cgi?id=158191 http://bugzilla.gnome.org/show_bug.cgi?id=158192 http://bugzilla.gnome.org/show_bug.cgi?id=158193 Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] open thumbnail and raw files
Joseph Heled wrote: Option b) Go through the file system - write a temporary file and load it via a PDB call. (b) is the probably the simplest, but I am not happy about going to the file system and all the issues it brings. I wouldn't be too shy about it. The jpeg plugin itself (last I saw) does a similar thing when in 'preview' mode. Whatever works! --Adam ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] open thumbnail and raw files
Hi, Joseph Heled [EMAIL PROTECTED] writes: After some more digging, I think I will use gdk_pixbuf_loader Yes, why not. Seems reasonable since you can probably assume that the embedded thumbnail won't be too large. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp Perl/Server
Hi Stu, The behavior you are seeing is what happens if no Perl Server is running. The perl server is invoked automatically if you call a script on the commandline; it makes its own instance of gimp, and passes commandline parameters to get the perl server running. At the completion of the script, it all exits gimp and the perl server. If you run the Perl Server from the Xtns-Perl-Server menu from a running gimp, it should instead connect to the already running perl server and use your already open version of gimp. This should-do closer to what you want. If you want to start an instance of gimp and leave a perl server running, you'll need to use the batch parameter to gimp to start it: gimp-2.2 --no-interface -b '(extension-perl-server 0 2 0)' It should result in something like: 1101093297: server version 2 started 1101093297: acception connections on /tmp/gimp-perl-serv-uid-1000/gimp-perl-serv After this, any attempts to run a script from a commandline should first talk on the already-running server interface. Happy GIMPing, Seth (currently you'll have difficulties compiling gimp-perl CVS HEAD for 2.2; but a compilation for 2.0 should still work ok, even with 2.2. Will look into fixing this, and updating deprecated scripts, as time permits) On Sat, 20 Nov 2004 23:31:40 +, stu seven [EMAIL PROTECTED] wrote: I have some gimp-perl scripts_ all these work with the Perl Server... either from the interface, or command line... ...but currently, I get an error after one script is completed. For instance, with the command line version; I see the server start, and the message: accepting new connections, after this, one script can be processed successfully... but then, the server connection stops... to run another gimp-perl script, I need to start another invocation of the server... that doesnt seem right. ...how can I keep the server running... avoid restarting the perl server for each script ? ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
