Hi, Indeed. Having documentation on the web is nice for exposure, but we have to bring the documentation in the environment for reducing the context switch.
As for the size, I would love to have the problem of having to remove 50MB of documentation from the image :) Doru On Sat, Sep 21, 2013 at 3:35 PM, Sean P. DeNigris <[email protected]>wrote: > Clément Bera-4 wrote > > the documentation would be on the web, available to anyone, > > and each class / each package inside Pharo has a link towards its online > > documentation. > > This way the image size does not grow because of massive documentation. > > I agree that it would be nice for the docs to be on the web. But for me I > would want that to be a mirror of what's available in the image. In > general, > I'd rather not context switch between the live, dynamic world of my image > and a browser. Also, I don't think saving image size is enough of a > benefit. > Pharo is already tiny compared to other technologies, and the documentation > would presumably be removed for production anyway. My 2c... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709505.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"
