good point and actually we should get this sorted out to go both ways so
that the main docs contain a reference to the rdoc and vice versa.
Need to figure out if gem install has the right hooks to handle some of
this, probably, so I think this goes on our todo list (hopefully resolved
soon).
The home page of the rdoc does have a link to masterview.org, so if you
installed the gem for the current release and were looking at its rdoc it
would get you to the main documentation, but this breaks down if
someone''s
working with an older version of the gem or a trunk version s.t. their
installed plugin is older or newer than the current release that would be on
the web site.
~ Deb
_____
From: masterview-devel-bounces at rubyforge.org
[mailto:masterview-devel-bounces at rubyforge.org] On Behalf Of Jeff Barczewski
Sent: Friday, November 03, 2006 10:05 AM
To: Hendy Irawan
Cc: masterview-devel at rubyforge.org
Subject: Re: [Masterview-devel] [masterview] [ticket] docs
On 11/3/06, Hendy Irawan <gauldong at gmail.com> wrote:
> I think that would be a good suggestion. Even though you can generate it
is> generated from the installed gem, it would be nice to have access to that
> separately. I will see what we can come up with.
Really? I fired up gem_server and not all docs you provide on the site
are provided by the gems.
No you are right. I forgot that we have more docs now then what is generated
by rdoc. The docs do ship in the gem and plugin, but there probably
isn''t a
link to them anyway unless you go digging manually. We need to provide a way
to get to those more easily.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20061106/90a96f80/attachment.html