- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Schwab,Wilhelm K

Lukas, Clearly you have tried Cog for making images :) How much faster is it? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] Sent: Saturday, September 18, 2010 2:32 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 No the images are built exactly the same way as before. I am looking forward being able to use Cog to build images in the future. Loading Monticello packages is considerably faster with the new VM. For now I don't use the Cog VM on the build server, also because I cannot do coverage analysis with it. Lukas On 18 September 2010 20:20, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Lukas, > > That's great, and I thought I had read that. But something else you wrote made me doubt that; I must have confused a comment on the speed of the one-clicks at runtime as a statement that they built quickly thanks to Cog (which would make them Cog images). > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] > Sent: Saturday, September 18, 2010 2:07 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 > >> Right, and thanks, but the question is whether or not we have switched over to Cog? Lukas mentioned the one-click images built quickly. Compared to what? Are their non-Cog versions of these images? > > None of the images are Cog images, this is just that the one-click > distributions include the Cog VM. The images can be opened with both > VMs until you save it with a Cog VM for the first time. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > 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 > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2010

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Lukas Renggli

No the images are built exactly the same way as before. I am looking forward being able to use Cog to build images in the future. Loading Monticello packages is considerably faster with the new VM. For now I don't use the Cog VM on the build server, also because I cannot do coverage analysis with it. Lukas On 18 September 2010 20:20, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Lukas, > > That's great, and I thought I had read that. Â But something else you wrote made me doubt that; I must have confused a comment on the speed of the one-clicks at runtime as a statement that they built quickly thanks to Cog (which would make them Cog images). > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] > Sent: Saturday, September 18, 2010 2:07 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 > >> Right, and thanks, but the question is whether or not we have switched over to Cog? Â Lukas mentioned the one-click images built quickly. Â Compared to what? Â Are their non-Cog versions of these images? > > None of the images are Cog images, this is just that the one-click > distributions include the Cog VM. The images can be opened with both > VMs until you save it with a Cog VM for the first time. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > 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 > -- Lukas Renggli www.lukas-renggli.ch

Sept. 18, 2010

Re: [Pharo-project] MethodName is now Finder

by StÃ©phane Ducasse

thanks benjamin we will have a look. This was a cool feeling to see you coding all evenings :) On Sep 18, 2010, at 6:45 PM, Benjamin Van Ryseghem wrote: > Hello everyone ^^ > > After a week in ESUG and thanks to Alain and Tobias, I've improved the Finder tool :) > > To test it, you have to download : > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'NullTextStyler'; > load > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'DialogItemsChooser'; > load > > and the last but not the least : > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'Finder'; > load > > It works only on Pharo 1.2 and you will probably have an error due to an issue about PluggableTextMorph : http://code.google.com/p/pharo/issues/detail?id=2973 > > To open it, just click World >> Tools >> Finder > > > Ben > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2010

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Schwab,Wilhelm K

Lukas, That's great, and I thought I had read that. But something else you wrote made me doubt that; I must have confused a comment on the speed of the one-clicks at runtime as a statement that they built quickly thanks to Cog (which would make them Cog images). Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] Sent: Saturday, September 18, 2010 2:07 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 > Right, and thanks, but the question is whether or not we have switched over to Cog? Lukas mentioned the one-click images built quickly. Compared to what? Are their non-Cog versions of these images? None of the images are Cog images, this is just that the one-click distributions include the Cog VM. The images can be opened with both VMs until you save it with a Cog VM for the first time. Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2010

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Lukas Renggli

> Right, and thanks, but the question is whether or not we have switched over to Cog? Â Lukas mentioned the one-click images built quickly. Â Compared to what? Â Are their non-Cog versions of these images? None of the images are Cog images, this is just that the one-click distributions include the Cog VM. The images can be opened with both VMs until you save it with a Cog VM for the first time. Lukas -- Lukas Renggli www.lukas-renggli.ch

