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

Re: [Pharo-users] Pharo for MacOs 10.6.8?

by stefano franchi

Thanks Esteban, 30 works indeed. I haven't had a chance to try 40, will try it tonight. Cheers, Stefano On Tue, Mar 6, 2018 at 3:41 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > hi, > > I would say > > get.pharo.org/30+vm > > or > > get.pharo.org/20+vm <http://get.pharo.org/30+vm> > > one of both should work. > there is also a chance that > > get.pharo.org/40+vm <http://get.pharo.org/30+vm> > > â¦ will work, but you need to try it ;) > > Esteban > > ps: but as Marcus say, it will be an older image and an older VM. Still > very usable (as it *was* usable at the time), but not the fresh stuff :) > > > On 6 Mar 2018, at 08:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > On 5 Mar 2018, at 20:16, stefano franchi <stefano.franchi(a)gmail.com> > wrote: > > > > On Mon, Mar 5, 2018 at 11:28 AM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Did you check >> >> http://get.pharo.org >> >> because we keep everything. >> >> > > Apologies for not having stated my question more precisely. Indeed, I > started from get.pharo.org, but the zeroconf script did not guess right. > The app it downloaded crashes at startup. Then I saw the *long* list of > versions available and had no idea where to begin. So my real question is: > > Does anyone know which among the many VMs available on > http://get.pharo.org would work on a MacOs Powerbook Pro running 10.6.9? > It was the latest 32 bit only machine Apple made, based on the Intel Core > Duo (NOT the Intel Core 2 Duo that came out a few months later). > > you could look for old VMs and downloads here: http://files.pharo.org/ > > But it is quite hard to for us (with our limited man power) to support old > machines foreverâ¦ e.g the vm from that time should run, > but at some point the VM gets improved and newer images require a newer VM > as we want to actually use the features that > new VMs provide. > > Keeping everything compatible in all possible directions (old images on > new VMs, new image on old VMs â¦) puts quite some > constraints on what you can do in futureâ¦ an maintaining new VMs for all > possible old MacOS versions could soon just > use up all our manpower. > > So this is not a simple problem to solve. Even very financially capable > projects (like Mozilla) can not support old MacOS > versions. And they spend 150K per *month* just on CI infrastructureâ¦ > imagine if they decide to not support anything older > then MaOS 10.9â¦ can we? should we? > > There are things to do on this front, but if I would spend effort the > first thing I would work on is running *old* images on > *new* VMs and explore what kind of abstraction would be needed to to that > nicely and in a way that it can be maintained > and in a way that all the needed code ( e.g. translation byte code from > old to new) would be not part of the VM but > part of the image. > > Making sure to run *current* images on old Machines can only be done by > backporting the current VM to the old OS. > This should be not that hard, worst case is that you need to combine some > old OS related code with the rest of the new VM, > but that should not be much. > > But one question: Considering what developer time costsâ¦ I am quite sure > that it is cheaper to just buy a current Mac. > > Marcus > > > -- __________________________________________________ Stefano Franchi stefano.franchi(a)gmail.com <stefano(a)tamu.edu> http://stefano.cleinias.org

March 7, 2018

Re: [Pharo-users] Ever growing image

by Stephane Ducasse

