RSS/Atom feed Twitter
Site is read-only, email is disabled

deeper into the export hole

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

deeper into the export hole Øyvind Kolås 24 Feb 15:39
  deeper into the export hole yahvuu 25 Feb 21:10
Øyvind Kolås
2013-02-24 15:39:52 UTC (almost 12 years ago)

deeper into the export hole

On Sun, Feb 24, 2013 at 7:23 PM, Alexandre Prokoudine wrote:

On Sun, Feb 24, 2013 at 4:09 PM, peter sikking wrote:

meanwhile, I am looking for a new small design project to put before my students in a months time. any ideas.

It seems that folks who create textures for 3D projects really want us to build advanced features on top of the new save/export model.

One such feature is mentioned in the GSoC2013 page: being able to export/overwrite from sets of layers.

Quoting an artist:

"It's quite common for texture artists to work with multiple parts of a texture in the same file. They may for instance have diffuse, spec and bump all in one xcf or psd file, then they change the visibility settings of the different layers or layer groups, to save out each texture type. Being able to define sets, and give them a path and file format to save to would be quite handy, as once that is set up, you could literally write out all the different parts of you texture at the push of a button."

I've heard this request from 2 or 3 people. That is not a significant sampling, but the feature will be handy to at least two more groups of users:

- web designers (keep design variations in a single file, export all) - photographers (use global mask for different processing variations, export all variations to different files)

I mocking up some potential ui ideas for another side of such export some years back - more along the lines of "export for web"; with different formats/compression settings as well as defined regions. Such a setup could also be used for easily creating themes/skins for quite a few toolkits (on the web as well as native) where one would work from an example UI screenshot (The quick borwn fox jumped over the lazy dog) screenshot.

http://pippin.gimp.org/tmp/export.png

/

The future is already here. It's just not very evenly distributed
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/
yahvuu
2013-02-25 21:10:47 UTC (over 11 years ago)

deeper into the export hole

Hi,

Am 24.02.2013 16:39, schrieb yvind Kols:

I mocking up some potential ui ideas for another side of such export some years back - more along the lines of "export for web"; with different formats/compression settings as well as defined regions.

which brings to mind the image frame concept -- here's another take on the topic: http://gimp-brainstorm.blogspot.de/2010/06/blog-post_05.html

best regards, yahvuu