Sept. 18, 2010

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Schwab,Wilhelm K

Right, and thanks, but the question is whether or not we have switched over to Cog? Lukas mentioned the one-click images built quickly. Compared to what? Are their non-Cog versions of these images? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sven Van Caekenberghe [sven(a)beta9.be] Sent: Saturday, September 18, 2010 12:43 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 On 18 Sep 2010, at 18:28, Schwab,Wilhelm K wrote: > I don't quite get the Hudson web interface yet. Pharo seemed like the place to go, but maybe it's the core? Then downstream of that are Development and others - that looks like it - hidden right under my nose :) But now I arguably have the problem of seeing only a one-click for Pharo dev and Seaside. Are they Cog-only images? Goto http://hudson.lukas-renggli.ch/job/Development/ or http://hudson.lukas-renggli.ch/job/Seaside%203.0/ and download the xxx-OneClick.zip artifact. Sven _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2010

[Pharo-project] MethodName is now Finder

by Benjamin Van Ryseghem

Hello everyone ^^ After a week in ESUG and thanks to Alain and Tobias, I've improved the Finder tool :) To test it, you have to download : Gofer new squeaksource: 'PharoTaskForces'; package: 'NullTextStyler'; load Gofer new squeaksource: 'PharoTaskForces'; package: 'DialogItemsChooser'; load and the last but not the least : Gofer new squeaksource: 'PharoTaskForces'; package: 'Finder'; load It works only on Pharo 1.2 and you will probably have an error due to an issue about PluggableTextMorph : http://code.google.com/p/pharo/issues/detail?id=2973 To open it, just click World >> Tools >> Finder Ben

Sept. 18, 2010

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Sven Van Caekenberghe

On 18 Sep 2010, at 18:28, Schwab,Wilhelm K wrote: > I don't quite get the Hudson web interface yet. Pharo seemed like the place to go, but maybe it's the core? Then downstream of that are Development and others - that looks like it - hidden right under my nose :) But now I arguably have the problem of seeing only a one-click for Pharo dev and Seaside. Are they Cog-only images? Goto http://hudson.lukas-renggli.ch/job/Development/ or http://hudson.lukas-renggli.ch/job/Seaside%203.0/ and download the xxx-OneClick.zip artifact. Sven

Sept. 18, 2010

Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1

by Schwab,Wilhelm K

Lukas, I don't quite get the Hudson web interface yet. Pharo seemed like the place to go, but maybe it's the core? Then downstream of that are Development and others - that looks like it - hidden right under my nose :) But now I arguably have the problem of seeing only a one-click for Pharo dev and Seaside. Are they Cog-only images? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] Sent: Saturday, September 18, 2010 12:05 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 > http://hudson.lukas-renggli.ch/ All the one-click distributions include the cog VM for Linux, Windows, and Mac. I don't know if other Hudson servers have been updated and rebuilt yet. I prepared the updated code during ESUG and it is on github. Lukas > > Your Hudson server shows a recent build (no Shout, core maybe?), but I am curious about the effects of Cog, and I don't see (or don't know where to look for) it. > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] > Sent: Saturday, September 18, 2010 10:19 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [ANN 1.1] Pre-built core 1.1.1 > > Ok, all images have been successfully rebuilt. > > The only thing I noticed (apart from the massive speedup in the > one-click images) is that the 'Test Coverage' button in the test > runner is not disabled. I thought that Mariano fixed that? > > Lukas > > On 18 September 2010 10:09, Lukas Renggli <renggli(a)gmail.com> wrote: >> I am already re-building everything on Hudson with this image. >> Hopefully things go well. One-click images will use Cog. >> >> Lukas >> >> On 18 September 2010 09:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> On Sep 18, 2010, at 9:34 AM, Sven Van Caekenberghe wrote: >>> >>>> >>>> On 12 Sep 2010, at 12:02, Marcus Denker wrote: >>>> >>>>> https://gforge.inria.fr/frs/download.php/27479/PharoCore-1.1.1.zip >>>> >>>> The images inside are 11414 but the filenames say otherwise: >>>> >>> Uhh.... I will redo it. >>> >>> There are two other fixes I missed, too. >>> >>>> >>>> Will the official 'stable' link move to this one too (or did it already) ? >>>> >>> >>> No, this will be done as soon as we have a full image, too. >>> >>> Marcus >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > 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 > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2010

