Hi,
On Thu, 2008-06-12 at 02:09 +0200, [EMAIL PROTECTED] wrote:
No, i'm thinking of the case where you saved those 25 steps to a jpeg and the
next day,
sitting in the plane to your customer, you discover that this curve should be
tweaked a litte bit more.
That is exactly why JPEG should
On Thu, 12 Jun 2008 08:36:39 +0200, Sven Neumann [EMAIL PROTECTED] wrote:
Hi,
On Thu, 2008-06-12 at 02:09 +0200, [EMAIL PROTECTED] wrote:
No, i'm thinking of the case where you saved those 25 steps to a jpeg
and the next day,
sitting in the plane to your customer, you discover that this
Hi all,
Sven Neumann wrote:
[..] JPEG should not be offered as a save format. Saving
to a JPEG file is clearly an export.
this is totally true.
The problem is that this violates widely accepted UI standards.
Usability shows it's ugly side here by demanding conformance to
users' expectations
On Thu, Jun 12, 2008 at 10:56 PM, [EMAIL PROTECTED] wrote:
Dreaming of Adam's Pupus Pipeline[3] for nearly a decade now, i doubt
the upcoming GEGL goodness will fill in that role anytime soon.
GEGL is basically Pupus, it doesn't do network transparent buffers
yet, but it has an infrastructure
Hi all,
Carl Karsten wrote:
proposed spec:
File Open/Save/Save_as_Copy only work on .xcf - all other formats must use
File Import/Export.[1]
What about using just Import/Export?
The GIMP could take care of saving automatically, e.g. by writing XCFs to a
private folder.
Import/Export work
[EMAIL PROTECTED] writes:
3) Putting Text on a .png (in-place file editing)
- Open bla.png
- Text layer created
- Export to bla.png exporting to currently opened file is
admittedly ugly, but
consistent. The image stays