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

Re: [Pharo-project] [ANN] 10205

by Keith Hodges

Michael Rueger wrote: > StÃ©phane Ducasse wrote: > > >> Next >> - category as packages collections level two >> - mike network refactoring (I hope it loads). >> > > One problem with the network refactoring is that it moves classes > between packages I dont see that the following follows. > "and thus needs to be loaded from a configuration map." > Option 1, Atomic loading. Available in MC1.5/6 as an option that can be enabled. Option 2, Out of order loading feature of MC1.5. > I tried loadTogether:merge: but that still ends up with classes missing > in the image. > Might be worth finding out why. > Suggestions on how to do this? I could port some of the ReleaseBuilder > code that allows to script loading of configuration maps. > > Installer handles mcm's. > Michael > Keith

Jan. 13, 2009

Re: [Pharo-project] various issue related to test

by StÃ©phane Ducasse

Hilaire if you want to reuse the trait created a TestCase subclass: uses: put the trait here. have a look at OrderedCollectionTest for example. On Jan 13, 2009, at 4:34 PM, Hilaire Fernandes wrote: > i am writting double link list and co, then a few test. > > i found it will be neat to reuse the linked list test. this one is > trait based. > > I found the following issue preventing reussability: > > - when i subclass linked list test with trait, I do not understand what you mean above. > i get the trait test but not the test from linked list test, i > expected to get these ones > as well > - when i sublcass without trait i get the test from linked list test > but not the trait ones, i guess this is an expected behavior > - when i subclass without trait then reimplement some of the test, i > only got the those test exexuted, not the one from super. > > how do you deal with such situation? check if the superclass is abstract when a test case class implement isAbstract ^ self name = #name of the class then your tests on the class are not executed but they are in the subclasses. stef > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 13, 2009

[Pharo-project] various issue related to test

by Hilaire Fernandes

i am writting double link list and co, then a few test. i found it will be neat to reuse the linked list test. this one is trait based. I found the following issue preventing reussability: - when i subclass linked list test with trait, i get the trait test but not the test from linked list test, i expected to get these ones as well - when i sublcass without trait i get the test from linked list test but not the trait ones, i guess this is an expected behavior - when i subclass without trait then reimplement some of the test, i only got the those test exexuted, not the one from super. how do you deal with such situation? -- http://blog.ofset.org/hilaire

Jan. 13, 2009

[Pharo-project] funy OB debugger

by Hilaire Fernandes

In last pharo core, updated, and installation of the pharo dev package. the debugger always point to the next line in the stack, not the current one. Hilaire -- http://blog.ofset.org/hilaire

Jan. 13, 2009

Re: [Pharo-project] Breakpoints (was [OT] Great job guys)

by Igor Stasenko

