December 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [squeak-dev] The Trunk: Network-ar.42.mcz
by StÃ©phane Ducasse Dec. 18, 2009

Dec. 18, 2009

> > mike > > is it worth/ integrable in pharo? > > Stef > > Begin forwarded message: > >> From: commits(a)source.squeak.org >> Date: December 4, 2009 7:19:29 PM GMT+01:00 >> To: squeak-dev(a)lists.squeakfoundation.org, packages(a)lists.squeakfoundation.org >> Subject: [squeak-dev] The Trunk: Network-ar.42.mcz >> Reply-To: squeak-dev(a)lists.squeakfoundation.org >> >> Andreas Raab uploaded a new version of Network to project The Trunk: >> http://source.squeak.org/trunk/Network-ar.42.mcz >> >> ==================== Summary ==================== >> >> Name: Network-ar.42 >> Author: ar >> Time: 4 December 2009, 10:19:10 am >> UUID: bd7d181a-24b5-ac4c-a9a3-28a2b472d669 >> Ancestors: Network-ul.41 >> >> Fixes for SMTPClient: >> - http://bugs.squeak.org/view.php?id=6843 >> - http://bugs.squeak.org/view.php?id=6768 >> - Add an accessor for the localHostName in SMPTClient since Unix systems often return 'localhost.localdomain' or '0.0.0.0' from NetNameResolver localHostName which is not accepted by many MTAs. If client code knows the name from elsewhere (by means of configuration etc.) it can provide it explicitly. >> >> =============== Diff against Network-ul.41 =============== >> >> Item was changed: >> ----- Method: SMTPClient>>encodeString: (in category 'utility') ----- >> encodeString: aString >> + | str dec out | >> - | str dec | >> str := String new: (aString size * 4 / 3 + 3) ceiling. >> dec := Base64MimeConverter new. >> dec >> + mimeStream: (out := WriteStream on: str); >> - mimeStream: (WriteStream on: str); >> dataStream: (ReadStream on: aString); >> + multiLine: false; >> mimeEncode. >> + ^out contents! >> - ^ str! >> >> Item was added: >> + ----- Method: SMTPClient>>localHostName: (in category 'public protocol') ----- >> + localHostName: aString >> + "The local host name for purposes of identifying the the server. >> + If nil, NetNameResolver localHostName will be used." >> + >> + ^self connectionInfo at: #localHostName put: aString! >> >> Item was added: >> + ----- Method: SMTPClient>>localHostName (in category 'public protocol') ----- >> + localHostName >> + "The local host name for purposes of identifying the the server. >> + If nil, NetNameResolver localHostName will be used." >> + >> + ^self connectionInfo at: #localHostName ifAbsent: [NetNameResolver localHostName]! >> >> Item was added: >> + ----- Method: SMTPClient>>useHelo: (in category 'public protocol') ----- >> + useHelo: aBoolean >> + "Tell client to use HELO instead of EHLO. HELO is the old protocol and >> + an old server may require it instead of EHLO." >> + >> + ^self connectionInfo at: #useHelo put: aBoolean! >> >> Item was changed: >> ----- Method: SMTPClient>>login (in category 'private protocol') ----- >> login >> self user ifNil: [^self]. >> + self initiateSession. >> self sendCommand: 'AUTH LOGIN ' , (self encodeString: self user). >> [self checkResponse] >> on: TelnetProtocolError >> do: [ :ex | ex isCommandUnrecognized ifTrue: [^ self] ifFalse: [ex pass]]. >> self sendCommand: (self encodeString: self password). >> self checkResponse! >> >> Item was changed: >> ----- Method: SMTPClient>>initiateSession (in category 'private protocol') ----- >> initiateSession >> + "EHLO <SP> <domain> <CRLF>" >> - "HELO <SP> <domain> <CRLF>" >> >> + self sendCommand: (self useHelo ifTrue:['HELO '] ifFalse: ['EHLO ']) , self localHostName. >> - "self checkResponse." >> - self sendCommand: 'HELO ' , NetNameResolver localHostName. >> self checkResponse. >> ! >> >> Item was added: >> + ----- Method: SMTPClient>>useHelo (in category 'public protocol') ----- >> + useHelo >> + "If client use HELO instead of EHLO. HELO is the old protocol and >> + an old server may require it instead of EHLO." >> + >> + ^self connectionInfo at: #useHelo ifAbsent: [false]! >> >> Item was removed: >> - ----- Method: SMTPClient class>>openOnHost:port: (in category 'instance creation') ----- >> - openOnHost: hostIP port: portNumber >> - >> - | client | >> - client := super openOnHost: hostIP port: portNumber. >> - client initiateSession. >> - ^client! >> >> > > > >

