- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3966 in pharo: String>>lines misses tests
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Status: FixToInclude Owner: damien.c...@gmail.com Labels: Type-Patch Difficulty-Easy Importance-Low Milestone-1.2.2 New issue 3966 by damien.c...@gmail.com: String>>lines misses tests http://code.google.com/p/pharo/issues/detail?id=3966 I've written a simple test for String>>lines: testLines | sampleCRString sampleLFString sampleCRLFString | sampleCRString := 'Fred', String cr , 'the' , String cr , 'Bear'. sampleLFString := 'Fred', String lf , 'the' , String lf , 'Bear'. sampleCRLFString := 'Fred', String crlf , 'the' , String crlf , 'Bear'. self assert: sampleCRString lines = #('Fred' 'the' 'Bear'). self assert: sampleLFString lines = #('Fred' 'the' 'Bear'). self assert: sampleCRLFString lines = #('Fred' 'the' 'Bear').

1 4

Re: [Pharo-project] Issue 2561 in pharo: findTokens: String lf , String cr
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Comment #4 on issue 2561 by damien.c...@gmail.com: findTokens: String lf , String cr http://code.google.com/p/pharo/issues/detail?id=2561 Name: Monticello-DamienCassou.506 Author: DamienCassou Time: 6 April 2011, 8:31:01 am UUID: e8f7e433-2bd8-4681-9ff0-aede03ed8102 Ancestors: Monticello-MarcusDenker.505 - Issue 2561: findTokens: String lf , String cr. Changes MCFileBasedRepository>>notifyList

1 3

[Pharo-project] Issue 3962 in pharo: More cleanup of PasteUpMorph
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Status: FixProposed Owner: marcus.d...@gmail.com Labels: Milestone-1.3 New issue 3962 by marcus.d...@gmail.com: More cleanup of PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3962 ... related to World-In-World support and general dead code Attachments: CleanPasteUpM.1.cs 4.4 KB

1 1

[Pharo-project] Issue 3959 in pharo: A little dead code removal SmalltalkImage
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Status: FixProposed Owner: marcus.d...@gmail.com Labels: Milestone-1.3 New issue 3959 by marcus.d...@gmail.com: A little dead code removal SmalltalkImage http://code.google.com/p/pharo/issues/detail?id=3959 1) test for formatter SmalltalkImage removeSelector: #testFormatter! SmalltalkImage removeSelector: #testFormatter2! not used, the current pretty printer is crap anyway. 2) #shutDownSound Attachments: RemoveFormatterTestsSmalltalkImage.1.cs 190 bytes RemoveShutDownSound.1.cs 142 bytes

1 1

