Okay, Scratch that. I guess a count isn't needed if the only thing you
can do is generate the output vxml anyways.
Question though... I'll write the code if folks think it would be useful to add
count() <-- length of lists
remove(3) <-- drop one element
get(1) <-- show one element
This would allow the developer to look at the list and modify it as
necessary. Taking that a step further... I'd also like to overload
the getVXMLOptionsMarkup()
method, allowing you to specify an optional start and end point of the list.
getVXMLOptionsMarkup(1,4)
What do you folks think? Should I just keep my data elsewhere until
I'm ready to turn it into markup, or shoud we allow the developer to
dynamically modify the list? My scenario is a rdc:select1, where I
may have 15 options from a database, but I would like to present only
5 at a time to the caller. The backend action populates my option
list, but I would like to be able to just pull a few at a time from
the list on the jsp side. Thoughts?
Thanks,
Shane
On 8/12/05, Shane Smith <[EMAIL PROTECTED]> wrote:
> Any reason not to also add a:
>
> public int count() {
> return values.size();
> }
>
> method to the class? (or is there a more appropriate way to name it)
>
> -Shane
>
> On 8/11/05, Rahul P Akolkar <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] wrote on 08/11/2005 11:19:58 PM:
> > > good job, now others are writing our code for us:-)
> >
> > Well, we really should have got this one right ourselves ;-) Thanks again
> > Shane.
> >
> > -Rahul
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
