Re: PropertyGetter ?
- From: Kirill Grouchnikov <kirillcool@yahoo.com>
- To: dev@trident.kenai.com
- Subject: Re: PropertyGetter ?
- Date: Wed, 7 Oct 2009 20:58:16 -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=Tot2vIe/4nV8kJPHXqZ69ChfNqjFXLW+qwi1nQ5MORivigZxhVd+Lm7FNMV43tX4441zrcbhVo3K6wOa5TeGvbTI16gqv84FXKeS0Qo7pmTwrFZ7/ZfaX/nJBuVEg/f5vlbjF/cXRauTmv9sJekLoB3iYGjaZJOkSyRAWiOJ0FI=;
This is a good idea. Would you mind filing an enhancement request so that this is added in the next Trident version? Most probably it will be a separate interface - PropertyGetter, and another one - PropertyAccessor - that extends both. This way the TimelinePropertyBuilder will provide extra flexibility.
Thanks
Kirill
Thanks
Kirill
From: Emmanuel Bourg <ebourg@apache.org>
To: dev@trident.kenai.com
Sent: Wednesday, October 7, 2009 8:51:10 AM
Subject: PropertyGetter ?
Hi,
I'm using a custom PropertySetter to store the interpolated values into a map. However, in this case it's impossible to animate from the current value to a target value, because the API assumes the existence of a get method to read the current value. The API lacks a way to define a custom property getter.
I suggest to turn the PropertySetter interface into a PropertyAccessor interface with two methods set() and get().
Emmanuel Bourg
| Emmanuel Bourg | 10/07/2009 | |
|
Re: PropertyGetter ? |
Kirill Grouchnikov | 10/08/2009 |





