Re: [Gimp-developer] deeper into the export hole

2013-02-24 Thread Øyvind Kolås
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 rea

Re: [Gimp-developer] unified transform tool

2013-02-24 Thread Alexandre Prokoudine
On Sun, Feb 24, 2013 at 6:37 PM, Joao S. O. Bueno wrote: > This kind of things can be imploemented as a Python script I very, very much doubt that. Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-developer-list mailing list gimp-developer-l

Re: [Gimp-developer] unified transform tool

2013-02-24 Thread Joao S. O. Bueno
On 24 February 2013 09:23, 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 wa

Re: [Gimp-developer] unified transform tool

2013-02-24 Thread Michael Muré
Add me on this request. Even if you don't generate several texture from a single xcf, you often have a layer with the unwrapped 3D model layout, that you forget to disable every time before exporting. 2013/2/24 Alexandre Prokoudine > On Sun, Feb 24, 2013 at 4:09 PM, peter sikking wrote: > > > m

Re: [Gimp-developer] unified transform tool

2013-02-24 Thread Alexandre Prokoudine
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 m

Re: [Gimp-developer] unified transform tool

2013-02-24 Thread peter sikking
I wrote: > Alexandre wrote: > >>> I will need some essential scenarios for that, beyond the obvious >>> photo horizon correction and getting verticals vertical. it must be >>> more complicated and the tool(s) should not end up as 2-trick pony(s). >> >> Would a Google+ post help you to collect in