I could argue about how I agree with you, but only in part. But the simple fact is this: the documentation is advertised in large letter on this page: http://pharo.org/documentation
If it's broken, it should be fixed. If the people with the technical access to fix it do not care, it should be removed from such a highly visible page. As it is, it is confusing for new users, who need it most, and reflects badly on the state of Pharo in general. > On 10 Jan 2016, at 22:25, Serge Stinckwich <serge.stinckw...@gmail.com> wrote: > > Dear David, > > yes this maybe broken, but most of the time, a Pharo developer will > never have a look to such a static documentation. > You can browse the class and the related methods very easily inside > the Pharo image, without relying on an external tool. > > Regards, > > On Sun, Jan 10, 2016 at 1:08 PM, David Allouche <da...@allouche.net> wrote: >> Hello, >> >> It seems the pharodocs website is broken. Pages for classes are rendered, >> but the documentation does not display the messages, only their docstrings. >> That makes it quite unusable. >> >> http://files.pharo.org/doc/4.0/#packageList=package.html&classList=package/Kernel.html&classView=class/ProtoObject.html >> >> I remember I looked at it once when I started and thought "whee, that's >> confusing, I'll play around and come back later". Now I understand why that >> was confusing... >> >> Who can fix that? > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >
