Future of the animation feature

[Dmitry Kazakov]

On Sat, Dec 20, 2014 at 10:14 PM, Jouni Pentikäinen <mctyyppi42 at gmail.com>
wrote:

On Sat, 20 Dec 2014, Dmitry Kazakov wrote:
>
>> Before starting refactoring I would highly recommend to prepare at
>> least a draft of UML diagrams of what you are planning to achieve.
>> This way the refactoring will come faster and more successful. I
>> usually create diagrams using http://creately.com They allow create
>> public diagrams and edit them collaboratively.
>>
>
> I made a quick draft of the different approaches discussed so far:
>
> https://creately.com/diagram/i3x32pss1
>
> The first one is modeled from Boud's description while the other two are
> the models I have proposed. Let me know if I misunderstood the description
> somehow.
>
> I hope we can iron out the remaining issues and find a model we can all
> agree on.
>

For the third approach I would try to make it basing on KisGroupLayer. That
is the class should be derived on a group layer, otherwise quite a lot of
code (updates, drag&drop will not work for it). Probably, you could
override the methods of KisNode, but I'm quite unsure about it. There are
lots of complications like KisCloneLayer which could point to some layer
that doesn't belong to current frame.

So speaking truly I would first try to make purely "paintable" animation
with KisPaintLayer only. And only then would start thinking about solving
all these complications with animated groups. It might really happen that
the users don't need it. I guess what then need is an animated paint layer
+ ability to change visibility and other properties of a all other node
according to the frame number.

So the list of requirements would be the following:

1) Only Paint Layer can be animated.
2) Other types of layers are static.
3) The properties of all the nodes can be saved for every node for every
frame. E.g. "one can activate Transformation Maks for a particular node
starting from frame X and till frame Y".


-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20141220/efac74f5/attachment.html>