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

Bloc: Simulating "Worlds"

by Sean P. DeNigris

Posted to Discord, but the ML is probably a better venue for discussionâ¦ Looks like it's time for my annual Bloc Dream check in ha ha! Are we any closer to World simulation, meaning controlling all the dependencies (e.g. by a test harness)? We discussed this last year (http://forum.world.st/Bloc-Space-within-a-Space-tp4877474.html & http://forum.world.st/bloc-status-update-june-2016-tp4901988p4902319.html) and touched on it the year before (http://forum.world.st/Bloc-Roadmap-tp4816171p4816769.html) It's essential for the world to be built up from building blocks which make few assumptions other than their communication protocol and can be easily plugged in and out by a courageous user. A test case for this, which opens up many exciting possibilities (imagine I want to control time in my space e.g. run a simulation at 10x speed...), would be to have a world within a world. I dabbled with this idea a bit in Morphic, but quickly became frustrated because Morphic makes too many assumptions e.g. relying on globals and hardcoded classes. Smalltalk is at heart a simulation bench and the inability to simulate the IDE itself has felt like heavy shackles when I tried to implement several possible-blue-plane ideas in the past. Thanks for all the hard work pushing forward. I am persistent with this particular request especially because this use case forces a design that is very modular and testable, and is not something that could easily be "tacked on" late in development, but rather something that rightly should be baked in via TDD! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 17, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Sean P. DeNigris

