- Pharo-dev - lists.pharo.org

Sista alternate bytecodes + Java Bytecode ?

by Ben Coman

Just wondering about an exotic idea, with Sista facilitating alternate bytecodes (btw, is that multiple bytecode sets within one Image?), how feasible would it be to have the VM process Java bytecode? cheers -ben

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Guillermo Polito

Could you write a blog post? :D - What is the good practice - extending FileLocator - managing paths in a platform independent way (what to extend for unix, mac, windows, default values for unknown platforms...) On Tue, Oct 3, 2017 at 12:52 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Ok. No objections yet. > I will prepare pull requests > > 2017-10-03 12:04 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Yes yes yes >> >> On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Hi denis >>> >>> I like it!. >>> >>> Stef >>> >>> On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> > Hi. >>> > >>> > Many times I was trying to find "global" files of some packages in >>> system. >>> > >>> > For example do you know how to find epicea session logs? >>> > There is class side method for this at EpMonitor: >>> > >>> > EpMonitor logsDirectory >>> > >>> > Is it easy to find when you never look at it? No. >>> > >>> > Do you know how to find sources file? There is message in Smalltalk >>> global: >>> > >>> > Smalltalk sourcesFile >>> > >>> > Is it easy to find? No. >>> > >>> > And there are many other examples. >>> > >>> > But if you read about FileSystem library. You know the common place >>> where to >>> > find well known files. It is FileLocator. >>> > For example changes file is here: >>> > >>> > FileLocator changes. >>> > >>> > So my idea is to introduce kind of pattern, the good style, how to >>> access >>> > global application files: they should be in FileLocator as extensions. >>> > Then it would be super easy to find files of any applications. >>> > >>> > What do you think? >>> > >>> > If it is good idea then we should fix current places in system to >>> follow >>> > this pattern. >>> > >>> > Best regards, >>> > Denis >>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Denis Kudriashov

Ok. No objections yet. I will prepare pull requests 2017-10-03 12:04 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Yes yes yes > > On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi denis >> >> I like it!. >> >> Stef >> >> On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> > Hi. >> > >> > Many times I was trying to find "global" files of some packages in >> system. >> > >> > For example do you know how to find epicea session logs? >> > There is class side method for this at EpMonitor: >> > >> > EpMonitor logsDirectory >> > >> > Is it easy to find when you never look at it? No. >> > >> > Do you know how to find sources file? There is message in Smalltalk >> global: >> > >> > Smalltalk sourcesFile >> > >> > Is it easy to find? No. >> > >> > And there are many other examples. >> > >> > But if you read about FileSystem library. You know the common place >> where to >> > find well known files. It is FileLocator. >> > For example changes file is here: >> > >> > FileLocator changes. >> > >> > So my idea is to introduce kind of pattern, the good style, how to >> access >> > global application files: they should be in FileLocator as extensions. >> > Then it would be super easy to find files of any applications. >> > >> > What do you think? >> > >> > If it is good idea then we should fix current places in system to follow >> > this pattern. >> > >> > Best regards, >> > Denis >> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Oct. 3, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Denis Kudriashov

