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

  • From: Kirill Grouchnikov <kirillcool@yahoo.com>
  • To: dev@trident.kenai.com
  • Subject: Re: Re: Re: Re: TimingFramework triggers for Trident - Let's try again
  • Date: Mon, 15 Jun 2009 12:54:29 -0700 (PDT)
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=1IUlQJXEV6qjmoLwp4Bn30Sdwj/24etPjTDA8+EZH39JlcdZd5H1KEY4rahufQ74MOXy1YmHcXHgiCLVxq6UamuLAhBcRZDfCN0eOqVLjisjco/svo5gh8M8WfO6iEF9iAvVsPLkh8tH9c6aF5gI2Lc5SI8QZ9vwUYXwlcg9Bos=;

Sure, they are both optional parameters on the KeyFrame.create method.
ie KeyFrame.create (0.7f, 1f, Interpolators.getLinearInstance(), new
MyUberCoolEvaluator()); You can have one, or the other, or both. The
case where you only set the interpolator in the keyframe is the most
common one in my opinion.

>>> That's what i don't like in both TF and Scenario APIs - you have N points, and N-1 intervals, and no "clean" APIs to define these. The interpolators / evaluators are for intervals, and values / times are for points. In TF (and Trident by extension) you pass the intervals as varargs, and in Scenario you pass the interval information in the closing key frame point.

Thanks
Kirill



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

Kirill Grouchnikov 06/07/2009

<Possible follow-up(s)>

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

remy.rakic 06/08/2009

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

Kirill Grouchnikov 06/10/2009

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

Kirill Grouchnikov 06/15/2009

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

remy.rakic 06/15/2009

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

Kirill Grouchnikov 06/15/2009

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

remy.rakic 06/15/2009

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

Kirill Grouchnikov 06/15/2009
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120127.ac94057)
 
 
Close
loading
Please Confirm
Close