August 2013 - Pharo-dev - lists.pharo.org

[ANN] Aida 6.6 Web Framework Released

by Janko MivÅ¡ek

Dear Pharoers, New version of Aida/Web framework and application server (http://www.aidaweb.si) is here with: - optimization on HTTP level to send first byte to the client as soon as possible - streaming of HTML, specially header to get first byte out immediately, - gzip compression of all text stuff like CSS, JS etc - CSS Sprites support added - internal vs. extarnal IP detection, to control access rights accordingly - Geolocation support improved - all JS and CSS libraries updated to latest versions, Twitter Bootstrap v3 added in parallel to v2.x More in Release notes: http://www.aidaweb.si/release-notes-6.6 On latest Pharo 2.0 open Configuration browser, right click and Switch repository to SqueakSource. Select Aida and Install it. Or load Aida with this script: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfAida'; load. (Smalltalk at: #ConfigurationOfAida) load. Then simply open http://localhost:8888 . Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

Aug. 30, 2013

Re: [Pharo-dev] TestCase Announcers classvar is bizarre

by Igor Stasenko

On 30 August 2013 13:52, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > you still do not believe me but I really think that wirting some documents > on > what are the practices > what ae the good practices > and what are the bad practices > is important just to make sure that people can refer to it in case. > > i didn't said i don't believe it. But what someone said (it was Esteban or someone else) in conversation, that existence of documentation does not guarantees there will be no abuses. Because , at the end, the developer can simply disagree with author's POV, and so he intentionally picks "not recommended" way. Of course it is not an excuse for not writing a documentation :) stef > > On Aug 30, 2013, at 1:45 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > the more i looking how people using announcements, the more it reminds me > the quote: > if the only *tool* you have is a *hammer*, to treat everything as if it > were a *nail* > > > On 30 August 2013 13:38, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> >> On 30 August 2013 13:31, Camille Teruel <camille.teruel(a)gmail.com> wrote: >> >>> >>> On 30 aoÃ»t 2013, at 13:16, Igor Stasenko wrote: >>> >>> > can someone explain me, PLEASE, what is it for, >>> > and why there are announcer per each subclass of TestCase needed >>> > and why you organize it in a dictionary >>> >>> It should be a class side instance variable instead of a classVar that >>> maps test cases to announcer. >>> >> >> why? >> >> >>> Anyway the whole announcement stuff in SUnit is weird. >>> There TestAnnouncement (used by TestRunner) and an independent >>> TestCaseAnnouncement hierarchy (that nobody use). >>> And there is this TestAnnouncer that subclass SystemAnnouncer... >>> >>> that i already dealt with. >> >> But really.. why whole SUnit package needs more than one announcer >> announcing all events happening about running tests, >> why people so obsessive with announcers that they put them everywhere?? >> >> >> >>> > ... and.. do we need so many announcers >>> > everywhere? >>> > >>> > -- >>> > Best regards, >>> > Igor Stasenko. >>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Aug. 30, 2013

Re: [Pharo-dev] NeoJSONCustomMapping>>#mapWithValueSchema:

by StÃ©phane Ducasse

sven can you add it to the readme so that when I turn it into a pier chapter we get it :) > Using the newly added NeoJSONCustomMapping>>#mapWithValueSchema: this is now possible, as the following unit test shows: > > testDictionaryOfObject2 > | data json reader | > data := Dictionary new. > data > at: #one put: NeoJSONTestObject2 example1; > at: #two put: NeoJSONTestObject2 example1. > json := NeoJSONWriter toString: data. > reader := NeoJSONReader on: json readStream. > reader for: #DictionaryOfObject2 customDo: [ :mapping | > mapping mapWithValueSchema: NeoJSONTestObject2 ]. > self > assert: (reader nextAs: #DictionaryOfObject2) > equals: data > > Note that the mapping mechanism in NeoJSON is optional. Without mapping you get Arrays and Dictionaries back, that you can then convert to your domain objects in the a next step. With mapping however, these intermediary representations are not used and maps or lists are parsed while creating and populating your domain objects directly, which should be more efficient. This does of course introduce the necessity of adding some form of static typing.

Aug. 30, 2013

Re: [Pharo-dev] TestCase Announcers classvar is bizarre

by Camille Teruel

