Up until version 1.6, documentation for previous versions are
available in their pdf versions only.

As soon as we move to PDoc we'll get per version documentation for
free.

Best,

Tobie

On Oct 26, 9:07 pm, Tom Gregory <[EMAIL PROTECTED]> wrote:
> Let me try and ask my root question at a higher level--what are the  
> plans (if any) to maintain (or not) documentation for older versions  
> of Prototype?
>
> In the future, PDoc will minimize the necessity, as docs could be  
> viewed by version number, but the current documentation doesn't work  
> that way.
>
> TAG
>
> On Oct 26, 2008, at 1:56 PM, Tobie Langel wrote:
>
>
>
> > I don't want to sound rude, but this is starting to look like a
> > designed by committee bike shed. :/
>
> > I suggest people who are interested in the helping out with the docs
> > (and that's really needed!) to either look at PDoc and help out
> > completing it or propose (and implement) an alternative solution.
>
> > Thanks!
>
> > Tobie
>
> > On Oct 26, 8:11 pm, Tom Gregory <[EMAIL PROTECTED]> wrote:
> >> On Oct 26, 2008, at 2:37 AM, Richard Quadling wrote:
>
> >>> -1 for strikeout - simply looks ugly.
>
> >>> +1 for [deprecated]
>
> >> Agreed.  Would it be too much information in the left menu to also  
> >> add
> >> the version the item was deprecated in?  There are several old
> >> versions still live in the wild.
>
> >> At the very least, the version number for deprecation (and removal)
> >> should probably be added to the descriptive text in the right. Maybe
> >> we should also consider added information on when something was added
> >> (if after v1.5?).
>
> >> TAG
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to