March 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Getting Pharo 1.2 on Hudson green/blue again
by Torsten Bergmann March 29, 2011

March 29, 2011

Hi Markus, I think I've found out what the problem with the hudson build for Pharo 1.2 is: - the Pharo-1.2.st Skript used to build it includes this line: ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) which now returns 1.3. instead of 1.2 since the config was extended. Guess who did it: ConfigurationOfPharo-MarcusDenker.148 on 22 March 2011, the day when the hudson build broke So change the line in Pharo-1.2.st to: ((Smalltalk at: #ConfigurationOfPharo) project version: '1.2-beta2') perform: #silently: with: true; perform: #load. and the build works. At least it does manually when I try it here. If that works you either send me a beer or you take the time to exchange the VM to the customized ones I've sent you so we can move 1.2 out of the door and concentrate on 1.3... Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

[Pharo-project] Issue 3898 in pharo: Remove some dead code from PasteUpMorph
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3898 by marcus.d...(a)gmail.com: Remove some dead code from PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3898 PasteUpMorph removeSelector: #automaticPhraseExpansion! PasteUpMorph removeSelector: #backgroundForm! PasteUpMorph removeSelector: #backgroundSketch! PasteUpMorph removeSelector: #checkCurrentHandForObjectToPaste2! PasteUpMorph removeSelector: #deleteBackgroundPainting! PasteUpMorph removeSelector: #displayWorldNonIncrementally! PasteUpMorph removeSelector: #optimumExtentFromAuthor! PasteUpMorph removeSelector: #prepareToPaint:! PasteUpMorph removeSelector: #saveOnFile! Attachments: RandomDeadCode.1.cs 571 bytes

1 2

[Pharo-project] Issue 3888 in pharo: Move Digital Signatur code to System-Hashing package
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3888 by marcus.d...(a)gmail.com: Move Digital Signatur code to System-Hashing package http://code.google.com/p/pharo/issues/detail?id=3888 There are two implementations of SHA1 in the system. This changeset just moved the SHA1/DSA code into the Hashing package so it can be merged later. Attachments: DSA.1.cs 6.1 KB

1 2

[Pharo-project] Issue 3899 in pharo: clean up #maybeDuplicateMorph:
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3899 by marcus.d...(a)gmail.com: clean up #maybeDuplicateMorph: http://code.google.com/p/pharo/issues/detail?id=3899 clean up #maybeDuplicateMorph: Plus some random small cleanups of dead code Attachments: MoreCleans.1.cs 4.2 KB

1 1

[Pharo-project] Issue 3892 in pharo: clean AbstractHierarchicalList
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3892 by marcus.d...(a)gmail.com: clean AbstractHierarchicalList http://code.google.com/p/pharo/issues/detail?id=3892 AbstractHierarchicalList has just one subclass. New code uses MorphTree Widget anyway. Attachments: CleanAbstractH.1.cs 2.2 KB

1 1

[Pharo-project] Thanks for Pharo
by Torsten Bergmann March 29, 2011

March 29, 2011

>Recently I had been given the opportunity to develop an application for a potential >customer. >... >I am very new to Smalltalk but I have been looking to help in any way You are welcome. There are many ways you are able to help/contribute. If it is possible you can report about your application so we can add it as (yet another) success story on the pharo web page. You can also help to fix bugs and move Pharo forward to 1.3. We all have limited time - but there is always a minute. You can also share your experience on what to do better, what you missed in Pharo to make it an enjoyable environment. So share as much as possible (bugfixes, code, docu, lessons learned, ...) and dont forget to use Pharo for your next project! Bye T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

1 0

Re: [Pharo-project] [Seaside] rack/wsgi/ring for smalltalk
by Sean Allen March 29, 2011

March 29, 2011

>> >> WAServerAdaptor isn't really much like ring, rack et al. > > Yes and no. It has the same responsibility in the "Seaside stack" but > is "object oriented" and not "string/byte array oriented" and more > high level. > >> But it does put the thought into my mind that it would be interesting >> down the road to >> try and take the Seaside infrastructure and work something like rack into it. > > > Well the "problem" is that "traditional" servers (Comanche, Swazoo, > OpenTalk) used to "object oriented" and fully featured web servers. > Since building something like that takes a lot of work more recent > servers (FastCGI, SCGI, AJP) are "string/byte array oriented". The > later ones are obviously easier to adapt to a ring/rack/wsgi style > interface. a bit of background from me could help here. i'm going to end up having redline smalltalk using either netty or jetty be the final target for my own personal use of this when i'm done so the 'string/byte oriented' is going to be important to me. i'm playing around with how restful resources using stored blocks would look and the final end result i would build on top of it is going to be a combination of some stuff i wrote earlier this year in smalltalk using pharo ( ported to redline ) and a later part that i had a much easier time expressing using clojure. thus the jvm is a big + for me, but in general as i'm one of the redline guys, it is probably going to be my primary platform sometime in the future ( although i still love pharo and gemstone which i've used for a few years now and plan to keep contributing to in whatever fashion i can. )

1 0

[Pharo-project] String asUppercase/asLowercase
by Denis Kudriashov March 28, 2011

March 28, 2011

Hello. asUppercase/asLowercase not work for non english strings (russian strings). Is it bug? How it can be implemeted?

2 3

[Pharo-project] [update 1.3] #13115
by Marcus Denker March 28, 2011

March 28, 2011

13115 ----- Issue 3893: PluggableListMorphOfMany better implementation of autoDeselect: Issue 3884: Cleaning st80 Paragraph Issue 3887: Clean Project more Issue 3681: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3681 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses
by pharo＠googlecode.com March 28, 2011

March 28, 2011

Status: Accepted Owner: laurent....(a)gmail.com New issue 3681 by laurent....(a)gmail.com: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3681 Pharo 1.2 Remaining: AnObsoleteAutoGeneratedClassForTestingSystemChanges, AnObsoleteMCMockClassG For AnObsoleteAutoGeneratedClassForTestingSystemChanges, to reproduce: 1. Take Pharo 1.2 full from Hudson 2. run ReleaseTest testObsoleteClasses, green 3. run ChangeHooksTest testClassCommentedEvent, green 3. rerun ReleaseTest testObsoleteClasses, red

1 6