2009/1/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > I have to check your trick because it seems to be a nice example of > meta prog for a chapter I'm have in mind. > btw, i started to write some UI, using OB tools. A simple window with a list of breakpoints, and some functionality, like remove/disable/enable breakpoint(s) later it could be extended with 'add condition' or 'set pass count' and other stuff. Not sure how to extend a menu for a method definition in OB. If someone could give me a hint, i will add a 'break on entry' item(s). Or even a submenu with different ways to set up a break, and open a breakpoints manager. > stef > On Jan 13, 2009, at 3:51 PM, Igor Stasenko wrote: > >> 2009/1/13 Marcus Denker <denker(a)iam.unibe.ch>: >>> >>> On 09.01.2009, at 16:19, StÃ©phane Ducasse wrote: >>> >>>> one of the point about breakpoint is that they should not get the >>>> method dirty. >>>> I know that some breakpoint code has been harvested but I do not >>>> remember how >>>> to use it. >>>> >>> >>> >>> There is a very simple breakpoint mechanism in Pharo (in Squeak, too, >>> but >>> it was a bit broken there). >>> >>> To try: There is a "toggle break on entry" item in the menu of >>> methods >>> in the >>> old browser. >>> >>> Technically, this just recompiles the method with a call to #break at >>> the beginning. >>> >> >> is it better than doing a trick with method dictionary, as i showed >> in example? >> >>> Could be improved a lot. >>> >> >>> Marcus >>> >>> >>> >>>> Stef >>>> >>>> On Jan 9, 2009, at 10:27 AM, Janko MivÅ¡ek wrote: >>>> >>>>> Dale Henrichs wrote: >>>>>> ----- "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> wrote: >>>>>> >>>>>> | And when you are already doing that, introduce also breakpoints >>>>>> back in >>>>>> | Pharo as they are on GLASS GemTools. Very intuitive and the same >>>>>> as on >>>>>> | most other Smalltalks. If they can be supported in GemTools, why >>>>>> | aren't yet in Pharo? Any technical reason? >>>>>> >>>>>> Breakpoints in GLASS/GemTools are taking advantage of the >>>>>> breakpoint feature in the GemStone/S VM. Remember, Squeak/Pharo >>>>>> are >>>>>> used as an OmniBrowser client for GLASS -- the debugger is running >>>>>> in a GemStone vm and the UI is running in the Squeak/Pharo vm. >>>>> >>>>> What I like about breakpoints in GemTools is the simplicity from >>>>> usability standpoint. And similarity of use to other Smalltaltalks. >>>>> >>>>> And because their UI part is implemented in OmniBrowser on >>>>> GemTools, >>>>> they should be easily ported back to Pharo OmniBrowser, even that >>>>> breakpoints in GS/S are implemented differently than in Squeak. >>>>> >>>>> In other words, let we port the UI for breakpoints first, on top of >>>>> whatever Squeak supports for breakpoints currently. Later >>>>> breakpoints >>>>> can be enhanced on VM level as well. >>>>> >>>>> Janko >>>>> >>>>> -- >>>>> Janko MivÅ¡ek >>>>> AIDA/Web >>>>> Smalltalk Web Application Server >>>>> http://www.aidaweb.si >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Jan. 13, 2009

Re: [Pharo-project] Breakpoints (was [OT] Great job guys)

by StÃ©phane Ducasse

I have to check your trick because it seems to be a nice example of meta prog for a chapter I'm have in mind. stef On Jan 13, 2009, at 3:51 PM, Igor Stasenko wrote: > 2009/1/13 Marcus Denker <denker(a)iam.unibe.ch>: >> >> On 09.01.2009, at 16:19, StÃ©phane Ducasse wrote: >> >>> one of the point about breakpoint is that they should not get the >>> method dirty. >>> I know that some breakpoint code has been harvested but I do not >>> remember how >>> to use it. >>> >> >> >> There is a very simple breakpoint mechanism in Pharo (in Squeak, too, >> but >> it was a bit broken there). >> >> To try: There is a "toggle break on entry" item in the menu of >> methods >> in the >> old browser. >> >> Technically, this just recompiles the method with a call to #break at >> the beginning. >> > > is it better than doing a trick with method dictionary, as i showed > in example? > >> Could be improved a lot. >> > >> Marcus >> >> >> >>> Stef >>> >>> On Jan 9, 2009, at 10:27 AM, Janko MivÅ¡ek wrote: >>> >>>> Dale Henrichs wrote: >>>>> ----- "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> wrote: >>>>> >>>>> | And when you are already doing that, introduce also breakpoints >>>>> back in >>>>> | Pharo as they are on GLASS GemTools. Very intuitive and the same >>>>> as on >>>>> | most other Smalltalks. If they can be supported in GemTools, why >>>>> | aren't yet in Pharo? Any technical reason? >>>>> >>>>> Breakpoints in GLASS/GemTools are taking advantage of the >>>>> breakpoint feature in the GemStone/S VM. Remember, Squeak/Pharo >>>>> are >>>>> used as an OmniBrowser client for GLASS -- the debugger is running >>>>> in a GemStone vm and the UI is running in the Squeak/Pharo vm. >>>> >>>> What I like about breakpoints in GemTools is the simplicity from >>>> usability standpoint. And similarity of use to other Smalltaltalks. >>>> >>>> And because their UI part is implemented in OmniBrowser on >>>> GemTools, >>>> they should be easily ported back to Pharo OmniBrowser, even that >>>> breakpoints in GS/S are implemented differently than in Squeak. >>>> >>>> In other words, let we port the UI for breakpoints first, on top of >>>> whatever Squeak supports for breakpoints currently. Later >>>> breakpoints >>>> can be enhanced on VM level as well. >>>> >>>> Janko >>>> >>>> -- >>>> Janko MivÅ¡ek >>>> AIDA/Web >>>> Smalltalk Web Application Server >>>> http://www.aidaweb.si >>>> >>>> _______________________________________________ >>>> 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 >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 13, 2009

