Cant you fire up the rdoc server? (gem server)

On Feb 24, 1:16 pm, Chuck van der Linden <[email protected]> wrote:
> On Feb 24, 1:35 am, Jarmo Pertman <[email protected]> wrote:
>
> > I can't remember and can't find anything in changelog either. But it
> > was done by someone else and at least feels like long time ago.
>
> > Jarmo
>
> > On Feb 23, 9:02 pm, Chuck van der Linden <[email protected]> wrote:
>
> 1) how can I view the rdoc for the 3.0 stuff before its released?
> 2) how can we update the rdoc so that the stuff on screenshot
> describes the new method needed to take screenshots with watir, or
> that the info is somehow included.   blog postings are great, but
> result in a fractured set of documentation that is hard for our users
> to find and reference.
>
>
>
>
>
>
>
>
>
> > > how long is a long time ago?  the rdoc for 2.0.4 has it listed (http://
> > > rubydoc.info/gems/watir/2.0.4/Watir/ScreenCapture), and I did not
> > > notice anything in the release notes for 3.0 about it being removed or
> > > altered.
>
> > > On Feb 23, 4:57 am, Jarmo Pertman <[email protected]> wrote:
>
> > > > Yes, since that method is deleted a long time ago already. Use
> > > > Win32::Screenshot instead.
>
> > > > First, install Win32::Screenshot
> > > >     gem install win32screenshot
>
> > > > Then, take the screenshot by providing browser.rautomation as a
> > > > parameter:
> > > >     Win32::Screenshot::Take.of(:rautomation,
> > > > browser.rautomation).write("screenshot.png")
>
> > > > More examples athttps://github.com/jarmo/win32screenshot
>
> > > > Jarmo Pertman
> > > > -----
> > > > IT does really matter -http://itreallymatters.net
>
> > > > On Feb 23, 2:30 am, hillary <[email protected]> wrote:
>
> > > > > for the pre-release version of watir (3.0.rc2) I get a no method error
>
> > > > > my code:
> > > > > browser.screen_capture($file_path,true,false)

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]

Reply via email to