1 0

[Pharo-project] New packages to MetacelloRepository
by Mariano Martinez Peck Dec. 18, 2009

Dec. 18, 2009

Hi: I am trying to create the metacello configurations of the external packages to do the pharo dev and web images. For now I have commited: - ConfigurationOfPharoSound - ConfigurationOfPharoMorphicExtras - ConfigurationOfShout But, they are not completed. They are just a first version. There are a lot of things to do. I need to create groups for the tests, etc. I have also started to create (not comitted yet): - ConfigurationOfPharo - ConfigurationOfAutomaticMethodCategorizer - ConfigurationOfRefactoringBrowser - ConfigurationOfOmniBrowser - ConfigurationOfEnhancedOmniBrowser - ConfigurationOfOCompletion (yes Romain we need to merge ;) I will send another email for this) Cheers, Mariano

1 0

[Pharo-project] [update 1.1] #11109
by Marcus Denker Dec. 18, 2009

Dec. 18, 2009

11109 ----- Issue 951: shadowed instance variables in tests Thanks to Cyrille Delaunay Issue 1626: OutofMemoryException Thanks to Andreas Raab Issue 1629: enhance #indexOfAnyOf: Thanks Nicolas!

1 0

[Pharo-project] [ANN] new pre-built 1.1#11106
by Marcus Denker Dec. 18, 2009

Dec. 18, 2009

#11106... http://gforge.inria.fr/frs/download.php/25074/PharoCore-1.1-11106-alpha.zip

1 1

[Pharo-project] managing external package with metacello
by StÃ©phane Ducasse Dec. 18, 2009

Dec. 18, 2009

mariano I was thinking about the problem of managing pharo with metacello we should start with the simple ones: the ones we removed from the system - Sounds - LedMorph - MorphicExamples - (ArchiveViewer) Then check the packages that are shared. May be we can also publish metacello descriptions to load them. and we republish them when they changed. For example for OB I think that lukas publish in squeaksource the latest version colin ships as sar files. So we can publish in the OBSqueakSouce (not sure that this is good) or in pharo a ConfigurationOfOB Stef

2 2

[Pharo-project] ProjectLauncher readDocumentAtStartup
by Michael Roberts Dec. 18, 2009

Dec. 18, 2009

Hi, this method was changed recently I think probably by the preferences work (Alain Plantec). It used to be a pref. Now it is hard coded to false. Is there a reason? It prevents scripts being executed on the command line. It causes the Mason example to not work in Pharo, and a bunch of other stuff to break. Is there a replacement for loading code on the command line? otherwise this needs changing, perhaps you did not know it is registered in the auto start mechanism. thanks, Mike

4 12

[Pharo-project] Services
by Alain Plantec Dec. 18, 2009

Dec. 18, 2009

gloups! I've just discovered that the Preferences class has a child. yes, yes, it is the ServicePreferences class with a dictionary full of Preference instances. So, I was always wondering, what are services ? are they used ? I don't know if I will have enough energy for that but do you think it is possible to use pragmas as we do for settings ? use the Setting browser for services ? (Lukas ?) thanks Alain

3 3