On 30 aoÃ»t 2013, at 13:38, Igor Stasenko wrote: > > > > On 30 August 2013 13:31, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 30 aoÃ»t 2013, at 13:16, Igor Stasenko wrote: > > > can someone explain me, PLEASE, what is it for, > > and why there are announcer per each subclass of TestCase needed > > and why you organize it in a dictionary > > It should be a class side instance variable instead of a classVar that maps test cases to announcer. > > why? Just because if one wants one <whatever> per class, using a class-side inst var seems better than a class-<whatever> dictionary class var. But as you said, SUnit could use only one announcer anyway. > Anyway the whole announcement stuff in SUnit is weird. > There TestAnnouncement (used by TestRunner) and an independent TestCaseAnnouncement hierarchy (that nobody use). > And there is this TestAnnouncer that subclass SystemAnnouncer... > > that i already dealt with. > > But really.. why whole SUnit package needs more than one announcer announcing all events happening about running tests, > why people so obsessive with announcers that they put them everywhere?? Don't know, do a survey ;) > > > ... and.. do we need so many announcers > > everywhere? > > > > -- > > Best regards, > > Igor Stasenko. > > > > > > -- > Best regards, > Igor Stasenko.

Aug. 30, 2013

Re: [Pharo-dev] TestCase Announcers classvar is bizarre

by StÃ©phane Ducasse

you still do not believe me but I really think that wirting some documents on what are the practices what ae the good practices and what are the bad practices is important just to make sure that people can refer to it in case. stef On Aug 30, 2013, at 1:45 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > the more i looking how people using announcements, the more it reminds me the quote: > if the only tool you have is a hammer, to treat everything as if it were a nail > > > On 30 August 2013 13:38, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 30 August 2013 13:31, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 30 aoÃ»t 2013, at 13:16, Igor Stasenko wrote: > > > can someone explain me, PLEASE, what is it for, > > and why there are announcer per each subclass of TestCase needed > > and why you organize it in a dictionary > > It should be a class side instance variable instead of a classVar that maps test cases to announcer. > > why? > > Anyway the whole announcement stuff in SUnit is weird. > There TestAnnouncement (used by TestRunner) and an independent TestCaseAnnouncement hierarchy (that nobody use). > And there is this TestAnnouncer that subclass SystemAnnouncer... > > that i already dealt with. > > But really.. why whole SUnit package needs more than one announcer announcing all events happening about running tests, > why people so obsessive with announcers that they put them everywhere?? > > > > ... and.. do we need so many announcers > > everywhere? > > > > -- > > Best regards, > > Igor Stasenko. > > > > > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko.

Aug. 30, 2013

Re: [Pharo-dev] SHA1 changed ??

by Sven Van Caekenberghe

On 30 Aug 2013, at 13:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Aug 30, 2013, at 1:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> I'm not aware of such a change... >> this is probably an error/side effect of something else. >> > This is a side effect of the merging of the two nearly identical but duplicated SHA1 implementations in the imageâ¦ > > https://pharo.fogbugz.com/f/cases/5469/SHA1-duplicated-implementations I want to wait for Max to respond/explain. But according to http://en.wikipedia.org/wiki/Sha1 "SHA-1 produces a 160-bit (20-byte) hash value. A SHA-1 hash value is typically expressed as a hexadecimal number, 40 digits long." The previous contract of returning a ByteArray of size 20 is more correct than an Integer, although both are mathematically equivalent. It is also very easy to send #hex to a ByteArray to get the most common human representation of such a hash. >> Esteban >> >> On Aug 29, 2013, at 3:05 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Max, >>> >>> Why was the contract of SHA1>>hashStream: changed ? >>> >>> It used to return a ByteArray like other HashFunction subclasses, now it returns an Integer. I see that you also changed the tests with this assumption. >>> >>> MD5 hashMessage: 'foo'. >>> >>> #[172 189 24 219 76 194 248 92 237 239 101 79 204 196 164 216] >>> >>> SHA1 hashMessage: 'foo'. >>> >>> 68123873083688143418383284816464454849230703155 >>> >>> It broke Zinc-WebSockets in 3.0 and now I will have to do an ugly hack to make the code work on multiple Pharo versions. >>> >>> Can you please explain ? >>> >>> Sven >> >> >

Aug. 30, 2013

Re: [Pharo-dev] [update 3.0] #30359

by StÃ©phane Ducasse

