> From: l...@holoweb.net
> To: for...@gimpusers.com
> Date: Thu, 5 Jul 2012 19:21:20 -0400
> CC: t...@gimpusers.com; gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] Thank you developers, for your patience.
>
> On Thu, 2012-07-05 at 12:23 +0200, eduperez wrote:
> >
On Thu, 2012-07-05 at 12:23 +0200, eduperez wrote:
> In my humble opinion, the "quid" of the question regarding the new
> save / export policy, relies on the fact that the new behaviour
> reflects a change in the intended audience for the project: the old
> "load JPEG + edit + save JPEG" serves per
Am 05.07.2012 12:23, schrieb eduperez:
[...] the old "load JPEG + edit + save JPEG" serves perfectly to a casual user,
who just needs a very basic image editor[...]
Disagreed. The length and the shape of the workflow doesn't tell
anything about the features of GIMP being used. You can use the
On Thu, 05 Jul 2012 12:23:52 +0200, eduperez wrote:
> In my
humble opinion, the "quid" of the question regarding the new save /
export policy, relies on the fact that the new behaviour reflects a
change in the intended audience for the project: the old "load JPEG +
edit + save JPEG" serves pe
On Mon, Jul 02, 2012 at 06:18:00PM +0400, Alexandre Prokoudine wrote:
[...]
> What I've learned is that no matter how patiently you explain things
> or how carefully you choose words, someone somewhere will always get
> things utterly wrong, overreact and annoy.
Yes that is a fact. Just accept it.
On Mon, Jul 2, 2012 at 6:40 PM, Richard Gitschlag wrote:
>> ...the discussion that isn't supposed to be happening anyway, given the
>
>> already explained status quo, which is: we will neither revert, nor make
>> it optional".
>>
>
> The "not make it an option" part is the part I just don't get.
>
> Date: Mon, 2 Jul 2012 18:18:00 +0400
> From: alexandre.prokoud...@gmail.com
> To: gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] Thank you developers, for your patience.
>
> ...the discussion that isn't supposed to be happening anyway, given the
> already expl
On Mon, Jul 2, 2012 at 5:20 PM, Daniel Smith wrote:
> I've been reading a lot of these down the nose "developer vs user"
> emails for what seems like a year now? And it strikes me how much this
> I guess is really a possible byproduct of open source development,
> though I think there are many OS p
On Jul 2, 2012 9:21 PM, "Daniel Smith" wrote:
>
> I've been reading a lot of these down the nose "developer vs user"
> emails for what seems like a year now? And it strikes me how much this
> I guess is really a possible byproduct of open source development,
> though I think there are many OS pack
I've been reading a lot of these down the nose "developer vs user"
emails for what seems like a year now? And it strikes me how much this
I guess is really a possible byproduct of open source development,
though I think there are many OS packages, Red Hat, Ubuntu etc that
are committed to "customer
* Johannes [01-01-70 12:34]:
>
>
> I can live with the new process, too. The only thing I am missing is to
> do the "Exit (close without saving)" step directly (after having
> overwritten the original BMP/JPEG/PNG/whatever).
>
> At the moment, "Exit (close without saving)" is a "two-step" step:
Am 02.07.2012 01:22, schrieb Bob Long:
>
> I'm a light-weight user (Windows). The most common process I do is:
>
> Drag a BMP image into GIMP.
> Crop using fixed aspect ratio - very handy for my purposes.
> Scale image.
> File|Overwrite
> Exit (close without saving).
>
> I'm not negating the f
Johannes wrote,
Am 01.07.2012 11:55, schrieb Dave Helgert:
I greatly appreciate the new save/export features of Gimp. It simplifies my
workflow greatly as I often save/export as both jpg and xcf. I realized the
benefits of saving to xcf the hard way and now save important steps as hidden
lay
Re: [Gimp-user] Thank you developers, for your patience.
On Sun, Jul 1, 2012 at 8:09 PM, houghi wrote:
>> > Also I would be interested in knowing if the
>> > default can be changed easily. e.g. I always work with jpg files.
>>
>> It can't.
>
> Well, that se
On Sun, Jul 1, 2012 at 8:09 PM, houghi wrote:
>> > Also I would be interested in knowing if the
>> > default can be changed easily. e.g. I always work with jpg files.
>>
>> It can't.
>
> Well, that seriously sucks. From how I read it, it is because of what GIMP
> wants, not what the user wants.
T
On Sun, Jul 1, 2012 at 6:43 PM, houghi wrote:
>> > If the "no's" you mentioned have been lacking arguments like this "no",
>> > then it's not surprising that the community keeps pushing.
>>
>> First of all, the community isn't pushing. You are not the community,
>> nor few dozens of people are.
>
On Sun, Jul 1, 2012 at 2:59 PM, Johannes wrote:
> If the "no's" you mentioned have been lacking arguments like this "no",
> then it's not surprising that the community keeps pushing.
First of all, the community isn't pushing. You are not the community,
nor few dozens of people are.
Also, it _was
Am 01.07.2012 12:27, schrieb Alexandre Prokoudine:
> On Sun, Jul 1, 2012 at 2:24 PM, Johannes wrote:
>
>> Therefore I suggest to make the new "fool proof" workflow optional, so
>> everybody can be happy.
>
> This has been suggested before. The answer was "no" ever time and
> won't become a "yes"
On Sun, Jul 1, 2012 at 2:24 PM, Johannes wrote:
> Therefore I suggest to make the new "fool proof" workflow optional, so
> everybody can be happy.
This has been suggested before. The answer was "no" ever time and
won't become a "yes" no matter how actively you keep pushing.
Alexandre Prokoudine
Am 01.07.2012 11:55, schrieb Dave Helgert:
> I greatly appreciate the new save/export features of Gimp. It simplifies my
> workflow greatly as I often save/export as both jpg and xcf. I realized the
> benefits of saving to xcf the hard way and now save important steps as hidden
> layers so I can
20 matches
Mail list logo
