Re: [Gimp-developer] What happened to daily digests in Gimp mailing lists?
Hi Howard, On Tue, Apr 3, 2012 at 10:10 AM, Howard Caluma wrote: > Is there a way to make the mails sent to me appear as daily digest? Yes. It's in your subscription options in the mailman web interface. > Another problem is that > some replies are deleted, separated or not shown to me but is only received > by author of the topic. Is it in the reply and reply to all? What you mean is not clear, but, yes, if you happen to hit reply rather than reply to all, then the email goes only to the person you are replying to and not to the mailing list. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] What happened to daily digests in Gimp mailing lists?
Is there a way to make the mails sent to me appear as daily digest? I like the organization of topics with daily digest because they are listed first to give an overview and then packed in a single mail. Although this makes the mails very long, I still find reading them easy and enjoyable. The mails I receive contain only one topic each. The mails are short and filtering mails I want to keep is easy so it is also good. Another problem is that some replies are deleted, separated or not shown to me but is only received by author of the topic. Is it in the reply and reply to all? I am also subscribed to Gimp user list and have same concern. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gsoc - Slicing Tool
On Mon, 2012-04-02 at 15:47 -0300, Joao S. O. Bueno wrote: [...] > indeed - while those have lots os space for improvement, they rely on > using guide, previusly placed on the image, for knowing where to cut. I'm not sure this is a bad thing. For sure you need to be able to save the file, come back tomorrow, adjust the slices and redo. And the position of the slice boundaries is sometimes part of the image design. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gsoc - Slicing Tool
Hello yes, slicing tool has been wished for a while because it was a really needed tool the past ten years. It was made to help make a complete layout and then cut it into parts and produce resulting HTML+CSS+JS (rollovers aso). I see 2 reasons why it is not actually so essential : 1. Vectors are more and more used to draw site templates 2. With future coming with HTML5+CSS3+SVG, there will be very fewer to be done in a program like gimp, because everyting will be css (shadow, round-corners, animations...) IMO, Any slice tool development beginning now should take this future into account to make it usefull for the following years, and compliant with those new technologies. pygmee ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gsoc - Slicing Tool
On 2 April 2012 15:21, Alexia Death wrote: > On Mon, Apr 2, 2012 at 8:48 PM, gfxuser wrote: >> Hi, >> >> I might have overlooked something, but what's the difference to the already >> existing Image-Map filter (see Filters/Web/Image-Map) and Slice dialog >> (Filters/Web/Slice...)? > Plugins cant have on canvas controls. indeed - while those have lots os space for improvement, they rely on using guide, previusly placed on the image, for knowing where to cut. js -><- > > -- > --Alexia > ___ > gimp-developer-list mailing list > gimp-developer-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gsoc - Slicing Tool
On Mon, Apr 2, 2012 at 8:48 PM, gfxuser wrote: > Hi, > > I might have overlooked something, but what's the difference to the already > existing Image-Map filter (see Filters/Web/Image-Map) and Slice dialog > (Filters/Web/Slice...)? Plugins cant have on canvas controls. -- --Alexia ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gsoc - Slicing Tool
Hi, I might have overlooked something, but what's the difference to the already existing Image-Map filter (see Filters/Web/Image-Map) and Slice dialog (Filters/Web/Slice...)? The first filter already has possibilities to make rectangular, circular or polygonal selections plus options for the URL or frame to jump to and Javascript event options. The map itself can be saved, too. Wouldn't that be a duplication of functionality? If not, maybe these already existing possibilities build a foundation for the "new slicing tool" and can partially be reused? Greetings, grafxuser ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gsoc - Slicing Tool
noob7 wrote: > Hey there! > Iam interested in this year gsoc. I would like to take slicing tool idea > which I heard that its one of most requested features. I get the main conept > of this tool. Ive tested guillotine action and slice filter on compiled trunk > version. I found that slice filter still have some issues. On irc I was told > to talk to ,,guiguru" which is mitch? about gui for this tool. Do you have > any comments about slice tool ? I would love to hear some feedback. this one has been brewing for a long time. Let's have look what is minimally needed and then you can gauge if you are up for this: let's call this tool ‘cutting mask’, because that what it is. it is a glorious export function, so it should live in the File menu. there needs to be a setup of the cutting mask and and execution of the cutting mask (the mass export). just to make this clear: in the UI the cutting mask has nothing to do with the guides, is not a layer nor a channel (which are saved selections, really). how you do it on the _inside_, technically, is fully up to you, your mentor and mitch. the cutting mask (let's say one per file, to keep it simple) is a mask that consist of any number of rectangles (again, simple and practical). these rectangles are vectors (can be changed for ever) and can overlap. the size of the cutting mask is that of the canvas (unless somebody protests). when the setup of the cutting mask is invoked, the mask is drawn over the canvas and rectangles can be added, deleted and edited. setting the position and size of each rectangle is both interactive on the mask and via numerical input. this can work a lot like the rectangle selection tool does (I expect that code can be reused for that). but: it is _not_ the rectangle tool does the actual editing. it is the property of the mask setup mode that working with these vector rectangles is highlighting one, dragging its handles or changing its coordinate numbers. also minimally needed in setup mode is that for each rectangle a filename and type is specified by users. the mask setup is OK'ed or cancelled and the mask projection ‘folds away.’ executing the cutting mask means users setting a folder name and location (via a file dialog). this folder will be created and all the files end up in it. overwrite existing folder if users wish to do so. users set in the same dialog whether to cut the current layer or a merge of all visible layers. the export settings for each file type that is in the mask (png, jpeg, tiff, the list goes on) must be set for each execution of the mask. I propose to keep things simple and do one setting dialog for each file type present on the mask and apply to all files of that type in the cut. file name clashes should be dealt with automatically. I think this is a nice beginning of a tool like this. yes, a lot more advanced feature could be added, but this is the core of it. --ps founder + principal interaction architect man + machine interface works http://blog.mmiworks.net: on interaction architecture ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Get currently active image in python
On 23 March 2012 15:06, Chris Mohler wrote: > On Fri, Mar 23, 2012 at 12:51 PM, Jon Decker wrote: >> Thanks for the reply. I do realize that the current image and drawable is >> passed to the plugin when first opened. Perhaps I should explain further. >> I'm trying to build more of an extension that is opened just once, and >> updates as you move from image to image. (Its a time tracking window which >> stays open along side gimp). I wanted to make it so that a new instance of >> the plugin doesn't have to run for each image - just open it once, and it >> "knows" which image is currently active so that it can populate my sqlite >> database. >> >> Is there a way to do this at in in gimp? No, there is not - at least no clean ways that I can think of. There is nothing on the GIMP's API that marks an image as the currently active image.(The "unclean way" I can think of would mean to use GTK+ instrumentation for GUI debugging to be able to introspect active windows, and infere the active image from its title) Another "unclean", but tidier, way would be to create a very simple script, with no parameters but "image and drawable" that would just signal your main plug-in when called - and you could bind it to a shortcut key and press it everytime you switch the active image. To notify your mainplug-in you could use some file-system signaling mechanism, xmlrpc, or some gtk+ mechanism.. I'd use this second approach. > > I'm not sure (reposting to list - be sure to 'reply-all' vs just 'reply'). > > Chris > ___ > gimp-developer-list mailing list > gimp-developer-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