> > > Now, I understand we could build images without development tools, but for > that there is some work needed (not only from the pharo side but also from > the developer's point of view). > In the file server you can download latest minimal images both 32 and 64 > bits (http://files.pharo.org/image/70/) > > - Pharo-metacello-7.0.0-alpha.build.654.sha.494bbfc.arch.32bit.zip > <http://files.pharo.org/image/70/Pharo-metacello-7.0.0-alpha.build.654.sha.4…>2018-03-06 > 10:314.4 MB > <http://files.pharo.org/image/70/Pharo-metacello-7.0.0-alpha.build.654.sha.4…> > - Pharo-metacello-7.0.0-alpha.build.654.sha.494bbfc.arch.64bit.zip > <http://files.pharo.org/image/70/Pharo-metacello-7.0.0-alpha.build.654.sha.4…>2018-03-06 > 10:314.5 MB > <http://files.pharo.org/image/70/Pharo-metacello-7.0.0-alpha.build.654.sha.4…> > > > Those are ~4.5M zip files containing 10MB images and 9MB changes files. > Probably that is small enough for you. We can do better but each line of > code we remove is indeed a lot of work. > > Those images have the following packages installed only: > > - Language Kernel + Traits + Class builder + Slots > - RPackage > - FFI Kernel > - Opal Compiler + AST + Chunk files reader writers > - Announcements > - Collections > - Colors > - Files > - Others (Hermes, Jobs, Transcript, System packages, UIManager...) > - Zinc Character encoders and Buffered streams > - Network > - Monticello > - Metacello + Filetree > > For a more detailed list, you can browse BaselineOfPharoBootstrap. > > If you want an image that requires packages that are not there (like > morphic), you should install them on top and specify those as dependencies > of your project. That is what we do with the Pharo IDE. Take a look at > BaselineOfIDE. Again, this could be enhanced and we will greatfully accept > any contribution, or discuss on skype about the details or help people to > get into this. > I love it. It opens so many doors. 4.4 mb for such a system is cool. I'm eager to see what we will do with carolina. Stef

March 7, 2018

Re: [Pharo-users] Ever growing image

by Stephane Ducasse

Hi hilaire I think that Pavel sent around a link with the bootstrapped image. For you, you do not want to play changing the bootstrap. What you want is to change and load your own customized baselines on top of the bootstrapped image (probably the one with compiler and Monti/metacello loaded). I do not know where they are (running now out of my office). But the pharo70 build is based on that. Then with carolina we will start building tools to build smaller bootstrap and smaller VMs for IoT. Stef On Mon, Mar 5, 2018 at 6:33 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Thanks Markus. > > I already saw an improvement when building drgeo against latest 32bits P7: > drgeo image down to 39.9MB... > > I use image cleaner plus some packages removal of my own[1], left over of > the cleaning I was doing on P3. Many of my package cleaning of P4 break on > P7. There is still place for improvement. I remembered doing it one by on > P3, keeping the safe one, then excluding the one breaking the image. > > Now if there is a guide to try bootstrap without the need to hit the head on > the door, I am interested to read it. > > Hilaire > > > [1] > https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/506/src/Dr… > > Le 05/03/2018 Ã 08:39, Marcus Denker a Ã©crit : >> >> I have put on my TODO: >> - do a pass on ImageCleaner Pharo6 and Pharo7 >> - start to find duplicated code to not load anymore in the >> bootstrap (e.g. >> old compiler, inspectorâ¦). > > > -- > Dr. Geo > http://drgeo.eu > > >

March 7, 2018

Re: [Pharo-users] my mistake on Spec?

by Stephane Ducasse

I'm happy Let us know about your project! And if you need I can do a code review. Stef On Tue, Mar 6, 2018 at 1:36 PM, Yuriy Babah <babah.yuriy06(a)gmail.com> wrote: > Yes, i'm undestand. Looks good now. > > > > > 2018-03-05 23:10 GMT+03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> You should initialize the instance variable >> >> #subjectTextInput >> >> I suggest to do your UI incrementally. >> >> Stef >> >> On Mon, Mar 5, 2018 at 9:08 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >> > defaultSpec2 >> > <spec: #default> >> > ^ SpecLayout composed >> > newColumn: [ :col | >> > col >> > newRow: [ :row | >> > row >> > add: #plaintiffsTextInput; >> > add: #addButtonPlaintiffs ]; >> > newRow: [ :row | >> > row >> > add: #defendantsTextInput; >> > add: #addButtonDefendants ]; >> > newRow: [ :row | >> > row >> > add: #thirdPartiesTextInput; >> > add: #addButtonThirdParties ]; >> > newRow: [ :row | row add: #addButtonCourtCase ] ]; >> > yourself >> > >> > is working >> > >> > >> > >> > >> > >> > >> > On Mon, Mar 5, 2018 at 9:00 PM, Stephane Ducasse >> > <stepharo.self(a)gmail.com> wrote: >> >> I'm trying to understand. >> >> I do not get a DNU with the following. You cannot put row out of >> >> nowhere. >> >> >> >> defaultSpec >> >> ^ SpecLayout composed >> >> newColumn: [ :col | >> >> col >> >> newRow: [ :row | >> >> row >> >> add: #plaintiffsTextInput; >> >> add: #addButtonPlaintiffs ]; >> >> newRow: [ :row | >> >> row >> >> add: #defendantsTextInput; >> >> add: #addButtonDefendants ]; >> >> newRow: [ :row | >> >> row >> >> add: #thirdPartiesTextInput; >> >> add: #addButtonThirdParties ] ]; >> >> yourself >> >> >> >> Now I do not understand why when I add the next lines I get an error >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Mon, Mar 5, 2018 at 7:03 PM, Yuriy Babah <babah.yuriy06(a)gmail.com> >> >> wrote: >> >>> yesterday i did it, and got --> doesNotUndestand #layout >> >>> >> >>> 2018-03-05 20:28 GMT+03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >>>> >> >>>> First implement all the missing methods that you use in the spec >> >>>> class >> >>>> method. >> >>>> Then let us know. >> >>>> >> >>>> Stef >> >>>> >> >>>> >> >>>> On Sun, Mar 4, 2018 at 2:56 PM, Yuriy Babah <babah.yuriy06(a)gmail.com> >> >>>> wrote: >> >>>> > Thanks for your help, Stef. >> >>>> > Mistakes remain, but I will try to understand them >> >>>> > >> >>>> > 2018-03-04 16:35 GMT+03:00 Stephane Ducasse >> >>>> > <stepharo.self(a)gmail.com>: >> >>>> >> >> >>>> >> I'm doing a pass on your code >> >>>> >> >> >>>> >> OrderedCollection new is better to me than #() >> >>>> >> asOrderedCollection. >> >>>> >> >> >>>> >> GUI_ListCourtCase new openWithSpec >> >>>> >> => DNU >> >>>> >> So I added the first missing method, but you should define the >> >>>> >> corresponding methods in the class. >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> On Sun, Mar 4, 2018 at 2:28 PM, Stephane Ducasse >> >>>> >> <stepharo.self(a)gmail.com> wrote: >> >>>> >> > Hi yuri >> >>>> >> > >> >>>> >> > some feedback before looking into spec. >> >>>> >> > tab method bodies >> >>>> >> > then do not use instance variables with uppercase. >> >>>> >> > >> >>>> >> > Stef >> >>>> >> > >> >>>> >> > >> >>>> >> > On Sun, Mar 4, 2018 at 2:26 PM, Yuriy Babah >> >>>> >> > <babah.yuriy06(a)gmail.com> >> >>>> >> > wrote: >> >>>> >> >> changed >> >>>> >> >> >> >>>> >> >> 2018-03-04 16:20 GMT+03:00 Yuriy Babah >> >>>> >> >> <babah.yuriy06(a)gmail.com>: >> >>>> >> >>> >> >>>> >> >>> Is it enough if I just attach it? >> >>>> >> >>> >> >>>> >> >>> I slightly changed the code, that leads to error: >> >>>> >> >>> "DoesNotUndestand >> >>>> >> >>> #plaintiffsTextInput" . >> >>>> >> >>> >> >>>> >> >>> Now I'm studying Help on Spec in SystemBrowser . >> >>>> >> >>> >> >>>> >> >>> >> >>>> >> >>> >> >>>> >> >>> 2018-03-04 15:23 GMT+03:00 Stephane Ducasse >> >>>> >> >>> <stepharo.self(a)gmail.com>: >> >>>> >> >>>> >> >>>> >> >>>> Hi Yuriy >> >>>> >> >>>> >> >>>> >> >>>> this is difficult to debug remotely. Do you have your code >> >>>> >> >>>> somewhere? >> >>>> >> >>>> >> >>>> >> >>>> Stef >> >>>> >> >>>> >> >>>> >> >>>> On Sat, Mar 3, 2018 at 8:41 AM, Yuriy Babah >> >>>> >> >>>> <babah.yuriy06(a)gmail.com> >> >>>> >> >>>> wrote: >> >>>> >> >>>> > Hi! >> >>>> >> >>>> > I'm trying to write GUI element with Spec, Pharo6.1x64 on >> >>>> >> >>>> > Linux. >> >>>> >> >>>> > Do according to the SpecBooklet. >> >>>> >> >>>> > >> >>>> >> >>>> > Finished the fragment, and try do: >> >>>> >> >>>> > >> >>>> >> >>>> > ui := GUI_ListCourtCase new openWithSpec . -> #value was >> >>>> >> >>>> > sent to >> >>>> >> >>>> > nil. >> >>>> >> >>>> > >> >>>> >> >>>> > I look in a debugger and: >> >>>> >> >>>> > >> >>>> >> >>>> > openWithSpecLayout: aSpec >> >>>> >> >>>> > "Build the widget using the spec name provided as >> >>>> >> >>>> > argument >> >>>> >> >>>> > and >> >>>> >> >>>> > display >> >>>> >> >>>> > it into a window" >> >>>> >> >>>> > >> >>>> >> >>>> > (window value notNil and: [ self needRebuild not ]) >> >>>> >> >>>> > ifTrue: [ "window != nil" >> >>>> >> >>>> > window value rebuildWithSpecLayout: aSpec ] >> >>>> >> >>>> > ifFalse: [ "If value = Nil --> send him a >> >>>> >> >>>> > message >> >>>> >> >>>> > ???" >> >>>> >> >>>> > window value: (self defaultWindowModelClass new >> >>>> >> >>>> > model: >> >>>> >> >>>> > self). >> >>>> >> >>>> > window value openWithSpecLayout: aSpec. >> >>>> >> >>>> > self takeKeyboardFocus ]. >> >>>> >> >>>> > >> >>>> >> >>>> > ^ window value >> >>>> >> >>>> >> >>>> >> >>> >> >>>> >> >> >> >>>> > >> >>>> > >> >>>> >> >>> >> >

March 7, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] 64 bits support preview

