December 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] chasing the double copy and paste
by StÃ©phane Ducasse Dec. 3, 2009

Dec. 3, 2009

mike asked in the bugtracker "After a double paste, is the undo undoing the double paste as well? That would indicate that not to paste commands come through but rather the paste string gets duplicated." please pay attention and let us know. Stef

2 3

[Pharo-project] proxy username and password
by Mariano Martinez Peck Dec. 3, 2009

Dec. 3, 2009

Hi! I am behind a fucki... proxy that requires user and password. The problem is that in the Pharo preferences I only see to set host and port, but not username and password. Do you know how can I manage this? Thanks! Mariano ps: I am in MacOS in case it helps

4 7

[Pharo-project] newinspector?
by StÃ©phane Ducasse Dec. 3, 2009

Dec. 3, 2009

Hi guys again I did a demo of smalltalk and the newInspecotr got in my way. I tried to analyze what did not work: - apparently the refresh does not work. Does change in instance variables get refreshed in the inspector? I try to understand what get in my way in general. - when an object has few instance variable I think that it is lost in the sea of trees. - I think that the |> class is not useful at the top level. May be just having Class: and the class Name is enough no need for the |> May be the Class : ByteString should appear after the Elements: - the |> methods to be useful should be sorted by category in the screenshot Why do I see the instance variable of the dictionary (array and tally) I find that confusing? Because I get elements and at the same time the instance variables. I do not understand why some lines are bold and other blue When we click on connectInfo I see on the right pane - size : 5 [#host] : a SocketAddress (size: 24) [#loginMethod] : #zork [#password] : nil [#port] : 110 [#user] : 'stephane.ducasse' But I cannot modify anything. What is the point to have Elements expanded in the left pane when I get the contents by clicking on the instance variable and getting the contents on the right. Then Keys should probably close to Elements. I do not see the point to have |> for individual method I do not understand why we see Elements and ByteCode I get a DNU when I click on Elements of a method BTW

3 5

[Pharo-project] class comment displayed
by StÃ©phane Ducasse Dec. 3, 2009

Dec. 3, 2009

hi I wanted to see the class comment so I selected ClassCommentOnClassSelected but apparently OBBrowser do not change. Is it normal? Supported? Stef

3 9

[Pharo-project] squared fly by help
by StÃ©phane Ducasse Dec. 3, 2009

Dec. 3, 2009

alex do you have your code for squared fly by help? Stef

2 3

Re: [Pharo-project] How to contribute [WAS] lukas-renggli.ch down, mirrors exists ?
by laurent laffont Dec. 3, 2009

Dec. 3, 2009

> > > > >> About the bugs (Slime-lr.24,current pharo rc1 web image), when I > select refactor > code critics: > > >> > > >> - it seems that ParserTreeSearcher has been renamed to > RBParserTreeSearcher. Thus there's several errors like > WAChangesStateWhileRenderingRule>>initialize (ParseTreeSearcher is > Undeclared) > Hi. As I've fixed above problems, I have a good opportunity to publish my first contribution to Pharo (heart beating ;). I've followed http://code.google.com/p/pharo/wiki/HowToContribute. Saving my Slime package create Slime-LaurentLaffont.25 package. Then I load it in a fresh image, it works. So I open Monticello, select Slime-LaurentLaffont.25, add PharoInBox repository, click Save. The "Edit Version Name and Log Message" dialog opens but the name of package is now Slime-LaurentLaffont.26, whithout my log message of version 25. How to publish version 25 and not create a version 26 ? Laurent Laffont

3 7

[Pharo-project] Fwd: [Moose-dev] Re: Re: duplication between default: and version40beta2:?
by StÃ©phane Ducasse Dec. 3, 2009

Dec. 3, 2009

> From: stephane ducasse <stephane.ducasse(a)gmail.com> > Date: December 3, 2009 8:27:27 PM GMT+01:00 > To: metacello(a)googlegroups.com > Cc: Pharo-project(a)lists.gforge.inria.fr, Related to the development of Moose and other related tools <moose-dev(a)iam.unibe.ch> > Subject: Re: [Pharo-project] [Moose-dev] Re: Re: duplication between default: and version40beta2:? > > > apparently we had a differetn definition of map. > my point is that we need map with exact numbers of component to be able to reload and build more. > Now I like the baseline idea. > > On Dec 3, 2009, at 8:14 PM, Dale Henrichs wrote: > >> >> In a Metacello context. >> >> The map of packages and their relationships is called a #baseline version. If one loads a #baseline version the latest version of each package is loaded. The "structure" is stable but loading a #baseline version is a risky proposition for everyone except project developers themselves who are prepared to address load-time conflicts/bugs. >> >> A #development version, imports structure from the #baseline, but a specific package version is supplied for each Monticello package or project. When a development version is loaded, the explicit list of package versions are loaded. IN a #development version, the package versions are not finalized and may change over time. When a #development version is saved, there is an presumption that some level of testing has gone on and that the package versions are expected to work together. One can go to a particular version of the package in which the configuration is saved and expect to load the same packages....However, the list of package versions will change over time. >> >> For all other 'released' versions, (beta, release, alpha, stable, etc.) it is expected that the list of package versions will never change - the code base may still be alpha, but it is a stable known point with respect to package versions. >> >> (BTW, I've added the metacello group to this cross-posted message:) >> >> Dale >> ----- "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: >> >> | Still still still you can always have a map (a map of all the >> | components you loaded that they work or not). >> | This is orthogonal to a release or just publications. This is a >> | sofware artefact. I know that you know it. >> | The fact to have map is orthogonal of the choice latest or one >> | version. >> | I just write that for others following our discussion.... >> | >> | Stef >> | >> | >> | >> | On Dec 3, 2009, at 3:59 PM, Tudor Girba wrote: >> | >> | > Hi, >> | > >> | > Not every loading strategy have the same goal or the same context. >> | > >> | > Sub projects will be developed and published in their own context >> | > without taking into account the overall project. However, when >> | > maintaining the overall project, I want to be able to say "load >> | > latest" so that I can easily load everything and check whether >> | > everything still holds together. >> | > >> | > For overall release management, I do not want to rely on "load >> | > latest". Instead I will release a coherent version when I see that >> | it >> | > works. This will be a fixed set of packages with exact versions that >> | >> | > will work together. >> | > >> | > Cheers, >> | > Doru >> | > >> | > >> | > On 3 Dec 2009, at 14:21, Marcus Denker wrote: >> | > >> | >> >> | >> On Dec 3, 2009, at 1:40 PM, Laval Jannik wrote: >> | >> >> | >>> Yeh, >> | >>> >> | >>> Now, I understand the process... (I am slow :) ) >> | >>> >> | >>> But, in this process we must specify versions and maintain it. >> | >>> Is there a solution (in monticello maybe) to say a version of a >> | >>> package is stable. >> | >>> So in this case, we can say "I want last stable version of my >> | >>> package" and we do not need to maintain ConfigurationOf. >> | >>> >> | >> >> | >> The problem is that it's not one package... your system will be 20 >> | >> | >> packges. You can say " load the latest of all, that works". >> | >> But: now I want to load the version that worked so great last >> | month. >> | >> Which set of packages exactly where that? >> | >> >> | >> Tagging single packages as "release" will not help, as you don't >> | >> have the info which released package works with which other >> | >> released package. >> | >> >> | >> >> | >> Marcus >> | >> _______________________________________________ >> | >> Moose-dev mailing list >> | >> Moose-dev(a)iam.unibe.ch >> | >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> | > >> | > -- >> | > www.tudorgirba.com >> | > >> | > "Obvious things are difficult to teach." >> | > >> | > >> | > >> | > >> | > _______________________________________________ >> | > Pharo-project mailing list >> | > Pharo-project(a)lists.gforge.inria.fr >> | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> | >> | >> | _______________________________________________ >> | Pharo-project mailing list >> | Pharo-project(a)lists.gforge.inria.fr >> | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > >

1 0

[Pharo-project] [ann 1.1] pre-built #11068
by Marcus Denker Dec. 3, 2009

Dec. 3, 2009

http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip

8 11

Re: [Pharo-project] [Moose-dev] Re: duplication between default: and version40beta2:?
by Laval Jannik Dec. 3, 2009

Dec. 3, 2009

Yeh, Now, I understand the process... (I am slow :) ) But, in this process we must specify versions and maintain it. Is there a solution (in monticello maybe) to say a version of a package is stable. So in this case, we can say "I want last stable version of my package" and we do not need to maintain ConfigurationOf. Maybe this discussion is more global than moose community, So I copy it in pharo mailing list. Jannik On Dec 3, 2009, at 13:15 , Tudor Girba wrote: > Hi Stef, > > As I mentioned before, default represents the work in progress. It can happen that the work in progress is the same as the previously released version, and that is why you will see duplication. > > Another possibility would be to reuse the previous configuration and just mention the delta (of adding new packages), but I am not sure this would scale in the long run. > > So, the current process is: > - work on default > - when we release, we copy the method in a new baselineXXX > - we create a hardcoded version in versionXXX > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

6 5

[Pharo-project] Slime at work
by laurent laffont Dec. 3, 2009

Dec. 3, 2009

Hi, I'm reading Dynamic Web Development with Seaside. I'm lost on how to open Slime on a specific package in Pharo, as described here: http://book.seaside.st/book/components/slime/at-work Regards, Laurent

3 3