Here's a first shot of PBE1 in html�http://lolgzs.free.fr/pharo/PBE1_html.zip.

Extract and open PBE1.html.

I had to fix manually several links and pictures. At least navigation works even if not nice. CSS needs improvement but I suck at design / visual :)

Laurent Laffont -�@lolgzs

Pharo Smalltalk Screencasts: http://www.pharocasts.com/
Blog: http://magaloma.blogspot.com/

Developer group: http://cara74.seasidehosting.st

On Sun, May 8, 2011 at 2:18 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:

I could not generate all the html because apparently there is a problem.
The table of contents was broken.

Stef

On May 6, 2011, at 2:05 PM, laurent laffont wrote:

> On Fri, May 6, 2011 at 11:56 AM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
> Ok if some good souls want to give a try to generate html.
>
>
> On OSX with MacTex-2010 installed, I've tried
>
> git clone --depth 1 https://github.com/SquareBracketAssociates/PharoByExample-english.git
> cd PharoByExample-english/
> htlatex PBE1.tex "html,2"
>
> Then open PBE1.html , one page per chapter.
>
> See http://www.tug.org/applications/tex4ht/mn-commands.html
>
> Laurent.
>
>
>
>
> Stef
>
>
>
> > Probably we should find a way to generate HTML from PDF or Latex.
> > Any ideas?
> >
> > I've used latex2html several years ago.
> >
> > +1 for html
> >
> > Laurent.
> >
> >
> >
> > >>>> Now for the documentation when did you send an help documentation for any part of the system?
> > >>>> Or a bug fix?
> > >>>> I find quite funny that people always talk but few are doing. We welcome comments/examples help.
> > >>> No need to get into a cat-fight here :)
> > >>
> > >> No this is not my point. But what do people really do to help?
> > >>
> > >>> I do agree with Stefan, as well as with you that we could help; but I'm unaware of a good documentation effort outside of the image to start with. Camillo's website project might be the best effort I've seen until now; but then I didn't really look either. Maybe I missed some great website?
> > >>
> > >> If this is just to spit out class comment on html I do not call that a documentation.
> > >> Now we can take the book contents and generate html
> > >> We have 350 pages in the first book and the same in the second one.
> > >> People are free to join and write one or two chapters.
> > >
> > > St�phane,
> > >
> > > Of course you are right: wining/complaining doesn't help, only action does. We need more people like Laurent focusing on documentation.
> > >
> > > I for one think that the well written, high quality books that exist (PBE, Seaside Book) are *very valuable*, much better than confusing wiki site (although these have their place as well).
> > >
> > > But the other point is: in most other popular languages, what current, young developers do, when they get an error that they don't understand is copy/paste the literal text in Google and in a surprisingly large number of cases you find some real answers in the first page.
> > >
> > > This is also related to popularity of course.
> > >
> > > Sven
> >
> >
> >
>
>
>