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

Re: [Pharo-project] List weekly digest

by Dmitri Zagidulin

Great job - this is fantastic summary! On Fri, Feb 11, 2011 at 4:55 PM, Francois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Hi, > > I've posted a small digest of past week activity in the Pharo-Project ML. I > find it difficult to follow the pace of this list so I hope it will be > useful to some of you. I will try to post an update every week. > > Feedback/critics are more than welcome :) > > Francois > > [ > http://articles.tulipemoutarde.be/this-week-in-the-pharo-project-mailing-li… > ] > >

Feb. 11, 2011

[Pharo-project] List weekly digest

by Francois Stephany

Hi, I've posted a small digest of past week activity in the Pharo-Project ML. I find it difficult to follow the pace of this list so I hope it will be useful to some of you. I will try to post an update every week. Feedback/critics are more than welcome :) Francois [ http://articles.tulipemoutarde.be/this-week-in-the-pharo-project-mailing-li… ]

Feb. 11, 2011

Re: [Pharo-project] [COTDC] 7 - CodeAnnotationMorph

by CÃ©drick BÃ©ler

in my image, it's used in CodeHolder>>addOptionalAnnotationsTo: at: plus: Le 11 fÃ©vr. 2011 Ã 18:18, Laurent Laffont a Ã©crit : > I cannot find in which case/tool it is used .... > > CodeAnnotationMorph allInstances is always empty and following senders don't help me much. > > > Laurent > > > Le 10 fÃ©vr. 2011 Ã 21:07, Noury Bouraqadi a Ã©crit : > >> Ok, let's join the party ;-) >> >> I am a "lightweight" Morph. I display annotations for some code holder (such as a browser). >> >> Noury >> >> Le 10 fÃ©vr. 2011 Ã 18:14, laurent laffont a Ã©crit : >> >>> Today: CodeAnnotationMorph >>> >>> >>> 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 >> >> Noury Bouraqadi >> http://car.mines-douai.fr/noury >> -- >> -6th National Conference on >> âControl Architecture of Robotsâ >> 24-25 mai 2011, Grenoble area, France >> http://car2011.inrialpes.fr/ >> >> -19th ESUG International Smalltalk Conference >> 22-26 August 2011, Edinburgh, UK >> http://www.esug.org/Conferences/2011 >> >> >> >> >> > > -- > Laurent Laffont - @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

Feb. 11, 2011

[Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by stephane ducasse

Hi guys let us do another pass at cleaning and realigning the system. Could we agree to deprecate caseOf: and caseOf:otherwise:? it will simply the compiler, decompiler and also we do not need that at all. | z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. #b caseOf: z => "| z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. z detect: [:each | each key value = #b] " there is one user which I fixing right now. Stef

Feb. 11, 2011

Re: [Pharo-project] Understanding regular expression matching

by Schwab,Wilhelm K

Have you looked at messages like #copyWithRegex:matchesTranslatedUsing:? It might help?? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Nick Ager [nick.ager(a)gmail.com] Sent: Friday, February 11, 2011 1:52 PM To: pharo-project Subject: [Pharo-project] Understanding regular expression matching Hi, Is it possible to make a regular expression which matches only part of a string. For example: testRegex | toSearch matcher doesMatch match1 match2 numMatches | toSearch := 'value: 6474 mm'. matcher := RxMatcher forString: ' (\d+) '. doesMatch := matcher matches: toSearch. numMatches := matcher subexpressionCount. match1 := (matcher subexpression: 1). match2 := (matcher subexpression: 2). self halt. which results in: doesMarch = false numMatches = 2 match1 = nil match2 = nil However if I replace the regular expression with: '.* (\d+) .*' so the whole string is matched I see doesMarch = true numMatches = 2 match1 = 'value: 6474 mm' match2 = '6474' I can always pad my sub-matches with '.*', but I wondered if I'm missing a trick to make the Regex work with substring matches Thanks Nick

Feb. 11, 2011

[Pharo-project] Understanding regular expression matching

by Nick Ager

Hi, Is it possible to make a regular expression which matches only part of a string. For example: testRegex | toSearch matcher doesMatch match1 match2 numMatches | toSearch := 'value: 6474 mm'. matcher := RxMatcher forString: ' (\d+) '. doesMatch := matcher matches: toSearch. numMatches := matcher subexpressionCount. match1 := (matcher subexpression: 1). match2 := (matcher subexpression: 2). self halt. which results in: doesMarch = false numMatches = 2 match1 = nil match2 = nil However if I replace the regular expression with: '.* (\d+) .*' so the whole string is matched I see doesMarch = true numMatches = 2 match1 = 'value: 6474 mm' match2 = '6474' I can always pad my sub-matches with '.*', but I wondered if I'm missing a trick to make the Regex work with substring matches Thanks Nick

Feb. 11, 2011

Re: [Pharo-project] about FS: a roadmap

by StÃ©phane Ducasse

- renamed workingDirectory into workingDirectoryPath - added FSDiskFileSystem class>>workingDirectory - renamed working into workingDirectory. - deprecate working - better printOn: for DirectoryEntry - comments allChildren, allFiles, allDirectories, children, files, directories, childDirectories, childDirectories. Since childDirectories is the same as directories and childFiles the same as files may be we should deprecate child* because this is not good to have both. Stef

Feb. 11, 2011

Re: [Pharo-project] Hudson and Squeaksource statistics

by StÃ©phane Ducasse

I do not think so. Squeaksource was always instable. Then soon we will have a cool server (in about two or three months). Now hudson automatic builds are **really** important to us (they are the basis for software engineering practices with a stress on engineering) so do not spoil our fun, you will not succeed :). Now if we see that squeaksource get down more than usual we will see what actions we can take to resolve that. Stef On Feb 11, 2011, at 3:12 PM, Levente Uzonyi wrote: > On Fri, 11 Feb 2011, Torsten Bergmann wrote: > >> See www.squeaksource.com: >> "Most Downloads: Pharo, Seaside, Seaside 3.0, Moose, ..." >> >> Side effect of the Hudson builds ;) > > Hm, maybe this is the cause of the recent performance problems of squeaksource.com. > > > Levente > >> >> -- >> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit >> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl >> >> >

Feb. 11, 2011

[Pharo-project] Issue 3696 in pharo: Default style loading problem

by pharo＠googlecode.com

Status: Fixed Owner: aplan...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3696 by aplan...(a)gmail.com: Default style loading problem http://code.google.com/p/pharo/issues/detail?id=3696 Pharo image: 1.2 and 1.3 When loading the default style, Watery2 is loaded instead of GLMUITheme. In 1.3, the image becomes unusable after the loading. a .cs is attached Attachments: UIThemeStandardAndWindowColor.3.cs 1.5 KB

Feb. 11, 2011

[Pharo-project] [ANN] Aida/Web 6.2 Spring edition is out

by Janko MivÅ¡ek

Dear Smalltalkers, On the sunny side of the Alps we have a spring already, so let me bring a bit spring to you too with this new Aida release :) Fresh features from last month: - new event framework - unified JSON messaging (over WebSocket, Ajax, Comet) - pure JavaScript for Ajax, Prototype loaded only on demand - image based persistence - snapshot every hour - view active/logged sessions in Security - whitelisted IPs in Security - red 'browser not supported' warning on top of page And to repeat new features from Christmas beta: *Mobile* devices like smartpone and tablet support, with mobile device detection and special mobile CSS as addition to screen CSS, so that you can easily adapt your existing apps to mobile simply by overriding the existing CSS. *HTML5* support: Aida switches now to HTML5 by default and HTML5 specific features will be gradually added, WebSocket is there already, local storage and offline support comes next. *WebSocket* support for bidirectional communication between server and browser, as a replacement for Comet. WebSocket channel is now automatically open on the session with WebSocket capable browser. *JSON* messaging introduced to be gradually used as only message format in unified (Ajax or WebSocket) communication between server and browser *Widget forms" introduced, hierarchy of forms follow the hierarchy of standalone widgets, each widget can Ajax submit its own form together with subforms in subwidgets. There is now a continuously built One-click Pharo image (with new Aida preloaded and running) available via Download now button on http://wwww.aidaweb.si/download.html (thanks Pharo guys!). 6.2 is released on Squeak/Pharo and VisualWorks and it will be also avaiable on the soon to be released VisualWorks 7.8 CD. Release notes with most important new features highlighted are available at: http://www.aidaweb.si/release-notes-6.2 . Happy web smalltalking with new Aida! Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Feb. 11, 2011