Ingo Ruhnke wrote:
> On Sat, Jun 14, 2008 at 4:29 PM, <[EMAIL PROTECTED]> wrote:
> > The basic idea is to forbid 'Save' to PNG here.
>
> Which of course would be stupid, since PNG is a perfectly valid
> information-loss-free choice in many cases
err, that sentence was with regard to the example
[EMAIL PROTECTED] wrote:
> This is definately not a bug.
[..]
> Gimp does all these things correctly. It is aimed at a competant user
> base, it does not try to be a beginner's guide using different formats.
It is true that GIMP provides correct functionality for export/save.
The corresponding
Hi,
Akkana Peck wrote:
> [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
> >
Hi,
thank you all for taking the time to consider and being patient with me.
It seems what's lacking most is the virtue of patience on my side...
I understand now that multiple UIs are too expensive. (As a sidenote, the
forking
idea doesn't imply to anticipate the UI team's work. More appropriat
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 wo
sorry, the links got chopped off in my previous post:
[1] Why does the user have to Save to disk at all? Are there inevitable hardware
reasons why software can't take care of user's data? I don't think so.
And old story and quite outside GIMP's scope, of course:
http://jef.raskincente
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
Jon Senior wrote:
> [EMAIL PROTECTED] wrote:
>
> > What would a user interface look like for exporting undo history and
> > for merging the history with the image again?
> >
> > Are there already proposals for this?
>
> Just my take... is this not something that GEGL and the non-destructive
> editi
Hi,
Alchemie foto\grafiche wrote:
>
> gib_mir_mehl wrote:
> > Don't all those export troubles disintegrate once we presume a little
> > more confidence in the undo function?
>
> More confidence will require a option to save undo history.
>
> As it is no
Hi again,
here's the first correction:
in section Conversion Rules,
read 'common format affected' as 'one example of a format affected by this
dialog'.
The conversion rules are listed by the current dialogs' texts to present the
user's point of view.
These dialogs are triggered by format capab
Hi all,
here is a spec which claims to clean up the existent save/export features in a
consistent manner.
Problems addressed:
- insufficient protection from data loss regarding layer & alpha information.
This is considered a UI bug [7]. For an example see [1].
- too many dialogs which pop up i
Hi,
from the docs:
The export file dialog shows up if the image type does not match the format
capabilites.
If the user chooses 'Export', a suitably altered copy of the image is used for
saving.
If the user chooses 'Ignore', the image is fed directly to the save plugin
instead.
Are there examp
Sven Neumann wrote:
> Hi,
>
> On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
> > The current protection mechanism for closing images is insufficient as
> it doesn't
> > differentiate between 'saved' and 'exported'.
>
> Yes, that is well-known and the plan is to change that at some p
Carl Karsten wrote:
> proposed spec:
>
> File Open/Save/Save_as_Copy only work on .xcf - all other formats must use
> File
> Import/Export.[1]
>
> Add File/Import and Export to handle alien formats.
Save_as_Copy and Export are the same (the user should be able to export as
.xcf).
This appro
The current protection mechanism for closing images is insufficient as it
doesn't
differentiate between 'saved' and 'exported'.
Symptom 1:
exporting to .png requires clicking a nag-screen
Sympton 2:
closing a multi-layered image which has been exported before
doesn't give a warning about loosing
15 matches
Mail list logo
