October 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1353: REVERT-22239-DataAndTimeTesttestAsDateAndTime-is-meaningful
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2018

Oct. 30, 2018

There is a new Pharo build available! The status of the build #1353 was: FAILURE. The Pull Request #1945 was integrated: "REVERT-22239-DataAndTimeTesttestAsDateAndTime-is-meaningful" Pull request url: https://github.com/pharo-project/pharo/pull/1945 Issue Url: https://pharo.fogbugz.com/f/cases/REVERT Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1352: 21667-Dropping-a-mcz-on-image-raises-an-error
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2018

Oct. 30, 2018

There is a new Pharo build available! The status of the build #1352 was: FAILURE. The Pull Request #1939 was integrated: "21667-Dropping-a-mcz-on-image-raises-an-error" Pull request url: https://github.com/pharo-project/pharo/pull/1939 Issue Url: https://pharo.fogbugz.com/f/cases/21667 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1351: 22615-Random-Core-can-be-removed-form-the-manual-dependencies-list-of-Collections-String
by ci-pharo-ci-jenkins2＠inria.fr Oct. 29, 2018

Oct. 29, 2018

There is a new Pharo build available! The status of the build #1351 was: FAILURE. The Pull Request #1944 was integrated: "22615-Random-Core-can-be-removed-form-the-manual-dependencies-list-of-Collections-String" Pull request url: https://github.com/pharo-project/pharo/pull/1944 Issue Url: https://pharo.fogbugz.com/f/cases/22615 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1350: 22499-modifying-a-method-in-a-trait-that-is-aliased-in-a-class-is-not-propagated-correctly-
by ci-pharo-ci-jenkins2＠inria.fr Oct. 29, 2018

Oct. 29, 2018

There is a new Pharo build available! The status of the build #1350 was: FAILURE. The Pull Request #1938 was integrated: "22499-modifying-a-method-in-a-trait-that-is-aliased-in-a-class-is-not-propagated-correctly-" Pull request url: https://github.com/pharo-project/pharo/pull/1938 Issue Url: https://pharo.fogbugz.com/f/cases/22499 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 22 October 2018
by estebanlm＠gmail.com Oct. 29, 2018

Oct. 29, 2018