Re: [Pharo-project] [ANN] 10205

by StÃ©phane Ducasse

On Jan 13, 2009, at 3:32 PM, Michael Rueger wrote: > StÃ©phane Ducasse wrote: > >> Next >> - category as packages collections level two >> - mike network refactoring (I hope it loads). > > One problem with the network refactoring is that it moves classes > between packages and thus needs to be loaded from a configuration map. > > I tried loadTogether:merge: but that still ends up with classes > missing > in the image. argh! > Suggestions on how to do this? I could port some of the ReleaseBuilder > code that allows to script loading of configuration maps. I would love to get some knowledge on configuration maps. So if you could it would be great. > Michael > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 13, 2009

Re: [Pharo-project] Breakpoints (was [OT] Great job guys)

by Igor Stasenko

2009/1/13 Marcus Denker <denker(a)iam.unibe.ch>: > > On 09.01.2009, at 16:19, StÃ©phane Ducasse wrote: > >> one of the point about breakpoint is that they should not get the >> method dirty. >> I know that some breakpoint code has been harvested but I do not >> remember how >> to use it. >> > > > There is a very simple breakpoint mechanism in Pharo (in Squeak, too, > but > it was a bit broken there). > > To try: There is a "toggle break on entry" item in the menu of methods > in the > old browser. > > Technically, this just recompiles the method with a call to #break at > the beginning. > is it better than doing a trick with method dictionary, as i showed in example? > Could be improved a lot. > > Marcus > > > >> Stef >> >> On Jan 9, 2009, at 10:27 AM, Janko MivÅ¡ek wrote: >> >>> Dale Henrichs wrote: >>>> ----- "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> wrote: >>>> >>>> | And when you are already doing that, introduce also breakpoints >>>> back in >>>> | Pharo as they are on GLASS GemTools. Very intuitive and the same >>>> as on >>>> | most other Smalltalks. If they can be supported in GemTools, why >>>> | aren't yet in Pharo? Any technical reason? >>>> >>>> Breakpoints in GLASS/GemTools are taking advantage of the >>>> breakpoint feature in the GemStone/S VM. Remember, Squeak/Pharo are >>>> used as an OmniBrowser client for GLASS -- the debugger is running >>>> in a GemStone vm and the UI is running in the Squeak/Pharo vm. >>> >>> What I like about breakpoints in GemTools is the simplicity from >>> usability standpoint. And similarity of use to other Smalltaltalks. >>> >>> And because their UI part is implemented in OmniBrowser on GemTools, >>> they should be easily ported back to Pharo OmniBrowser, even that >>> breakpoints in GS/S are implemented differently than in Squeak. >>> >>> In other words, let we port the UI for breakpoints first, on top of >>> whatever Squeak supports for breakpoints currently. Later breakpoints >>> can be enhanced on VM level as well. >>> >>> Janko >>> >>> -- >>> Janko MivÅ¡ek >>> AIDA/Web >>> Smalltalk Web Application Server >>> http://www.aidaweb.si >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Jan. 13, 2009

Re: [Pharo-project] [ANN] 10205

by Michael Rueger

StÃ©phane Ducasse wrote: > Next > - category as packages collections level two > - mike network refactoring (I hope it loads). One problem with the network refactoring is that it moves classes between packages and thus needs to be loaded from a configuration map. I tried loadTogether:merge: but that still ends up with classes missing in the image. Suggestions on how to do this? I could port some of the ReleaseBuilder code that allows to script loading of configuration maps. Michael

Jan. 13, 2009

[Pharo-project] [ANN][Dev-Images] January 2000 versions

by Damien Cassou

