- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.3] #13073
by StÃ©phane Ducasse March 6, 2011

March 6, 2011

13073 ----- - Issue 3728: Changed MenuMorph references to go through UIManager default menuClass. Thanks Fernando Oliviero for reviewing the changes. Stef

1 0

[Pharo-project] [COTDC] 25 - PolymorphSystemSettings
by laurent laffont March 6, 2011

March 6, 2011

Today: PolymorphSystemSettings Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

1 1

[Pharo-project] I'm doing an integration of some fixes now.
by StÃ©phane Ducasse March 6, 2011

March 6, 2011

1 0

[Pharo-project] Just a thought :)
by StÃ©phane Ducasse March 6, 2011

March 6, 2011

Hi guys in the train friday I read event code during a couple of hours... and I came to the conclusion I want to rewrite part of them :). Now the real interested part of this email is the following: 2 years ago event handling was looking mysterious to me, why? because I never needed to understand that part. Now I started to read, build hypothesis, read again, break the system and I get an understanding to the point I can say ok I want them better. So the lesson in there: this is cool, at the beginning you are not an expert, you just learn a little bit here and here and you consolidate, and you understand more and more. Sound stupid and naive story but this is a cool one. I like to read the code of the system just because I learn a lot. So I hope that this is a good and positive message for you. Step back and realize that you have learned a lot and that you can learn a lot more. And in the process fix the system to make it better and easier to be understood. Magic no? Stef

1 0

[Pharo-project] Fwd: Https Url in Pharo 1.2
by laurent laffont March 6, 2011

March 6, 2011

Is it planed / possible to have SqueakSSL plugin in official VM shipped with Pharo ? Laurent ---------- Forwarded message ---------- From: Levente Uzonyi <leves(a)elte.hu> Date: Sat, Mar 5, 2011 at 6:33 AM Subject: Re: [Cryptography Team] HttpsUrl MNU in Pharo 1.2 To: laurent laffont <laurent.laffont(a)gmail.com> Cc: Cryptography Team Development List < cryptography(a)lists.squeakfoundation.org> On Fri, 4 Mar 2011, laurent laffont wrote: On Fri, Mar 4, 2011 at 5:55 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > > On Thu, 3 Mar 2011, laurent laffont wrote: >> >> Hi, >> >>> >>> I've tried to use https in Pharo. I've loaded SSL package from >>> Cryptography. >>> >>> (HttpsUrl absoluteFromText: 'https://www.google.com') raises MNU. >>> >>> I've fixet it by changing: >>> >>> SSLCipherSuite class>>supportedSuites >>> >>> "hexCodeStrings := #('000A' '0009' '0004' '0005' '0012' '0013' '0015' >>> '0016' >>> '0018' '001A' '001B')." >>> >>> | hexCodeStrings | >>> hexCodeStrings := #('000A' '0009' '0012' '0013' '0015' '0016' '0004' >>> '0005' >>> '0018' '001A' '001B'). >>> ^ (hexCodeStrings collect: [:e | self cipherSuiteAtHexString: e]) reject: >>> [:aSuite| aSuite isNil]. >>> >>> >>> (rejecting nil suites). >>> >>> I don't know the impact. >>> >>> >> SSL it built on top of the Cryptography package. Since Pharo has some >> parts >> of the Cryptography package already loaded, thing probably won't work as >> they should. The last time I checked, this SSL implementation was >> incomplete, so I'd suggest you to use SqueakSSL instead. >> >> > > I've tried SqueakSSL but it seems it needs a plugin which is not shipped > with Cog nor Pharo One-Click VM. Am I right ? > That's right, but you can download prebuilt versions from here: http://code.google.com/p/squeakssl/downloads/list Levente > Laurent. > > > > > >> >> Levente >> >> >> Cheers, >>> >>> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >>> >>> >>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>> Blog: http://magaloma.blogspot.com/ >>> >>> _______________________________________________ >>> >> Cryptography mailing list >> Cryptography(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography >> >> >

3 3

[Pharo-project] a slim holiday present, cpic
by Eliot Miranda March 6, 2011

March 6, 2011

Hi All, don't know if this is useful to you or whether you've already written it yourself but I finally caved and wrote a shell command that copies an image/changes file pair, replacing the hundreds of times I've issued the two parallel commands, cpic = copy image and changes. Happy holidays -------8<------- #!/bin/sh # copy image and changes force=0 if [ "$1" = -f ]; then force=1 shift fi if [ $# != 2 -o "$1" = "-?" -o "$1" = --help ]; then echo "usage: $0 [-f] image-name-no-ext [image-name-no-ext|dir]" test $# != 2 && exit 1 exit 0 fi if [ -f "$2.image" -o -f "$2.changes" ]; then if [ "$force" = 0 ]; then echo "$2.image and/or $2.changes already exist." 1>&2 exit 1 fi elif [ -d "$2" ]; then if [ -f "$2/$1.image" -o -f "$2/$1.changes" ]; then if [ "$force" = 0 ]; then echo "$2/$1.image and/or $2/$1.changes already exist." 1>&2 exit 1 fi fi cp "$1.image" "$1.changes" "$d" exit 0 fi cp "$1.image" "$2.image" cp "$1.changes" "$2.changes"

3 4

[Pharo-project] Fwd: SIXX in Pharo 1.2
by Serge Stinckwich March 6, 2011