Hello! This is my weekly ChangeLog, from 22 October 2018 to 28 October 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=22/10/2018&to=28/10/2018 ChangeLog ========= 22 October 2018: ---------------- * I (finally) finnished couple of PRs for Calypso! * [Issue 304](https://github.com/pharo-ide/Calypso/pull/346) * [Issue 335](https://github.com/pharo-ide/Calypso/pull/348) This two are the content of my work of last week. It was complicated to understand the model behind calypso and that took more time than preview. A bit of an explanation: 1. First one eliminates the extension that takes +Traits+ as if they would be superclasses of somekind. While I understand what Denis tried to do here, the premise he took is wrong: traits are not a multiple inheritance mechanism (even if they can be used to simulate it), traits are a *composition* strategy (and there is a trait composition arithmetic that is somekind complex that needs to be taken into account). As a result, the price of simulating a multiple-inheritance scenario where there is not was complexifying the model at levels way higher than desired. Also it was not working properly and patching it to make it work was resulting on re-writing all the trait arithmetic at UI level. So the right approach here is just to remove. And to be clear: I'm not oposed to the existence of a plugin that hides methods comming from traits (even if I think is incorrect because once a trait is applied, those methods actually 'belong' to the class). But in case you want something like this, it can be implemented in a much simpler way by not mixing what a superclass and a trait is. 2. Second PR also eliminates something :) This time I eliminate the inclusion of metaclasses in the extension list while displaying a package. Again, I understand what Denis tried to do: to easy the view of which classes are extended in the class side and the ones that are extended in instance side. Problem with thid is that it was breaking completely the cognitive model the system browser offers, which is already complex enough to add also an exceptional behaviour. Anyway, this list now works as before: if there are extensions classes are shown and to see the class side extensions you need to click in class side option. cheers! Esteban

1 0

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by John M McIntosh Oct. 29, 2018

Oct. 29, 2018

Although xCode makes much of that process easier it is just a GUI front end for a bunch of command line tools. You can re-sign and submit an app from the command line for enterprise usage, no doubt the same for the store. Apple at one time had a utility app to submit apps to the store for people needed to sub 100âs of apps at a time. .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk On Sun, Oct 28, 2018 at 21:04, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > I'm more about wanting an iOS VM and to do that you need to build and sign through Apple's tool set as far as I know. > > And the debugging experience is much more pleasant - especially when making FFI calls into Apple's system libraries. > > CMake can build an Xcode project from a CMake build system I believe. At least there is a cross platform marine navigation project called OpenCPN (written in C++ and which relies on wxWidgets) that does this. > > So I'm not arguing to have the official builds in Xcode, but if you want to build an app and ship it on iPhone or Mac, Xcode is the build system you are going to need to submit it to the App store. > >> On Oct 28, 2018, at 12:27 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Todd, >> >> On Fri, Oct 26, 2018 at 10:00 AM Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >>> Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? >> >> First I'd like to know your use case. I presume it;'s for debugging, but it may be more for browsing. Can you say? (Personally I find raw lldb adequate for debugging). >> >> Second, my reasons for not using Xcode projects for building the Mac VMs are that >> - Xcode projects, being a serialization of an object graph, are difficult to edit, and they offer no parameterisation, so whereas there is one small set of makefiles (8 in all) for all of the 32-bit and 64-bit builds on Mac, there had to be a separate Xcode project for each build. When adding Spur this was simply unsupportable >> - clearly Xcode is not necessary for building, browsing, or debugging; people are able to accomplish all three tasks using other tools >> >> However, I do appreciate that Xcode is a more pleasant and higher-level GUI interface than the shell, make, lldb and one's favorite editor. What I would support is a tool that created an Xcode project from Makefiles; such tools used to exist. I'd love to see such a tool. What I will fight against until my dying breath is any attempt to replace the Makefile based build system with Xcode. I hope the reasons above justify why. >> >> _,,,^..^,,,_ >> best, Eliot

1 0

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by Eliot Miranda Oct. 29, 2018

Oct. 29, 2018

Hi Todd, On Fri, Oct 26, 2018 at 10:00 AM Todd Blanchard via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Does anyone have Xcode projects for building the VM on iOS or Mac? Can > they share them or give me some tips for setting one up? > First I'd like to know your use case. I presume it;'s for debugging, but it may be more for browsing. Can you say? (Personally I find raw lldb adequate for debugging). Second, my reasons for not using Xcode projects for building the Mac VMs are that - Xcode projects, being a serialization of an object graph, are difficult to edit, and they offer no parameterisation, so whereas there is one small set of makefiles (8 in all) for all of the 32-bit and 64-bit builds on Mac, there had to be a separate Xcode project for each build. When adding Spur this was simply unsupportable - clearly Xcode is not necessary for building, browsing, or debugging; people are able to accomplish all three tasks using other tools However, I do appreciate that Xcode is a more pleasant and higher-level GUI interface than the shell, make, lldb and one's favorite editor. What I would support is a tool that created an Xcode project from Makefiles; such tools used to exist. I'd love to see such a tool. What I will fight against until my dying breath is any attempt to replace the Makefile based build system with Xcode. I hope the reasons above justify why. _,,,^..^,,,_ best, Eliot

2 1

Open Croquet will ahve issues in next version of Mac OS X
by LawsonEnglish Oct. 28, 2018

Oct. 28, 2018

https://blog.krestianstvo.org/en/open-croquet-for-squeak-6/ <https://blog.krestianstvo.org/en/open-croquet-for-squeak-6/> This sounds really cool, but thereâs an issue coming up: Apple is doing away with ANY support for 32-bit apps and plugins and of course, Croquet is built for 32-bits and uses 32-bit plugins all over the place. Croquet could STILL be the killer-app for Smalltalk even though it never realized its potential in the past, and it wonât be able to if something isnât done about the looming 32-bit vs 64-bit issue. Need I point out that it should work on Pharo just the same way it does on Squeak? L

2 1

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by Esteban Lorenzano Oct. 27, 2018

Oct. 27, 2018

Iâm sorry I forget to answer your mail :( Anyway, my response was not something you wanted to hear: I maintained the iOS version of the VM and up to three years ago (before spur) it was working, but I didnât try it since a lot of time and most of the work I did (who was based in CMakeMaker) is now not used anymore so I do not think they will work âout of the boxâ if needed. I find sad that we have to depend on otherâs Xcode projects to being able to do something, but wellâ¦ is better than nothing :) Esteban > On 26 Oct 2018, at 19:55, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Todd Blanchard <tblanchard(a)mac.com> > Subject: Re: [Pharo-dev] Xcode projects for VM on iOS or Mac? > Date: 26 October 2018 at 19:55:24 CEST > To: John M McIntosh <johnmci(a)smalltalkconsulting.com>, Pharo Development List <pharo-dev(a)lists.pharo.org> > > > That would be super awesome! Please let me know if/when you do. > > Thanks, > -Todd Blanchard > >> On Oct 26, 2018, at 9:43 AM, John M McIntosh <johnmci(a)smalltalkconsulting.com <mailto:johnmci@smalltalkconsulting.com>> wrote: >> >> I have one. I should see about adding it to a branch. >> >> .... >> John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk <https://www.linkedin.com/in/smalltalk> >> >> >> >> >> On Fri, Oct 26, 2018 at 09:39, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >>> Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? >>> >>> Thanks, >>> -Todd > > >

1 0

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by John M McIntosh Oct. 26, 2018

Oct. 26, 2018

I have one. I should see about adding it to a branch. .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk On Fri, Oct 26, 2018 at 09:39, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? > > Thanks, > -Todd

2 1