Re: Re: Re: TimingFramework triggers for Trident - Let's try again

[Kirill Grouchnikov <kirillcool@yahoo.com>]

Here's how the alpha of the cool iris use case would look in TF:
(straight from your test :)

KeyValues alphaValues = KeyValues.create(0.0f, 1.0f, 1.0f, 0.0f);
KeyTimes alphaTimes = new KeyTimes(0.0f, 0.3f, 0.7f, 1.0f);
progressTimeline.addPropertyToInterpolate("alpha", new
KeyFrames(alphaValues, alphaTimes));

And here's how it would look in Scenario:
Clip progressClip = Clip.create (5000, KeyFrames.create (this, "alpha",
KeyFrame.create (0f, 0f),
  KeyFrame.create (0.3f, 1f), KeyFrame.create (0.7f, 1f),
KeyFrame.create (1f, 0f)));

>>> Do you know how do you specify the interpolators for each one of the steps? The API invocation doesn't look too different to me, as long as the code behind the design tool knows to create these two slightly different invocation sequences.

Regarding the property themselves, using only property descriptors ties
you to bean properties, ie with a getter and setter method. The trident
user is not able to create his own property animations respecting 1)
his own property syntax eg name(String) instead of setName, 2) his own
property framework (like bean-properties or pulpcore's) 3) create
"virtual" properties and animate them, like some kind of composite
between two values, etc.

>>> Right now you'd have to do this with a callback registered on the timeline. When the specific request comes in, i'll be happy to discuss the details.

Oh btw i think it'd be nice to have two trident-plugin.properties,
right now using the swing one depends on swt at runtime, and vice
versa, and trident crashes when they're not both available. Am i
missing something here ?

>>> Would you mind attaching a stack trace?

https://kenai.com/svn/trident~source/www/webstart/ButtonFg.jnlp
https://kenai.com/svn/trident~source/www/webstart/Fireworks.jnlp

>>> These two WebStart apps are Swing demos and they run on my machine - without SWT being available. I also ran them locally.

Thanks
Kirill