- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Version 1.39 of Versionner

by Torsten Bergmann

> > Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 > > so one can easily load via Configuration browser from within the 2.0 image. > > Excellent! > Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about. > > For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small. > > Maybe we can use as a convention a method #readme on each ConfigurationOf ? > > Alexandre I completely agree that more work is needed. I started a new config browser for 3.0 (based on Spec) as a changeset - currently I cant find the issue on this horrible new issue tracker ;) Yes - the config itself would be a good place. One problem: if you want to have a slick UI (fast moving in the list) you would have to load all the configs into the image. Or one needs an updating server job that collects all #readmes and provides a txt/xml file for the config browser client Bye T.

April 19, 2013

Re: [Pharo-project] Old bugs fixed by Opal

by Marcus Denker

On Apr 19, 2013, at 4:31 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On Apr 19, 2013, at 2:27 PM, Marcus Denker wrote: > >> >> On Apr 19, 2013, at 1:56 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> >>> On Apr 19, 2013, at 1:35 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>>>>> >>>>> >>>>> Did you use >>>>> >>>>> https://ci.inria.fr/rmod/job/Opal/ >>>>> >>>>> The Opal in the image is a bit out-datedâ¦ >>>> >>>> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic stateâ¦ >>>> Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) >>>> >>> >>> Yes, we committed some changes that might have broken thingsâ¦ >>> I will check. >>> >> Ok, found itâ¦ at least the debugger appears again after a "self halt" :-) >> >> https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip >> >> We should remember to never think it works before the regression tester is successfulâ¦ >> Clement wrote a blog post: >> http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-… >> >> Marcus >> >> > That's *really* great! > With everything properly initialized, it works smoothly! (other than having to click more than once to advance PC into the optimized to:do: blocks) > > One thing I ran into that doesn't work as I'd expect now, is UHE's when using "Through"; > > Debugging > "nil asInteger" or, "ClosureTests new testToDoOutsideTemp" (which has collection uninitialized, and exhibits the same at #add: send) > - pressing "Over" I get the expected behavior of opening MessageNotUnderstood: in the same Debugger > - pressing "Through", I get the MNU in new pre-debugger after a loooong delay on first click, then, presumably with PC erroneously incremented, an unrelated error on 2nd click, also in new pre-debugger. > Ok, we will have a look at that. Marcus

April 19, 2013

Re: [Pharo-project] Version 1.39 of Versionner

by Alexandre Bergel

>> No idea why happened. >> I copied the a missing file in the repository >> Try again, it should work now >> >> Alexandre > > Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 > so one can easily load via Configuration browser from within the 2.0 image. Excellent! Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about. For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small. Maybe we can use as a convention a method #readme on each ConfigurationOf ? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 19, 2013

Re: [Pharo-project] Fwd: [Moose-dev] Roassal new algorithms

by Frank Shearar

I've played with these before [1]. They work best with hierarchical names. In other words, in a flat namespace (say, showing class dependencies with just the class name) you end up with a very messy diagram. Let's assume you use "." as the name token separator. If you prefixed the names with their packages, say Tools-Debugger.Debugger, you'd get a better graph, where the bundles would be tighter. If you made things more hierarchical still, say with names like Tools.Debugger.Debugger, things would look even better. The deeper the naming hierarchy the fewer fat bundles you get in the image. frank [1] http://mbostock.github.io/d3/talk/20111116/bundle.html On 19 April 2013 16:37, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Let's have this discussion in the Pharo list. > > Alexandre > > Begin forwarded message: > > *From: *Alexandre Bergel <alexandre.bergel(a)me.com> > *Subject: **[Moose-dev] Re: Roassal new algorithms* > *Date: *April 19, 2013 11:25:31 AM GMT-04:00 > *To: *Moose-related development <moose-dev(a)iam.unibe.ch> > *Reply-To: *Moose-related development <moose-dev(a)iam.unibe.ch> > > There are more than simply linear, quadratic and cubic Bezier curves. In > fact, as you can have as many control points as you wish, you can have a > Bezier curve of any order. > > > Ok > > But what I was calling RadialBezierCurve was a kind of strategy, I mean I > have an abstract class which knows how to compute a curve, but I still have > to choose my control points so I was thinking to create different > subclasses whose role is to know what are their control points : > > - The radial one choose its control points within the same radius as its > source and its target. > > > Ah ok > > I wanted to create an ortoVertical and an ortoHorizontal whose control > points would have been computed differently, so that we could use Bezier > curve for regular tree too. > > > It would be cool to have hierarchical bundles edges in Roassal. > A screenshot of what it looks like: > > The technical description: > http://www.win.tue.nl/~dholten/papers/bundles_infovis.pdf > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 19, 2013

