Norbert, Ah, yes different use case ... for the scripts I'm writing I wanted to leverage "loaded code" as I've got a whole class hierarchy supporting the GsDevKit environment and did not relish the idea of doing that all in bash distributed across a number of different scripts ...
Haha, I live in tODE all the time, where Smalltalk _is_ the scripting language so I don't feel your particular brand of pain:) Dale On Thu, Jul 24, 2014 at 7:33 AM, Norbert Hartl <norb...@hartl.name> wrote: > Dale, > > thanks for this extensive explanation. That looks all really good but I > think I'm looking for the exact opposite. You arrange a lot of pieces in a > huge environment and you make it bootstrap itself. The environment/project > is defined and all parts need to work together. I'm looking for help doing > simple tasks. I have a lot of bash scripts but there is a border of > complexity where shell scripts become a pain in the spine. And even more > important I'm faster with smalltalk then with bash so I just need an easy > entrance to the world/image here. > I did some of this in the past with preloaded code that can be triggered > by commandline handlers. But you get easily the problem that you need to > load new code in the image before you can use it from the commandline which > somewhat defeats the purpose. I would like something in between: Having > supporting code in the image but I'm also able to do the same scripts from > the shell. So you can easily move responsibility of things between > commandline and image. > > Norbert > > Am 24.07.2014 um 16:07 schrieb Dale Henrichs < > dale.henri...@gemtalksystems.com>: > > Norbert, > > I've just recently made the decision to start using Pharo3.0 to do all of > the heavy lifting for my GsDevKit project[1] shell scripts. > > I use boilerplate bash code to setup the environment[2] and then call > Pharo CommandLineHandler[3] to do the real work ... > > I embed the script repository[4] in the project, so the script code > matches the directory structure and I build the command line pharo image[5] > as part of my installation. > > I've been pretty pleased with the results, too. It's pretty > straightforward to run the scripts from within an interactive Pharo for > debugging and it beats the heck out of trying to do *simple things* with > bash... > > My only wish is that CommandLine had better getopts support - I have a > posix getopts commandline parser implementation that iI use for tODE that > I'd be willing to share ... hint hint:). > > Dale > > [1] > https://github.com/GsDevKit/gsDevKitHome#open-source-development-kit-for-gemstones-64-bit > [2] https://github.com/GsDevKit/gsDevKitHome/blob/master/bin/createStone > [3] > https://github.com/GsDevKit/gsDevKitHome/blob/master/bin/createStone#L78-82 > [4] https://github.com/GsDevKit/gsDevKitHome/tree/master/repository > [5] > https://github.com/GsDevKit/gsDevKitHome/blob/master/bin/createTodeImage#L67-93 > > > On Thu, Jul 24, 2014 at 3:37 AM, Norbert Hartl <norb...@hartl.name> wrote: > >> What are you using to do jobs on the commandline. I'm sick of doing bash >> and sed,perl,jq,... stuff. What would be the quickest start when using a >> normal image? And what if I want to give coral a start. Does it work in >> 3.0? Best place to load stuff from? >> >> thanks, >> >> Norbert >> >> >> > >
