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 perfectly to a casual user, who
> just needs a very basic image editor; while the new "import JPEG +
> edit + save XCF + export JPEG" matches the flow of a power user, who
> uses GIMP to the full of its capabilities.
I think if gimp had file->import that might be clearer.
A recognition that lots of power users and professional users of gimp do
not always need to save in xcf (and ggenerally know when they do or
don't), and that pretty much every professional workflow ends with
exporting a file, would really help.
E.g. before you close an image, you need to know:
(1) have you saved it as xcf and, if so, to where
(2) have you exported it and, if so, to where
Similarly, save and export need to default to the same folder, so that
after you've exported an image, save defaults to putting it alongside
the exported file, not in ~/Documents each time.
I'm not sure how much of this is bugs, how much is gradual evolution of
the spec with user experience, and how much is bugs in the spec.
Long-term I hope we end up with the concept of a "Project" which can
involve multiple files, resources like brushes, fonts and colours, and
its default import, open, save and export places.
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Co-author "Beginning XML", Wrox, July 2012
gimp-user-list mailing list