abergel wrote > Yesterday we also experienced many problem when using Launcher on OSX :-( Hmm, I've been using exclusively daily for many months with minimal glitches. Please post OS, Pharo system report, download method and any other relevant details. The major "gotchas" of the past were: 1) The app has to be in the "Applications" folder 2) the first time it was started you needed to work around a signing issue e.g. via [right click]->Open->[Confirm dialog]. The app will not open, but from now on you can just open in the normal way (e.g. double clicking the .app). HTH ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 17, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Stephan Eggermont

Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > No. Each build just loads specified version. I do not need to create new > version for new build. > But I think I still not understand you That specified version will no longer work in a newer pharo build. Pharo changes, making it necessary for your dependencies to change. Will you make a new release each time one of your dependencies needs to change? Stephan

March 17, 2018

Re: [Pharo-dev] Adapt ImageReadWriter hierarchy to need only pure binary streams

by Ben Coman

On 17 March 2018 at 20:28, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > https://pharo.manuscript.com/f/cases/21611 > > With the new File/Stream changes in Pharo 7, ImageReadWriter and > subclasses broke because these classes are not yet capable of working with > simple binary streams. > > I created a new test case (attached) to catch the functional degradation. > For each image type (class) there are 2 tests, IO in memory and IO to file. > I have a bunch of changes that make all tests pass. They clean up some > strange coding as well. > I will make a proper PR later. > Thanks for everyone's efforts working on this. cheers -ben

March 17, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Ben Coman

On 17 March 2018 at 19:57, kmo <voxkmp(a)gmail.com> wrote: > I tried the default download of Pharo Launcher on my Windows 7 (32 bit) PC > at > work. It installs. Runs fine - creates images and vms but when you try to > run them nothing happens. It fails to start the selected image. It just > fails to run the vm at all as far as I can see. > > I tried it on my Windows 10 (32 bit) laptop and got exactly the same > result. > > This is not important for me as I use pharo on Linux - but I thought I'd > point it out. If having the launcher as the default download causes more > problems than the traditional vm and image download then perhaps it should > be reconsidered. A pity since I love the launcher. We've seen before when features are promoted in visibility (e.g. each GT tool) they come under more scrutiny and bump a wider set of environments that cause hiccups. Ultimately this feedback is beneficial to the tool. So I don't think there is any need to panic into a reversal. Lets give a chance to work through the issues. (but it might be good for the older links to be also available further down the page while Launcher issues are sorted out) cheers -ben

March 17, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Denis Kudriashov

2018-03-17 13:29 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > 2018-03-17 13:15 GMT+01:00 Stephan Eggermont > <stephan(a)stack.nl>: > > > >> Denis Kudriashov <dionisiydk(a)gmail.com> > >> wrote: > >> > >>> So to get all minor fixes from all dependencies the code should be > loaded > >>> from such floating branch (0.5.x). The main project can be locked to > fix > >>> current version (only dependencies will be updated). > >>> And all released versions (0.5.3 tag) will be completely reproducible. > >>> > >> > >> So your goal for released versions is to be only loadable on a specific > >> pharo build? > >> > >> > > On any pharo build. I not understand what you mean > > Your dependencies will need to be updated to run on newer pharo builds, > wonât they? No. Each build just loads specified version. I do not need to create new version for new build. But I think I still not understand you Stephan > > > >

March 17, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Stephan Eggermont

Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2018-03-17 13:15 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > >> Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> So to get all minor fixes from all dependencies the code should be loaded >>> from such floating branch (0.5.x). The main project can be locked to fix >>> current version (only dependencies will be updated). >>> And all released versions (0.5.3 tag) will be completely reproducible. >>> >> >> So your goal for released versions is to be only loadable on a specific >> pharo build? >> >> > On any pharo build. I not understand what you mean Your dependencies will need to be updated to run on newer pharo builds, wonât they? Stephan

March 17, 2018

Adapt ImageReadWriter hierarchy to need only pure binary streams

by Sven Van Caekenberghe

https://pharo.manuscript.com/f/cases/21611 With the new File/Stream changes in Pharo 7, ImageReadWriter and subclasses broke because these classes are not yet capable of working with simple binary streams. I created a new test case (attached) to catch the functional degradation. For each image type (class) there are 2 tests, IO in memory and IO to file. For example: testJpegWriteReadInMemory | form bytes result | form := self pharoLogoFormNonTransparent. bytes := ByteArray streamContents: [ :out | PluginBasedJPEGReadWriter putForm: form onStream: out ]. "Without format detection" result := (JPEGReadWriter on: bytes readStream) nextImage. self assert: form bits size equals: result bits size. "With format detection" result := ImageReadWriter formFromStream: bytes readStream. self assert: form bits size equals: result bits size testJpegWriteReadUsingFiles | form file result | form := self pharoLogoFormNonTransparent. file := (self class name asString , '-pharo-logo.jpeg') asFileReference. file ensureDelete. (PluginBasedJPEGReadWriter on: file binaryWriteStream) nextPutImage: form. "gets closed ?!" "Without format detection" result := file binaryReadStreamDo: [ :in | (JPEGReadWriter on: in) nextImage ]. self assert: form bits size equals: result bits size. "With format detection" result := file binaryReadStreamDo: [ :in | ImageReadWriter formFromStream: in ]. self assert: form bits size equals: result bits size. file delete I have a bunch of changes that make all tests pass. They clean up some strange coding as well. I will make a proper PR later. Sven

March 17, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by CÃ©drick BÃ©ler

Little feedback too. I was surprised by the new download as some students had to install on windowsâ¦ hopefully, I had old win versions but it has disturbed me :) Still handy and straightforward to just put an image on the VM. Butâ¦this being said, I just tried on Mac and this works nicely and this is true that launcher makes the management of image clearer and easier.. I donât know about windows but I have to care about as 98% of students uses Pharo on windows... I was thinking of some adjustments: 1) maybe a default/advanced mode on the launcher to show only, as default, Mooc/PBE5/Official distributions. 2) a proper icon name to display in OSâs task bars. When several image are opened, they should have different icons, at least different name when hovering, and not only Pharo. A more general feedback is about cloud drive OSâs (iCloud Drive, Dropbox, â¦). I have 3 macâs (pro and personal). I put often files in a directory that are synchronized across these devices. - sometimes I get a message that an image are in different states - sync image might be long (+changes) depending on network conditions I think the question is important as the launcher download in the Document folder (OSX) and this directory is synchronized by default. What do you think about such common situation ? What are your common practices ? - lets says on two Macs and works on both - or I use a dropbox folder => cloud drive are cool and my impression is that we could take a better advantage of them for data that could be shared between (personal) images (Play-Cache ? Packages-cache ? â¦ ) ==> would it be possible to have several files for one image (chunked over time so only the last chunk is modified and then less file would be synchronized) - (I donât know at all if possible) ? ==> same for changesâ¦ but this one should be easier I think. => I also find longer to share pharo system the old ways - zipping (or not) via USB - I think git integration produces a large number of files that relies slows down system copy paste (if only image this is ok)â¦ My 2 cents, CÃ©drick PS: my experiments to make students use Pharo are very coolâ¦ I need to adjust my presentations/lecture but already I think I succeeded in getting more attraction (and potential results) than what I tried last year with whatever technologies (Python especially). I still use AppInventor and Arduino.cc <http://arduino.cc/>. PS2: I just like what Sean said (but might be frightening at first for newcomers ^^) Pharo all the way down > >> But just in case we step into the quicksand even further, in this dystopian > >> future you can just copy paste this definition: > >> Pharo is a Pharo app that manages Pharo images, which can be used to make > >> Pharo apps, which can be used to manage Pharo images, [which can be used to > >> make Pharo apps, which can be used to manage Pharo images]* > > > Haha, yes it is so fluid it cannot be described only be experienced through prolonged exposure, it is truly magical. > > Actually, that is not so far from the truth.

March 17, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Denis Kudriashov

2018-03-17 13:15 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > > So to get all minor fixes from all dependencies the code should be loaded > > from such floating branch (0.5.x). The main project can be locked to fix > > current version (only dependencies will be updated). > > And all released versions (0.5.3 tag) will be completely reproducible. > > > > So your goal for released versions is to be only loadable on a specific > pharo build? > > On any pharo build. I not understand what you mean > Stephan > > > > > >

March 17, 2018