March 6, 2011

Thanks to Umezawa-san SIXX is working now on Pharo 1.2 & Squeak 4.2. All 127 tests are green under Pharo 1.2 ! To load the last version of SIXX: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSIXX'; load. (Smalltalk at:#ConfigurationOfSIXX) load. Regards ---------- Forwarded message ---------- From: Masashi UMEZAWA <masashi.umezawa(a)gmail.com> Date: Sat, Mar 5, 2011 at 7:25 PM Subject: Re: SIXX in Pharo 1.2 To: Serge Stinckwich <serge.stinckwich(a)gmail.com> Hi Serge-san, Sorry for the delayed reply. I've updated ConfigurationOfSIXX. I believe the latest SIXX runs on Pharo 1.2 and Squeak 4.2 nicely. Best regards, 2011/2/22 Masashi UMEZAWA <masashi.umezawa(a)gmail.com>: > Hi Serge-san, > > Updating XMLSupport to version: '1.1.7', I was able to reproduce the > test failures. > According to ConfigurationOfSIXX, SIXX assumes XMLSupport 1.0.0. > So I need to catch up new XMLSupport APIs... > > Best regards, > > 2011/2/22 Serge Stinckwich <serge.stinckwich(a)gmail.com>: >> On Mon, Feb 21, 2011 at 8:41 PM, Masashi UMEZAWA >> <masashi.umezawa(a)gmail.com> wrote: >>> Hi Serge-san, >>> >>> I've updated Pharo 1.2 to the latest version.(#12336). >>> And loaded SIXX via ConfigurationOfSIXX ( >=0.3.4 [ConfigurationOfSIXX]). >>> >>> Luckily all the tests were green. Perhaps there were some temporary problems? >> >> Hum ... strange. I try again with a PharoOneClick1.2 version (#12336). >> I have some problems with deprecated methods : >> >> The method XMLNodeWithElements topElement has been deprecated. >> use #firstElement instead >> >> Are you running the SIXXTests ? >> >> Regards, >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Every DSL ends up being Smalltalk >> http://doesnotunderstand.org/ >> > -- > [:masashi | ^umezawa] > -- [:masashi | ^umezawa] -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

2 1

[Pharo-project] Fwd: Https Url in Pharo 1.2
by Stephan Eggermont March 6, 2011

March 6, 2011

Stef wrote: >On Mar 6, 2011, at 8:39 AM, laurent laffont wrote: > Is it planed / possible to have SqueakSSL plugin in official VM shipped with Pharo ? >What is the license? You know the last time we got trapped into the game "oh I did not decided yet" so never again. >What is the status? On squeaksource it is MIT, last update from jan. 12. Stephan

1 0

Re: [Pharo-project] [squeak-dev] [ANN] ESUG supports once again SqueakDBX
by Mariano Martinez Peck March 6, 2011

March 6, 2011

On Sun, Mar 6, 2011 at 12:40 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Fri, 4 Mar 2011, Mariano Martinez Peck wrote: > > We are really happy to announce that ESUG will sponsor us once again >> through >> the ESUG Summer Talk project. This means that we have reached the ESUG >> expectations and that they still think that relational database access is >> an >> important matter in Smalltalk. >> > > snip > > 5) Cog compatibility. >> > > What has to be done? > > Indeed, nothing. We were not sure if FFI was working on it, but it turns out that it was. The idea is to be aware if Eliot releases a threaded VM/FFI so that we do not lock the VM (even if we have our micro-lock strategy when possible) > > >> 6) Use Alien instead of FFI. >> Eliot is working on a threaded CogVM. One of the projects of the GSoC of >> this year was to make something similar to a threaded FFI. What the >> student >> did is a modification in Alien (I think) that can be run in a >> multithreaded >> envirorment. He worked with Eliot. The idea is when Eliot releases the >> threaded CogVM, this FFI would work our of the box, and would avoid >> locking >> the WHOLE vm while a C function is being invoked (as it happens today with >> FFI).....So....when that VM is released, we MUST migrate to that). >> > > How is Alien better than FFI? We do not know. However, we will not spend time in Alien unless it is working out of the box and integrated in all standard VMs. > AFAIK Alien itself is not developed anymore, > parts of it will be merged with FFI. > > Ahh ok, we didn't know. Thnkas. > > Levente > > P.S.: http://www.squeaksource.com/SqueakDBX.html states that code in the > repository has MIT license, but it includes Glorp which has LGPL(S) license. > > Yes, the problem is that SqueakDBX as itself (the database driver), is MIT. Thus, the repository is MIT. Glorp is LGPL. When we started (years after SqueakDBX) with GlorpDBX, we found it easier to commit our changes to SqueakDBX repo instead of the Glorp one (because not everybody may agree with our changes). The good news is that Alan Night was considering making Glorp MIT. I cc'ed him to see if there are news. Cheers Mariano

1 0

[Pharo-project] defaultBorderColor and defaultBorderStyle
by DougEdmunds March 6, 2011

March 6, 2011

Styles ( such as #inset, #raised, etc) should be separated out from non-intuitive "defaultBorderColor" methods and consistently replaced with defaultBorderStyle. For example, Slider>>defaultBorderColor is #inset. Slider>>defaultBorderStyle would be much clearer. -- View this message in context: http://forum.world.st/defaultBorderColor-and-defaultBorderStyle-tp3337429p3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1