I implement query for annotations of concrete class. So right now if you will do MyFrameworkAnnotation registeredInstances it will return only MyFrameworkAnnotation instances. It will not include any MyConcreteAnnotation instance. We can change this part if it is better to work with all subclasses. Or we can introduce another message like registeredSubInstances with consistency to general allSubInstances method, Another detail about inheritance: subclasses inherit superclass annotations and override them. 2017-10-03 12:10 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Ok, I'm back from vacations so I'll give a comment other than what I did > :P. > > First I like it. > > Second, how does it work with respect to inheritance? I mean, if I have > for example: > > ClassAnnotation subclass: MyFrameworkAnnotation. > > And then > > MyFrameworkAnnotation subclass: MyConcreteAnnotation1. > MyFrameworkAnnotation subclass: MyConcreteAnnotation2. > > Can I query all my annotations or should do an isKindOf: by hand? > > On Fri, Sep 29, 2017 at 1:10 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> tx! >> >> On Fri, Sep 29, 2017 at 9:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> >>> 2017-09-28 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>>> I would not use meta because you would not write annotationAnnotations >>>> :) >>>> and annotations is meta by its name. >>>> >>>> classAnnotation is much better than metaAnnotation >>>> >>> >>> Done. >>> >>> >>>> >>>> Stef >>>> >>>> >>>> On Thu, Sep 28, 2017 at 5:40 PM, Denis Kudriashov <dionisiydk(a)gmail.com >>>> > wrote: >>>> >>>>> So I renamed it to ClassAnnotation with all related names. >>>>> >>>>> But I keep meta prefix in #metaAnnotations Class extension to avoid >>>>> general name: >>>>> >>>>> MyClass metaAnnotations >>>>> >>>>> You can check updated readme for details https://github.com/dio >>>>> nisiydk/ClassAnnotation >>>>> >>>>> 2017-09-26 17:31 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>>> >>>>>> ;) >>>>>> >>>>>> On Tue, Sep 26, 2017 at 1:28 PM, Ben Coman <btc(a)openinworld.com> >>>>>> wrote: >>>>>> >>>>>>> Shhh... The first rule of meta-club is we don't talk about meta-club. >>>>>>> >>>>>>> >>>>>>> cheers -ben >>>>>>> >>>>>>> >>>>>>> On Mon, Sep 25, 2017 at 11:09 PM, Guillermo Polito < >>>>>>> guillermopolito(a)gmail.com> wrote: >>>>>>> >>>>>>>> Why calling them meta-annotation and not just annotation? >>>>>>>> Annotations are in general already meta :) >>>>>>>> >>>>>>>> On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov < >>>>>>>> dionisiydk(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi. >>>>>>>>> >>>>>>>>> I glad to present one class package which introduces reusable >>>>>>>>> mechanism for first class annotations. >>>>>>>>> >>>>>>>>> The project can be found on github https://github.com/dion >>>>>>>>> isiydk/ClassMetaAnnotation. >>>>>>>>> And I tried to describe why it is needed in my blog >>>>>>>>> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >>>>>>>>> >>>>>>>>> And here is overview: >>>>>>>>> >>>>>>>>> Every annotation should be subclass of ClassMetaAnnotation. To >>>>>>>>> attach it to class you create new class side method which will return an >>>>>>>>> instance of the annotation. Method should be marked with pragma >>>>>>>>> #classMetaAnnotation: >>>>>>>>> >>>>>>>>> >>>>>>>>> MyClass class>>specialAnnotation >>>>>>>>> >>>>>>>>> <classMetaAnnotation> >>>>>>>>> >>>>>>>>> ^MySpecialAnnotation new >>>>>>>>> >>>>>>>>> >>>>>>>>> To query annotations from system there are two methods: >>>>>>>>> >>>>>>>>> 1) You can ask concrete annotation class for all declared >>>>>>>>> instances: >>>>>>>>> >>>>>>>>> MySpecialAnnotation declaredInstances >>>>>>>>> >>>>>>>>> 2) You can ask given class for all attached annotations: >>>>>>>>> >>>>>>>>> MyClass metaAnnotations >>>>>>>>> >>>>>>>>> Every annotation includes information about annotated class and >>>>>>>>> the selector of declaring method. >>>>>>>>> All annotations are cached. So it is cheap to query them. There >>>>>>>>> are extra messages to enumerate annotations using block. >>>>>>>>> >>>>>>>>> Now let's discuss it. I think it can be good addition for the >>>>>>>>> Pharo 7. Especially that it is very small code. >>>>>>>>> >>>>>>>>> Also I would like to thank Marcus who helps me realize this >>>>>>>>> concept in Commander and Calypso which I start simplify with this library. >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Denis >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Guille Polito >>>>>>>> >>>>>>>> Research Engineer >>>>>>>> >>>>>>>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>>>>>>> >>>>>>>> CRIStAL - UMR 9189 >>>>>>>> >>>>>>>> French National Center for Scientific Research - *http://www.cnrs.fr >>>>>>>> <http://www.cnrs.fr>* >>>>>>>> >>>>>>>> >>>>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>>>>> >>>>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Oct. 3, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Guillermo Polito

