May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by stephane ducasse

> I believe the things I do regarding the fork because of personal > conversations with people close to the decision. Fun because we are the people who took the decisions and we never got a real discussions so far. So this means that so far you got discussions with people that believe that they know why we forked but may be these people have only a partial view on it. ;D And since we created Pharo with Marcus and a couple of others I can tell that this is not a ego nor a personal point that drove us. I was thinking to go to ruby, python or lua at that time. This is a life vision. People should simply look at what our acts! We are not doing Pharo for us but because we believe in a smalltalk way of programming. But we want more much more than an old ST-80 system. >> If you ask me, we should have started to do Pharo way before because we all lost >> energy for nothing. If I should redo it I would. > > That may be so. Squeak in 2013 is not the same community as Squeak in > 2007/2008 (and not just because most of the community moved to Pharo). Sure! Now when you wake up the morning you have to decide what you want to do and we decided to build Pharo to create a sustainable eco system where companies can make money and wealth/knowledge/innovation can expand. I have no idea what is the goal of squeak but our goal is clear (and may be it is not reasonable) is to make a true alternative to dynamic languages out there and the best Smalltalk implementation we can. We wrote a 40 pages document and one day I will revise it. So people sharing this vision can join or not. Pharo is not a closed project we welcome newcomers. We even hired them when they share our vision and we have money (with I fight for). for example the first time I met esteban he was not really happy about Pharo, then he **understood** after discussing for real with us our vision. Stef

May 22, 2013

Re: [Pharo-dev] TxText new version 0.8

by Igor Stasenko

On 22 May 2013 10:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I would use > > TextModelCore > TextModelExtensions > > TextModelCore-Tests > > No extra dash in the middle. nooooo :) But for tests, i +1, the names are not very good. For package: Package-Name-Tick-Tack tests should be in: Package-Name-Tick-Tack-Tests This convention used everywhere in pharo. > Stef > > On May 21, 2013, at 10:24 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2013/5/21 stephane ducasse <stephane.ducasse(a)free.fr> >> >> >> On May 21, 2013, at 9:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >> 2013/5/20 stephane ducasse <stephane.ducasse(a)free.fr> >>> >>> >>> Hello. >>> >>> New TxText version 0.8 is ready: >>> >>> - editor stuff extracted to separate packages TxText-Editor and >>> TxTextTests-Editor >>> >>> may be you should call the second package TxTextEditor-Tests >> >> >> I just follow convention of other TxText packages: TxText-Model -> >> TxTextTests-Model, TxText-Layout -> TxTextTests-Layout and etc. >> Some times ago I suggest such repackaging and nobody was against it >> >> >> Still I think that the packages names are not good. I do not hitnk that >> having tests mixed with the package name is a good approach >> and we should clean all of them for 3.0 > > > So what the correct way (Pharo way) to name test packages? > For example I have 'MyPackage-SubCat1-SubCat2'. What name for test package > should be? > >> >> >> Stef >> >> >> >> > > -- Best regards, Igor Stasenko.

May 22, 2013

UIPainters, or seducing developers in not building the right abstractions

by Stephan Eggermont

In a GSoC proposal comment ben asked me to comment on what I wrote: > For building good UIs, UIPainters of the most common kind > (Delphi, Visual Studio, Interface Builder) provide very little added value. > They sometimes provide guidelines for spacing and alignment, > but also seduce developers in not building the right abstractions, > making the applications prohibitively expensive to evolve. The typical way developers get started in Delphi, is by dragging some controls on a window and directly filling in the event handlers. That makes projects easy to plan, as there will be a lot of repetitive work with not much thinking needed. Once you get to 50 screens, making small adjustments to the layout of the application gets to be annoying though. "We have a new company house style, this is the new background color and we now use a Gill Sans instead of Arial". The editing of component attributes is at the lowest level, so it needs to be changed in all components individually. Different fonts have different widths, so changing fonts has layout consequences throughout the whole application. Interface Builder provides pop-up guides to help with alignment and spacing instead of a simple grid. It knows about sizes and expected distances to make an application look like a mac application. > The added value of a UIPainter is in attracting people new to the platform, > and helping them explore the environment and its possibilities. One of the things that makes Delphi attractive as a platform is that you can build and deploy a simple application in less than 5 minutes. Stephan