Re: [Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
by Marcus Denker April 7, 2011

April 7, 2011

On Apr 6, 2011, at 7:02 PM, HernÃ¡n Morales Durand wrote: > Hi, > > Installing O2 gives me a MNU, I've evaluated: > > "- If you want to use another System Browser than the default > (OmniBrowser), you can install O2 browser: " > > Gofer new > squeaksource: 'MetacelloRepository'; > package:'ConfigurationOfO2'; > load. > > ((Smalltalk at: #ConfigurationOfO2) project version: '1.2') load: 'Dev'. > > bug report attached. > It's noted to be fixed for 1.2.2: http://code.google.com/p/pharo/issues/detail?id=3831 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] On fixed release planning [was: Actions done in 1.3]
by laurent laffont April 7, 2011

April 7, 2011

On Wed, Apr 6, 2011 at 10:32 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > On Wed, Apr 6, 2011 at 1:30 AM, laurent laffont <laurent.laffont(a)gmail.com > > wrote: > >> >> On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> Planning is also important. >>> >>> Time is good, but another thing is i think we should think about, >>> what features we want to be in new release, and do not release until >>> they delivered. >>> >> >> I don't really like this. I prefer rhythm, agility. Timeboxing enables >> maximum value in each release. If a feature is really important, it will be >> on time. If not on time, it means it was no so important. >> > > I couldn't disagree more. Especially with VisualWorks time-boxing has > caused problems with quality and delivery of functionality. Fundamentally > there is no point putting out a release for the sake of it. A release is > about functionality, both new functionality and bug fixes. Without either > of these there is absolutely no point in releasing anything beyond > marketing. Yes, during a release one can make the call that because a > subset of the functionality will arrive much later than the rest of the > functionality it makes sense for that late functionality to slip the release > and arrive in a later one. But that doesn't imply putting out an > essentially empty release for the sake of promptness. > Let me talk about my experience. Quality may suffer with timeboxing without continuous integration and good test coverage. CI + tests enable timeboxing because I can maintain high quality level. And now we have CI it's wonderful. As a user, I like software developed with fixed iterations because I know exactly when it wil be released, plan upgrades and validations. I'm easily in sync. As a developer I like fixed iterations because 1/ We care more about quality. Cannot develop all this feature in the iteration ? do only a part and check that it works well - write missing tests. Not enough time left to integrate this feature ? Just work on the many details that we need to fix and integrate the new feature soon in next iteration. 2/ We maintain energy. No long waiting period of stuff xxxx to be done without realeasing. The more we wait, the less productive we are. 3/ I like to change the planning from "what features this version can't be released without ?" to "what can we develop in 1 / 3 / 6 months (with high quality) ?". 4/ ok I stop here. Even every day at work I'm timeboxing with 25mn iterations (Pomodoro technique) for several years - I cannot live without now. That makes me deliver a lot of energy. I've never seen empty release because of fixed iterations. And even if the release contains only fixed bugs, details adjustment and no new big feature it's great. Details matters a lot. In a former job my team was doing a new features iteration, then a "care about details iteration", then a new features iteration, and so on.... it was a lot of fun and worked. Indeed I would like try and see if it works with Pharo. I also would like Pharo to be a reference of modern agile development - that would be a step forward. Laurent. > > One thing I do approve of is maintennance releases, where some time after > an initial release one puts out a maintennance release that only contains > bug fixes and no new functionality and I think there are good arguments for > and positive experience with scheduling the maintennance release to arrive > at some fixed time after the first release, e.g. 4 to 6 months. But major > releases must IMO be driven by content. > > best > Eliot > > >> >> Always green test is a must-have. >> >> >> >>> Besides bug fixing and minor improvements, there should be some >>> functionality which we want to have in new release, >>> >> >> That should be a goal, but don't delay a release because the feature is >> not here. If releases are often ( for example every 3 months), shorter, it >> won't be a big problem to wait for the next one. >> >> I prefer to have a release *now* without my feature and wait 3 months for >> the next release than no release and waiting for 3 months more with less and >> less energy. >> >> >> Laurent. >> >> >>> so then you could say: 1.x is better than previous because of A,B,C, >>> but not because a,b,c ( capital letters is major stuff, while regular >>> ones is for minor stuff ) :) >>> >>> >>> On 6 April 2011 10:01, Serge Stinckwich <serge.stinckwich(a)gmail.com> >>> wrote: >>> > On Wed, Apr 6, 2011 at 12:56 PM, laurent laffont >>> > <laurent.laffont(a)gmail.com> wrote: >>> >> On Tue, Apr 5, 2011 at 10:49 PM, Mariano Martinez Peck >>> >> <marianopeck(a)gmail.com> wrote: >>> >>> >>> >>> Yes!!! totally agree. Now that we release 1.2, I would freeze and >>> release >>> >>> PharoCore 1.3 beta. Update the link to stable pharo to that, and >>> start >>> >>> trying to load the dev tools there. >>> >> >>> >> +10 >>> >> And propose a fixed date for release - no compromise, will be release >>> at >>> >> this date. >>> > >>> > +1 >>> > Timeboxing sounds great. >>> > Podomoro for software development ;-) >>> > >>> > Regards, >>> > -- >>> > Serge Stinckwich >>> > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>> > Every DSL ends up being Smalltalk >>> > http://doesnotunderstand.org/ >>> > >>> > >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >

2 1

Re: [Pharo-project] Actions done in 1.3
by Marcus Denker April 7, 2011

April 7, 2011

On Apr 5, 2011, at 9:10 PM, StÃ©phane Ducasse wrote: > Hi guys > > to help us in the future I started > > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotThree > > The list starts to get long... Maybe we should do a 1.3 release soon... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

8 11

[Pharo-project] [ANN] Pharo Release 1.2.1
by Adrian Lienhard April 7, 2011

April 7, 2011

The Pharo Project is proud to announce the release of Pharo 1.2.1, the third major release of this clean, innovative, open-source Smalltalk environment. Static URL for this ANN: http://www.pharo-project.org/pharo-download/release-1-2-1 French translation: http://code.google.com/p/pharo/wiki/Pharo12FrenchAnnouncement * Update #12345 On Tuesday, March 29th 2011, update #12345 was issued to Pharo's 1.2 development line, a line that started back in June 2010 and was frozen in January 2011. Next, Pharo's continuous integration machinery successfully started building various artifacts based on this 'Pharo Core 1.2', the most important one being 'Pharo 1.2' proper, the full featured development image. Pharo Core 1.2.1 passes 7.836 unit tests, Pharo 1.2.1 no less than 10.760. A large, international community of developers worked hard for several months to iron out all problems and to make Pharo compatible with various Smalltalk libraries and frameworks, among them Seaside 3.0.3 which passes its 1.599 tests. * Pharo Core Changes True to the Pharo philosophy, this release contains numerous small changes, refactorings, cleanups and bugfixes improving the overall quality. Important changes include: â Cleaned the Pluggable hierarchy â Added new undo framework â Cleaned Morph and PasteUpMorph â Added DummyUIManager, a UIManager for operating without a UI â Added NewTextMorph â Removed left overs from MVC: PopUpMenu, SelectionMenu and CustomMenu â Cleaned Utilities, Preferences and TheWorldMenu â Included SimpleMorphic preview â Removing empty classes â Added new TextEditor and SmalltalkEditor â Added new, clean and simple Glamorous, Glamorous Orange GUI Themes â Added new Pro GUI Theme â Added Cog compliant behavior â Added better blocks debugging â Better support for separating SmalltalkImage and SystemDictionary â Fixed package dependencies, providing a good platform for kernel images â Removed old JIT experiments â Migrated to MethodReferenceWithSource and friends â Added more pages under the Help system â Improved the number of commented classes â New Finder tool (replacing Messages Names and Method Finder) â New Recent Changes tool (replacing Recent Submissions) â Improved SpaceTally â Fixed pointer finders tools â Integrated SUnit 4 Started Continuous Integration: use Hudson/Jenkins to automatically build images, run tests, and compile VMs For the Core 1.2 Image development line, 693 issues were resolved. * Pharo Changes The full featured Pharo development image is built automatically by loading the Metacello configuration aptly called ConfigurationOfPharo. Important changes include: â Updated to latest Metacello and all configurations used to use symbolic versions â New tools: Metacello Configuration Browser, Memory Monitor, and Autotest â Updated versions of Shout, RoelTyper, OCompletion, OmniBrowser, AutomaticMethodCategorizer, RefactoringBrowsers, Nile, ProfStef â Added XML-Support, and more Help â Removed NewInspector For the Full Dev 1.2 Image development line, 57 issues were resolved. * Downloads: see http://www.pharo-project.org/pharo-download * Success Stories Pharo has a large user base spread all over the world. Hence there is a growing collection of success stories (www.pharo-project.org/about/success-stories) projects using Pharo that choose to go public with this. Recently, the following were added: DrGeo - an award winning interactive geometry application also used for teaching primary and secondary level students Issys Tracking - a workflow platform to support authorization procedures for the medical practice for a large social organization/health insurance in Argentina Inceptive's Custom ERP - an application for the event planning and resource management administration of a large cultural centre in Flanders __________________________ www.adrian-lienhard.ch twitter.com/adrianlienhard

1 0

[Pharo-project] Issue 3957 in pharo: MethodWrappers left method after uninstall
by pharo＠googlecode.com April 6, 2011

April 6, 2011

Status: New Owner: ---- New issue 3957 by lem...@gmail.com: MethodWrappers left method after uninstall http://code.google.com/p/pharo/issues/detail?id=3957 Pharo image: Pharo 1.2.1 Latest update: #12345 Virtual machine used: 'Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.54]' Class browser used (if applicable): OB Steps to reproduce: 1. create a new class, example Foo 2. install a method wrapper on Foo, on a selector non defined locally. 3. uninstall the method wrapper. 4. now you have the method defined locally, with the inherited behavior. Example: | a | a := ObjectAsMethodWrapper on: Foo selector: #hash. a install. a uninstall. Now you have a hash method on Foo, that should not be there. One solution is to add something like this to the install code: (self wrappedClass localSelectors includes: self selector) ifTrue: [needCleanUp := false.] ifFalse: [needCleanUp := true]. And this to the uninstall code: needCleanUp ifTrue: [self wrappedClass removeSelector: self selector]

3 7

[Pharo-project] Question about the Refactoring Browser
by Jan van de Sandt April 6, 2011

April 6, 2011

Hi, I want to analyze some Smalltalk code in a collection of Monticello packages without actually loading these packages in the image. Can I use the Refactoring Browser for this? Jan.

4 6