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

[Pharo-project] Issue 3689 in pharo: Transcript preference for #characterLimit
by pharo＠googlecode.com Feb. 12, 2011

Feb. 12, 2011

Status: New Owner: ---- New issue 3689 by bstj...(a)yahoo.com: Transcript preference for #characterLimit http://code.google.com/p/pharo/issues/detail?id=3689 It would be useful for some of us to be able to specify a different #characterLimit for the Transcript display in a Preferences setting. 20000 characters is sometimes not enough for some tasks/logging.

1 5

[Pharo-project] [update 1.2] #12334
by StÃ©phane Ducasse Feb. 12, 2011

Feb. 12, 2011

12334 ----- Issue 3696: Default style loading problem. Thanks Alain Plantec. Stef

1 0

[Pharo-project] Issue 3696 in pharo: Default style loading problem
by pharo＠googlecode.com Feb. 12, 2011

Feb. 12, 2011

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

1 3

[Pharo-project] [update 1.3] #13052
by StÃ©phane Ducasse Feb. 12, 2011

Feb. 12, 2011

13052 ----- - Issue 3583: beStyled and unStyled. - Issue 3696: Default style loading problem. Thanks Alain Plantec. Stef

1 0

[Pharo-project] [ANN] Aida/Web 6.2 Spring edition is out
by Janko MivÅ¡ek Feb. 12, 2011

Feb. 12, 2011

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

2 1

[Pharo-project] Hudson and Squeaksource statistics
by Torsten Bergmann Feb. 12, 2011

Feb. 12, 2011

See www.squeaksource.com: "Most Downloads: Pharo, Seaside, Seaside 3.0, Moose, ..." Side effect of the Hudson builds ;) -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

4 6

[Pharo-project] Understanding regular expression matching
by Nick Ager Feb. 12, 2011

Feb. 12, 2011

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

3 3

Feb. 12, 2011

I can understand your position. I do not have strong opinion on that and indeed I would like to avoid that this is becoming handy to do isKindOf: so may be we should remove is: Stef On Feb 11, 2011, at 9:56 PM, Colin Putney wrote: > On Thu, Feb 10, 2011 at 5:41 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> Just yesterday i had discussion about this with people in the lab. I >> can't say that i heard something new regarding this, >> and not saying that i'd like to resurrect the discussion. >> So, in short: there was no objection concerning getting rid of isXXX >> in favor of using #is: method. >> The only thing which still looks controversial is too simple default >> implementation which answers false. > > No so. I think #is: is a terrible idea, and I object to it on those > grounds. I only object to the default implementation because it's the > thin edge of the wedge which invites people to use an anti-pattern. > > Colin >

1 0

[Pharo-project] ConfigurationOfGlorpDBX
by Sven Van Caekenberghe Feb. 12, 2011

Feb. 12, 2011

Hi, While switching to Pharo 1.2 (starting from the Seaside CI build), I loaded ConfigurationOfGlorpDBX. This worked fine (after also loading PostgresV2 in my case and setting some defaults). So thanks a lot to whoever maintained the configs and packages. However, the Compiler package in now dirty in Monticello: Scanner>>#xLetter BlockNode>>#arguments The first one comes from ConfigurationOfGlorpDBX>>#loadUnderscoreFix (if this is really needed, for Glorp SQL table/method names ?, could this not be put in its own package or could Pharo support this out of the box, maybe with a preference ?). The second one seems to come from Mocketry (Core). Anyway, this is not something that I cannot live without, it is just that I like Monticello to be clean, especially for core packages. Sven

2 1

[Pharo-project] [COTDC] 8 - WikiStyleHelpBuilder
by laurent laffont Feb. 12, 2011

Feb. 12, 2011

Today: WikiStyleHelpBuilder 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