[Pharo-project] [ANN 1.0] 1.0#10502rc1
by Marcus Denker Dec. 18, 2009

Dec. 18, 2009

http://gforge.inria.fr/frs/download.php/25075/PharoCore-1.0-10502rc1.zip This one includes two important fixes... stability should be improved wrt. to strange errors when rendering UIs. Issue 889: MouseOverHandler send messages to nil Issue 1136: DejaVu strinkeFonts render ascii character in WideStrings as black boxes

1 0

Dec. 17, 2009

I will reply because this situation is silly and keith has some good points. > ---------- Forwarded message ---------- > From: keith <keith_hodges(a)yahoo.co.uk> > Date: 2009/12/16 > Subject: Re: [squeak-dev] Stuff > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > >> > So the question is, has ever been considered to simply build the bridge between >> > communities and to use the PharoCore image as the base for Squeak? >> >> This wouldn't work for the same reasons that it wouldn't work to use a >> Squeak-trunk image as the basis for Pharo. You should propose that at >> some point just to see what kind of reaction you get ;-) >> >> Cheers, >> - Andreas > > Yes please propose it. That is an excellent idea. Lets use the PharoCore image as the base for future Squeak releases! It would work excellently, it might require some humility from Andreas. In my opinion it is the only sensible way forward. > > Let me divulge a little secret here, the biggest reason that we kept the original 3.11 development always said to be about "process" and not about the actual release image, is that with a decent image building and testing process in place it would then have been possible to build and test a future squeak release pilot on top of some of the pharo-core packages. For us Pharo was simply a pilot project moving the core forward that we could borrow the best bits from it as appropriate. By adopting pharo in carefully integrated pieces we would perhaps of stood a chance of keeping the community together. > > The annoying thing was that Pharo team seemed to be insisting on diverging far more than was necessary and consistently refused to adopt any shared values or code that would have made this approach easier, we really need as a starting point, shared code loading tools, package management tools, and shared testing tools at the very least. i.e. Installer, and MC1.5/6 were developed with this in mind, and so was SUnit-improved, but the Pharo team refused to touch either of these projects. > > The more that the squeak-core image changes (i.e. in trunk) without tracking pharo's core packages the more diverse and impossible future integration will become. The old 3.11 effort was about having the tools to enable packages to be developed and tested in both Pharo and Squeak and all other forks, and then extending this to suggest common core packages as a way forward for everyone. > > So now that our to-be carefully planned evolution of squeak-core, using pharo for inspiration, has been trashed by random hacking on trunk, adopting PharoCore as a base image is probably the viable way forward for this community to remain viable. > > You already know that I don't see the squeak community as viable, since it eats its young. > > Sooner or later the board or someone will realize this, they will get elected to the board, and all those of you who have been working hard on trunk will discover that all your contributions have been wasted. Never mind eh. > > Keith > > > > > > > -- > CÃ©drick

16 41

[Pharo-project] [ANN] MagmaBrowser
by HernÃ¡n Morales Durand Dec. 17, 2009

Dec. 17, 2009

Dear all, I did a new Browser for the Magma object-oriented database, implemented on top of the OmniBrowser framework. I've uploaded a demo video in YouTube for the impatient : http://www.youtube.com/watch?v=VxUaOFRHFPk The project Home Page is : http://swikicaicyt.homeip.net/WebOpus/56 (you may access to other projects using http://www.caicyt.gov.ar/letodoc/paquetes-publicados) you will find there pre-built images ready for download for both Pharo and Squeak, besides installation instructions for installing and testing the MagmaBrowser in your image. Currently the status is under testing and bug-fixing, and I know there is a lot of things I should include, but you may take a look anyway as I browsed local repositories without problems last times I've used it, so I hope you may find it useful too. Finally, I want to publicly thank to Norberto Manzanos for letting me doing this, Chris Muller for his nice reviews and the OmniBrowser developers for mantaining such a great framework. HernÃ¡n

5 9