Tested on latest build and bug is still present. It turns out object doesn't need to have Shrinkwrap modifier. Individual origins and enabled Proportional editing still apply.

+1 for simplicity.
People don't use TexFace mapping these days because it's not compatible with Cycles, external render and game engines. If people really need to bring back old BI scenes to 2.8 they can download 2.79 and convert them easily. We might think of providing official addon for 2.79 that do this automatically.

I don't think fusing OS title bar with our top-bar is good idea. Lack of blend filepath and save status would be a significant drawback. Where that will go?

Thanks for clarifying. I was asking because I actually have brief idea how this might be solved, but since this task is closed I'm not sure where to post it. Should I send it to mailing lists or start new design task under someones permission?

The new manipulator oriented tool workflow (of course the shortcut oriented one will still be there)

Thank you @Julian Eisel (Severin)! :) I think people will like new logic for this slider, it works good in other programs.

@Joshua Leung (aligorith) That's a relief. ;)

Is this planed to work in all blender areas or exclusively in pose mode?

I also not fan of preserving 'visibility bits'. This will be very confusing and super error-prone. While managing scene users must not only take care of layers but also set up this visibility bits. This is basically forcing users to do same task twice, every time he move objects between layers. We can just use sub-layers for similar behavior but make everything clear, intuitive and familiar.

Didn't tested that. Thanks.
On 2.76 jiggling still happen but only on boolean intersection.
Both in 2.76 and current master Decimation set to Collapse works fine, topology stays intact.

@Aaron Carlisle (Blendify) - Today on IRC Sergey pointed me to assign this task to him. This issue is not necessarily related to addon itself. Will add Greg and Bartek as subscribers but reassigning this back to @Sergey Sharybin (sergey).

Clear and well organized. Good job. :)

Hi @Michel Anders (varkenvarken). Any updates on this patch?

Manhattan F2-F1 is very popular in conjunction with mapping shifting by various noises to produce organic structures. Plain Manhattan can be used for nice technical patterns but f2-f1 is used most.

Misunderstood your post Sergey. Phew... ;)
I also agree that SynaGl0w proposition that Michel linked will work best for this features.

Oh my...

Made my day. Thank you Dalai, Sergey and others! :)

Yes. Most of us agree on that. But there is no simple choice between ergonomy and user habits (from other softwares). Two similar standard keymaps would be great.

I think that ASD is fine just like WER. It will be great if we can create 2 "standard" keymaps by switching only ASD and WER keys, rest of keymap should be the same.

@Pablo Vazquez (venomgfx), you showed extreme example but its completely different situation. If we remove word "Editor" from "Video Sequence Editor" whole menu shrink drastically in width (gaps behavior) resulting even less mouse movement. Next thing- in layout proposed by @William Reynish (billrey) we operate mostly on two first columns which also reduce mouse movement in practice.

Doh... Windows and Mac builds links display: "this goo.gl shortlink has been disabled. It was found to be violating our Terms of Service." Funny because of GSoC. ;)

I don't know how to build this but can make some test with provided Win7-64bit build. I will ask someone for that.
Finally some love for cycles baking! :)

@Greg Zaal (gregzaal) OK. Sorry for misunderstanding. Then, +1 for this!

@Greg Zaal (gregzaal) I find your arrangement very confusing, cannot understand logic behind it. What timeline and properties window have in common? What Move clip tracker has to do witch asset menagement? IMHO its obvious that it it fits to workcpaces.

FINALLY! So we now can consider OSL in Cycles baking as fully working feature! :) Why so long if code was just there? "Better" is the enemy of "good enough".

@Miki (MeshLogic) - Well.... I assume blender devs are not interested in cycles baking anymore. Still there is lack of essential things was described on code.blender.org blog (working OSL, AA, rayblockers) and other obvious things like displacement. We need to wait for some fresh blood developer willing to rewrite cycles baking for proper resources consumption (18 gigs of RAM for baking 15 objects?!) and add missing features.

Considering all discusion I also vote for A-S-D setup. Those keys will work nice with standard blender navigation and also with "emulate 3 button mouse" navigation style. Many users (including me) enable this options because they find pressing scrollwheel uncomfortable.

But we have no feedback that tells when cursor is close enough to grab it. You click some pixels next to it and you grab vertex but one pixel further you will deselect all.

CTRL+A for Select All is fine for me. Maybe double tapping A While holding CTRL will work for deselecting all. We still can use Shift+A for Add menu like now.

@ronan ducluzeau (zeauro) - You mean W,E,R keys, right? I don't know any 3d app that use E,R,T keys for that but I worked on 5 programs that use W,E,R.