March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] platforms/Nopsys submodule

by Denis Kudriashov

This is so cool!!! 2017-03-18 16:30 GMT+01:00 jan.struz <public+pharo(a)struz.cz>: > Hi, > please stop for a while... I want to show you something... > > > > Actually it is already done... > Save The World! > > ------------------------------ > View this message in context: Re: platforms/Nopsys submodule > <http://forum.world.st/platforms-Nopsys-submodule-tp4939215p4939230.html> > Sent from the Pharo Smalltalk Developers mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at > Nabble.com. >

March 18, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by jan.struz

Hi, please stop for a while... I want to show you something... <http://forum.world.st/file/n4939230/pharonos.png> Actually it is already done... ----- Save The World! -- View this message in context: http://forum.world.st/platforms-Nopsys-submodule-tp4939215p4939230.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 18, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by Guido Chari

Hi, We didn't expect to be found yet :). But well...we are actually working on a second revival of the SqueakNOS project. Hope to give news in the mailing list soon, but we are still far from having something working with all the new stuff. Concerning submodules, yes there are plenty of arguments for and against. I've been using them successfully in some projects depending on the Truffle/Graal platform. Nonetheless, in case we managed to make progress and the community is interested on the results, for sure we will be open to discuss about this. Best, Guido. 2017-03-18 10:53 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > In the network graph hovering over charig/2-March commit I see a new > platform Nopsys added for SqueakNOS. > [A] https://github.com/OpenSmalltalk/opensmalltalk-vm/network > > Thats cool !!! It'll be great to see this work with OpenSmalltalk. > However I notice its been added as a submodule. > [B] https://github.com/charig/opensmalltalk-vm/commit/ > 2bd87b525b6b46439c90506c0a47e17ea1d5ac93 > > Submodules bring additional complexity, so I thought there should be > some discussion on this topic. > Here are a couple of balanced introductions to submodules... > [C] http://www.catalyst-au.net/blog/git-submodule- > misunderstood-beast-or-remorseless-slavering-monster > [D] https://www.philosophicalhacker.com/post/using-git-submodules- > effectively/ > > And a couple of cautions about using them... > [E] http://slopjong.de/2013/06/04/git-why-submodules-are-evil/ > [F] https://rufflewind.com/2017-02-21/quirks-with-submodules > > > Guido & Javier, > Have you used submodules successfully elsewhere? > Could you discuss your strategy using a submodule for the platform > code rather than adding directly into the opensmalltalk-vm repository? > > I see your parent repository includes opensmalltalk-vm as a submodule > similar to how I *thought* Pharo was doing it, but wait on comment > from Esteban. . > [G] https://github.com/charig/Nopsys > [H] https://github.com/charig/Nopsys/blob/master/.gitmodules > So it seems platforms/Nopsys is a sub-sub-module. > > > > Esteban, > I thought that you were using submodules to incorporate > opensmalltlak-vm into the pharo-vm, > but I can't see a .gitmodules file there. > [I] https://github.com/pharo-project/pharo-vm > So did you do it another way, or am I missing something? > Could you report your experience with adding opensmalltalk-vm into the > pharo-vm repository? > > > cheers -ben > >

March 18, 2017

Re: [Pharo-dev] about propertyAt: and others

by phil＠highoctane.be