Ok, I'm back from vacations so I'll give a comment other than what I did :P. First I like it. Second, how does it work with respect to inheritance? I mean, if I have for example: ClassAnnotation subclass: MyFrameworkAnnotation. And then MyFrameworkAnnotation subclass: MyConcreteAnnotation1. MyFrameworkAnnotation subclass: MyConcreteAnnotation2. Can I query all my annotations or should do an isKindOf: by hand? On Fri, Sep 29, 2017 at 1:10 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > tx! > > On Fri, Sep 29, 2017 at 9:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2017-09-28 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >>> I would not use meta because you would not write annotationAnnotations :) >>> and annotations is meta by its name. >>> >>> classAnnotation is much better than metaAnnotation >>> >> >> Done. >> >> >>> >>> Stef >>> >>> >>> On Thu, Sep 28, 2017 at 5:40 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>>> So I renamed it to ClassAnnotation with all related names. >>>> >>>> But I keep meta prefix in #metaAnnotations Class extension to avoid >>>> general name: >>>> >>>> MyClass metaAnnotations >>>> >>>> You can check updated readme for details https://github.com/dio >>>> nisiydk/ClassAnnotation >>>> >>>> 2017-09-26 17:31 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>> >>>>> ;) >>>>> >>>>> On Tue, Sep 26, 2017 at 1:28 PM, Ben Coman <btc(a)openinworld.com> >>>>> wrote: >>>>> >>>>>> Shhh... The first rule of meta-club is we don't talk about meta-club. >>>>>> >>>>>> >>>>>> cheers -ben >>>>>> >>>>>> >>>>>> On Mon, Sep 25, 2017 at 11:09 PM, Guillermo Polito < >>>>>> guillermopolito(a)gmail.com> wrote: >>>>>> >>>>>>> Why calling them meta-annotation and not just annotation? >>>>>>> Annotations are in general already meta :) >>>>>>> >>>>>>> On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov < >>>>>>> dionisiydk(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hi. >>>>>>>> >>>>>>>> I glad to present one class package which introduces reusable >>>>>>>> mechanism for first class annotations. >>>>>>>> >>>>>>>> The project can be found on github https://github.com/dion >>>>>>>> isiydk/ClassMetaAnnotation. >>>>>>>> And I tried to describe why it is needed in my blog >>>>>>>> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >>>>>>>> >>>>>>>> And here is overview: >>>>>>>> >>>>>>>> Every annotation should be subclass of ClassMetaAnnotation. To >>>>>>>> attach it to class you create new class side method which will return an >>>>>>>> instance of the annotation. Method should be marked with pragma >>>>>>>> #classMetaAnnotation: >>>>>>>> >>>>>>>> >>>>>>>> MyClass class>>specialAnnotation >>>>>>>> >>>>>>>> <classMetaAnnotation> >>>>>>>> >>>>>>>> ^MySpecialAnnotation new >>>>>>>> >>>>>>>> >>>>>>>> To query annotations from system there are two methods: >>>>>>>> >>>>>>>> 1) You can ask concrete annotation class for all declared instances: >>>>>>>> >>>>>>>> MySpecialAnnotation declaredInstances >>>>>>>> >>>>>>>> 2) You can ask given class for all attached annotations: >>>>>>>> >>>>>>>> MyClass metaAnnotations >>>>>>>> >>>>>>>> Every annotation includes information about annotated class and the >>>>>>>> selector of declaring method. >>>>>>>> All annotations are cached. So it is cheap to query them. There are >>>>>>>> extra messages to enumerate annotations using block. >>>>>>>> >>>>>>>> Now let's discuss it. I think it can be good addition for the Pharo >>>>>>>> 7. Especially that it is very small code. >>>>>>>> >>>>>>>> Also I would like to thank Marcus who helps me realize this concept >>>>>>>> in Commander and Calypso which I start simplify with this library. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Denis >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> >>>>>>> >>>>>>> Guille Polito >>>>>>> >>>>>>> Research Engineer >>>>>>> >>>>>>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>>>>>> >>>>>>> CRIStAL - UMR 9189 >>>>>>> >>>>>>> French National Center for Scientific Research - *http://www.cnrs.fr >>>>>>> <http://www.cnrs.fr>* >>>>>>> >>>>>>> >>>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>>>> >>>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Guillermo Polito

