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

[Pharo-project] Issue #112: Enhanced colors
by Adrian Lienhard March 1, 2009

March 1, 2009

http://code.google.com/p/pharo/issues/detail?id=112 Who thinks that we should add these colors? These are more than 100 additional named colors like #paleGoldenrod, #mediumOrchid, #thistle, etc. I'd vote against adding them since I don't see their merit. Other opinions? Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

5 7

[Pharo-project] changing default font
by Sebastian Sastre March 1, 2009

March 1, 2009

hi there, sorry for the noob question but I see pharo has freetype in the image but it's only accuny font among options. Shouldn't freetype read the fonts on the system and offer those too? thanks, sebastian

5 11

[Pharo-project] towards pharo 1.0 (from pavel)
by StÃ©phane Ducasse March 1, 2009

March 1, 2009

> > Hi Stef, > > there are some opened issues so we may start with them: > 310 and 311 - the goal is to be able to unload all tests. As Adrian > sugested, we may place it the package Tests - at least for now. > 346 - easy and safe to integrate > 348 - very important issue. Maybe you should place in one update fix > for MorphicUIManager>>interactiveParserFor: and in the next the rest > of the patch to prevent loading problems > There was one wrong step in the development of Pharo during removing > of MVC. Pharo deleted all MVC related code however in some cases it > was the sign to use the UIManager. > 71, 59 - very critical patch but I will have to check if the patches > are suitable for the latest pharo > > I suggest to remove the unused class variable Current from the > ColorTheme (issue 467) firstly - that cleans a lot of obsoleteClasses. > > I think that we need one important step in the development of Pharo - > the next image that will not contain any code that can be unloaded. > That should help us to increase the Pharo quality because now most > packges are on the logical level in contradistiction to KernelImage > where all packages are standalone unloadable entities. > The ideal state is when we have the minimal core image with logical > packages (like Collections) and the rest will be all unloadable > packages. > > Cheers, > -- Pavel > > > > On Sun, Mar 1, 2009 at 9:57 AM, stephane ducasse > <stephane.ducasse(a)free.fr> wrote: >> >>> The KernelImage ZOO including the building environment is here: >>> http://squeak.cz/public/pub/KernelImage/current/ >>> >>> Of course it is not perfect - the smallest image works only in Linux >>> and MorphicCore needs a lot of fixes so people should start with >>> MorphicExt and so on but it is usable starting point if someone is >>> interested... >>> >>> -- Pavel >> >> Hi pavel >> >> do you have some fixes, cs list that we could slowly integrate to >> pharo? >> >> Stef >> >

2 1

[Pharo-project] from #foo:bar: to foo: arg1 bar: arg2
by StÃ©phane Ducasse March 1, 2009

March 1, 2009

Hi does one of you get to know a method for doing that? #foo:bar: -> foo: arg1 bar: arg2 Stef

2 2

[Pharo-project] [Idea] method source with it
by Mariano Martinez Peck March 1, 2009

March 1, 2009

Very often I need to search a string in the whole code of a package. Someone tell me to select the world and then select "method source with it". This works fine, but it searches in ALL the image. I would like to specify a package for example. Perhaps there is a way I don't know. If this is the case, please let me know. Sorry for just telling the idea and not to offering to do it myself. But I think this is better than nothing :) greetings, Mariano

3 8

[Pharo-project] issue 467 update - obsolete Classes
by Pavel Krivanek March 1, 2009

March 1, 2009

Hi, I added some code to the issue 467 so all obsolete classes can be removed (part of Milestone-1.0) Cheers, -- Pavel

2 1

[Pharo-project] Some issues with Pharo-dev build #10243
by Igor Stasenko March 1, 2009

March 1, 2009

This is mostly feedback on using Debugger - on DNU, if i press 'create a method' debugger opens, and shows extra (debugger related) context frames up to the method context which is just created. (while writing this, i found that it shows these extra contexts even if i simply press 'debug') : -------------- Process>>suspend OTToolset class>>debug:context:label:contents:fullView: OTToolset class>>debugError: [] in DEVToolSet class>>debugError: {[:obtools | obtools debugError: anError]} [] in DEVToolSet class>>ifOBTools:else: {[:obtools | aBlock value: obtools]} OTToolset class(Object)>>ifNil:ifNotNilDo: DEVToolSet class>>ifOBTools:else: DEVToolSet class>>debugError: ToolSet class>>debugError: UnhandledError>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: UnhandledError(Exception)>>signal UnhandledError class>>signalForException: Error>>defaultAction UndefinedObject>>handleSignal: Error(Exception)>>pass [] in PasteUpMorph>>becomeActiveDuring: {[:ex | ActiveWorld := priorWorld. ActiveEvent := priorEvent. ActiveHand :...]} BlockContext>>valueWithPossibleArgs: [] in MethodContext(ContextPart)>>handleSignal: {[(self tempAt: 2) valueWithPossibleArgs: {exception}]} BlockContext>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: Error(Exception)>>signal Error(Exception)>>signal: ...... only here starts the context i'm interested in ..... ------------ - mistakenly clicked on 'proceed' while not saved the method caused a losing unsaved work - i'll be happy, to have 'create a method' button, when code throws #subclassResponsibility error :) -- Best regards, Igor Stasenko AKA sig.

6 14

March 1, 2009

Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :)

4 7

[Pharo-project] Swazoo 2.2 released
by Janko MivÅ¡ek March 1, 2009

March 1, 2009