Hi, I've just uploaded new dev and web images based on Squeak3.9.1-7075, Squeak3.10.2-7179 and Pharo0.1-10158. More information and download: http://damiencassou.seasidehosting.st/Smalltalk/squeak-dev Pharo-based images can be downloaded at: http://code.google.com/p/pharo/wiki/Downloads?tm=2 Download statistics at http://damiencassou.dabbledb.com/publish/dev-imagesdownloads Changes in this version: --------------------------- - Pharo images are based on version 10205 - eCompletion has been improved by Lukas Renggli - now looks better - uses the user prefered browser instead of a fixed one - makes the method source view much faster (this one has been done by Ramon Leon) - Installer has also been updated (sorry for not having kept track of the changes) - OmniBrowser has also seen a lot of bug fixes, improvements and newly designed icons (David RÃ¶thlisberger) - Polymorph (formerly known as UIEnhancements) has been updated (Gary Chambers) - OB-Tools has seen a major upgrade thanks to Dale Henrichs (only available in Pharo) - make selections in debugger inspector panels 'sticky' across context selection changes - Add a choice request before opening the debugger (debug, proceed, or abandon) - now you can inspect or print expressions in the debugger window depending on the current context - provide an OB-based predebug window - change order of the buttons so that they match the old order Contained packages: ------------------------ This image contains the following packages (some packages are only in the squeak-web image or 3.10-based images): Aida version 5.6 Algernon version 1.2 AST version 160 AutomaticMethodCategorizer version 0.25 AutomaticMethodCategorizerOB version 0.2 DynamicBindings version 2.7 eCompletion version 0.102 eCompletion-Traits version 0.1 eCompletionOmniBrowser version 0.5 Installer version 4.3.280 KomHttpServer version 7.0.30 KomServices version 1.12 Magritte-Model version 1.0.17.331 Magritte-Seaside version 1.0.17.278 Magritte-Tests version 1.0.17.148 OB-Enhancements version 0.284 OmniBrowser version 0.434 OmniBrowser-Algernon version 0.5 OmniBrowser-Full version 0.27 OmniBrowser-Morphic version 0.68 OmniBrowser-Refactory version 113 OmniBrowser-Regex version 0.9.1 OmniBrowser-Standard version 0.384 Pier version currentnew Pier-Blog version 1.0.17.90 Pier-Documents version 1.0.17.7 Pier-EditorEnh version 1.0.17.16 Pier-Model version 1.0.17.238 Pier-Seaside version 1.0.17.311 Pier-Security version 1.0.17.113 Pier-Tests version 1.0.17.104 Polymorph EventEnhancements version 1.1 Polymorph Geometry version 1.0 Polymorph TaskbarIcons version 1.0 Polymorph ToolBuilder version 1.1 Polymorph Tools Diff version 1.1 Polymorph Widgets version 1.1 Refactoring Core version 11 RoelTyper version 0.60 RSRSS2 version 2.8.3.11 Scriptaculous version 2.8.3.242 ScriptManager version 0.6 Seaside version 2.8.3.572 Seaside-Adapters-Core version pmm.2.mcz Seaside-Adapters-Swazoo version 9 Seaside-Squeak-Adapters version pmm.3.mcz SeasideAdaptersCompatibility version pmm.1.mcz Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.4 SmaCC runtime version 13 Sport version 2.31 Squeak dev packages version 0.27 Squeak dev packages beta version 0.32 Squeak web packages version 0.2 SUnit-improved version 4.0.118 SUnitGUI-improved version 4.0.50 Swazoo version 2.1 Universes version 50 Universes OmniBrowser version 0.38 VBRegex version 1.9 YAXO version 9 Updating the image: ------------------------- You are not obliged to download a new image if you don't want. You can always update your image. To upgrade your already existing squeak-dev image: 1) World menu->open...->Package Universe Browser 2) Update list from network 3) Select all upgrades 4) Install selection 5) Execute: 'DEVImageCreator default install' (all windows will be closed) Prepared packages: -------------------------- There are a lot of packages prepared for you in this image. They are not loaded in the image, but they can be easily. - Open Package Universe Browser (world->open...->Package Universe Browser). - Click on "Update list from network" - Wait a few seconds - Select your packages - Install them -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 13, 2009