Plasma + QT Kinetic Preliminary Design Decisions

[Alexis Ménard]

Hi,

On Thu, Jun 4, 2009 at 3:12 PM, Gökmen GÖKSEL <gokmen at pardus.org.tr> wrote:

> On Thursday 04 June 2009 15:34:22 Akmanalp, Mehmet A wrote:
> > Hello,
> Hi,
>
> > I wanted to distill the discussions made previously on the list + my
> > thoughts and findings into something more concrete, so I can start
> > making a prototype soon.
> Cool
>
> > * For grouping, our Animation object (or whatever) can just subclass
> > QAnimationGroup. QAG supplies all we need, no need to go lower to
> > QAbstractAnimation imho. This way, we can interopt with other Kinetic
> > stuff nicely. IIRC, it was also mentioned the js / ruby / python APIs
> > will not need to know about Kinetic.
> "QAG supplies all we need" -> What do we need exactly ?


Running sequential animation and some of same at the same time. Let's say
bounce growing effect kind of...


>
>
> > * Now that I thought of it, I'm not exactly sure what aseigo meant by
> > "auto-start-when-event-loop-enters magic". Would we make QAG start
> > automagically with the next tick of the event loop. If so, providing
> > an option to not do this would also be neat, so people using our stuff
> > in conjunction with Kinetic stuff can have more freedom. However, how
> > would we detect that an animaton object is done being created?(Maybe
> > we're going to add more properties to it.)
> We can handle it by using some properties or something different with some
> low
> level tricks :)
>

>
> > * Should we set the object to animated in the Animation ctor or set it
> > later with a function such as .setObject()?
> Can't we make it in both way ?
>
> > * Imho the new library should not depend on Plasma::Animator, I can
> > reimplement the stuff I need.
> Looks fine
>
> > * For consistency / compatibility between all the different language
> > bindings, returning a reference instead of using something like the <<
> > operator as a grouping shortcut seems like a better idea.
> +1
>
> > * Example (looks a bit cleaner in monospace):
> > Animation a,b;
> > a.setParallel(1)
> >  .add(Animator.blur(0.6))
> >  .add(Animator.bounce(2))
> > b.add(a)
> >  .add(Animator.pause(1))
> Looks fine,
>
> > * A list of effects to be definitely implemented (since they were
> > already being used / wanted by someone):
> >     - Flip
> >     - Slide In / Out
> >     - Fade In / Out
> >     - Expand / Contract in a direction
> >     - Grow / Shrink / Scale
> Animate, animate every thing :)
>
> > * I'm still lacking a decent name for the class. SimpleAnimator?
> > KineticAnimator? Animator2? :P Maybe something shorter and easier to
> > type?  Dunno.
> just Kinetic in namespace of Plasma should be fine; Plasma::Kinetic ;)


Kinetic means nothing for a dev, if you read this class name without knowing
what it's doing behind, what you expect that thing do? You don't know...
Plasma::Animator is a good name, you guess it "animate" something. It's
already taken so AnimationManager, AnimationFactory, AnimationProvider
perhaps.


>
>
> --
> Gökmen GÖKSEL
> Pardus Developer
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/plasma-devel/attachments/20090604/3b981a67/attachment-0001.htm