Yes yes yes On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi denis > > I like it!. > > Stef > > On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > Hi. > > > > Many times I was trying to find "global" files of some packages in > system. > > > > For example do you know how to find epicea session logs? > > There is class side method for this at EpMonitor: > > > > EpMonitor logsDirectory > > > > Is it easy to find when you never look at it? No. > > > > Do you know how to find sources file? There is message in Smalltalk > global: > > > > Smalltalk sourcesFile > > > > Is it easy to find? No. > > > > And there are many other examples. > > > > But if you read about FileSystem library. You know the common place > where to > > find well known files. It is FileLocator. > > For example changes file is here: > > > > FileLocator changes. > > > > So my idea is to introduce kind of pattern, the good style, how to access > > global application files: they should be in FileLocator as extensions. > > Then it would be super easy to find files of any applications. > > > > What do you think? > > > > If it is good idea then we should fix current places in system to follow > > this pattern. > > > > Best regards, > > Denis > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 3, 2017

Re: [Pharo-dev] Iceberg - loading baseline

by Esteban Lorenzano

> On 3 Oct 2017, at 11:23, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Don't forget to enable Metacello integration in settings. ah, yes :) In pharo 6.1 this is a must (I keep forgetting it, heh) Esteban > > On Tue, Oct 3, 2017 at 8:55 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >> On 3 Oct 2017, at 08:47, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz <mailto:bliznjan@fit.cvut.cz>> wrote: >> >> Hello >> >> I have a local clone of git repository and I am looking for code that adds >> this repository to Iceberg and then loads its baseline into Pharo. I am >> using Pharo 6.1 (image 60510) and last stable Windows VM. >> >> Right now I am experimenting with following code, it adds the project into >> Iceberg, but does not load the baseline. The code is: >> >> SystemSettingsPersistence updateSettingNodes. "sets ssh key locations" >> >> (Smalltalk at: #IceRepositoryCreator) new >> url: 'git(a)gitlab.com <mailto:git@gitlab.com>:bliznjan/nameofmyproject.git'; >> location: '/C:/Users/User/Pharo/repo/nameofmyproject/filetree' >> asFileReference; >> subdirectory: 'filetree'; >> createRepository. "this part seems to work fineâ > > I think this is your error: '/C:/Users/User/Pharo/repo/nameofmyproject/filetree, needs to be '/C:/Users/User/Pharo/repo/nameofmyproject (without the filetree part, which is the subdirectory) > > now, I think if you do: > > Metacello new > repository: âgitlab://bliznjan/nameofmyproject/filetree' <>; > baseline: âMyProjectâ > load. > > ir will also do what you want without the two steps. > >> >> Metacello new baseline: 'NameOfMyProject'; repository: >> 'gitlocal:///C:/Users/User/Pharo/repo/nameofmyproject/filetree <>'; load. "this >> one fails with exception below" >> >> >> loading the baseline ends with Exception >> Could not resolve: BaselineOfNameOfMyProject [BaselineOfNameOfMyProject] >> in C:\Users\User\Pharo\images\TestingImage1\pharo-local\package-cache >> C:\Users\User\Pharo\repo\nameofmyproject\filetree (Libgit) >> >> Those paths seem correct - the package-cache is located in exactly that >> position (but does not contain anything that relates to my project) and the >> filetree (repository) in the mentioned path and there is a >> BaselineOfNameOfMyProject.package directory in there. >> >> Also, if I then try loading the baseline manually via Iceberg, by right >> clicking on BaselineOfNameOfMyProject in Packages tab, I get exactly same >> exception. >> >> Loading packages one by one manually via Iceberg Packages tab works. Also, >> loading the baseline via GitFileTree works. >> >> Thank you >> Jan >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> >> > >