by Ben Coman

Side question. What is the status of Windows support for OSSubProcess ? cheers -ben On 6 March 2018 at 11:19, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys, > > Thanks for Guillermo Polito we now have 64 bits support for OSSubprocess. > You can see the required changes in this PR [1]. I made a branch called > `support64bits` so that you can help us test it even if CI said it was good > [2]. If you do test it and come back to us with the results, please tell us > which OS you used. > > To install from the branch: > > Metacello new > configuration: 'OSSubprocess'; > repository: 'github://marianopeck/OSSubprocess:support64bits/ > repository'; > version: #stable; > load. > > > Roadmap: Current release is v0.2.5. So I will let that release for Pharo > <= 5.0. I will make a new release with the Pharo 64 bits and call it v0.3. > That release should be used for Pharo 6.x. Once v0.3 is out, I will make a > new release v0.4 with some changes I wanted to do since a loooong time and > its a small refactor to minimize OSSubprocess dependency on OSProcesses > primitives (at VM side). This is thanks to Holger Freyther and Alistair > Grant [3]. As that requires a new VM, then v0.4 should be used in Pharo >= > 7.0. > > Cheers, > > > [1] https://github.com/marianopeck/OSSubprocess/pull/30 > [2] https://travis-ci.org/guillep/OSSubprocess/builds/349280174 > [3] https://github.com/pharo-project/pharo-vm/pull/142 > > -- > Mariano > http://marianopeck.wordpress.com >

