On Mon, May 24, 2010 at 11:41 PM, Torsten Bergmann <[hidden email]> wrote:
Maybe I am dreaming too much, but it would be cool to export somehow some chapters to HelpSystem. Is there a way to export from Latex to ASCII ? even more, how difficult could be to code a plugin (or whatever name is) to automatically generate the nice code for HelpSystem from Latex code? Then we can include PBE in the image also ;) Cheers Mariano Would be nice to have a real Metacello help book _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Mariano Martinez Peck wrote:
> > On Mon, May 24, 2010 at 11:41 PM, Torsten Bergmann <[hidden email]<mailto:[hidden email]>> wrote: >> We should listen to Torsten but as far as I would expect, only HelpSystem, >> but it is already included in both PharoCore and Squeak. > > The help system is included in Squeak trunk and Pharo core, so > one should be able to load the three example books (Squeak, Pharo, > Metacello) which I uploaded in squeksource/HelpSystem in both > environments. Still they are just small demo books - no real > docu since there is not much content yet. I have pulled the Metacello-Help package over to the metacello repository and have added to a baseline for 1.0-beta.27... but it should have more content... > > However - we could reuse them to document these systems if > for instance Dale is willing to contribute stuff to the > Metacello book or we create an ASCII version of the Metacello > preview PBE chapter. Mariano is actually doing all of the heavy lifting on the PBE chapter:) > > Maybe I am dreaming too much, but it would be cool to export somehow some chapters to HelpSystem. > Is there a way to export from Latex to ASCII ? even more, how difficult could be to code a plugin (or whatever name is) to automatically generate the nice code for HelpSystem from Latex code? > > Then we can include PBE in the image also ;) This would be very cool! It seems that there is a place for online (pdf..) documentation, but the online and in-image documentation really needs to stay in synch! Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
The only way is the pharo book
you can generate latex browse it via google query it. There is a visitor so we can produce what we want from the book structure. Please no copy and paste. Stef On May 25, 2010, at 12:28 AM, Dale Henrichs wrote: > Mariano Martinez Peck wrote: >> On Mon, May 24, 2010 at 11:41 PM, Torsten Bergmann <[hidden email]<mailto:[hidden email]>> wrote: >>> We should listen to Torsten but as far as I would expect, only HelpSystem, >>> but it is already included in both PharoCore and Squeak. >> The help system is included in Squeak trunk and Pharo core, so >> one should be able to load the three example books (Squeak, Pharo, >> Metacello) which I uploaded in squeksource/HelpSystem in both >> environments. Still they are just small demo books - no real >> docu since there is not much content yet. > > I have pulled the Metacello-Help package over to the metacello repository and have added to a baseline for 1.0-beta.27... but it should have more content... > >> However - we could reuse them to document these systems if >> for instance Dale is willing to contribute stuff to the >> Metacello book or we create an ASCII version of the Metacello >> preview PBE chapter. > > Mariano is actually doing all of the heavy lifting on the PBE chapter:) > >> Maybe I am dreaming too much, but it would be cool to export somehow some chapters to HelpSystem. >> Is there a way to export from Latex to ASCII ? even more, how difficult could be to code a plugin (or whatever name is) to automatically generate the nice code for HelpSystem from Latex code? >> Then we can include PBE in the image also ;) > > This would be very cool! > > It seems that there is a place for online (pdf..) documentation, but the online and in-image documentation really needs to stay in synch! > > Dale > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Tue, May 25, 2010 at 09:21, Stéphane Ducasse
<[hidden email]> wrote: > The only way is the pharo book > you can generate latex > browse it via google > query it. > > There is a visitor so we can produce what we want from the book structure. > Please no copy and paste. Embedding a copy of the pier kernel in the image could work, especially since there is already a morphic pier browser. But then why not browse it online? Embedding is only really useful if it's fully exploiting the possibility of linking between text and code. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |