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

Re: [Pharo-users] HMAC-SHA512

by HernÃ¡n Morales Durand

2018-03-07 23:07 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > > > On 8 March 2018 at 02:38, Michael Forster <mike(a)forsterfamily.ca> wrote: >> >> On Fri, Mar 2, 2018 at 9:40 PM, Ben Coman <btc(a)openinworld.com> wrote: >> [...] >> > >> > If that is the one available from the Pharo Catalog, when I tried it, it >> > used a different api than the libsodium library supplied by Ubuntu >> > 16.04. >> > >> > It makes this call out... >> > crypto_hash_sha512_ref() >> > but Ubuntu libsodium library did not export that, but instead... >> > crypto_hash_sha512() >> > >> > I failed to track down the implications of the "_ref", >> > and at that time Crypto-Nacl did not supply a 64-bit library, >> > so a single FFI matching the system supplied libsodium library was >> > easier. >> > Also as a minor policy, I prefer to use the system library than one >> > compiled >> > by a third-party. >> > >> > cheers -ben >> [...] >> >> >> Hi, >> >> Yes, I recommend using the OS/package-manager supplied libsodium >> (based on https://github.com/jedisct1/libsodium) The downloads >> provided on Tony's site were based on early commits that exported the >> "_ref" functions instead: >> >> commit e144f9d40d5695b69306bde729d6d8adcd62b1c4 >> Author: Frank Denis <github(a)pureftpd.org> >> Date: Mon Apr 22 16:30:31 2013 -0700 >> >> crypto_hash_sha(256|512) are the exported functions that have >> to be exported. >> _ref are implementations, that shouldn't be exported. > > > Thanks for clarifying that. > > >> >> >> To be useful, http://smalltalkhub.com/#!/~tonyg/Crypto-Nacl/ should be >> updated to use a system-supplied libsodium. > > > Or at least to the later api. In general there is some advantage in > packaging the C-lib with the Smalltalk package > for people experimenting with it the first time, to ensure the function > prototypes match. But flipping into production > may prefer the system library. Currently it seems awkward to switch later to > a system library since the library used is hard coded. Hi Ben, "system library" means it's pre-installed in some Linux distros? I installed a Debian 4.9.65-3+deb9u1 (2017-12-23) last week and libsodium is not present. I use Windows and also isn't available by default. In any case, how do you ensure libsodium system lib matches your interface code? What do you do now if target has a different version? > How do others work around that? > > Perhaps it would be good to have the external library initialized into an > instance variable of FFILIbrary, > so a user-application can change the external C-library used without > changing code in someone else's ffi-interface package. > > cheers -ben > > P.S. On the dream list would be a GUI for managing referenced external > C-libraries, including browsing their exported functions. That would be really cool HernÃ¡n

March 8, 2018

Re: [Pharo-users] HMAC-SHA512

by Ben Coman

On 8 March 2018 at 02:38, Michael Forster <mike(a)forsterfamily.ca> wrote: > On Fri, Mar 2, 2018 at 9:40 PM, Ben Coman <btc(a)openinworld.com> wrote: > [...] > > > > If that is the one available from the Pharo Catalog, when I tried it, it > > used a different api than the libsodium library supplied by Ubuntu 16.04. > > > > It makes this call out... > > crypto_hash_sha512_ref() > > but Ubuntu libsodium library did not export that, but instead... > > crypto_hash_sha512() > > > > I failed to track down the implications of the "_ref", > > and at that time Crypto-Nacl did not supply a 64-bit library, > > so a single FFI matching the system supplied libsodium library was > easier. > > Also as a minor policy, I prefer to use the system library than one > compiled > > by a third-party. > > > > cheers -ben > [...] > > > Hi, > > Yes, I recommend using the OS/package-manager supplied libsodium > (based on https://github.com/jedisct1/libsodium) The downloads > provided on Tony's site were based on early commits that exported the > "_ref" functions instead: > > commit e144f9d40d5695b69306bde729d6d8adcd62b1c4 > Author: Frank Denis <github(a)pureftpd.org> > Date: Mon Apr 22 16:30:31 2013 -0700 > > crypto_hash_sha(256|512) are the exported functions that have > to be exported. > _ref are implementations, that shouldn't be exported. > Thanks for clarifying that. > > To be useful, http://smalltalkhub.com/#!/~tonyg/Crypto-Nacl/ should be > updated to use a system-supplied libsodium. > Or at least to the later api. In general there is some advantage in packaging the C-lib with the Smalltalk package for people experimenting with it the first time, to ensure the function prototypes match. But flipping into production may prefer the system library. Currently it seems awkward to switch later to a system library since the library used is hard coded. How do others work around that? Perhaps it would be good to have the external library initialized into an instance variable of FFILIbrary, so a user-application can change the external C-library used without changing code in someone else's ffi-interface package. cheers -ben P.S. On the dream list would be a GUI for managing referenced external C-libraries, including browsing their exported functions.

March 8, 2018

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

by Sean P. DeNigris

Yuriy Babah wrote > something understood, worked Great! Feel free to keep asking questions and also there are several Discord channels where one can often get immediate dialogue and answers. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 7, 2018

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

by Sean P. DeNigris

EstebanLM wrote > get.pharo.org/30+vm <http://get.pharo.org/30+vm> And if you prefer a GUI over the command line, Launcher automatically downloads images pretty far back (I just confirmed that 1.4 works on a MBP 2017) and matches them up to the correct VM. One caveat: if the image is very old (e.g. the 1.4 above), Launcher will hang when you try to run the DLed image with a "determining correct VM for imageâ¦" dialog. The solution is simple: create a `pharo.version` text file in the image folder with `majorVersionNumber asString, minorVersionNumber asString` (e.g. for Pharo 1.4 -> '14'). That will tell Launcher which VM to use. I happily use Launcher for all my development images. HTH ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 7, 2018

Re: [Pharo-users] Ever growing image

by Hilaire

A "How to" as we used to have at the linux early time will be very helpful to get started. When I tried on this last summer I lost myself and gave up. Hilaire Le 06/03/2018 Ã 11:55, Guillermo Polito a Ã©critÂ : > 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. -- Dr. Geo http://drgeo.eu

March 7, 2018

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

by Yuriy Babah

something understood, worked " m: = GUI_ListCourtCase new. m openWithSpec: # defaultSpec2. "do something" m inspect " I see an instance variable that is not related to widgets 2018-03-07 22:11 GMT+03:00 Yuriy Babah <babah.yuriy06(a)gmail.com>: > i'm very pleased to! > Generally, I'm not a professional programmer. I'm a builder-designer. > Ðlthough I have been interested in programming for a long time. Ðnd > sometimes I use it. > Faro is very elegant, he has a cool debugger and an inspector, in my > opinion. > Well, you yourself probably know this. > I do my home project in my spare time, very slowly. Because of the large > amount of basic work now. > I want to sort out a bunch of court cases of relatives and related > information. Although, probably, some third-party service would make it > much easier. > Probably, it's more just learning Faro and Spec. > Now there are questions how to associate my ComposableModel subclass and a > regular class with my code. > When I do so "l: = GUI_ListCourtCase new openWithSpec: # defaultSpec2." and > try to look at the variable l, I do not see an instance variable that is > not related to widgets. > I'm trying to initialize it in initializeWidjets, because when I create > the method "initialize", I get an error. > Worst of all, that i'm not able be in time to investigate the emerging > issues myself by the time I get the answers. > I do not want to make you think that I'm trying to get you to do my job ))) > I can formulate my questions a little later)) > > > 2018-03-07 17:41 GMT+03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> 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] my mistake on Spec?

by Yuriy Babah

i'm very pleased to! Generally, I'm not a professional programmer. I'm a builder-designer. Ðlthough I have been interested in programming for a long time. Ðnd sometimes I use it. Faro is very elegant, he has a cool debugger and an inspector, in my opinion. Well, you yourself probably know this. I do my home project in my spare time, very slowly. Because of the large amount of basic work now. I want to sort out a bunch of court cases of relatives and related information. Although, probably, some third-party service would make it much easier. Probably, it's more just learning Faro and Spec. Now there are questions how to associate my ComposableModel subclass and a regular class with my code. When I do so "l: = GUI_ListCourtCase new openWithSpec: # defaultSpec2." and try to look at the variable l, I do not see an instance variable that is not related to widgets. I'm trying to initialize it in initializeWidjets, because when I create the method "initialize", I get an error. Worst of all, that i'm not able be in time to investigate the emerging issues myself by the time I get the answers. I do not want to make you think that I'm trying to get you to do my job ))) I can formulate my questions a little later)) 2018-03-07 17:41 GMT+03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > 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] does pharo 5 work in mac high sierra?

by Sean P. DeNigris

Paul DeBruicker wrote > I assume it works fine but I'm thinking about upgrading and just want to > be sure. Launched a quick image via Launcher and seems okay ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 7, 2018

Re: [Pharo-users] HMAC-SHA512

by Michael Forster

On Fri, Mar 2, 2018 at 9:40 PM, Ben Coman <btc(a)openinworld.com> wrote: [...] > > If that is the one available from the Pharo Catalog, when I tried it, it > used a different api than the libsodium library supplied by Ubuntu 16.04. > > It makes this call out... > crypto_hash_sha512_ref() > but Ubuntu libsodium library did not export that, but instead... > crypto_hash_sha512() > > I failed to track down the implications of the "_ref", > and at that time Crypto-Nacl did not supply a 64-bit library, > so a single FFI matching the system supplied libsodium library was easier. > Also as a minor policy, I prefer to use the system library than one compiled > by a third-party. > > cheers -ben [...] Hi, Yes, I recommend using the OS/package-manager supplied libsodium (based on https://github.com/jedisct1/libsodium) The downloads provided on Tony's site were based on early commits that exported the "_ref" functions instead: commit e144f9d40d5695b69306bde729d6d8adcd62b1c4 Author: Frank Denis <github(a)pureftpd.org> Date: Mon Apr 22 16:30:31 2013 -0700 crypto_hash_sha(256|512) are the exported functions that have to be exported. _ref are implementations, that shouldn't be exported. To be useful, http://smalltalkhub.com/#!/~tonyg/Crypto-Nacl/ should be updated to use a system-supplied libsodium. Best, Mike

March 7, 2018

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

by stefano franchi

Dear Marcus, thanks for the detailed answer. Let me say that my question did not in any ways imply that Pharo should assume the burden of maintaining current images and VMs on old machines. My goal was (is) simply to find out whether it was possible to repurpose a number old machines I have laying around by installing *old* versions of Pharo. And I now have a positive answer, having installed vm30 and verified that it works perfectly. In fact, I think adding a few lines to the website listing the last supported version for the major MacOs releases would be a valuable addition and nicely complement your commendable policy of keeping everything. All the best, Stefano On Tue, Mar 6, 2018 at 1:47 AM, 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