What is Cocoon? Phil <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Mar 18, 2017 at 1:18 PM, stepharong <stepharong(a)free.fr> wrote: > Hi > > I'm looking at cocoon and other property systems. I would like to get a > nice library once for all. > I want to also revisit Artefact stylesheets. > > I'm checking the semantics regarding the lookup of a property in a parent > when it is not found in the receiver. > > I have the impression that when there is a parent access and modification > should modify the same object: i.e., the parent if the key is found in the > parent or the child if the property is found in the child. > > > in cocoon we have a mix of the two semantics and I would like to get your > feel about it. > > propertyAt: aKey > "Answer the value of the property ==aKey==, raises an error if the > property doesn't exist." > > ^ self propertyAt: aKey ifAbsent: [ > self hasParent > ifTrue: [ self parent propertyAt: aKey ] > ifFalse: [self errorPropertyNotFound: aKey ]] > > propertyAt: aKey default: aBlock > "Answer the value of ==aKey==. If the key have no entry I look on > the parent or execute a block if i'm an orphan." > > ^ self > propertyAt: aKey > ifAbsent: [ > self hasParent > ifTrue: [ self parent propertyAt: aKey > default: aBlock ] > ifFalse: aBlock ] > > but > > propertyAt: aKey ifAbsent: aBlock > "Answer the value of the property ==aKey==, or the result of > ==aBlock== if the property doesn't exist." > > ^ self properties at: aKey ifAbsent: aBlock > > propertyAt: aKey ifAbsentPut: aBlock > "Answer the value of the property ==aKey==, or if the property > doesn't exist adds and answers the result of evaluating ==aBlock==." > > ^ self properties at: aKey ifAbsentPut: aBlock > > > > In PetitParser there is no lookup. But we can get back to this situation > by just not setting a parent. > My gut feeling is telling me that overriding on write is not really good > because > a client of the parent will not see the changes coming from a child. > > > I thaought that stylesheet was supporting lookup but it does not > > testSubstyleAttributesOverride > styleSheet at: #textColor put: #red. > styleSheet > #sub > #subsub at: #textColor put: #blue. > self assert:( styleSheet get: #textColor ) equals: #red. > self assert:( styleSheet > #sub get: #textColor ) equals: #red. > self assert:( styleSheet > #sub > #subsub get: #textColor ) > equals: #blue. > Does not work > > > What you think? > > Stef > >

March 18, 2017

platforms/Nopsys submodule

by Ben Coman

In the network graph hovering over charig/2-March commit I see a new platform Nopsys added for SqueakNOS. [A] https://github.com/OpenSmalltalk/opensmalltalk-vm/network Thats cool !!! It'll be great to see this work with OpenSmalltalk. However I notice its been added as a submodule. [B] https://github.com/charig/opensmalltalk-vm/commit/2bd87b525b6b46439c90506c0… Submodules bring additional complexity, so I thought there should be some discussion on this topic. Here are a couple of balanced introductions to submodules... [C] http://www.catalyst-au.net/blog/git-submodule-misunderstood-beast-or-remors… [D] https://www.philosophicalhacker.com/post/using-git-submodules-effectively/ And a couple of cautions about using them... [E] http://slopjong.de/2013/06/04/git-why-submodules-are-evil/ [F] https://rufflewind.com/2017-02-21/quirks-with-submodules Guido & Javier, Have you used submodules successfully elsewhere? Could you discuss your strategy using a submodule for the platform code rather than adding directly into the opensmalltalk-vm repository? I see your parent repository includes opensmalltalk-vm as a submodule similar to how I *thought* Pharo was doing it, but wait on comment from Esteban. . [G] https://github.com/charig/Nopsys [H] https://github.com/charig/Nopsys/blob/master/.gitmodules So it seems platforms/Nopsys is a sub-sub-module. Esteban, I thought that you were using submodules to incorporate opensmalltlak-vm into the pharo-vm, but I can't see a .gitmodules file there. [I] https://github.com/pharo-project/pharo-vm So did you do it another way, or am I missing something? Could you report your experience with adding opensmalltalk-vm into the pharo-vm repository? cheers -ben

March 18, 2017

about propertyAt: and others

by stepharong

Hi I'm looking at cocoon and other property systems. I would like to get a nice library once for all. I want to also revisit Artefact stylesheets. I'm checking the semantics regarding the lookup of a property in a parent when it is not found in the receiver. I have the impression that when there is a parent access and modification should modify the same object: i.e., the parent if the key is found in the parent or the child if the property is found in the child. in cocoon we have a mix of the two semantics and I would like to get your feel about it. propertyAt: aKey "Answer the value of the property ==aKey==, raises an error if the property doesn't exist." ^ self propertyAt: aKey ifAbsent: [ self hasParent ifTrue: [ self parent propertyAt: aKey ] ifFalse: [self errorPropertyNotFound: aKey ]] propertyAt: aKey default: aBlock "Answer the value of ==aKey==. If the key have no entry I look on the parent or execute a block if i'm an orphan." ^ self propertyAt: aKey ifAbsent: [ self hasParent ifTrue: [ self parent propertyAt: aKey default: aBlock ] ifFalse: aBlock ] but propertyAt: aKey ifAbsent: aBlock "Answer the value of the property ==aKey==, or the result of ==aBlock== if the property doesn't exist." ^ self properties at: aKey ifAbsent: aBlock propertyAt: aKey ifAbsentPut: aBlock "Answer the value of the property ==aKey==, or if the property doesn't exist adds and answers the result of evaluating ==aBlock==." ^ self properties at: aKey ifAbsentPut: aBlock In PetitParser there is no lookup. But we can get back to this situation by just not setting a parent. My gut feeling is telling me that overriding on write is not really good because a client of the parent will not see the changes coming from a child. I thaought that stylesheet was supporting lookup but it does not testSubstyleAttributesOverride styleSheet at: #textColor put: #red. styleSheet > #sub > #subsub at: #textColor put: #blue. self assert:( styleSheet get: #textColor ) equals: #red. self assert:( styleSheet > #sub get: #textColor ) equals: #red. self assert:( styleSheet > #sub > #subsub get: #textColor ) equals: #blue. Does not work What you think? Stef