May 22, 2013

[update 3.0] #30160

by Marcus Denker

30160 ----- 10716 update shrinking methods https://pharo.fogbugz.com/f/cases/10716 7382 TextModel should allow users to cancel/validate an accept action https://pharo.fogbugz.com/f/cases/7382 10725 unify #binding, #variableBinding and #ocBinding https://pharo.fogbugz.com/f/cases/10725 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.185… http://smalltalkhub.com/mc/Pharo/Pharo30/main/SmartSuggestions-MarcusDenker… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Interpreter-Core-MarcusDe…

May 22, 2013

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by Goubier Thierry

Le 22/05/2013 15:26, Camillo Bruni a Ã©crit : > > On 2013-05-22, at 15:22, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Le 22/05/2013 15:12, Camillo Bruni a Ã©crit : >>> >>> On 2013-05-22, at 15:05, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>>>>> Not sure I can answer that; in the meantime, I just added a FileTreeUrl as a >>>>>>> subclass of FileUrl, and Gofer seems happy with that. >>>>>> >>>>>> Neat. >>>>> >>>>> Now, I can do: >>>>> >>>>> ./pharo Pharo.image eval --save Gofer new url: \'filetree://`pwd`/../../src\'\; package: \'TauC-Parser\'\; load >>>> >>>> cool! >>>> >>>>> And a long time after (package loading is slowwww), it's done. >>>>> >>>>> However, the --install in the config handler doesn't work; had to use --install=stable instead. >>>> >>>> that's in 2.0 I guess, since I changed it to use #stable by default in 2.0. >>>> So we should push the FileTreeUrl into the 2.0 repository for FileTree.. >>> >>> or simpler, change the command line handler to use GenericURL >> >> Well, with FileTreeUrl, if you have a config in your filetree repo, you can use config filetree:///whatever ConfigurationOf; no need to change the ConfigurationCommandLineHandler for that. >> >> I haven't done a ConfigurationOf for that project, so I wanted to load packages by packages (hence the eval) but you'll notice this is almost the same code as ConfigurationCommandLineHandler. > > yes, I came to the same conclusion: https://github.com/dalehenrich/filetree/issues/74 :) I've uploaded a MonticelloFileTree-Core package with a FileTreeUrl in it in the ss3 FileTree repository. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

May 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 51 regressions found. AST.Interpreter.Test.ASTInterpreterTest.testExceptionReturn AST.Interpreter.Test.ASTInterpreterTest.testSend AST.Interpreter.Test.ASTInterpreterTest.testLookUp AST.Interpreter.Test.ASTInterpreterTest.testSignalException AST.Interpreter.Test.ASTInterpreterTest.testPrimitive AST.Interpreter.Test.ASTInterpreterTest.testAssert AST.Interpreter.Test.ASTInterpreterTest.testDNU AST.Interpreter.Test.ASTInterpreterTest.testBlockOutOfHomeContext AST.Interpreter.Test.ASTInterpreterTest.testLazyInitialization AST.Interpreter.Test.ASTInterpreterTest.testMethodArguments AST.Interpreter.Test.ASTInterpreterTest.testDNUCatched AST.Interpreter.Test.ASTInterpreterTest.testThisContext AST.Interpreter.Test.ASTInterpreterTest.testDNUInNestedBlock AST.Interpreter.Test.ASTInterpreterTest.testEnsureTricky AST.Interpreter.Test.ASTInterpreterTest.testBlockVar AST.Interpreter.Test.ASTInterpreterTest.testPerform AST.Interpreter.Test.ASTInterpreterTest.testLoop AST.Interpreter.Test.ASTInterpreterTest.testBasicCode AST.Interpreter.Test.ASTInterpreterTest.testBlockArgument AST.Interpreter.Test.ASTInterpreterTest.testExternalBlock ...

