I think there should be 2 ... one for top level frames and one that is
exhaustive.
Not that both features are necessary out of the gate ... top level
frames would be a good start .
j.
On 8/3/05, Paul Rogers <[EMAIL PROTECTED]> wrote:
> ah, good point. Should it perhaps only iterate the top level frames?
>
> and if you wanted lower level frames, you would apply an iterator to that
> frame. Seems like this way would save me work;-) But probably be less
> intuiitive.
>
> ----- Original Message -----
> From: Bret Pettichord <[EMAIL PROTECTED]>
> Date: Wednesday, August 3, 2005 2:35 am
> Subject: RE: [Wtr-general] I have a couple of questions...
>
> > At 10:33 PM 8/2/2005, Paul Rogers wrote:
> > >I want to add a frame iterator object as soon as I get the chance:
> > >
> > >Ie.frames.each {|f| .... }
> > >
> > >When that's, there, it would be simple for you to add your 'click
> > a link
> > >in any frame' method. It wont be this release though.
> > >
> > >Paul
> >
> > This will be harder than the other iterators because frame
> > collections can
> > be nested. If you only search document.frames[], you won't
> > actually
> > traverse all of the frames.
> >
> >
> >
> > _____________________
> > Bret Pettichord
> > www.pettichord.com
> >
> > _______________________________________________
> > Wtr-general mailing list
> > [email protected]
> > http://rubyforge.org/mailman/listinfo/wtr-general
> >
>
> _______________________________________________
> Wtr-general mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/wtr-general
>
--
"So long, and thanks for all the fish"
Jeff Wood
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
