Takuya,
Feel free to implement that solution and see how it works (and close this issue in the process :-)
Maybe we could do a code review of it as well.
Cheers, Philip
--On Thursday, February 24, 2005 5:13 PM -1000 Takuya Yamashita <[EMAIL PROTECTED]> wrote:
Hi Aaron,
Are you talking about this <http://hackydev.ics.hawaii.edu:8080/browse/HACK-171>?
Yes. that is really what I concerned. The easiest way to solve this problem is that "TextField" would be going to a attribute in the request object and it would be defined in a subclass and instantiated in the class.
This would be pretty easy and let developers to easily extend the TextFieldSelector class with just defining attribute name (static method should be defined in each subclass though), and use multi text field selectors.
Cheers,
Takuya
On Thu, 24 Feb 2005 16:55:42 -1000 Aaron Kagawa <[EMAIL PROTECTED]> wrote:
Hey Takuya,
Are you talking about this <http://hackydev.ics.hawaii.edu:8080/browse/HACK-171>?
thanks, aaron
At 03:56 PM 2/24/2005, you wrote: > Hi Hackystat hackers, > > I got a problem when using text field selector. It's because I can not > define the same selector in a analysis (because of the TextField > attribute name is hard coded), thus can not use the multiple > org.hackystat.stdext.common.selector.text.TextFieldSelector. > > I would like to propose make its class be abstract (or at least the > text field name could be overrided easily) and developer can extends > the the class. > > In addition, I could not find the pull down menu (or similar > functioning) selector in the common package. I guess it would be > useful if the general PullDownMenuSelector class were provided, and > developer can easily extend the class with the own option map and > attribute names. > > What do you guys think? > > Cheers, > > Takuya > > > ================================ > Takuya Yamashita > E-mail: [EMAIL PROTECTED] > ================================
================================ Takuya Yamashita E-mail: [EMAIL PROTECTED] ================================
