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

Re: [Pharo-project] a bug with Installer

by Keith Hodges

jannik.laval.gmail wrote: > Ok, it works with the last version. > > Now, I have a problem with the method browse: > Installer ss project:'Installer'; browse: 'InstallerAll'. > > The browser open on the class Loading.MCVersionLoader. > > Is there any reason ? > Thanks > > Jannik The reason being that earlier versions of installer would return an MCVersion in order to laod a single version. Current versions return an MCVersionLoader which doesnt implement browse, and so falls back to the implementation on Object. Fixed in latest MC1.5/6, and a workaround has been added to latest Installer. Keith

Dec. 3, 2008

Re: [Pharo-project] About ecompletion

by Simon Denier

On 3 dÃ©c. 08, at 13:38, Damien Cassou wrote: > On Wed, Dec 3, 2008 at 1:07 PM, Simon Denier <Simon.Denier(a)inria.fr> > wrote: >> As a newcomer, I dont know who is the developper/maintainer for >> eCompletion. > > There is no maintainer of eCompletion actually. Ruben Bakker > implemented it. I have write access to the repository if you have > something to commit. OK, thanks for the info, I will try to get into it. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Simon

Dec. 3, 2008

[Pharo-project] Polymorph password dialog enhancement

by Torsten Bergmann

>multiply it by a factor of 100. Then you get to what the current state is in Squeak. You dont have to tell me. Since I know Squeak since Version 1.0 and later (see [1]) the factor I would apply would definitely be greater than 100 ;) >Yes. The bug-tracker is like a TODO list. OK: http://code.google.com/p/pharo/issues/detail?id=371 Bye T. [1] http://www.fit.vutbr.cz/study/courses/OMP/public/software/sqcdrom2/Tutorial… -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

Dec. 3, 2008

Re: [Pharo-project] a bug with Installer

by jannik.laval.gmail

Ok, it works with the last version. Now, I have a problem with the method browse: Installer ss project:'Installer'; browse: 'InstallerAll'. The browser open on the class Loading.MCVersionLoader. Is there any reason ? Thanks Jannik Le 2 dÃ©c. 08 Ã 21:20, Keith Hodges a Ã©crit : > jannik.laval.gmail wrote: >> Hi all, >> >> I would run this: (present in InstallerMonticello>>basicView) >> Installer ss project: 'Installer'; view: 'Installer-Core'. >> >> But, I have an error: doesNotUnderstand: #definitions. >> >> Can anyone help me ? >> Thanks >> >> Jannik > Fixed properly with latest Monticello1.5/1.6 > > Workaround added to latest Installer for older Monticello releases > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 3, 2008

Re: [Pharo-project] Polymorph password dialog enhancement

by Gary Chambers

Well, I will try to maintain things such that Polymorph is compatible with both for now (an extra package for Squeak). If Markus can let me know the differences I'll move the affected methods out. As for the PasswordDialogWindow... just putting in now. Reworked to be more in keeping with Polymorph. Regards, Gary. ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, December 03, 2008 2:33 PM Subject: [Pharo-project] Polymorph password dialog enhancement > It's not a question of compatibility, the question is where will > Polymorph be continued - in SqS/Pharo or SqS/UIEnhancements or both? > > I didnt notice (until now) that the integrated plymorph packages are now > also > in the SqS/Pharo repository. > > A new branch or just a move? Same question applies for other packages > integrated later. > > Bye > Torsten > > > BTW: Will I have to open an issue when I just put something into the inbox > (like a new ScriptLoader from today that fixes Seaside loading)? > > > > > > > > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: > http://www.gmx.net/de/go/multimessenger > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 3, 2008

Re: [Pharo-project] Polymorph password dialog enhancement

by Marcus Denker

On 03.12.2008, at 15:33, Torsten Bergmann wrote: > It's not a question of compatibility, the question is where will > Polymorph be continued - in SqS/Pharo or SqS/UIEnhancements or both? > > I didnt notice (until now) that the integrated plymorph packages are > now also > in the SqS/Pharo repository. > > A new branch or just a move? Same question applies for other packages > integrated later. > The problem is that removing etoys is not a clean thing. We have first methods that are needed to be changed for both removing etoys *and* polymorph. So that's why the packages need to be in the pharo repository. In general, if you think about code quality or modularity in the context of Squeak: Think about the worst you can think of, then multiply it by a factor of 100. Then you get to what the current state is in Squeak. It's a mess of epic proportions... > Bye > Torsten > > > BTW: Will I have to open an issue when I just put something into the > inbox > (like a new ScriptLoader from today that fixes Seaside > loading)? Yes. The bug-tracker is like a TODO list. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Dec. 3, 2008

[Pharo-project] Polymorph password dialog enhancement

by Torsten Bergmann

It's not a question of compatibility, the question is where will Polymorph be continued - in SqS/Pharo or SqS/UIEnhancements or both? I didnt notice (until now) that the integrated plymorph packages are now also in the SqS/Pharo repository. A new branch or just a move? Same question applies for other packages integrated later. Bye Torsten BTW: Will I have to open an issue when I just put something into the inbox (like a new ScriptLoader from today that fixes Seaside loading)? -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

Dec. 3, 2008

Re: [Pharo-project] Re: Missing #dispatchResultsIntoHistory

by Alexandre Bergel

> The problem we are facing right now is that OB-Enhancements is at > the moment dependent on a particular version of SUnit, one that > contains these history enhancements. As OB-Enhancements is supposed > to work in Pharo and Squeak, we can now either update the SUnit > version in Squeak-dev to also use your work on test history (which > would make sense to me) or I can change OB-Enhancements to test > whether the history-aware SUnit is loaded or not... This seems to be a cleaner solution to me. Else, people may wonder why there is an empty dispatchResultsIntoHistory defined somewhere (even with an appropriate note). Actually, simply testing whether this method exist should be sufficient. I am doing it now... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 3, 2008

[Pharo-project] Seaside29 and pharo

by Torsten Bergmann

David, dont use the changeset. If you have the latest pharo image (#10185) you can use use ScriptManager loadSeaside29 to get the latest. Note: before running that just remove the line in this method that installs "RSS-Squeak-Core". This package was kicked on Monday by pmm (see [1]). An update for ScriptManager is also in the pharo inbox. Bye Torsten [1] http://lists.squeakfoundation.org/pipermail/seaside-dev/2008-December/00201… -- Sensationsangebot verlÃ¤ngert: GMX FreeDSL - Telefonanschluss + DSL fÃ¼r nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a

Dec. 3, 2008

[Pharo-project] Re: Missing #dispatchResultsIntoHistory

by Alexandre Bergel

So, it seems that adding an empty dispatchResultsIntoHistory in Testing@SS will prevent having two versions of OBCmdTestClass I will do it in a minutes... Alexandre On 3 Dec 2008, at 10:53, Damien Cassou wrote: > On Wed, Dec 3, 2008 at 2:49 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> Just to make sure that I fully understand your email. Are you >> suggesting the >> history feature should be integrated into the Standard SUnit? >> I haven't got the time to check what is in Testing@squeaksource >> yet. I hope >> to do it before next week. > > I'm not suggesting anything. I just would like that the testing > features you have implemented one year ago continue to work in Squeak. > Currently, I can't run the tests from the browser anymore because of > this missing method. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 3, 2008