Re: [Pharo-users] Yet another Pharo in docker

Could you build a roadmap of the actions to be done to improve the situation (like porting NB...) Stef On Sun, Mar 4, 2018 at 5:11 AM, Pierce Ng wrote: > On Sat, Mar 03, 2018 at 09:04:59AM -0700, Sean P. DeNigris wrote: >> Cool! I noticed the following [1]: >> ln -s \

Re: [Pharo-users] Ever growing image

Hi Hilaire, > On 3 Mar 2018, at 15:21, Hilaire wrote: > > Le 02/03/2018 à 22:52, Marcus Denker a écrit : >> >> we should again do some analysis where space is going… the Pharo7 download >> is now 38MB (the image, decompressed). > > Situation improved :) Remember P3 was just

Re: [Pharo-users] Ever growing image

--- Begin Message --- Estaban, I understand the difference between the 2 approaches my point was just to mention that I guess there are some advantages to shrink the image (as compared to bootstrapping from a minimal image) since all major vendors used that approach (and are still using it). 

Re: [Pharo-users] Ever growing image

I think that vendors did not go the bootstrap way because it is a lot more difficult to implement than a bunch of scripts to unload packages. On Sun, Mar 4, 2018 at 11:53 AM, Benoit St-Jean via Pharo-users wrote: > > > -- Forwarded message -- > From:

Re: [Pharo-users] Ever growing image

Le 04/03/2018 à 11:13, Esteban Lorenzano a écrit : In our community, Pavel is the person that has the bigger experience on shrinking process images. I followed his work for years and I know the fragility of the process. Basically each new addition/removal was breaking it and needing dependency

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

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 wrote: > Hi! > I'm trying to write GUI element with Spec, Pharo6.1x64 on Linux. > Do according to the SpecBooklet. > > Finished the fragment,

Re: [Pharo-users] Ever growing image

But the building process is working and we can incrementally create custom images. And this is what we will use in the future but we will not build the image that suits everybody needs. Stef On Sun, Mar 4, 2018 at 1:08 PM, Hilaire wrote: > Le 04/03/2018 à 11:13, Esteban

Re: [Pharo-users] Ever growing image

Hilaire It is up to you to give a real try. 1) Did you look for REAL at our infrastructure? Because you can take the bootstrapped image and change our build scripts. It took us may years to produce the loading scripts and this is the future. In Pharo 7 we have the possibility to have a core and

[Pharo-users] Looking for names for the booklet collection

Hi I would like to make a distinction between booklet on Pharo technologies (Smacc, Voyage, Scraping ...) and the booklets more oriented towards teaching something with pharo (building an interpreter, a reflective language...) Right now we have The Pharo Booklet Collection. And I'm looking for

Re: [Pharo-users] Ever growing image

> > > It looks like this topic comes and goes since 20 years: new features added, > image growth then/or it becomes hard to unload ; on Squeak then now with > Pharo at a much higher rate. > > We all know about the right approach (GNU Smalltalk, CUIS Smalltalk), I will not comment on that and

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

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 : > Hi Yuriy > > this is difficult to debug

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

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 wrote: > changed > > 2018-03-04 16:20 GMT+03:00 Yuriy Babah : >> >> Is it

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

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

Re: [Pharo-users] Ever growing image

On 4 March 2018 at 20:08, Hilaire wrote: > Le 04/03/2018 à 11:13, Esteban Lorenzano a écrit : > >> In our community, Pavel is the person that has the bigger experience on >> shrinking process images. I followed his work for years and I know the >> fragility of the process.

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

changed 2018-03-04 16:20 GMT+03:00 Yuriy Babah : > 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

Re: [Pharo-users] Ever growing image

> On 3 Mar 2018, at 16:35, Benoit St-Jean via Pharo-users > wrote: > > > From: Benoit St-Jean > Subject: Re: [Pharo-users] Ever growing image > Date: 3 March 2018 at 16:35:19 CET > To: pharo-users@lists.pharo.org, Hilaire >

Re: [Pharo-users] Ever growing image

Pharo Smalltalk Users mailing list wrote > Estaban, > I guess there are some advantages to shrink the image (as compared to > bootstrapping from a minimal image) Also, they are not mutually exclusive. While bootstrapping seems a clear choice for building images. A tool could then scan an image

Re: [Pharo-users] [Pharo-dev] Looking for names for the booklet collection

> Pharo Tools & Technologies > Pharo Language & Environment +1 ... simple, obvious, to the point please no cryptic/"clever" names On Sun, Mar 4, 2018 at 4:41 PM, Benoit St-Jean via Pharo-users < pharo-users@lists.pharo.org> wrote: > > > -- Forwarded message -- > From: Benoit

Re: [Pharo-users] HMAC-SHA512

2018-03-04 0:45 GMT-03:00 Pierce Ng : > On Fri, Mar 02, 2018 at 11:24:36AM -0300, Esteban A. Maringolo wrote: >> There is a PBKDF2 package made by Udo Schneider, and seems to be >> easily pluggable with a different hashing algorithm, so I'd need a >> SHA512 class. > >

Re: [Pharo-users] Yet another Pharo in docker

Sean P. DeNigris wrote >> https://hub.docker.com/r/herbysk/pharo/ > How are the images built from https://lolg.it/herby/pharo-docker? Researching a bit it seems that Docker Hub only supports GitHub and BitBucket, and IIUC you can't change the image name if you use automated building. Therefore, I

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