May 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 51 regressions found. AST.Interpreter.Test.ASTInterpreterTest.testExceptionReturn AST.Interpreter.Test.ASTInterpreterTest.testSend AST.Interpreter.Test.ASTInterpreterTest.testLookUp AST.Interpreter.Test.ASTInterpreterTest.testSignalException AST.Interpreter.Test.ASTInterpreterTest.testPrimitive AST.Interpreter.Test.ASTInterpreterTest.testAssert AST.Interpreter.Test.ASTInterpreterTest.testDNU AST.Interpreter.Test.ASTInterpreterTest.testBlockOutOfHomeContext AST.Interpreter.Test.ASTInterpreterTest.testLazyInitialization AST.Interpreter.Test.ASTInterpreterTest.testMethodArguments AST.Interpreter.Test.ASTInterpreterTest.testDNUCatched AST.Interpreter.Test.ASTInterpreterTest.testThisContext AST.Interpreter.Test.ASTInterpreterTest.testDNUInNestedBlock AST.Interpreter.Test.ASTInterpreterTest.testEnsureTricky AST.Interpreter.Test.ASTInterpreterTest.testBlockVar AST.Interpreter.Test.ASTInterpreterTest.testPerform AST.Interpreter.Test.ASTInterpreterTest.testLoop AST.Interpreter.Test.ASTInterpreterTest.testBasicCode AST.Interpreter.Test.ASTInterpreterTest.testBlockArgument AST.Interpreter.Test.ASTInterpreterTest.testExternalBlock ...

May 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 51 regressions found. AST.Interpreter.Test.ASTInterpreterTest.testExceptionReturn AST.Interpreter.Test.ASTInterpreterTest.testSend AST.Interpreter.Test.ASTInterpreterTest.testLookUp AST.Interpreter.Test.ASTInterpreterTest.testSignalException AST.Interpreter.Test.ASTInterpreterTest.testPrimitive AST.Interpreter.Test.ASTInterpreterTest.testAssert AST.Interpreter.Test.ASTInterpreterTest.testDNU AST.Interpreter.Test.ASTInterpreterTest.testBlockOutOfHomeContext AST.Interpreter.Test.ASTInterpreterTest.testLazyInitialization AST.Interpreter.Test.ASTInterpreterTest.testMethodArguments AST.Interpreter.Test.ASTInterpreterTest.testDNUCatched AST.Interpreter.Test.ASTInterpreterTest.testThisContext AST.Interpreter.Test.ASTInterpreterTest.testDNUInNestedBlock AST.Interpreter.Test.ASTInterpreterTest.testEnsureTricky AST.Interpreter.Test.ASTInterpreterTest.testBlockVar AST.Interpreter.Test.ASTInterpreterTest.testPerform AST.Interpreter.Test.ASTInterpreterTest.testLoop AST.Interpreter.Test.ASTInterpreterTest.testBasicCode AST.Interpreter.Test.ASTInterpreterTest.testBlockArgument AST.Interpreter.Test.ASTInterpreterTest.testExternalBlock ...

May 22, 2013

Re: [Pharo-dev] do not forget to register to the pharo web day

by stephane ducasse

Hi rafa The conference will be in a mix of french and english because it is a local conference but we will have videos. Inria nicely accepted to send a professional to shot the conference. We will have to do the post processing. > > Steph, Which will be the conference language? English of French? and, do you plan to record and publish the sessions? > > Rafa > > > > > 2013/5/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Please register for the pharo web day > > http://www.inria.fr/centre/lille/agenda/conference-web-3.0-avec-pharo > >

May 22, 2013

[update 3.0] #30159

by Marcus Denker

30159 ----- 10724 Remove AST Semantic Analysis package https://pharo.fogbugz.com/f/cases/10724 10722 Old compiler should have iv compilationContext https://pharo.fogbugz.com/f/cases/10722 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.469.diff

May 22, 2013