See the answer of the main developer of the normal editing feature.

Adjustment.

1. An option to preserve (lock) normals when removing a adjacent loop.

Is not a bug. This is the right behavior.
Your issue can be solved with the "Copy From Mesh" button. Just make a copy of your mesh before deleting anything from it and copy normals from this mesh.

Hi!

1. An option to preserve (lock) normals when removing a adjacent loop.
2. Resolve problems after mirror & flip (all normals are "randomly" split).

This items can be qualified as Blender bugs, because all hard work related to mesh updates is done in the Blender kernel. I will make bug reports.

3. When rotating a selection, allow for local coordinates. The screenshot show current behaviour: you can't rotate all normals by their own Y axis, for example.

Good point. Will add this in TODO.

4. Function for flattening normals, like you would normally do with (S)cale -> 0.0.

You mean a feature like "Split Mode" -> "Restore" bound to a hotkey?

Здравствуйте!

Скажите пож-ста, что именно вводится в поле "имя анимации"?

Возможны 3 варианта:

• Обычный Action:
• Система частиц типа Emitter:
• Шейдерный Action:

Если оставить поле пустым, будет использоваться анимация с таймлайна

При пустом поле будет воспроизводиться анимация, которая задана по умолчанию, например Action, как на первой картинке.

И можно ли как то посмотреть сцены примеров тех же выдвигающихся ящиков?

Сцена с ящиками доступна в SDK.

Почему после данной схемы нод анимация объекта воспроизводится автоматически без учета select? Или это нормально? Спасибо еще раз.

Нода Select & Play Animation не управляет таймлайном, она управляет анимациями упомянутых выше типов.

Hi!
Hiding/showing groups is not supported now, but will be enabled in the near future.
In the meantime, you should use hide/show node for each object in dupligroup.

If somebody sees an error "…MSVCRT120…..dll " when using the project manager, please install visual c++ redistributable 120 as a temporary workaround. This should be fixed after the stable Blender 2.76 release comes out.

Если у кого-то при использовании инструмента управления проектами на Windows возникает ошибка …MSVCRT120…..dll , то следует установить visual c++ redistributable 120 (в качестве временной меры).

The current design assumes the absence of the control flow branching. We see no need for branching, moreover, it can create synchronization problems. In order to simultaneously playback two animations, we plan to implement the possibility to asynchronously evaluate nodes, i.e. the control will transferred to the next node without waiting when the current node is over. This way it'll be possible to simultaneously playback sounds, animations etc.
For now there exists a way to create more than one control flow - by using multiple Entry Point nodes.

Good suggestions. We had similar thoughts. What I liked the most is having different types of entry points as event handlers. At the moment, we see the Logic Editor in context of a single script per scene which is important for usability. A single tree is easier to understand: all logic is described on a single sheet and you do not have to switch to other trees. With the current set of nodes, this method is quite optimal. As soon as we develop more sofisticated nodes which will be associated with separate objects, I think we can choose the road similar to what you suggested.

В комментах пишут про Intel XDK, он мне тоже показался самым простым решением. И он еще и со своей средой разработки поставляется.