- Pharo-dev - lists.pharo.org

FloatArray

by Jimmie Houchin

I just recently discovered FloatArray by accident. I was close to having to use Python/Numpy due to considerable performance differences. Performance is very important. In one of my test using a 212000 item array of floats and doing a sum on each iteration through the array Pharo was taking 17 minutes verses Python/Numpy taking 20 seconds. Using FloatArray closes the gap to 40 seconds. That is acceptable. However when looking at the FloatArray comment it says it uses 32bit floats. I need 64bit. I don't even know where to look to create 64bit FloatArrays. I am surprised that they didn't get converted when moving to 64bit Pharo. Would I need to change VM source? Compile a new VM and create image side classes? I have not messed with VM in years. I do not know where the FloatArray plugin would be. Any pointers would be a great help. If this needs to be on the vm-dev list I can move it there. Thanks. Jimmie

April 24, 2019

Lectures at Montreal

by StÃ©phane Ducasse

Hello Just a little mail to mention that I will visit montreal and give some lectures 23 and 24 of May. If Montreal Smalltalkers want to discuss let me know. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

April 23, 2019

Re: [Pharo-dev] how implement isAbstract?

by Tudor Girba

Hi, I think that it is good that isAbstract does not mean isInstantiatable. However, I also think that isAbstract is too generic and that it would be better to have the tools implement their meaning rather than relying on a generic term. Cheers, Doru > On Apr 23, 2019, at 5:58 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > I ended up being surprised today that classes that have abstract > methods (send #subclassResponsibility) were returning false to > `isAbstract` and true to `hasAbstractMethods`. > I see that the behavior for isAbstract changed over the years: when it > was added [1] it was checking for abstract methods. Then it was > changed to always return false and allow overrides [2]. > > Is there an explicit need to have/keep `isAbstract` at the class > level? Users can still instantiate those classes, send message to them > and get SubclassResponsibility errors. Tools could implement specific > solutions for handling this. > > Cheers, > Andrei > > [1] https://github.com/pharo-project/pharo/pull/541/files > [2] https://github.com/pharo-project/pharo/pull/1090/files > > On Mon, Apr 1, 2019 at 3:02 PM Tim Mackinnon <tim(a)testit.works> wrote: >> >> On 1 Apr 2019, at 09:54, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> >> >> Or, if the class has subclasses, one could get a suggestion/action to >> implement the missing method as >> missingMethod >> ^self subclassResponsibility >> >> Which also has the benefit of working nicely with the "expected (or was that >> "missing"?) protocol" functionality. >> Unless you meant something else? >> >> >> >> I donât know if we are all talking about the same thing. In my image, I have a class where I havenât got the isAbstract defined, and so Calypso shows a red message - as it thinks Iâm supposed to implement #execute (if it knows my intent that my class is abstract, then it doesnât show the red warning). I think this is Denisâ question? >> >> Sure, if I choose to use the abstract class, then its my choice, but as a lint checker -having useful warnings is helpful. But it is a nuisance defining isAbstract - and Iâd almost prefer it assumes its abstract in this case (the normal expectations?) unless I tag it as concrete and signal to users that they might consider using my class (its probably a design smell these days though) >> > -- www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

April 23, 2019

Re: [Pharo-dev] how implement isAbstract?

by Andrei Chis

I ended up being surprised today that classes that have abstract methods (send #subclassResponsibility) were returning false to `isAbstract` and true to `hasAbstractMethods`. I see that the behavior for isAbstract changed over the years: when it was added [1] it was checking for abstract methods. Then it was changed to always return false and allow overrides [2]. Is there an explicit need to have/keep `isAbstract` at the class level? Users can still instantiate those classes, send message to them and get SubclassResponsibility errors. Tools could implement specific solutions for handling this. Cheers, Andrei [1] https://github.com/pharo-project/pharo/pull/541/files [2] https://github.com/pharo-project/pharo/pull/1090/files On Mon, Apr 1, 2019 at 3:02 PM Tim Mackinnon <tim(a)testit.works> wrote: > > On 1 Apr 2019, at 09:54, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > > Or, if the class has subclasses, one could get a suggestion/action to > implement the missing method as > missingMethod > ^self subclassResponsibility > > Which also has the benefit of working nicely with the "expected (or was that > "missing"?) protocol" functionality. > Unless you meant something else? > > > > I donât know if we are all talking about the same thing. In my image, I have a class where I havenât got the isAbstract defined, and so Calypso shows a red message - as it thinks Iâm supposed to implement #execute (if it knows my intent that my class is abstract, then it doesnât show the red warning). I think this is Denisâ question? > > Sure, if I choose to use the abstract class, then its my choice, but as a lint checker -having useful warnings is helpful. But it is a nuisance defining isAbstract - and Iâd almost prefer it assumes its abstract in this case (the normal expectations?) unless I tag it as concrete and signal to users that they might consider using my class (its probably a design smell these days though) >

April 23, 2019

[Pharo 8.0] Build #232: 3196-ObjectLayout: remove var compactClassIndex

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #232 was: SUCCESS. The Pull Request #3208 was integrated: "3196-ObjectLayout: remove var compactClassIndex" Pull request url: https://github.com/pharo-project/pharo/pull/3208 Issue Url: https://github.com/pharo-project/pharo/issues/MarcusDenker Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 20, 2019

[Pharo 8.0] Build #231: 3206-NautilusRefactoring-contains-dead-code

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #231 was: FAILURE. The Pull Request #3207 was integrated: "3206-NautilusRefactoring-contains-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/3207 Issue Url: https://github.com/pharo-project/pharo/issues/3206 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 20, 2019

Re: [Pharo-dev] [Pharo-users] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

by StÃ©phane Ducasse

> > > Hi Esteban, > > This is fantastic! We are eager to investigate how Roassal3 can run in an external window. this will possible even without GTK3 :) Stef > > Alexandre > >> On Apr 18, 2019, at 6:08 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: >> >> We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! >> >> Why we want a Spec 2.0 with different backends? >> >> There are reasons that converged to decide us to make it: >> >> â¢ First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). >> â¢ Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: >> â¢ Because there is still an important place for desktop applications market and most medium-size to big business still require them. >> â¢ Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). >> >> For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. >> >> Why Gtk3? >> >> There are some other important players in the "native widgets scene", so why we choose Gtk3? >> >> Again, several reasons were taken into account: >> >> â¢ Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. >> â¢ It is very mature and popular. >> â¢ It is made in plain C. >> >> Next step: tool migration >> >> The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: >> >> â¢ Old GT tools will be replaced by new Spec tools (while preserving its power). >> â¢ Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). >> â¢ Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. >> >> And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) >> >> >> A small screenshot of the new Inspector (WIP): >> >> <Screenshot 2019-04-18 at 12.07.16.png> >> >> Esteban > > > > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