Dear Smalltalkers, After one year I'm glad to announce a new release 2.2 of Swazoo Smalltalk Web Server, currently just for Squeak and VisualWorks. What is new? * upload streaming 30 times better for large file uploads * additional improvements of streamed upload performance, as a result of a nice "competition" with GÃ¶ran Krampe doing the same on the Commance * two important classes renamed to avoid namespace clashes: Site to SwazooSite, Resource to SwazooResource * more reliable post data parsing * more and better tests * benchmarking support added. Detailed release notes: http://www.swazoo.org/release-notes-2.2.html Download page: http://www.swazoo.org/download.html Special thanks to Paolo Bonzini, Lautaro FernÃ¡ndez, Julian Fitzell, GÃ¶ran Krampe, Philippe Marschall and Stefan Schmiedl for your valuable inputs to this release! Best regards Janko MivÅ¡ek Swazoo maintainer

1 0

March 1, 2009

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Date: February 28, 2009 2:07:42 PM CEST > To: Matthew Fulmer <tapplek(a)gmail.com> > Cc: Marcus Denker <denker(a)iam.unibe.ch> > Subject: Re: Some personal thoughts and questions about Pharo > > Hi matthew > > >> Hi. I stumbled across a rather interesting email while I was >> researching to write up my campaign platform for the squeak >> election. Stef wrote this email 4 years ago, and it challenged a >> lot of what I thought about Pharo: >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-January/087532.… >> >> It prompted me to write this email, and lay out exactly what I >> think about Pharo, both good, bad, and not understood. > > Ok I think that this is important to have a look at what we did and > wrote in the past > to understand our attitude today. Lot of people judge without really > knowing. > > This is not the best email I sent. but it just gives a facett of the > problem > >>> From what I can tell, this email was written just before you >> guys started the 3.9 team. > > I imagine. > >> Firstly, I see that you have really cared about bug response >> latency for a long time. I'm really glad you care and do >> something about it. > > Yes. > We cared also about transparency and trust. > The idea is that I already said that to the squeakfoundation and I > gave up > long time ago. > If we do not give a chance to knowlegdaebale people to get a look then > we failed. Once janko which I trust sent a fix for network and I > thought that > we should integrate it but bert had a look and said it was not good. > So this makes me thing > a lot. So if an opensource movement we do not have communication > then nothing good > can happen. > > For 3.10 I proposed to ralph to help but he declined. They thought > we had no process > and when I explained him what we were doing he said that this is > what he planed to do. > I think that people thiught that ralph was Jesus but he was not. > >> Second, you solved this problem back then by releasing 3.9, >> and now you are solving it thru Pharo. Why did you choose to >> fork this time? >> >> If I may be blunt, I've long suspected that there are exactly >> two reasons why you forked: >> 1. Edgar J. De. Cleene >> 2. Andreas Raab > > You are not blunt > Been called a randomrefactorer is blunt. I do not want to tell more on > that but we are a solid group of people all getting the same feeling > nd this is not > because we are wash-brained. Just our experiences are following the > same line. > Ask mike why andreas does not talk to him. > >> Thirdly, I've heard Stef mention a number of times that "Marcus >> got burned", and therefore doesn't read squeak-dev, or no longer >> runs for board, or several things most squeak people do. >> However, this is by far the earliest mention of said burning >> I've ever seen. I had assumed the burning was people (Edgar and >> Andreas) complaining about Traits, but this was long before >> that. > > marcus was burnt to the point of been sick of smalltalk. > The problem is that marucs dreamt with us at bern about beauty and > a better world and that people like andreas were most of the time > negative and playing for themselves. Look at Tweak Andreas forked it > even people working in Sophie did not have access to his branch. > > >> What is it that happened to Marcus? If you are still bitter >> about something that happened over 4 years ago, perhaps it is >> time to forgive and re-join the squeak community. > > No we are not bitter. The squeak community has no vision except > toying with the past. > If I would be you I would not lose my time there. We harvested since > squeak > 3.6 and we did our best but it failed and it will fail. > >> As 3.11 release team leader, and Squeak board nominee, I'm >> really excited about what you guys are doing with Pharo. From my >> perspective, one thing you have done is take up the reigns for >> harvesting bugs, and left the release team free to consider a >> long-standing issue in the community: who is responsible for >> merging bug fixes from one distribution to another, and how can >> we make their lives easier > > No we did the only thing that make us breath again and not > jump into ruby or python or just hack in our little corner > stuff in VW or other. > Pharo is not an accident this is a survival reflex. > You know when you want to fix sometihng that a guy shout at you > because you push > a fix in his package.... Then after a while you stop this is why > there are some > fonts problem in 39 because we stop to harvest anything related to > andreas. > > >> Another valuable thing you have done is show the community that >> one image does not fit all; the monolithic image does not work >> for anybody. Squeakland showed it does not work for end-users >> Croquet showed it does not work for researchers. > > No Croquet shows nothing. Ask lombardi because he gave a presentation > last year at ESUG and we felt he was just alone lost. > And we are researcher much more than they :). Look at our > publication records. > Now we want a good Smalltalk and make evolve: first class slots, > packages.... > It will take time but we will do it. > >> And now Pharo >> shows that it does not work for developers. I really think that >> Pharo finishes painting that picture in the minds of the >> community, and you have thus paved the way for the release team >> and the squeak board to get away from the monolithic image, and >> toward modularity. I really think the community is ready now, >> and it's all thanks to you guys. I intend to exploit this >> opportunity. > > If you want. But I'm not sure that this is the right analysis. > >> I sent this email in private, because I don't think it would be >> appropriate to ask some of these questions publicly. However, >> feel free to reply to any of this in public, as you see fit. > > Sure I have no secret on that topic. > > >> >> >> -- >> Matthew Fulmer -- http://mtfulmer.wordpress.com/ >> >

1 0