So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of the launcher...
pharo6-64-ui PharoLauncher.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit... How is one using the launcher for 64 bit stuff? Phil On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > If you don't try you will not understand what you miss. > > On Sun, Nov 26, 2017 at 2:10 PM, Herby Vojčík <he...@mailbox.sk> wrote: > > Stephane Ducasse wrote: > >> > >> Then do not try :) like that you will never get a chance to know :) > > > > > > Could you please explain? I understood your sentence has high dose of > homour > > which I cannot decipher since I lack certain abilities for that. > > > > Thanks, Herby > > > >> Stef > >> > >> > >> On Sun, Nov 26, 2017 at 1:48 PM, Herby Vojčík<he...@mailbox.sk> wrote: > >>> > >>> Stephane Ducasse wrote: > >>>> > >>>> Why don't you try? It does not bite. > >>>> > >>>> For me it works in all scenario. I have projects that i manage over > >>>> several weeks and others I drop day to day. > >>>> And I have also startup script per versions. > >>> > >>> > >>> Maybe I will. The main problem was I didn't what it's good about at > all - > >>> load image for a version, runs it - what's the "wow it's great" about? > >>> Missed part was it loads correct vm; plus makes sense when you have > >>> hundreds > >>> (I don't). Now it must be combined with the startup script magic to > work > >>> with long-time projects, but those are also new to me - did not know of > >>> them > >>> until your booklet, not using them at all yet. > >>> > >>> Herby > >>> > >>> > >>>> Stef > >>>> > >>>> On Fri, Nov 24, 2017 at 3:10 PM, Herby Vojčík<he...@mailbox.sk> > wrote: > >>>>> > >>>>> Thank you all, now I understand it better. Good for lots of > "branches". > >>>>> > >>>>> However, I wonder how does it work with the rule I read somewhere: > >>>>> "start > >>>>> each day [of work on a project] with a new image", which means I > should > >>>>> not > >>>>> reuse clean new image (as it needs populating from VCSes etc.) nor > >>>>> reuse > >>>>> existing image (I should start with the new one). Or does it combine > >>>>> with > >>>>> some startup-magic described in one of the recent Steph's booklets, > the > >>>>> "one > >>>>> start per [new] image" case (but again, one should discriminate > >>>>> projects > >>>>> from each other)? > >>>>> > >>>>> Thanks, Herby > >>>>> > >>>>> Peter Uhnák wrote: > >>>>>> > >>>>>> Hi Herby, > >>>>>> > >>>>>> normally people use different images for their different projects, > >>>>>> different versions, trying things, etc. Which means we end up with > >>>>>> many > >>>>>> locations on disk, and it can be hard to track. > >>>>>> So PharoLauncher is a nice tool where you can download fresh image > >>>>>> just > >>>>>> by clicking, and you see the list of your local images and can > launch > >>>>>> them, etc. > >>>>>> > >>>>>> Peter > >>>>>> > >>>>>> On Thu, Nov 23, 2017 at 12:56 PM, Herby Vojčík<he...@mailbox.sk > >>>>>> <mailto:he...@mailbox.sk>> wrote: > >>>>>> > >>>>>> Stephane Ducasse wrote: > >>>>>> > >>>>>> Hi > >>>>>> > >>>>>> I love the PharoLauncher. > >>>>>> > >>>>>> > >>>>>> Pardon my question, I have downloaded it and looked at it, > but I > >>>>>> don't get it. What does it do / what are the use cases (honest > >>>>>> question)? > >>>>>> > >>>>>> Thanks, Herby > >>>>>> > >>>>>> > >>>>>> It helps me to manage my parallel development and > projects. > >>>>>> > >>>>>> We should put a link on the Pharo web site because > >>>>>> > >>>>>> http://files.pharo.org/platform/launcher/ > >>>>>> <http://files.pharo.org/platform/launcher/> > >>>>>> > >>>>>> is arcane. > >>>>>> > >>>>>> Stef > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>> > >> > > > > > > >