Re: [Pharo-project] [squeak-dev] Morphic

by StÃ©phane Ducasse

we cleaned a lot already but juan where would you start to clean (which kind of features for example)? On Sep 17, 2010, at 11:58 PM, Juan Vuletich wrote: > DeNigris Sean wrote: >> I was doing a lot of playing with Morphic this week at ESUG in Barcelona. Many people seem to really not like it and complain about it, but it seems very vague i.e. they can't point to a specific problem with it. >> >> I think it's amazingly powerful and universally misunderstood. > > I agree. > >> Many people are pushing for native widgets for end users, which I think is awesome, but serves a different role. For me, there are two use cases: >> 1. People (mostly Smalltalkers, including myself) interested in the UI's of the future and exploring what's possible >> 2. People who love their (e.g. Mac) look and feel or are in a setting (e.g. enterprise) where they have to use a particular GUI. >> >> Morphic seems ideal for group #1. I think the key questions are: >> * if you were implementing Morphic today, knowing what you know after it being used over the years, how would you do it? >> > > I _am_ implementing Morphic today. In fact I'm doing it twice at the same time: > - Morphic in Cuis ( www.jvuletich.org/Cuis/Index.html ) is much simpler and smaller than in Squeak, although the basic ideas are the same. > - Morphic 3 ( http://www.jvuletich.org/Morphic3/Index.html and http://www.jvuletich.org/Morphic3/Morphic3-201006.html ) is a deep redesign. The main ideas are to make it a ZUI, independent of pixel resolution, and use new, higher quality techniques for rendering. > >> * what would it take (if possible) to get there from the current implementation? >> > > The path I'm walking is: Phase 1 - Remove all non-essential stuff, simplify as much as possible. Phase 2 - Redesign from there. Morphic in Cuis is phase 1. Morphic 3 is phase 2. > >> Two issues I've noticed: >> 1. there seems to be an explosion of classes with slightly different behavior e.g. TextMorph, TextMorphForShout, PluggableTextMorph, PluggableShoutMorph. >> 2. I'm not clear whether the hooks for modifying behavior are >> a. available in all the right places >> b. working >> c. widely understood >> >> I'm forming an informal panel to discuss this. I've reached out to Morphic's creators and some original users. >> > > I'd like to be part of that. Are you setting up a mail list? > >> A quick example of my (seemingly common) experience: >> For example, I'm writing an implementorsOf browser that shows the execution path as a graph of MethodMorphs connected by LineMorphs, because the standard paned browser does not capture the metaphor of drilling down through implementors. So I Created a MethodMorph and added as a submorph a PluggableShoutMorph to hold the code. At that point, I couldn't figure out a good/easy way to react to mouse events and pop out a new MethodMorph. >> >> I tried (one of these felt very satisfying): >> * Morph>>on:send:to:, which sounded good, but never got called >> * intercepting Morph>>processEvent:using: (which I was told was not a good idea) >> * (after seeking help), locking the submorphs and overriding the dozen or so event-related methods in the chain from my morph to TextMorphForShout (the Morph that actually handles the text and input). >> * subclassing TextMorphForShout and then subclassing PluggableShoutMorph to use that subclass. >> >> Sean > > Your morph should answer true to #handlesMouseDown: and implement #mouseDown:. Same for mouseUp, mouseMove, etc. There are many examples of this in the image already. > > You'd really try Cuis. You'll find it much easier to understand and extend. > > Cheers, > Juan Vuletich >

Sept. 18, 2010