Re: [Gimp-developer] Save + Export proposal
[Looks like every time I post, I kill the list. My apologies; reposting] On 2009-10-05, photoco...@gmail.com wrote: > So why do not offer a chance to speed up the workflow, save time and > patience > achieving both result simultaneusly ? > > A image is worth 1.000 words ,to avoid misunderstunding i invite to give a > look to this > mock up > http://farm3.static.flickr.com/2653/3981269891_998c2f513b_o.jpg Suppose you do this. You edit something, and press C-s. What would happen? Ilya ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Save + Export proposal
On Tue, Oct 20, 2009 at 11:02 AM, peter sikking wrote: > so that is why I am against this. > > --ps Even that said, anyone is free to develop a save and export plugin and offer it up for public consumption. It may not make it into the core, but assuming it is worthwhile, it will find use. -Rob A. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Save + Export proposal
photocomix wrote: > i knew that Peter Sikking (or somebody else from Gimp UI brainstorm > staff)replied but the message get lost for technical problems (full > storage > disk) yes, I am (by default) the Gimp UI brainstorm staff, and I had about 3 threads going on here before the list collapsed. > I am very interested to know the content of that reply,i hope you > may send > again now here we go: OK, I waited with replying because I wanted to think about this carefully. that is because quite a few issues are combining here. first two fundamental issues: 1) let's face it: this is a new feature request. it is not that we broke something in this 50 pictures a day (10 minutes each) workflow. actually, on balance things got a bit better for this with clear saving and exporting. 2) an even bigger picture: does GIMP has to solve this problem? since part of what you want is a no-brainer conversion from png to jpeg. sounds like a job for a batch tool. this way you would save your GIMP file, then ctrl-shift-E, return, return, and GIMP does remember if you wanted TIFF or png all the time. run the batch job at the end of the day. so why not add it anyway, doesn't hurt no? yes it does: - by associating 2 or more export files, "Export to foo.png" (ctrl-E) has to be redesigned and never be as good as now. - you have coupled saving to exporting of multiple files, hard. in general these things do not happen at the same time, saving work is a different thing then delivering. write times go up by a factor of 1+N, where N is the number of export formats. - so it is easy to set (well, you will have to 50 times a day) but how to stop it for a file? it was in the Save dialog, but to get there again? Save as? - UI also needs to be not-error-inducing and give a clear model to users to how things work. this proposal here is one of several to get a litle bit of export back into the Save dialog. each of these creates _a_ way to export, that users may figure out as _the_ way to export, because they are migrating from 2.6 to 2.8. No, it does not help that we have clear Export on the File menu. we simply cannot let these models of export develop. so that is why I am against this. --ps founder + principal interaction architect man + machine interface works http://mmiworks.net/blog : on interaction architecture ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Save + Export proposal
On Mon, 2009-10-05 at 22:24 +0200, Martin Nordholts wrote: > Hi, > > On 10/05/2009 02:10 AM, photoco...@gmail.com wrote: > > But even if conceptually different in practice , both operation are always > > needed for the every edited image: > > is needed to Save the original AND to export as jpg or png . > > This assumption is wrong. Complex compositions will need to be refined for > weeks. All work is done in XCF. Before final delivery there is only an > occasional need to export to some other format. Actually the two statements don't contradict each other -- it's fair to say that the most likely workflows are (1) load image (jpeg. png, tiff, cr2, etc) work on image maybe save image in proprietary format temporarily, between sessions eventually, do at least one of . save in archive format (tiff, png) . export to jpeg or gif or .mov or whatever . print (2) create new image, and rest as above. And in most cases you'll need to export the image at some point, for every image. It's got a little harder to track what you've done, now, because you need to know if the export filenames are up to date as well as the xcf filenme, and right now you can't tell. E.g. an "image file history" panel showing save status, or adding save & export events to the undo history (even though you can't undo them they are part of the history) might help. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org www.advogato.org ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Save + Export proposal
Hi, On 10/05/2009 02:10 AM, photoco...@gmail.com wrote: > But even if conceptually different in practice , both operation are always > needed for the every edited image: > is needed to Save the original AND to export as jpg or png . This assumption is wrong. Complex compositions will need to be refined for weeks. All work is done in XCF. Before final delivery there is only an occasional need to export to some other format. / Martin -- Latest blog post Sunday, October 4, 2009: "Single-window mode progress report" My GIMP Blog: http://www.chromecode.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Save + Export proposal
photoco...@gmail.com wrote: ::snip? SNIP!:: > As you may see the idea is not to replace the Export dialog, but to offer a > handy option from the Save dialog, to simultaneously export , with same name > and in the same directory in other file formats Wouldn't this be fairly straightforward to do as a plugin/python-fu/script-fu? Adding code makes things slower. If this isn't something that would benefit the vast majority of GIMP users (and I'm not sure it would), it seems better to offer it as an option for those who want it, rather than to add extra code for the users who won't touch it. --xsdg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