March 7, 2018

Re: [Pharo-users] Mounting/seeing samba network files on Pharo

by Ben Coman

Can you provide a bit more info about the setup. e.g. For two machines/users, describe the paths to the executables that are run and the method of launching. cheers -ben On 5 March 2018 at 21:41, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Hi all, > > I try to use Pharo in my lecture, therefore in our virtualized > architecture. > > The problem is once dowloaded and launched (on Desktop or Document - the > student repository that is mounted on the virtualized machine), Pharo > cannot access the networked file system (source is not accessible, save as > not possible, etc..). > > Does someone has experience on that ? > Is it possibile to mount a samba directory ? > > TIA, > > CÃ©drick >

March 7, 2018

Re: [Pharo-users] [Pharo-dev] PharoDays?

by Esteban Lorenzano

> On 28 Feb 2018, at 18:09, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi guys > > many people are asking when and where there will be PharoDays. > And we do not know. > We are looking for local organisers and else we do it at Lille. > Now what would be a good date? > > What about > 7-8 June? yes, is ok for me :) Esteban > > Stef >

March 7, 2018

Re: [Pharo-users] [Pharo-dev] PharoDays?

by Myroslava Romaniuk

What about sometime mid-May? On 28 February 2018 at 19:10, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Or 24-25 of May > Or 31 - 1 June? > > On Wed, Feb 28, 2018 at 6:09 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > Hi guys > > > > many people are asking when and where there will be PharoDays. > > And we do not know. > > We are looking for local organisers and else we do it at Lille. > > Now what would be a good date? > > > > What about > > 7-8 June? > > > > Stef > > -- Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº.