Re: [Pharo-project] Old bugs fixed by Opal

by Henrik Johansen

On Apr 19, 2013, at 2:27 PM, Marcus Denker wrote: > > On Apr 19, 2013, at 1:56 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Apr 19, 2013, at 1:35 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>>>> >>>> >>>> Did you use >>>> >>>> https://ci.inria.fr/rmod/job/Opal/ >>>> >>>> The Opal in the image is a bit out-datedâ¦ >>> >>> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic stateâ¦ >>> Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) >>> >> >> Yes, we committed some changes that might have broken thingsâ¦ >> I will check. >> > Ok, found itâ¦ at least the debugger appears again after a "self halt" :-) > > https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip > > We should remember to never think it works before the regression tester is successfulâ¦ > Clement wrote a blog post: > http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-… > > Marcus > > That's *really* great! With everything properly initialized, it works smoothly! (other than having to click more than once to advance PC into the optimized to:do: blocks) One thing I ran into that doesn't work as I'd expect now, is UHE's when using "Through"; Debugging "nil asInteger" or, "ClosureTests new testToDoOutsideTemp" (which has collection uninitialized, and exhibits the same at #add: send) - pressing "Over" I get the expected behavior of opening MessageNotUnderstood: in the same Debugger - pressing "Through", I get the MNU in new pre-debugger after a loooong delay on first click, then, presumably with PC erroneously incremented, an unrelated error on 2nd click, also in new pre-debugger. Cheers, Henry

April 19, 2013

[Pharo-project] [update 3.0] #30045

by Marcus Denker

30045 ----- 10317 files.pharo.org: change image to use new update server https://pharo.fogbugz.com/f/cases/10317 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/KernelTests-MarcusDenker.484 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/UpdateStreamer-Core-MarcusDe… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Zinc-System-Support-MarcusDe…

April 19, 2013

Re: [Pharo-project] Old bugs fixed by Opal

by stephane ducasse

>>>>> >>>> >>>> Did you use >>>> >>>> https://ci.inria.fr/rmod/job/Opal/ >>>> >>>> The Opal in the image is a bit out-datedâ¦ >>> >>> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic stateâ¦ >>> Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) >>> >> >> Yes, we committed some changes that might have broken thingsâ¦ >> I will check. >> > Ok, found itâ¦ at least the debugger appears again after a "self halt" :-) > > https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip > > We should remember to never think it works before the regression tester is successfulâ¦ > Clement wrote a blog post: > http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-… nicely written :) Thanks clement this is cool! Push we are getting there.

April 19, 2013

Re: [Pharo-project] Metacello configuration conventions

by Sean P. DeNigris

> Metacello supports both, but not at the same time. Either you mark your configuration with fixed versions (best for patches) or with symbolic versions (best for releases). I don't understand this. If you don't want your dependencies upgraded, you don't change the versions referenced in your new version, if you do, you manually change them. Either way, you make a new version, whether it's a patch, enhancement, or total overhaul. The symbolic versions, OTOH, map your versions to their status on respective platforms. You would do this for every new version. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-configuration-conventions-tp4681777p4682563… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 19, 2013

Re: [Pharo-project] Old bugs fixed by Opal

by Marcus Denker

On Apr 19, 2013, at 1:56 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 19, 2013, at 1:35 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>>> >>> >>> Did you use >>> >>> https://ci.inria.fr/rmod/job/Opal/ >>> >>> The Opal in the image is a bit out-datedâ¦ >> >> I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic stateâ¦ >> Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) >> > > Yes, we committed some changes that might have broken thingsâ¦ > I will check. > Ok, found itâ¦ at least the debugger appears again after a "self halt" :-) https://ci.inria.fr/rmod/job/Opal/lastSuccessfulBuild/artifact/Opal.zip We should remember to never think it works before the regression tester is successfulâ¦ Clement wrote a blog post: http://clementbera.wordpress.com/2013/03/22/toward-a-zero-bugs-interpreter-… Marcus

April 19, 2013

Re: [Pharo-project] Old bugs fixed by Opal

by Marcus Denker

On Apr 19, 2013, at 1:35 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> >> >> Did you use >> >> https://ci.inria.fr/rmod/job/Opal/ >> >> The Opal in the image is a bit out-datedâ¦ > > I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic stateâ¦ > Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) > Yes, we committed some changes that might have broken thingsâ¦ I will check. Marcus

April 19, 2013