Oct. 3, 2017

Re: [Pharo-dev] Iceberg - loading baseline

by Peter UhnÃ¡k

Don't forget to enable Metacello integration in settings. On Tue, Oct 3, 2017 at 8:55 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 3 Oct 2017, at 08:47, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> wrote: > > Hello > > I have a local clone of git repository and I am looking for code that adds > this repository to Iceberg and then loads its baseline into Pharo. I am > using Pharo 6.1 (image 60510) and last stable Windows VM. > > Right now I am experimenting with following code, it adds the project into > Iceberg, but does not load the baseline. The code is: > > SystemSettingsPersistence updateSettingNodes. "sets ssh key locations" > > (Smalltalk at: #IceRepositoryCreator) new > url: 'git@gitlab.com:bliznjan/nameofmyproject.git'; > location: '/C:/Users/User/Pharo/repo/nameofmyproject/filetree' > asFileReference; > subdirectory: 'filetree'; > createRepository. "this part seems to work fineâ > > > I think this is your error: '/C:/Users/User/Pharo/repo/nameofmyproject/filetree, > needs to be '/C:/Users/User/Pharo/repo/nameofmyproject (without the > filetree part, which is the subdirectory) > > now, I think if you do: > > Metacello new > repository: âgitlab://bliznjan/nameofmyproject/filetree'; > baseline: âMyProjectâ > load. > > ir will also do what you want without the two steps. > > > Metacello new baseline: 'NameOfMyProject'; repository: > 'gitlocal:///C:/Users/User/Pharo/repo/nameofmyproject/filetree'; load. > "this > one fails with exception below" > > > loading the baseline ends with Exception > Could not resolve: BaselineOfNameOfMyProject [BaselineOfNameOfMyProject] > in C:\Users\User\Pharo\images\TestingImage1\pharo-local\package-cache > C:\Users\User\Pharo\repo\nameofmyproject\filetree (Libgit) > > Those paths seem correct - the package-cache is located in exactly that > position (but does not contain anything that relates to my project) and the > filetree (repository) in the mentioned path and there is a > BaselineOfNameOfMyProject.package directory in there. > > Also, if I then try loading the baseline manually via Iceberg, by right > clicking on BaselineOfNameOfMyProject in Packages tab, I get exactly same > exception. > > Loading packages one by one manually via Iceberg Packages tab works. Also, > loading the baseline via GitFileTree works. > > Thank you > Jan > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > >

Oct. 3, 2017

Re: [Pharo-dev] Pharo Launcher Error

by Christophe Demarey

Hi Brad, > Le 3 oct. 2017 Ã 09:51, stephan <stephan(a)stack.nl> a Ã©crit : > > On 03-10-17 02:05, Brad wrote: >> I was under the understanding that everything was 64 bit, launcher image and vm. > > No, but it supports loading and running 64 bit images. It downloads a 64 bit vm to run those. Stephan is right. For now, the launcher is only shipped with a Pharo 6.1 - 32 bits image. But, it is now able to fetch automatically needed VMs to run 64-bits images (and others). You can find a bundled version (pharo launcher + its vm) here: http://files.pharo.org/platform/launcher/. I recommand to use v1.0. Regards, Christophe

Oct. 3, 2017

Re: [Pharo-dev] Pharo Launcher Error

by stephan

On 03-10-17 02:05, Brad wrote: > I was under the understanding that everything was 64 bit, launcher image and vm. No, but it supports loading and running 64 bit images. It downloads a 64 bit vm to run those. Stephan

Oct. 3, 2017