March 18, 2017

Re: [Pharo-dev] Script to download Pharo 4 vm for Mac os sierra

by Cyril Ferlicot D.

Le 18/03/2017 Ã 11:47, Esteban Lorenzano a Ã©crit : > because that link is incorrect, and you should not use it (it was a > development stage that once released 4.0 was never updated again). > you (and everybody else) needs to use the stable VM for pharo 4.0: > If it is never updated again maybe it should be removed? > http://files.pharo.org/get-files/40/pharo-mac-stable.zip (which is the > one that zeroconf uses) > http://files.pharo.org/platform/Pharo4.0-mac.zip for the âall inclusiveâ > (with image) download. > > >> >> Is there a script that allows to download a pharo 4 vm working for >> mac os sierra, from a linux machine ? > > this phrase does not has sense :) > you can use a macOS VM just in macOS, and a linux VM in linux. > This sentence make sense in our context :) Our Jenkins only got Linux's slaves and we want to produce some zip to deploy a server on mac (vm included). If we use zeroconf we can only get the Linux vm (or there is an option I missed). > Anyway for linux links are: > > http://files.pharo.org/get-files/40/pharo-linux-stable.zip > http://files.pharo.org/platform/Pharo4.0-linux.zip > > cheers, > Esteban > -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

March 18, 2017

Re: [Pharo-dev] Script to download Pharo 4 vm for Mac os sierra

by Esteban Lorenzano

> On 17 Mar 2017, at 21:56, stepharong <stepharong(a)free.fr> wrote: > > Nice to see on this list after all these years :) > This is important for synectiquers to use the power of the open-source :) > > > > Hello, > > We have a jenkins job, running on a linux machine, that is responsible for building and outputing a Pharo 4 development image + vm ready to be used on mac machines. > > We use this command line to download the VM and archived it as output of the job: > > curl -O http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip <http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip> > > On my mac (10.12.1), when i open the pharo image with this vm , I am facing what seem to be some known issues for Mac OS sierra: > > Pharo[13048:431565] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path ... > > Now, when I try to download a Pharo 4 vm directly from my mac sierra machine, > with a zeroconf script (get.pharo.org/vm40 <http://get.pharo.org/vm40>), > It works: I am able to open the pharo image with this vm. because that link is incorrect, and you should not use it (it was a development stage that once released 4.0 was never updated again). you (and everybody else) needs to use the stable VM for pharo 4.0: http://files.pharo.org/get-files/40/pharo-mac-stable.zip <http://files.pharo.org/get-files/40/pharo-mac-stable.zip> (which is the one that zeroconf uses) http://files.pharo.org/platform/Pharo4.0-mac.zip <http://files.pharo.org/platform/Pharo4.0-mac.zip> for the âall inclusiveâ (with image) download. > > Is there a script that allows to download a pharo 4 vm working for mac os sierra, from a linux machine ? this phrase does not has sense :) you can use a macOS VM just in macOS, and a linux VM in linux. Anyway for linux links are: http://files.pharo.org/get-files/40/pharo-linux-stable.zip <http://files.pharo.org/get-files/40/pharo-linux-stable.zip> http://files.pharo.org/platform/Pharo4.0-linux.zip <http://files.pharo.org/platform/Pharo4.0-linux.zip> cheers, Esteban > > -- > Cyrille Delaunay > > > > -- > Using Opera's mail client: http://www.opera.com/mail/ <http://www.opera.com/mail/>

March 18, 2017

Re: [Pharo-dev] PharoSpur32Vm

by Nicolai Hess

2017-03-17 23:41 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > > > 2017-03-17 23:40 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > >> >> >> 2017-03-17 23:32 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >>> >>> >>> 2017-03-16 21:51 GMT+01:00 Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com>: >>> >>>> >>>> >>>> 2017-03-15 18:14 GMT+01:00 Nicolas Cellier < >>>> nicolas.cellier.aka.nice(a)gmail.com>: >>>> >>>>> >>>>> >>>>> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>>> sorry for coming late to this threadâ¦ hard week :) >>>>>> why we are trying to compile with cygwin? >>>>>> is there a problem with the mingw distro? >>>>>> >>>>>> I didnât have the time to update the README, sadly. But wellâ¦ >>>>>> following appveyor configuration should give you all you need to reproduce >>>>>> the build (thatâs what I did last time I built an environment). >>>>>> >>>>>> Esteban >>>>>> >>>>>> >>>>>> Hi Esteban, >>>>> How did you solve the directx problem? >>>>> >>>>> >>>> >>>> Hurrah, I succeeded in compiling Win32 Pharo VM from cygwin by using >>>> cross-compiler i686-w64-mingw32 >>>> (cygwin64 here but it could be cygwin32). >>>> >>>> This is good news, because it means that: >>>> - we don't have to rely anymore on non-redistributable legacy directx >>>> SDK >>>> - we can compile with clang if we want too (well, for all the 3rd party >>>> dependencies, that's a bit more work) >>>> - it opens the door to win64 version >>>> >>>> Some details remain: I have to pick the right libgcc and libwindpthread >>>> as weel as iconv.dll and copy them to the pharo build directory to satisfy >>>> the SDL2 dependencies. >>>> Maybe there's a better option for compiling SDL2 with more static >>>> stuff? -static-libgcc or something... >>>> >>>> cairo required another dirty hack, not the one of Igor which must be >>>> eliminated for cygwin compilation, but one for working around the files >>>> that are not truncated when overwritten... >>>> I wonder where this bug comes from? make? cygwin itself? VirtualBox >>>> (unlikely)? >>>> >>> >>> what hack from Igor ? I thought the pharo build just downloads a tar.gz >>> archive from cairo and starts the configure/build ? >>> >>> >> >> https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/f7d >> 3c98eaa001d2d07c1f2b75cad00fa16f86a73 >> >> > and https://lists.cairographics.org/archives/cairo/2012- > October/023675.html > Ok :)

