# Feedback FG Presentation 3

## What is Lottie? (Jens)
- adobe after effects
- open format
- svg, html morph, gets into html of the website
- just a control -> progress

## Does one need to interact with the jsons? Is it possible to interact with it? (Robert)
- created by designer
- external animation
- "our" animations are different
- we don't expect someone to work with our animations outside of the editor
- but it is possible to do so with code

## Is there a way to see all changes one could do on one view? (Robert)
- have an overview in the beginning what features are available
- might be good for people who are not that confident in discovering features
- we think of it as a powertool

## Is the typeshift workflow the best one? (Robert)
- maybe discuss this with Robin and Doreen
- if one of the two is ill, nothing really works
- maybe we can tell were we see flaws in the workflow

## How were animations made before our editor was build?
- it was also code
- Robin builded a small tool support for himself, but in the end it was all code
- a lot of the code that Robin wrote were always the same and no complicated code

### Follow Up: How are lottie animations handled
- designer have their tools and when exporting it is a json
- Robin and Doreen don't alter them
- just like a normal lottie animation on a html site
- we have a html morph where we can include them
- not just lottie files, also a lot of other animation

## Which properties are available in the inspector?
- at the moment we just wanted to have those and we decided which ones are "relevant"
- we want more than just the ones we have at the moment
- we think more are possible but at the same time many of the properties in the internal inspector are internal or booleans

## Synchronizing between two sequences (Tom?)
- display two tabs next to each other
- so both can be edited at the same time/ are visual next to each other
- synchronize many keyframes
- primitive animation -> to complex one
- primitive interactions -> complex interactions where many timeline sequences or many keyframes

## Animations and Codegeneration
- many animations are relative to the screen width and no absolute values
- should we make also animations relative?
- at the moment two scrollytellings are created
- create code and substitute the constants with relative values
- should there be variables in the keyframe editing and we generate the code from this?

## Scenegraph
- make a tree view of the sequences and their morphs because we can't see the hierarchy of the morphs in the global view and this is mixed in the overview

## Over-time behavior
- gabminder-like trails [https://youtu.be/PUv66718DII?t=818](https://youtu.be/PUv66718DII?t=818) where one can see the effect over time immediatly

## Other questions
- low code vs nocode: which expressions can doreen write?
- can we connect properties with each other? eventually even between different objects
- is there a way to structure a session? Something like checkpoints and undo? to experiment and tolerate mistakes?
- how to structure the keyframe view? how to have the overview? maybe use colors and shapes to differentiate them?

## Chat
Da ihr over-time behavior abbilden wollt, könntet ihr Gapminder-like Trails verwenden ( https://youtu.be/PUv66718DII?t=818 ), an dem man den Effekt über Zeit sofort sehen kann.

Bzgl. "low code" und "nocode": Welche Ausdrücke kann Doreen schreiben? "123", "1.000", "10 %", ... "3 + 4"? "tilt = blur + 0.5"? Kann man Properties miteinander verbinden? Vielleicht sogar zwischen mehreren Objekten? Wie kann Doreen eine Session strukturieren? Gibt es eine Art "Checkpoint" oder irgendein "Undo", um zu experimentieren und Fehler zu tolerieren? Wie kann man die Übersicht behalten, wenn alles voller "Keyframes" ist? Könnte man vielleicht Form und Farbe nutzen, um Properties schneller voneinander zu unterscheiden? Gibt es Ankerpunkte an Morphs, an die man einfach "snappen" könnte, wenn man mittels Drag/Drop dieses "Fine-Tuning" zwischen Morphs vornimmt? Oder muss man sich die Werte merken/abschreiben?

mymorph.position: screen_size + Point(30, 30) -> position: screen_size + Point(-50, -20)