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

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #52 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Thanks Benjamin for looking into this.

Feb. 11, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #51 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 'too', not 'two' oO

Feb. 11, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #50 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 I've tried to do a merge, there is only one conflict, I choose to keep the current version, and it works fine ... And the workspace two in both case ...

Feb. 11, 2011

[Pharo-project] UI Enhancements

by Gary Chambers

Just a couple of changesets... Shift-click for PluggableListMorphOfMany. Not Perfect but better than nothing. Have a play (e.g. Select Classes from the finder tool). Some adjustments for Theme/builder label groups to be more flexible (takes the vResizing of individual rows into account (the control rather than the label for each). Removes the spaceFill ("spread") variant that was less flexible. Regards, Gary

Feb. 11, 2011

Re: [Pharo-project] A new GUI visual designer

by StÃ©phane Ducasse

> Hi all > > Am 2011-02-11 um 09:58 schrieb StÃ©phane Ducasse: >> Hi geert >> >> The problem is not simply the license. The problem is: >> - integrating widgets >> - integrating extra libraries >> >> We cannot stack libraries. >> So there is an engineering effort needed. >> > > I do not understand that. > Can you elaborate? do we want signal? How do they compare with announcements and event and #changed In the case of the UIBuilder of void, there are new widgets that extend existing ones but It would be better to not subclass and get better widgets. May be fixing copy/postcopy, use of _,...... references to Preferences,.... This kind of work. > So Long > -Tobias > >

Feb. 11, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #49 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Loading a slice does not mean that you only load what is needed. Here you load all the difference that have been changed between 12 and 13. So have a look at it doing merge. For the CS can you open a workspace after. I cannot.

Feb. 11, 2011

[Pharo-project] Hudson and Squeaksource statistics

by Torsten Bergmann

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

Feb. 11, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #48 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 I do not understand ... I just took the last 1.2 image from Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/132/ and load the slice, it works fine. I've tried with the 4 cs, it works fine too ... Strange

Feb. 11, 2011

Re: [Pharo-project] [Hudson] updates

by Schwab,Wilhelm K

Marcus, Nice work!! The .st file could be very useful. Can you add them for the clients too? Doing that would document what the various images test and provide some examples for using Metacello. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sven Van Caekenberghe [sven(a)beta9.be] Sent: Friday, February 11, 2011 1:28 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [Hudson] updates You were being too modest last time, Marcus, you are really pushing this CI thing forward and forward, really nice to see. Thanks! On 11 Feb 2011, at 01:10, Marcus Denker wrote: > done in the last week: > > - current core and full are now automatically loaded from gforge for building and testing the core image > (1.3 just updates the last core build artefact) > > - For 1.3, there is now a new script build13 that does not kill the image when a debuglog is written. > (all 1.3 builds use this) > > - updated the vm used for running builds and tests (not yet the one bundled in the One-Click) > > - there is now the latest cog. the buildWithCog.sh uses this > > - seaside is build with cog, but tests are run on the interpreter for now > > - aida, seaside, xmlrpc and petitparser used as client tests for 1.2 > https://pharo-ic.lille.inria.fr/hudson/view/Pharo-Clients/ > > - RMod now has it's own view: > https://pharo-ic.lille.inria.fr/hudson/view/Rmod/ > > - the script used for building now available as an artefact > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.1/lastSuccessfulBuild/… Super! > - Disk usage plugin installed Sven

Feb. 11, 2011

Re: [Pharo-project] Issue 3695 in pharo: Redesign AboutBox

by Gary Chambers

As the class comment says, the AboutDialog is for application about boxes and is intended to be subclassed. Is pretty general, overriding newContentMorph allows for any content required depending on the desires of the application author... Example cs attached. "typically your main application window, World here for the example..." World openModal: ReportBuilderAboutDialogWindow new Regards, Gary ----- Original Message ----- From: <pharo(a)googlecode.com> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Friday, February 11, 2011 7:39 AM Subject: [Pharo-project] Issue 3695 in pharo: Redesign AboutBox > Status: Accepted > Owner: Torsten....(a)astares.de > Labels: Milestone-1.3 > > New issue 3695 by Torsten....(a)astares.de: Redesign AboutBox > http://code.google.com/p/pharo/issues/detail?id=3695 > > Beside the Pharo number we should display VM infos > in the about box too: > > Smalltalk isRunningCog > > We should also display the JIT version (if running Cog): > > Smalltalk getSystemAttribute: 1008 > > It is also confusing that SmalltalkImage>>aboutThisSystem > uses a "LongMessageDialogWindow" for the about box although > there is a class "AboutDialogWindow" (which is not used) in > the image. > > > >

Feb. 11, 2011