April 20, 2019

Re: [Pharo-dev] [squeak-dev] Any experts on using path in app bundles willing to help me?

by Esteban Lorenzano

> On 19 Apr 2019, at 20:38, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Esteban, > > On Fri, Apr 19, 2019 at 12:51 AM Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > yep. > The Pharo distribution uses install_name_tool to deal with it, if you want an example already in osvm code: > > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.macos64x64… <https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.macos64x64…> > > It's perhaps a case of "if it ain't broke, don't fixit", but I wonder if it would be better for Pharo to use Frameworks to hold dlls and Resources to hold plugin dlls/bindles. Contents/MacOS/Plugins is, I *think*, unique to Pharo. Yes, this is an inherited situation and I ignore the rationale behind it. I agree this way of distributing is not appropriate but I just didnât have the time to fix it (because after all, it is working so I always have something more urgent to do). Esteban > > > Esteban > >> On 18 Apr 2019, at 19:35, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >> >> >> >> On Thu, Apr 18, 2019 at 10:08 AM Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >> Hi All, >> >> I have a plugin dependent on several support libraries that ma y be shared with other plugins. So I want the support libraries in a common place (TheVm.app/Contents/Frameworks) while the plugins themselves are bundles in TheVM.app/Contents/Resources. In allowing one to install plugin support libraries in TheVM.app/Contents/Frameworks I have to use the linker's -rpath feature to specify where dlopen may find the search libraries. The question i don't see an answer to in Apple's documentation is whether one uses -rpath when linking the plugin, or when linking the VM into which the plugin will be loaded, or both. Anybody ever done this and know definitively what to do? >> >> Never mind. I think I've found what I need: >> https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4… <https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4…> >> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath <https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath> >> >> _,,,^..^,,,_ >> best, Eliot > > > > > -- > _,,,^..^,,,_ > best, Eliot

April 20, 2019

Small Pharo developer contract

by ducasse

Hi guys This may interest some of you. Stef

April 20, 2019

Re: [Pharo-users] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

by Alexandre Bergel

Hi Esteban, This is fantastic! We are eager to investigate how Roassal3 can run in an external window. Alexandre > On Apr 18, 2019, at 6:08 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: > > We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! > > Why we want a Spec 2.0 with different backends? > > There are reasons that converged to decide us to make it: > > â¢ First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). > â¢ Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: > â¢ Because there is still an important place for desktop applications market and most medium-size to big business still require them. > â¢ Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). > > For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. > > Why Gtk3? > > There are some other important players in the "native widgets scene", so why we choose Gtk3? > > Again, several reasons were taken into account: > > â¢ Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. > â¢ It is very mature and popular. > â¢ It is made in plain C. > > Next step: tool migration > > The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: > > â¢ Old GT tools will be replaced by new Spec tools (while preserving its power). > â¢ Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). > â¢ Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. > > And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) > > > A small screenshot of the new Inspector (WIP): > > <Screenshot 2019-04-18 at 12.07.16.png> > > Esteban

April 19, 2019