Hi, On Wed, Nov 13, 2013 at 1:45 PM, Jehan Pagès <jehan.marmottard@xxxxxxxxx> wrote: > Hi, > > On Sun, Nov 10, 2013 at 2:25 PM, peter sikking <peter@xxxxxxxxxxxx> wrote: >> guys + girls, >> >> it is a tricky thing, this overwrite vs. export. >> >> there is a difference, overwrite is for working ‘backward’ >> as I called it: doing some work on a non-gimp file and >> feeding this directly back to it. it is labelled brutally and >> frankly, with intent. export is for working ‘forward’, towards >> a new result. >> >> but as Richard comments, the difference is not that big. >> this is what I exploited in the design for repurposing >> the Export-to item for Overwrite. >> >> of course one can use Export... to set up to write over >> one of the source files of the composition one is working on. >> >> thus exporting is the general game, with one special case >> built in: hardwiring the initiating source file as export >> target and giving this a fearsome name (beware: burning bridges) >> >> Yes, Export-to and Export... mirror images of Save and Save-as... >> >> I think I can see what Akkana means: when there is no export >> target, the menu items are “Export to” and “Export...” >> that is not ideal. and it’s clear that it irritates people. >> >> note that the export-to item cannot be grayed out in this case. >> ctrl-E just has to work (leading to an Export..., yes, just >> as the first Save is a Save As...) > > Just checking master, currently when "overwrite" is shown, export-to > is not grayed out but it is invisible. > That means that it is active and can be run if you know the shortcut, > but you can't export from the menu (for people who don't know > shortcuts, new or casual users, etc.). > Is it intended? I feel like this is a mistake and that "Export To" > should always show up in the menu. > I could easily fix this. > >> reviewing the situation, I see that the straightforward solution >> is to relabel >> >> Export... -> Export As... (in all states) >> >> “Export to” -> Export (when no export target) >> > > I like the change. When there is an export target, should it become > "Export As somefile.png"? > In any case, I have written a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=712192 I guess you can tell if that's good for you, so that it can be committed. :-) Jehan > Jehan > >> you can see that this achieves perfect mirroring of >> Save and Save As... >> >> “Export to foo.xyz” and “Overwrite foo.xyz” stay as-is, >> they work well with Export As... >> >> (just in case you wonder, yes I am giving up on something >> by doing this: in so many other application the label on >> the export menu item is Export... ) >> >> --ps >> >> founder + principal interaction architect >> man + machine interface works >> >> http://blog.mmiworks.net: on interaction architecture >> >> >> >> _______________________________________________ >> gimp-developer-list mailing list >> List address: gimp-developer-list@xxxxxxxxx >> List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
