On 2013-03-12, at 19:39, Mariano Martinez Peck <[email protected]> wrote:
> Why don't we add a link in the Pharo website with such an online help? > It would be nice if this is indexable by Google. once I fixed the rough edges of this new export, yes :), google will be happy and everybody can search for code snippets online! :) > Thanks Cami!!! Nice job > > On Tue, Mar 12, 2013 at 2:00 PM, Camillo Bruni <[email protected]>wrote: > >> how I hate the options of the VM |( >> >> no --help, >> -help exits unsuccessful >> .... grml grml grml >> >> On 2013-03-12, at 17:20, "[email protected]" <[email protected]> wrote: >> >>> And it is not even true >>> >>> <imageName> defaults to `Squeak.image'. >>> >>> as I get a file dialog when such an image is in the folder. (Duly >>> created with the save command) >>> >>> Phil >>> >>> 2013/3/12 Camillo Bruni <[email protected]>: >>>> >>>> On 2013-03-12, at 16:51, Sven Van Caekenberghe <[email protected]> wrote: >>>> >>>>> These are the standard installed handlers: >>>>> >>>>> $ ../vm.sh Pharo.image --list >>>>> Currently installed Command Line Handlers: >>>>> st Loads and executes .st source files >>>>> Fuel Loads fuel files >>>>> config Install and inspect Metacello Configurations from >> the command line >>>>> save Rename the image and changes file >>>>> test A command line test runner >>>>> update Load updates >>>>> printVersion Print image version >>>>> eval Directly evaluates passed in one line scripts >>>>> >>>>> for each of them you can do --help >>>>> >>>>> $ ../vm.sh Pharo.image save --help >>>>> Usage: save <imageBaseName> [--delete-old] >>>>> <imageName> a base name for the image >>>>> --delete-old remove the old image and changes file >>>>> >>>>> Documentation: >>>>> Saves the image and changes file under a new name. >>>>> >>>>> Examples: >>>>> # create a 'bar.image' and 'foo.changes' >>>>> $PHAROVM Foo.image saveAs bar >>>>> # create the same file as in the previous example but delete >> Foo.image and Foo.changes >>>>> $PHAROVM Foo.image saveAs bar --delete-old >>>>> >>>>> Sven >>>> >>>> ups, typos, typos: saveAs => save :/ >>>> I'll open an issue >>>> >>>> >>>>> On 12 Mar 2013, at 16:48, Sven Van Caekenberghe <[email protected]> wrote: >>>>> >>>>>> That already exists no ? >>>>>> >>>>>> $ ./vm.sh Pharo.image save Foo >>>>>> >>>>>> will do a 'Save As..' to Foo.[image|changes] >>>>>> >>>>>> On 12 Mar 2013, at 16:45, "[email protected]" <[email protected]> >> wrote: >>>>>> >>>>>>> BTW, an interesting additional ./vm.sh command would be: >>>>>>> >>>>>>> $./vm.sh clone Pharo WebDocExperiment >>>>>>> >>>>>>> which would do a copy of Pharo.image and Pharo.changes to the >>>>>>> WebDoc.image and WebDoc.changes >>>>>>> >>>>>>> Phil >>>>>>> 2013/3/12 Martin Dias <[email protected]>: >>>>>>>> impressive!! >>>>>>>> >>>>>>>> On Tue, Mar 12, 2013 at 3:06 PM, [email protected] < >> [email protected]> wrote: >>>>>>>>> http://pharo.gforge.inria.fr/doc/1.4/doc/package/undefined >>>>>>>>> >>>>>>>>> RSArrayNode. >>>>>>>>> >>>>>>>>> 2013/3/12 Camillo Bruni <[email protected]>: >>>>>>>>>> >>>>>>>>>> On 2013-03-12, at 14:49, Guillermo Polito < >> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> On Tue, Mar 12, 2013 at 2:18 PM, Camillo Bruni < >> [email protected]>wrote: >>>>>>>>>>> >>>>>>>>>>>> finally, after the 100th attempt I managed to export the >> documentation on >>>>>>>>>>>> 1.4 >>>>>>>>>>>> >>>>>>>>>>>> http://pharo.gforge.inria.fr/doc/1.4 >>>>>>>>>>>> >>>>>>>>>>>> this weekend I will tackle 2.0 :) and of course, it still needs >> some love! >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> - How can I export it myself too? >>>>>>>>>> >>>>>>>>>> currently work in progress, but there is a configuration for it: >>>>>>>>>> >>>>>>>>>> Gofer new >>>>>>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main' >>>>>>>>>> configurationOf: 'WebDoc'; >>>>>>>>>> loadDevelopment. >>>>>>>>>> >>>>>>>>>> And I think you have to manually start up a seaside adapter, once >> that is done: >>>>>>>>>> >>>>>>>>>> http://localhost:8080/doc >>>>>>>>>> >>>>>>>>>> should do the trick. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> - We should report issues about it in the foogzbuz (or whatever >> it is >>>>>>>>>>> called I cannot reproduce yet :P). >>>>>>>>>> >>>>>>>>>> yes, maybe let's wait until next weekend :) since it doesn't run >> under >>>>>>>>>> 2.0 yet :P. I won't work on during the day :P that is reserved >> for Guido and >>>>>>>>>> the paper... >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com