Thanks for your help, Stef. Mistakes remain, but I will try to understand them 2018-03-04 16:35 GMT+03:00 Stephane Ducasse : > I'm doing a pass on your code > > OrderedCollection new is better to me than #() asOrderedCollection. > > GUI_ListCourtCase new openWithSpec >

Re: [Pharo-users] [Pharo-dev] Looking for names for the booklet collection

Envoyé de mon iPhone > Le 4 mars 2018 à 13:21, Stephane Ducasse a écrit : > > Hi > > I would like to make a distinction between booklet on Pharo > technologies (Smacc, Voyage, Scraping ...) and the booklets more > oriented towards teaching something with pharo

Re: [Pharo-users] [Pharo-dev] Looking for names for the booklet collection

On 4 March 2018 at 20:21, Stephane Ducasse wrote: > Hi > > I would like to make a distinction between booklet on Pharo > technologies (Smacc, Voyage, Scraping ...) and the booklets more > oriented towards teaching something with pharo (building an > interpreter, a

Re: [Pharo-users] [Pharo-dev] Looking for names for the booklet collection

--- Begin Message --- Why not simply: Pharo Tools & TechnologiesPharo Language & Environment - Benoît St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an

Re: [Pharo-users] [Pharo-dev] Looking for names for the booklet collection

2018-03-04 13:49 GMT-03:00 Peter Uhnák : >> Pharo Tools & Technologies >> Pharo Language & Environment > > +1 ... simple, obvious, to the point I adhere to this. I add one more option: "Pharo Tools & Libraries" Regards, Esteban A. Maringolo

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

Please, if you do implement something, start with a Collection class and call it something like BitArray. It might be appropriate to subclass under ByteArray, but perhaps not. On Mar 4, 2018 12:45 PM, "Esteban A. Maringolo" wrote: > 2018-03-04 17:15 GMT-03:00 Sven Van

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

Take a 24-bit number and you want to isolate the first 5 (these are actually the last, higher order) bits. n := 2r10101000. n >> (16+3). If necessary, you can apply a mask (assume there are bits earlier/later still). (n >> (16+3)) bitAnd: 2r1 Large integers behave as bit

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

I do bitshifts and masks on Integer. What if you want to take the bits from the 3rd to the 7th? You have to do a some arithmetic to get the slice you want. I'm simply asking for something more dev-friendlier that adds a "layer" on top of that, but that internally does regular bitwise. What I

Re: [Pharo-users] [Pharo-dev] Looking for names for the booklet collection

On 04/03/18 11:49, Peter Uhnák wrote: > > Pharo Tools & Technologies > > Pharo Language & Environment > > +1 ... simple, obvious, to the point > > please no cryptic/"clever" names > +1. I can see Grafoscopio booklets in the first one, for example. Cheers, Offray

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

2018-03-04 17:15 GMT-03:00 Sven Van Caekenberghe : > Bits are actually numbered from right to left (seen from how they are > printed). I understand bit operations, used it extensively with IP address eons ago. But if a spec says: "Take the first n bits from the hash", it means the

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

Is there any package/library that makes bitwise operations as simple as with an Integer, but for larger numbers (as in a ByteArray). Something that allows me to "slice" a sequence of bits, or extract some using the same protocol as with a String of ones and zeros. Now when I need to work with

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

Bits are actually numbered from right to left (seen from how they are printed). But in a fixed amount of bits you could indeed number them the other way around. It does not matter that you write the leading zeros or not, everything to the left is zero anyway. When shifting, the right thing

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

--- Begin Message --- Just put that in Integer. bitsSliceFrom: start to: end     "     Extract bits 4 to 6, i.e. 111 which equals to 7     2r1111000 bitsSliceFrom: 4 to: 6     "     | num mask  |     self < 0 ifTrue: [self error: 'This operation is not allowed for

[Pharo-users] [ANN] SpecUIAddOns

Hi, SpecUIAddOns is a set of widgets for Spec. The aim of SpecUIAddOns is to provide additional widgets missing in the current distribution of Spec. Please be aware this is still an experimental package. Tested in Pharo 6.1 and Windows. Installation, sceenshots and usage instructions can be

[Pharo-users] Pharo for MacOs 10.6.8?

I am trying to find a version of Pharo that would run on an old Mac Powerbook that cannot be upgraded past 10.6.8, but I 'm having no luck. Any suggestions on what I should download? Cheers, Stefano -- __ Stefano Franchi

Re: [Pharo-users] Ever growing image

> On 4 Mar 2018, at 17:46, Sean P. DeNigris wrote: > > Pharo Smalltalk Users mailing list wrote >> Estaban, >> I guess there are some advantages to shrink the image (as compared to >> bootstrapping from a minimal image) > > Also, they are not mutually exclusive. While

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

--- Begin Message --- Hi Esteban, When you say "extract", what exactly do you mean? Let's suppose you have 86, i.e. 2r1010110 Which case do you want? a) 2r1010110 "2 to 5 = 2r10[1011]0 = 2r1011 = 11" or b) 2r1010110 "2 to 5 = 2r10[1011]0 = 2r00[1011]0 =  2r0010110 =  22" Both cases can be