On 08/07/2012 05:52 PM, Alexandre Prokoudine wrote:
The usability team spent quite a while writing all the reasoning down
at gui.gimp.org. I don't really understand why we need yet another
long thread to go through all these things yet again.
Alexandre Prokoudine
Alexandre,
IMHO the answers
On 08/07/2012 04:59 PM, Anoko wrote:
On Tue, Aug 7, 2012 at 10:49 PM, Anoko wrote:
The explanation page says "In other words, GIMP used to assume
that you don't mind accidental loss of unrecoverable project data and
bothered you with confirmation dialogs. It was a convoluted logic,
but people
On Wed, Aug 8, 2012 at 1:42 AM, Anoko wrote:
> Its wrong because users don't think that way?
What users? :)
The are no "users in general". There are all sorts of workflows and
uses for applications. There are all kinds of users too.
The kind of users we are targeting, mostly understand and acce
On Wed, Aug 8, 2012 at 1:10 AM, Rob Antonishen wrote:
> And this is where your use case is wrong! The whole point of separating save
> and export is that ONLY save is "safe". An export is NOT guaranteed to be
> either safe or lossless. It may be, depending on the source image. Your
> example e
On Wed, Aug 8, 2012 at 12:59 AM, Anoko wrote:
> I understand that you are bored of the discussion, but by
> suggesting that it is my problem alone of seeing it wrong,
> I think that's a bit insulting and really unnecessary.
Well, what if it _is_ your problem alone? I could wrap that up in a
cheer
> I suspect though that you have misunderstood my use case.
>
>User: lets say he wants so save image with transparance as jpg, clicks save
>Gimp: you have to use export
>User: Export to jpg
>Gimp: ok! (no message that transparance got lost)
>User: click exit
>Gimp: Sure? not saved!
>User: uh, I jus
On Tue, Aug 7, 2012 at 10:49 PM, Anoko wrote:
> However, I do not understand why no one discusses a compromise
> that does neither enforce nor burden exporting.
The secondary workflow _is_ the compromise.
> Are the developers really willing to give up a "part" of their users for
> something whic
On Tue, Aug 7, 2012 at 8:49 PM, Anoko wrote:
> I do not see why this is solved. Someone who is not familair with GIMP, that
> wants to store something as a png file, clicks save, finds it needs to
> export, clicks export and has lost their layered data nevertheless, now
> basically without a wa
We have found that logic does not apply here. The only allowed interactions
are those approved by the developers.
On 8/7/2012 2:23 AM, Anoko wrote:
2012/8/6 Anoko:
I've seen the new "you have to use export" messagebox about 20 times now, very
annoying ;-). Why is it not OK to allow saving
> You are "hung up* on a single word, "save" vs "export". Change
your key
> bindings to match what *you* want.
Totally agreed. The
criticism to the new behaviour is quite bureaucratic.
___
gimp-user-list mailing list
gimp-user-list@gnome.org
https
> Date: Tue, 7 Aug 2012 11:23:49 +0200
> From: for...@gimpusers.com
> To: gimp-user-list@gnome.org
> CC: t...@gimpusers.com
> Subject: [Gimp-user] HATE the new save vs. export behavior
>
>
Well habbits or not, I still wonder why it is explicitly disallowed to
save as something other than xcf. A
* Anoko [08-07-12 05:25]:
> >2012/8/6 Anoko :
>
> >> I've seen the new "you have to use export" messagebox about 20 times
> >> now, very annoying ;-). Why is it not OK to allow saving to e.g.
> >> png (especially when not using layers!), but keep the export function
> >> ALSO as it is? That wa
On Tue, Aug 7, 2012 at 1:23 PM, Anoko wrote:
> GIMP is not the only program I use, so yeah I keep pressing CTRL+S
> thinking that should save whatever I'm editting to whatever file extension
> I gave it, just like in Inkscape, Libreoffice, KDevelop, etc.
Inkscape does it wrong too, and the plan i
On 07.08.12 at 11:23, Anoko wrote:
2012/8/6 Anoko :
I've seen the new "you have to use export" messagebox about 20 times now, very
annoying ;-). Why is it not OK to allow saving to e.g. png (especially when not using
layers!), but keep the export function ALSO as it is? That way, everyone will
On Tue, Aug 7, 2012 at 2:30 PM, Olivier wrote:
> 2012/8/6 Anoko :
>> I just want to add I'm also not happy with the new export vs save feature. I
>> use GIMP for all my edit tasks; from complex foto editting to really simple
>> screenshot taking and trimming it slightly. I used to love it for bo
2012/8/6 Anoko :
> I just want to add I'm also not happy with the new export vs save feature. I
> use GIMP for all my edit tasks; from complex foto editting to really simple
> screenshot taking and trimming it slightly. I used to love it for both,
> especially since it GIMP can do both small and
> Date: Tue, 17 Jul 2012 21:27:59 +0200
> From: for...@gimpusers.com
> To: gimp-user-list@gnome.org
> CC: t...@gimpusers.com
> Subject: [Gimp-user] HATE the new save vs. export behavior
>
> (JPEG and RTF are both low-quality editable formats which lose
> data/formatting, compared to the native X
Kasim did state "12-year-old" so let's just let that slide, shall we? BTW this
also means that between the age of your students now and the way Kasim says
bobbo is acting, I'd say you still have one good year. :)
Top posting is just so unnatural (at least for me). Think how that relates to
the
As someone who teaches 11 year old kids, I can safely say you're not being
fair to the kids, they're generally more nature than that.
On Jul 1, 2012 12:19 AM, "Kasim Ahmic" wrote:
> Seriously? I don't like the Save vs. Export thing any more than you or
> anyone else here but instead of discussing
Seriously? I don't like the Save vs. Export thing any more than you or anyone
else here but instead of discussing it normally you complain about it like a 12
year old. Call me crazy, but I'm pretty sure that's not the way to get your
opinions noticed...
Sent from my iPod
On Jun 30, 2012, at 11
On Sat, Jun 30, 2012 at 7:15 PM, bobbo wrote:
> Dear GIMP developers, you have shittiet GIMP even more with your retarded
> ideas about how we should save our files.
>
> And please, any "hurr designerrrs" don't counter me with GIMP saving dialog
> paradigm- what's going on is developers trying to
On Friday, June 22, 2012 04:10:27 Alexandre Prokoudine wrote:
> On Fri, Jun 22, 2012 at 3:28 AM, Oon-Ee Ng wrote:
> >> UPS delivery or email?
> >
> > Please, don't be rude to such an esteemed and valuable former member
> > of this community. A personal visit is the only satisfactory solution
> > h
On Sat, Jun 23, 2012 at 1:47 PM, Marco Ciampa wrote:
> So GIMP devs, hip hip hooray, go on the great job!
> You will never know how some users are grateful to you!
You've just given a pretty good idea :)
Alexandre Prokoudine
http://libregraphicsworld.org
_
On Fri, Jun 22, 2012 at 02:58:07PM -0700, Richard Gitschlag wrote:
[...]
> .. which gives me a laugh every time I hear the argument that GIMP is
> not intended to be a Photoshop clone. Sure that may be true, but isn't
> it true that the line between GIMP and Photoshop gets narrower with
> every ne
> Date: Fri, 22 Jun 2012 06:14:30 +0200
> From: for...@gimpusers.com
> To: gimp-user-list@gnome.org
> CC: t...@gimpusers.com
> Subject: [Gimp-user] HATE the new save vs. export behavior
>
> Isn't Gimp still open source? Hasn't one of the many great things about OSS
> always been that you can hac
> On Fri, Jun 22, 2012 at 8:10 AM, Alexandre Prokoudine
> wrote:
>> On Fri, Jun 22, 2012 at 3:28 AM, Oon-Ee Ng wrote:
>>
UPS delivery or email?
>>>
>>> Please, don't be rude to such an esteemed and valuable former
>>> member
>>> of this community. A personal visit is the only satisfactory
>>
On Fri, Jun 22, 2012 at 8:10 AM, Alexandre Prokoudine
wrote:
> On Fri, Jun 22, 2012 at 3:28 AM, Oon-Ee Ng wrote:
>
>>> UPS delivery or email?
>>
>> Please, don't be rude to such an esteemed and valuable former member
>> of this community. A personal visit is the only satisfactory solution
>> here
On Fri, Jun 22, 2012 at 3:28 AM, Oon-Ee Ng wrote:
>> UPS delivery or email?
>
> Please, don't be rude to such an esteemed and valuable former member
> of this community. A personal visit is the only satisfactory solution
> here
Now I'm getting confused: which of us two is being ironic?
> after a
On Thu, Jun 21, 2012 at 6:12 PM, Alexandre Prokoudine
wrote:
> On Thu, Jun 21, 2012 at 12:10 PM, CoreForce wrote:
>
>> The new save feature is not user friendly and it just kills productivity.
>> I can see no other purpose of it other than a political game.
>> Because of that, GIMP just lost me af
On Thu, Jun 21, 2012 at 12:10 PM, CoreForce wrote:
> The new save feature is not user friendly and it just kills productivity.
> I can see no other purpose of it other than a political game.
> Because of that, GIMP just lost me after 10+ years of heavy use.
> I've switched over to Pixelmator.
> Pl
On 05/31/2012 04:04 AM, darnkitten wrote:
I sell LibreOffice, by pointing out that not only can it OPEN almost everything,
including DOCX and old Works files, It also allows the option of setting default SAVES
defaults to DOC --which can be read by everyone-- though with a "you will lose
forma
On 5/30/2012 8:04 PM, darnkitten wrote:
Late to the discussion:
...this thread simply will not die. lol...
___
gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list
Jonathan Kamens wrote:
>I hate the new Save vs. Export behavior. It is completely non-intuitive to me,
>it makes my brain stumble every time
>I try to do just about any of the things that I do in GIMP on a regular basis,
>and it makes most of my workflows take more thought and more button click
> Date: Wed, 16 May 2012 14:38:43 +0200
> From: si...@budig.de
> To: gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] HATE the new save vs. export behavior
>
> If you use CTRL-E for "Export to " (which is available after
> the first export after saving to xcf)
Johan Vromans (jvrom...@squirrel.nl) wrote:
> One thing I do, however, slightly agree with you. When for example
> working on a PNG, saving it (as XCF), and then export repeatedly as PNG
> I wonder whether it should ask *every* *time* if it's okay to overwrite
> the file.
If you use CTRL-E for "Ex
Sicofante writes:
> “Save” means “overwrite the original file”, period
This is true for applications that simply on a specific file and can
store/restore all relevant informatin the that file format. This is,
indeed, the majority of applications.
However, several applications that deal with mor
On 05/16/2012 10:13 AM, Sicofante wrote:
“Save as…” means “save to a new file with a different name and/or format”.
“Export” means “put the contents of the current document in a file of a nature
this app isn’t intended to handle”. (At the same time “Import” means “bring
data from an alien file
On Sun, 06 May 2012 23:24:04 -0400
Steve Kinney wrote:
> On 05/06/2012 10:51 PM, John Coppens wrote:
>
> > -When starting to edit, why not immediately do a Save as xxx.xcf?
>
> That's what I do and it has come in very handy.
>
> > -Why not add (to Gimp) the possibility to maintain an autosave
Hi,
ad...@pilobilus.net (2012-05-06 at 2324.04 -0400):
> > -Why not add (to Gimp) the possibility to maintain an autosave copy
> > in (.XCF format) each N minutes? And not delete it for X days?
>
> I would not use that. For instance, just a couple of minutes ago I
> opened an XCF file, merged se
On 05/06/2012 10:51 PM, John Coppens wrote:
> -When starting to edit, why not immediately do a Save as xxx.xcf?
That's what I do and it has come in very handy.
> -Why not add (to Gimp) the possibility to maintain an autosave copy
> in (.XCF format) each N minutes? And not delete it for X days?
On Sat, 5 May 2012 12:32:22 +0400
Alexandre Prokoudine wrote:
> > I'm not sure what this question means.
>
> The question should be understood literally :) Is GIMP the only tool
> to get your job done?
>
I wrote a couple of macros in Guile which help me, so Gimp is
my preferred tool, yes. Say
i also have modified this code:
*gimp base folder/app/paint/gimppaintoptions.c*
*#define DEFAULT_BRUSH_SIZE 50.0*
#define DEFAULT_BRUSH_ASPECT_RATIO 0.0
#define DEFAULT_BRUSH_ANGLE 0.0
*gimppaintoptions-gui.c*
*scale = gimp_prop_spin_scale_new (config, "brush-size",*
*_("Size"), **1, 1.0,
i have modified the sources...
2012/5/5 GSR - FR
> Hi,
> strata_ran...@hotmail.com (2012-05-04 at 2119.16 -0700):
> > > OTOH, I no longer have to worry about
> > > accidentally flattening my 10-layer composition when saving a PNG and
> > > then forgetting to resave as XCF.
> > > Chris
> > You sh
Hi,
strata_ran...@hotmail.com (2012-05-04 at 2119.16 -0700):
> > OTOH, I no longer have to worry about
> > accidentally flattening my 10-layer composition when saving a PNG and
> > then forgetting to resave as XCF.
> > Chris
> You should be saving your .xcf file first, THEN save the PNG copy of
> i
> Date: Sat, 5 May 2012 14:19:49 +0800
> From: ngoonee.t...@gmail.com
> To: for...@gimpusers.com
> CC: t...@gimpusers.com; gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] HATE the new save vs. export behavior
>
> ... (single-window on a tiling WM, whee!!)
Speak
On Sat, May 5, 2012 at 10:33 AM, Alexandre Prokoudine
wrote:
> However I stlll find it highly disturbing that so many people felt
> that the project wasn't doing dccent PR work, and yet noone else
> volunteered. If I'm run down by a truck tomorrow, what is the
> community going to do about the lac
>
> Is it really that complicated to change the menus
> and dialog boxes or the existence of them based
> around user preferences?
> [...]
> Dan
> ___
> gimp-user-list mailing list
> gimp-user-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gimp
On Sat, May 5, 2012 at 10:04 AM, Jay Smith wrote:
> c) The developers UTTERLY FAILED to manage public relations on this. It was
> completely obvious to me (from monitoring the discussions on the developer
> list) that this subject was going to touch of an enormous storm of anger
> among some user
On Fri, May 4, 2012 at 11:19 PM, Richard Gitschlag
wrote:
> You should be saving your .xcf file first, THEN save the PNG copy of it.
> Priorities :)
Indeed. I also try to "Save As" every hour or so and bump up the
version of the XCF. Disk space is cheap ;)
But mistakes can happen, particularly
On 05/05/2012 10:30 AM, Alexandre Prokoudine wrote:
> We are not separating people into better of worse users, or the
> deserving and non-deserving, or entitled and not entitled. This would
> not be a constructive approach.
>
> What we _are_ doing is _focusing_ on a group of users who are
> under
On Sat, May 5, 2012 at 7:04 PM, Jay Smith wrote:
> c) The developers UTTERLY FAILED to manage public relations on this. It was
> completely obvious to me (from monitoring the discussions on the developer
> list) that this subject was going to touch of an enormous storm of anger
> among some users
I didn't mean for Gimp proper to offer different versions
or make it part of the program in preferences etc.
I meant where are the files that determine what the dialog
boxes and menus say, and where exporting and/or saving
are accomplished to? It can't be that hard, you're just talking
about meta f
On Sat, May 5, 2012 at 6:42 PM, Daniel Smith wrote:
> Is it really that complicated to change the menus
> and dialog boxes or the existence of them based
> around user preferences?
> Is there a link anywhere to how it's written?
> I can guarantee you that when I worked in a big
> graphics house the
On 05/05/2012 10:30 AM, Alexandre Prokoudine wrote:
On Sat, May 5, 2012 at 12:21 PM, Ken Warner wrote:
but many posts calling for civility have come from people who want to divide
the user base into two groups where one group is somehow more entitled to
use GIMP than the other because of the th
Personally I like these new changes. Alexander is quite correct about
that it is notfor not wanting "light users" but adding suport which was
not there for those in real need for something more. This something more
is that when you work with layers, lots of ioperations, you get all this
in the
Is it really that complicated to change the menus
and dialog boxes or the existence of them based
around user preferences?
Is there a link anywhere to how it's written?
I can guarantee you that when I worked in a big
graphics house they'd find a way to alter them.
Dan
__
On Sat, May 5, 2012 at 12:21 PM, Ken Warner wrote:
> but many posts calling for civility have come from people who want to divide
> the user base into two groups where one group is somehow more entitled to
> use GIMP than the other because of the things they do with GIMP.
You know, it's quite fru
On 05/05/2012 11:14 AM, Olivier wrote:
Just to add one more link to this long thread, do you remember when
the Toolbox menus disappeared? How many people whined or screamed
because this change ruined their way to use GIMP? How many people
spoke about MY workflow, MY habits, MY opinion about this
In general, I agree with you Archie. This discussion should be more civil but
many posts calling for civility have come from people who want to divide the
user base into two groups where one group is somehow more entitled to use GIMP
than the other because of the things they do with GIMP.
I f
Just to add one more link to this long thread, do you remember when
the Toolbox menus disappeared? How many people whined or screamed
because this change ruined their way to use GIMP? How many people
spoke about MY workflow, MY habits, MY opinion about this stupid
change, and threatened to stick to
On Sat, May 5, 2012 at 1:17 AM, John Coppens wrote:
> On Fri, 4 May 2012 09:52:32 +0400
> Alexandre Prokoudine wrote:
>
>> We don't know exactly what you do ing GIMP during those unsafe workflows.
>
> About 90% of the time I load PNGs or jpegs (100s of them), edit them,
> and save them back in th
The classic case of YMMV.
Some do love the new GIMP, while others prefer the old layout. Changes can be
pretty difficult for others but ... I would camp with Oon-Ee Ng when he wrote,
"and it took all of 2 sessions to get used to the change.
Face it. There are the GIMP users, and there are those
On Sat, May 5, 2012 at 11:56 AM, Lyle wrote:
> Yeah; file this decision under if it ain't broke, fix it anyway category.
> lol
>
> Maybe there is a method to the developer's madness, but I've yet seen the
> reason why. Doubt it will get changed back now though, so I've just
> accepted it, b
>
> For myself, export/overwrite still seems clumsy when working on
> simple, one-off edits. OTOH, I no longer have to worry about
> accidentally flattening my 10-layer composition when saving a PNG and
> then forgetting to resave as XCF. I'm thinking the long-term gain of
> not having to recre
Nothing like a flame war. Though I must say that I love these
"topics" cause it lets a lot of info out about how people have
their different workflows, etc. I'm on a Mac and thus relegated to 2.6
but I've leanred an awful lot from reading all said posts.
I really love this list and the helpful natu
On Fri, May 4, 2012 at 7:40 PM, Daniel Smith wrote:
> Can I ask if this decision to go to export vs. save, is it somewhat based
> around needs of people running gimp without the interface, as a server
> component?
No - it has to do with these two items, specifically:
http://gui.gimp.org/index.ph
Can I just ask Alexander Prokoudinea question then, since he's obviously
very tied to the project intimately?
Can I ask if this decision to go to export vs. save, is it somewhat based
around needs of people running gimp without the interface, as a server
component?
Just wondering.
Dan
Houston
_
So 2.8 saves the history as well?
Just wondering. On a Mac and still
looking...Course'n, it's a ppc mac so it probably
won't work even when they do offer...
Thanks.
Dan
On 5/4/12, jfrazie...@nc.rr.com wrote:
>
>
>> It certainly is not intuitive. The operation should be symmetrical: If I
>> open a
> It certainly is not intuitive. The operation should be symmetrical: If I
> open a PNG, save should save a PNG (unless I applied changes which would
> disappear if saved as a PNG, in which case I'd like a warning).
And that's the point, GETTING rid of the damn warnings! For me, every single
t
On Fri, May 4, 2012 at 4:03 PM, Steve Kinney wrote:
> On 05/04/2012 02:10 PM, Akkana Peck wrote:
>
>> And a fifth option: write a plug-in that does what you want Save to
>> do, perhaps involving gimp-file-save, and bind it to Ctrl-S.
>>
>> I don't like the new model either, but I'm going to work w
On Fri, 4 May 2012 09:52:32 +0400
Alexandre Prokoudine wrote:
> We don't know exactly what you do ing GIMP during those unsafe workflows.
About 90% of the time I load PNGs or jpegs (100s of them), edit them,
and save them back in the same format - I don't have any necessity for
XCF in these case
Alexandre,
That change is there for a reason. And the reason is that we are
trying to target a special group of users who have certain workflows
and work on files in certain ways.
As I said in my previous email, I understand the reasons and
fundamentally agree with the change, and I really do
On 05/04/2012 02:10 PM, Akkana Peck wrote:
> And a fifth option: write a plug-in that does what you want Save to
> do, perhaps involving gimp-file-save, and bind it to Ctrl-S.
>
> I don't like the new model either, but I'm going to work with it for
> a while and see if I continue to feel that way
kevin writes:
> I have already made my thoughts known - I don't like the new system.
>
> That said, I have three options: (1) adapt my work habits, (2) stay on 2.6.
> or
> (3) change the source.
>
> There is a fourth option: the dev's revert to the old functionality. But,
> clearly, this is no
On Fri, May 4, 2012 at 9:17 PM, Daniel Jensen wrote:
> My main reason for writing here is to warn about the elitist attitude
> starting to show itself, which would harm the project in the long run.
> Saying "Look, your use case means you might not understand the reasons
> behind our design decis
First off, I'll say that I understand the rationale for the newer
save/export behavior, and even if it needed to be tweaked a little to
provide a better user experience it's best for devs to see how people
adjust and look at how feedback develops over the next months rather
than simply giving u
> From: jvrom...@squirrel.nl
> To: gimp-user-list@gnome.org
> Date: Fri, 4 May 2012 08:28:36 +0200
> Subject: Re: [Gimp-user] HATE the new save vs. export behavior
>
> Richard Gitschlag writes:
>
> > It is true, however, that many professional and commercial apps do
>
> In short, it makes perfect sense to me that a high end bitmap editor
> should, by default, save in its native format and export to other
> formats.
>
> Just about every other program I know uses this pattern.
>
What about Adobe Photoshop? Or doesn't proprietary software count? because
that's
kevin wrote:
> I have already made my thoughts known - I don't like the new system.
>
> That said, I have three options: (1) adapt my work habits, (2) stay on 2.6.
> or
> (3) change the source.
>
> There is a fourth option: the dev's revert to the old functionality. But,
> clearly, thi
I have already made my thoughts known - I don't like the new system.
That said, I have three options: (1) adapt my work habits, (2) stay on 2.6. or
(3) change the source.
There is a fourth option: the dev's revert to the old functionality. But,
clearly, this is not going to happen.
Of the thre
Hi Alexandre,
On 04 May 12 06:52 Alexandre Prokoudine
said:
> The problem I see in this thread is that few people tell us exactly
> what they do and then complain that we don't do the right thing for
> them.
80% of the time I load a .jpg to make some minor edits (use the Curves
tool to adjust b
Thanks for asking, Alexandre!
1) Currently I'm using GIMP mostly (95% of the time) for photo
retouching. The rest is mostly image adjustment for scientific
visualization and for presentations. More complex works that need
multilayer etc.: only 2 last year.
2) Photo: I always start from RAW form
Alexandre Prokoudine writes:
> The problem I see in this thread is that few people tell us exactly
> what they do and then complain that we don't do the right thing for
> them.
Haven't tried 2.8 yet, but as I understand it:
- XCF is the native format for GIMP <-- GOOD
- everything else is an ex
Richard Gitschlag writes:
> It is true, however, that many professional and commercial apps do not
> make a save/export distinction and allow you to "save" your document
> in any supported filetype -- MS Word, for example. You can open/save a
> document in a non-native format at any time, all you
Ken Warner writes:
>Why are the GIMP developers interposing their own preferences on all
>the people who use and support GIMP? They are making this a much more
>complicated and contentious problem than it needs be
I have not used the newer version of GIMP yet, but I have to ask the same
questi
On Thu, May 3, 2012 at 11:11 PM, Maurice wrote:
> On Thursday 03 May 2012 14:48:47 Steve Kinney wrote:
>
>> Look into imagemagick. It
>> might be possible to fully automate all or a large part of that work.
>
> I already use Imagemagick's 'Convert' as the 1st part of my task, the
> 2nd part of wh
On Fri, May 4, 2012 at 7:26 AM, Richard Gitschlag wrote:
> The lack of an ability to "save" in any file type but GIMP's native XCF is a
> necessary drawback for the change, but I do agree that it is an
> uncomfortable one for many users (myself sometimes included).
>
> If you compare Inkscape, it'
On Fri, May 4, 2012 at 5:38 AM, Ken Warner wrote:
> Or instead of the GIMP developers assuming that the users of GIMP are too
> stupid to know what they want, they could just let the user make all the
> decisions in a modal fashion.
>
> If I start GIMP and generate a New file, bring up the usual fi
resave.
-- Stratadrake
strata_ran...@hotmail.com
--------
Numbers may not lie, but neither do they tell the whole truth.
> Date: Thu, 3 May 2012 18:38:08 -0700
> From: kwarner...@verizon.net
> To: a...@cphr.edu.cu; gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] HA
gt; From: maur...@bcs.org.uk
> To: gimp-user-list@gnome.org
> Date: Thu, 3 May 2012 15:53:31 +0100
> Subject: Re: [Gimp-user] HATE the new save vs. export behavior
>
> On Thursday 03 May 2012 10:15:29 Jay Smith wrote:
>
> > when editing a JPG, repeatedly
> > saving/exp
@hotmail.com
Numbers may not lie, but neither do they tell the whole truth.
+1 with this
this seems to be the best approach I've seen in this discussion
Alex
> From: maur...@bcs.org.uk
> To: gimp-user-list@gnome.org
> Date: Thu, 3 May 2012 15:53:31 +0100
>
On Thursday 03 May 2012 14:48:47 Steve Kinney wrote:
> Look into imagemagick. It
> might be possible to fully automate all or a large part of that work.
I already use Imagemagick's 'Convert' as the 1st part of my task, the
2nd part of which needs Gimp.
--
/\/\aurice
In 05/2012 a lot of people wrote:
> Wait, the Save dialog changed? OH NOES!!
My position can be guessed from the workflow I have followed since
somewhere the first ports of the GIMP to Win32 (Tor Lillqvist ruined
me for life):
1. Open an image file.
2. Save as .xcf
3. [everything else]
4. D
This is the 37th message in this series.
I love the "new" save vs. export behavior, which has existed for one
year and half now, and thus is not so new after all. I'm completely
accustomed to the simple idea that you don't save to Jpeg of PNG, you
export to these formats, and you save only to the
her do they tell the whole truth.
> From: maur...@bcs.org.uk
> To: gimp-user-list@gnome.org
> Date: Thu, 3 May 2012 15:53:31 +0100
> Subject: Re: [Gimp-user] HATE the new save vs. export behavior
>
> On Thursday 03 May 2012 10:15:29 Jay Smith wrote:
>
> > when ed
Hi,
p...@readiescards.co.uk (2012-05-03 at 0703.06 +0100):
> My use case: I use GIMP for its mult-layer features, creating images from
> scratch and I want to save all my work in this multi-layer format (XCF) but
> I need to send draft versions and the finished image to
> friends/customers/website
On Thursday 03 May 2012 10:15:29 Jay Smith wrote:
> when editing a JPG, repeatedly
> saving/exporting to JPG (your step 4) reduces the quality (actually
> compresses / deletes data).
Having been away I've just been reading this thread, and would like to
add my wish to those others who are
On 05/02/2012 08:45 PM, Jonathan Kamens wrote:
New way:
1. "gimp file.jpg".
2. Make changes.
3. Open File menu and select "Overwrite" (no keyboard shortcut for
that!).
4. Periodically type ctrl-e to save further progress (because for
some inexplicable reason, once you use
Jonathan Kamens (j...@kamens.us) wrote:
> It seems clear to me at this point that either you are too invested
> in your work and backed into a corner at this point to be able to
> admit that there is any room for improvement, or you really /are/
> trying to drive away users who aren't part of your
On 05/03/2012 07:11 AM, Alexandre Prokoudine wrote:
In other words, just when we got rid of disruptive warnings you are
siggesting to return one of them and add another one so that the first
one wouldn't feel lonely? :)
No, in other words, if the user's intent isn't clear, the program should
/as
201 - 300 of 324 matches
Mail list logo