March 17, 2017

Re: [Pharo-dev] PharoSpur32Vm

by Nicolas Cellier

2017-03-17 23:40 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > > > 2017-03-17 23:32 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2017-03-16 21:51 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmai >> l.com>: >> >>> >>> >>> 2017-03-15 18:14 GMT+01:00 Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com>: >>> >>>> >>>> >>>> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> >>>>> sorry for coming late to this threadâ¦ hard week :) >>>>> why we are trying to compile with cygwin? >>>>> is there a problem with the mingw distro? >>>>> >>>>> I didnât have the time to update the README, sadly. But wellâ¦ >>>>> following appveyor configuration should give you all you need to reproduce >>>>> the build (thatâs what I did last time I built an environment). >>>>> >>>>> Esteban >>>>> >>>>> >>>>> Hi Esteban, >>>> How did you solve the directx problem? >>>> >>>> >>> >>> Hurrah, I succeeded in compiling Win32 Pharo VM from cygwin by using >>> cross-compiler i686-w64-mingw32 >>> (cygwin64 here but it could be cygwin32). >>> >>> This is good news, because it means that: >>> - we don't have to rely anymore on non-redistributable legacy directx SDK >>> - we can compile with clang if we want too (well, for all the 3rd party >>> dependencies, that's a bit more work) >>> - it opens the door to win64 version >>> >>> Some details remain: I have to pick the right libgcc and libwindpthread >>> as weel as iconv.dll and copy them to the pharo build directory to satisfy >>> the SDL2 dependencies. >>> Maybe there's a better option for compiling SDL2 with more static stuff? >>> -static-libgcc or something... >>> >>> cairo required another dirty hack, not the one of Igor which must be >>> eliminated for cygwin compilation, but one for working around the files >>> that are not truncated when overwritten... >>> I wonder where this bug comes from? make? cygwin itself? VirtualBox >>> (unlikely)? >>> >> >> what hack from Igor ? I thought the pharo build just downloads a tar.gz >> archive from cairo and starts the configure/build ? >> >> > > https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/ > f7d3c98eaa001d2d07c1f2b75cad00fa16f86a73 > > and https://lists.cairographics.org/archives/cairo/2012-October/023675.html

March 17, 2017