On 20 June 2012 22:04, Jay Smith j...@jaysmith.com wrote:
People seem to learn best from adversity. If you corrupt your own image
file and did not make a pre-editing backup copy, you just might learn
something. However, if that same user is protected from doing something
stupid, then the
On 06/21/2012 12:48 AM, Tobias Oelgarte wrote:
All i would ask for is that the Save Image Dialog will always default
to *.xcf, but still would provide some quick way to save (export) to
another format at choice. At the moment i often find myself (purely out
of habit, which isn't only Gimps
On 21/06/12 10:20, Thorsten Wilms wrote:
You already mentioned habit. Having such an option would allow you to
keep what is now a bad habit (to not discern between saving the work and
exporting), instead of forming a new, productive one.
IMHO the distinction between saving and exporting is an
Von: Ben Harrington-Ellsmore adamantium...@hotmail.co.uk
Hi I have been trying to work out how to get Gimp to only show fonts from
the user/fonts file rather than the vast amount of system fonts can anyone
point me at the code section I need to start mucking about with?
Have you exhausted
Am 21.06.2012 10:20, schrieb Thorsten Wilms:
On 06/21/2012 12:48 AM, Tobias Oelgarte wrote:
All i would ask for is that the Save Image Dialog will always default
to *.xcf, but still would provide some quick way to save (export) to
another format at choice. At the moment i often find myself
On Thu, Jun 21, 2012 at 12:48 PM, Karl Günter Wünsch wrote:
BTW: I asked a few of my friends (who are less into image editing but
well capable of using a computer and who at most only knew the GIMP by
name) what export was supposed to mean and they all responded that it
was the use of
On Thu, Jun 21, 2012 at 10:46 AM, Ben Harrington-Ellsmore wrote:
Hi I have been trying to work out how to get Gimp to only show fonts from
the user/fonts file rather than the vast amount of system fonts can anyone
point me at the code section I need to start mucking about with?
Which version
On 21/06/12 12:02, Alexandre Prokoudine wrote:
On Thu, Jun 21, 2012 at 12:48 PM, Karl Günter Wünsch wrote:
BTW: I asked a few of my friends (who are less into image editing but
well capable of using a computer and who at most only knew the GIMP by
name) what export was supposed to mean and
On Thu, Jun 21, 2012 at 2:31 PM, Karl Günter Wünsch wrote:
BTW: I asked a few of my friends (who are less into image editing but
well capable of using a computer and who at most only knew the GIMP by
name) what export was supposed to mean and they all responded that it
was the use of external
Alexandre wrote:
P.S. Why is it a gimp-developer@ list material?
I directed him here, because he wants to solve it in code.
--ps
founder + principal interaction architect
man + machine interface works
http://blog.mmiworks.net: on interaction architecture
On 21 June 2012 10:48, Karl Günter Wünsch k...@mineralien-verkauf.de wrote:
On 21/06/12 10:20, Thorsten Wilms wrote:
You already mentioned habit. Having such an option would allow you to
keep what is now a bad habit (to not discern between saving the work and
exporting), instead of forming a
In fact it kills the motivation of developers who are
putting sizable parts of their life into creating, maintaining and
improving GIMP. When you kill motivation in volunteer-driven project,
you are not just destroying someones hobby - the project will
eventually stagnate, wither and die.
Oh
On Thu, Jun 21, 2012 at 2:59 PM, Monty Montgomery wrote:
I was happy to hold my tongue until this. The developers are
*victims* of users being unhappy with a design decision?
Well, there's always been a certain pressure on the team. It comes
with maintaining a popular product. And since GIMP
On Thu, 21 Jun 2012 12:51:36 +0200
Jon Nordby jono...@gmail.com wrote:
With these current facts, I do not think we shall try to deceive the
user into thinking that save and export is the same. They are not and
the consequence for mixing them up can result in a loss of data. None
of these facts
On 21 June 2012 12:59, Monty Montgomery xiphm...@gmail.com wrote:
In fact it kills the motivation of developers who are
putting sizable parts of their life into creating, maintaining and
improving GIMP. When you kill motivation in volunteer-driven project,
you are not just destroying someones
On Thu, 21 Jun 2012 14:40:09 +0400, Alexandre Prokoudine wrote:
On Thu, Jun 21, 2012 at 2:31 PM, Karl Günter Wünsch wrote:
BTW: I asked a few of my friends (who are less into image editing but
well capable of using a computer and who at most only knew the GIMP by
name) what export was
My intent was to say that a volunteer project is driven mostly by the
motivation of the contributors, and that the feedback from users can
be a major driver in this.
Yes. I assume the developers have strong feedback from users who do
like the change. Here, though, we're hearing from users
On Thu, Jun 21, 2012 at 4:33 PM, Robert Krawitz wrote:
Think in physical terms.
There's no way I will think about files in physical terms. It doesn't
make any sense whatsoever and it's going to only to complicate an
already annoying discussion.
I hereby resign from this thread.
Alexandre
Von: Alexandre Prokoudine alexandre.prokoud...@gmail.com
Well, there's always been a certain pressure on the team. It comes
with maintaining a popular product. And since GIMP is not a commercial
product, there's no support service between developers and users to be
shouted at.
And the few
From: pe...@mmiworks.net
Date: Wed, 20 Jun 2012 17:58:33 +0200
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Bring back normal handling of other file
formats
Richard Gitschlag wrote:
So if I may throw an echo into the room and ask why the particular message
Now I remembered what I wanted to say earlier. I can't remember in response to
whom exactly, but here goes.
Save must record everything that is part of the document; that is the law.
That law also works in reverse.
If you write to a file format that cannot support everything in the
open
Von: Richard Gitschlag strata_ran...@hotmail.com
-- why is that? If you were working on an XCF file and make a significant,
possibly destructive change (like changing to indexed-color mode), there
is no mechanism to protect you from accidentally selecting Save if you
really meant Save As,
The first time I encountered the new export/save options, for some
reason I got angry. Odd, don't you think, getting angry at an
interface?
At one point I needed to open 9 screen-saved pngs in order to zealous
crop the margins and export back to the original pngs. Dismissing the
persistent save
On 06/21/2012 10:58 AM, Elle Stone wrote:
It also might ease the pain of transitioning to a new way of doing
things if Save read as Save xcf, Save a Copy read Save xcf
Copy, xcf serving as a gentle reminder of what will really will
happen.
+1
___
Elle wrote:
There is one little interface change that would make things easier for
me. I'll suggest it, most tentatively. At present, the order in the
Gimp 2.9 drop-down menu is Save, Save as, Save a Copy, Revert, then a
big line in the sand, then Export to, Export, Create Template (I
can't
Am 21.06.2012 19:58, schrieb Elle Stone:
The first time I encountered the new export/save options, for some
reason I got angry. Odd, don't you think, getting angry at an
interface?
At one point I needed to open 9 screen-saved pngs in order to zealous
crop the margins and export back to the
On 6/21/12, Tobias Oelgarte tobias.oelga...@googlemail.com wrote:
I entirely agree with the observation that the export entry in the
menu is badly positioned. It really disappears between the icon heavy
save and print sections, which really seduces me to accidentally
switch off my brain and
El 21/06/12 20:22, Elle Stone escribió:
On 6/21/12, Tobias Oelgartetobias.oelga...@googlemail.com wrote:
I entirely agree with the observation that the export entry in the
menu is badly positioned. It really disappears between the icon heavy
save and print sections, which really seduces me to
28 matches
Mail list logo