March 6, 2018

Re: [Pharo-users] PetitParser Question

by Asbath

OK, Thanks, Asbath On 06/03/2018 08:43, Julien wrote: > Hello, > > I think this blogpost is a good place to start: > https://www.lukas-renggli.ch/blog/petitparser-1 > > There is also the chapter about PetitParser in Deep Into Pharo: > http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.… > > Cheers, > > Julien > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille 1 > http://juliendelplanque.be/phd.html > Equipe Rmod, Inria > BÃ¢timent B 40, avenue Halley 59650Â VilleneuveÂ d'Ascq > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > >> Le 5 mars 2018 Ã 19:26, Asbath via Pharo-users >> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> a >> Ã©crit : >> >> >> *De: *Asbath <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>> >> *Objet: **PetitParser Question* >> *Date: *5 mars 2018 Ã 19:26:49 UTC+1 >> *Ã: *pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> >> >> >> Hi everybody, >> >> We are a group of students working on Pillar, and we notice that the >> Parser of Pillar is based on PetitParser Library. Then we want to >> know more about PetitParser !? >> >> Thanks, >> >> Asbath >> >> >> >> >

March 6, 2018

Re: [Pharo-users] Bitwise operations in ByteArray (slicing, etc.)

by Esteban A. Maringolo

2018-03-06 12:06 GMT-03:00 Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no>: > Esteban A. Maringolo wrote > BaseX encode/decode can be simple enough to fit in a small workspace: > > base := 58. > base58Lookup := > '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'. > myNumber := 12345678901234567890. > > myString := encode value: myNumber. > (decode value: myString) = myNumber. If you're encoding numbers to strings, and viceversa, that's ok. If you also need to support encoding strings (as bytearrays) that didn't work for me. I like your approach, it was more concise and didn't require reversing the output as the one i used [1] > The appeal of Base64 is it transforms the // and \\ operations into simple > shifts / masks. I guess, every bit and byte operation is simpler when happens in multiples of 8 :) Regards! [1] https://github.com/eMaringolo/pharo-base58/blob/master/src/Base58-Core.pack… Esteban A. Maringolo

March 6, 2018