I fixed it :) On Aug 30, 2013, at 9:28 AM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Hi, > > This image seems broken. > When I try to open the Monticello browser, I get PointPair(Object)>>doesNotUnderstand: #adaptToPoint:andSend: > In the stack, it is sent by Rectangle>>expandBy:. So maybe the fix for the issue 2489 is not fully working. > > Christophe. > > > Le 29 aoÃ»t 2013 Ã 22:22, StÃ©phane Ducasse a Ã©crit : > >> >> 30359 >> ----- >> >> - issue 2489 Strange Behavior of Rectangle Part Two >> https://pharo.fogbugz.com/default.asp?2489 >> >> - issue 11502 Override Class >> #setName: >> https://pharo.fogbugz.com/default.asp?11502 >> >> - issue 11505 Remove obsolete icons >> https://pharo.fogbugz.com/default.asp?11505 >> Diff information: >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-StephaneDucasse.1230.di… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-StephaneDuc… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusCommon-StephaneDucass… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-StephaneDucasse.524.… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-StephaneDucasse.… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-StephaneDucasse.1585.d… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Graphics-Tests-StephaneDucass… >> >> >

Aug. 30, 2013

Re: [Pharo-dev] TestCase Announcers classvar is bizarre

by Igor Stasenko

the more i looking how people using announcements, the more it reminds me the quote: if the only *tool* you have is a *hammer*, to treat everything as if it were a *nail* On 30 August 2013 13:38, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 30 August 2013 13:31, Camille Teruel <camille.teruel(a)gmail.com> wrote: > >> >> On 30 aoÃ»t 2013, at 13:16, Igor Stasenko wrote: >> >> > can someone explain me, PLEASE, what is it for, >> > and why there are announcer per each subclass of TestCase needed >> > and why you organize it in a dictionary >> >> It should be a class side instance variable instead of a classVar that >> maps test cases to announcer. >> > > why? > > >> Anyway the whole announcement stuff in SUnit is weird. >> There TestAnnouncement (used by TestRunner) and an independent >> TestCaseAnnouncement hierarchy (that nobody use). >> And there is this TestAnnouncer that subclass SystemAnnouncer... >> >> that i already dealt with. > > But really.. why whole SUnit package needs more than one announcer > announcing all events happening about running tests, > why people so obsessive with announcers that they put them everywhere?? > > > >> > ... and.. do we need so many announcers >> > everywhere? >> > >> > -- >> > Best regards, >> > Igor Stasenko. >> >> >> > > > -- > Best regards, > Igor Stasenko. > -- Best regards, Igor Stasenko.

Aug. 30, 2013

Re: [Pharo-dev] SHA1 changed ??

by Marcus Denker

On Aug 30, 2013, at 1:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I'm not aware of such a change... > this is probably an error/side effect of something else. > This is a side effect of the merging of the two nearly identical but duplicated SHA1 implementations in the imageâ¦ https://pharo.fogbugz.com/f/cases/5469/SHA1-duplicated-implementations > Esteban > > On Aug 29, 2013, at 3:05 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Max, >> >> Why was the contract of SHA1>>hashStream: changed ? >> >> It used to return a ByteArray like other HashFunction subclasses, now it returns an Integer. I see that you also changed the tests with this assumption. >> >> MD5 hashMessage: 'foo'. >> >> #[172 189 24 219 76 194 248 92 237 239 101 79 204 196 164 216] >> >> SHA1 hashMessage: 'foo'. >> >> 68123873083688143418383284816464454849230703155 >> >> It broke Zinc-WebSockets in 3.0 and now I will have to do an ugly hack to make the code work on multiple Pharo versions. >> >> Can you please explain ? >> >> Sven > >

Aug. 30, 2013

Re: [Pharo-dev] TestCase Announcers classvar is bizarre

by Igor Stasenko

On 30 August 2013 13:31, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 30 aoÃ»t 2013, at 13:16, Igor Stasenko wrote: > > > can someone explain me, PLEASE, what is it for, > > and why there are announcer per each subclass of TestCase needed > > and why you organize it in a dictionary > > It should be a class side instance variable instead of a classVar that > maps test cases to announcer. > why? > Anyway the whole announcement stuff in SUnit is weird. > There TestAnnouncement (used by TestRunner) and an independent > TestCaseAnnouncement hierarchy (that nobody use). > And there is this TestAnnouncer that subclass SystemAnnouncer... > > that i already dealt with. But really.. why whole SUnit package needs more than one announcer announcing all events happening about running tests, why people so obsessive with announcers that they put them everywhere?? > > ... and.. do we need so many announcers > > everywhere? > > > > -- > > Best regards, > > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Aug. 30, 2013