[Bf-committers] Google Summer Of Code: UV - Tools

Joe Eagar joeedh at gmail.com
Mon Mar 21 19:00:27 CET 2016


I had an embarrassing moment last year when trying to help a coworker
find a feature in Blender's UV editor.  It. . .no longer existed.  We
definitely need some work done here.  One thing that absolutely drove
her insane was the inability to hide UV islands without altering the
mesh selection state.  That was a big deal for her.

It might be worth concentrating on improving the UI workflow and not
spend too much time on new unwrapping features.

Best,
Joe

On Mon, Mar 21, 2016 at 10:28 AM, Phil Gosch <phil at saphirestudio.at> wrote:
> Hey again!
>
> I just submitted/shared my proposal via the GSOC form and would love to get some feedback from possible mentors, seasoned devs and Ton of course. As usual I'm also available via IRC.
>
> I'd especially be interested in what specific improvements to the Unwrap algorithm ("Improved automatic UV Layout") the mentors had in mind when writing the ideas page as well as general feedback regarding the proposal.
>
> Thanks in advance and best wishes,
> Phil
>
>
>
> Am 13.03.2016 um 12:49 schrieb Phil Gosch:
>> Hey everybody!
>>
>> My name is Phil Gosch, I'm from Graz University of Technology and I'm
>> interested in the "UV Editing Tools" GSOC project.
>> I'd be very happy to realize this project and wanted to get some
>> help/tipps or hints beforehand, that's why I'm writing this mail.
>>
>> About me: I'm a long time Blender user and active member of the Blender
>> community. Besides university I'm working as a 3D/Technical Artist
>> freelancer, where I'm mostly doing illustrations, visualizations
>> including custom tool development and gameart/gamedev. You can have a
>> look at my portfolio at my homepage [0] or at my Blender Network profile
>> [1].
>>
>> As someone who uses Blender as his main tool on a daily basis I know the
>> UV Editor (and its shortcomings) and because of that fact I not only
>> think I'm fitting for this project but I also have a great personal
>> interest in improving these tools. I'm no complete stranger to Blender
>> core coding, I already had some of my patches applied to trunk a few
>> years ago. Of course the codebase is changing all the time, that's why
>> I'm already getting familiar with the codebase again. I already compiled
>> the newest Blender version and I'm spending my free time reading
>> uvedit_*.c files. ;)
>>
>> I think the outline presented at the ideas page [2] makes sense, however
>> while writing my proposal I found that I liked the idea of trying to
>> convert some of the useful UV python scripts I'm using to C code (I'm
>> sure people have lots of scripts they use which I don't even know
>> about). So if you use a python addon for the UV tools and would like me
>> to consider it for inclusion into my proposal, please let me know by
>> answering to this mail. :)
>>
>> If any of the potential mentors (Bastien, Campbell, Howard) have some
>> useful input I'd be very thankful! Also if anyone could have a look at
>> my proposal before submitting that would be great! It's not finished
>> yet, but you can poke me anytime on IRC/blendercoders, I'm always
>> lurking there. My IRC nick is "saphires".
>>
>> Best wishes,
>> Phil
>>
>> [0] http://www.saphirestudio.at/
>> [1] https://www.blendernetwork.org/phil-gosch
>> [2] http://wiki.blender.org/index.php/Dev:Ref/GoogleSummerOfCode/2016/Ideas
>>
>> PS: Sorry if this mail shows up twice, there was an error when I first
>> tried sending it
>>
>
> --
> pixel-pusher at saphirestudio.at
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list