April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] MC diffs are seriously broken in Pharo2.0

by Nicolas Cellier

Esteban, you probably have a recent computer, not an old Core2duo like me... What diffing Monticello from latest Pharo3.0 with latest Squeak trunk costs attached. For VMMaker it's worse. It's matter of seconds for displaying the old diff tool... 2014-04-07 17:19 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > 2014-04-07 13:28 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, >> >> Sorry but I do not have *any* of this problems (and I use same things as >> you all the time for the vm stuff). >> I wonder what happened to you to get this kind of behaviour. >> Can I have your image to test it? >> >> Esteban >> >> ps: afaik, vmmaker was loading in 3.0 with some fixes, but there is still >> not configuration released for it. >> >> > Hi Esteban, > The most probable explanation is that you are so used to these failures > that you adopted a circumvention strategy, consciously or not. > You must consider me as a newbie, and as a newbie I step where the > experimented user has learned not to... > > Try > https://pharo.fogbugz.com/f/cases/13181/MCVersion-should-NEVER-cache-a-snap… tell me if this is reproducible for you or not. > > >> On 06 Apr 2014, at 12:36, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> > I'm trying to fix some Pharo VM issues (11330), but have awfully bad >> experience with Pharo2.0 tools. >> > >> > The autocompletion stuff is a joke, it moves the input cursor randomly >> and spoils my input. That's the first thing I disable. >> > >> > The pharo's PolyMorphDiffTool is good looking but awfully sloooow >> > It clearly does not scale (10 minutes or so to diff Eliot's branch) so >> I reverted to the old diff tool. >> > But of course, someone broke MCMethodDefinition>>summary >> (gratuitously?) and I had to revert this method to have class names >> displayed again. >> > >> > But worse than all, there are insane caches operating in MCVersion that >> drove me crazy. >> > Here is the scenario: >> > 1) I diff working copy against package.branchA-version.mcz >> > 2) I cherry pick and install a few methods >> > 3) I diff against package.branchA-version.mcz again to check if I >> missed smthing >> > 4) Huh? it looks like my cherry pick have not been installed??? >> > Yes they were installed, but the completePackageSnapshot has been >> cached in MCVersion!!! >> > What a mistake! The working copy is going to evolve, caching a snapshot >> of it is a DUMB thing.It means that methods that I further change in the >> working copy will NEVER be taken into account next time I'll do a diff. >> > So I had to change MCVersion>>changes >> > ^ self completeSnapshot patchRelativeToBase: self >> loadCompletePackageSnapshot >> > >> > This is so broken that I have to report here. >> > Note that I did not check if symptoms are still in Pharo 3.0, but the >> working copy scnapshot cache still is for sure! >> > >> > Guys, it makes me wonder, who is eating the dog food? >> > Did anyone progress into developing VM in Pharo 3.0, because if I must >> eat it, I'd prefer the freshest ;) >> > Or if I fix some more bug, I'd like my efforts to not apply to an >> obsolete version. >> >> >> >

April 7, 2014

Re: [Pharo-dev] ghost windows

by Carlo

Hi Try holding down shift and then right click on the world (or in a workspace execute: âWorld findWindow: nil.â). A âfind windowâ pop-up should appear. Look through the PanelMorphs by selecting each one and the haloâs should appear. If you find the correct one then delete it and it should be removed. Tested in Pharo1.3 and Pharo3 and works for me. Cheers Carlo On 07 Apr 2014, at 2:28 PM, Ben Coman <btc(a)openInWorld.com> wrote: I has this happen to me quite a while ago. http://forum.world.st/old-windows-in-image-not-responding-td3922341.html As well as the suggestion there, you might also try... SystemWindows allInstances [ :w | w delete ]. cheers -ben Johan Brichau wrote: > > Hi there, > > I often get in a situation where 'ghost windows' remain in the Pharo window (see screenshot). > These windows are closed (see taskbar) and I cannot select nor click these ghost windows to remove them. > > Is there a way to remove them programmatically? > They cause visual clutter when working with multiple real windows and I do not want to rebuild an entire development image each time this occurs. > > Though this is in Pharo3, I think I occassionally had these in Pharo1.4 as well. > > cheers > Johan > >

April 7, 2014

Re: [Pharo-dev] Hierarchy view in Nautilus

by Sebastian Sastre

glad to hear this On Apr 6, 2014, at 6:18 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 2014-04-06 10:46 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 06 Apr 2014, at 02:39, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > Hi! > > > > Selecting a class in a hierarchy view in Nautilus switches back to the Flat new. > > Is this really something we want? > > No, seems like a serious recent regression ! > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > Its already reported > 13171 When browsing a hierarchy, Nautilus changes the view unexpectedly > and this is the cause of this regression: > 13099 nautilus is not refreshing package tree panel on certain operations > > > nicolai

April 7, 2014

Re: [Pharo-dev] Case 13007 Cannot-integrate-a-slice-with-monticello-red-square-in-the-UI

by Pharo4Stef

Hi I did not check the latest submission but to me putting a mutex on list looks like a bad decision. May be the original forking of the project list is the problem. What is the point of view of the people that work on the issue. Forking to get speed is often a way to pay high price after. Synchronisation points are important. Stef On 07 Apr 2014, at 18:36, Ben Coman <btc(a)openInWorld.com> wrote: > Priority 2 fix ready for review. Please come pick it apart. > https://pharo.fogbugz.com/f/cases/13007/Cannot-integrate-a-slice-with-monti… > cheers -ben >

April 7, 2014

Re: [Pharo-dev] [Vm-dev] Pharo VM bug 11130

by Pharo4Stef

> > > > Yes, I did: > https://pharo.fogbugz.com/f/cases/13180/Class-class-superclassOrder-should-… > > Of course, those kind of expectations should be asserted by a test (I didn't). TX! > >> >> After fixing it, compilation went well... >> >> >> >> 2014-04-03 4:13 GMT+02:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> >> >> >> >> 2014-04-02 23:59 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: >> >> >> Nicolas wrote: >> >Hmm, don't waste too much time. >> >All these methods are unchanged in github pharo-vm head revision (VMMaker-oscog-StefanMarr.313) >> >The cause must be completely different in latest pharo vms. >> >> Uhm, why? They havenât changed. >> >> Sorry, haven't changed means that there's no diff with the corrected version. >> IOW, the fixes from Eliot have been integrated for a long time already. >> You are seeing another symptom, probably another bug impacting the same code. >> There are many diffs between pharo's and Eliot's branch, but not where you're looking at. >> >> Pharo vms 105 and later no longer crash, but all reliably show the bug. >> And 236 is the last Squeak one to show the problem. >> >> I might take a look at Estebanâs versions from the same time, >> 228 and 229 >> >> Stephan

April 7, 2014

Fast render of a bitmap in Athens?

by Alexandre Bergel

Hi! How can a form be quickly displayed in a surface? Is it correct to do? athensCanvas pathTransform restoreAfter: [ athensCanvas setPaint: self form. athensCanvas draw ] Apparently, the root is AthensCairoSurface>>#fromForm: is really slow. How to have a fast bitmap rendering in Athens? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 7, 2014

Re: [Pharo-dev] [Inspiration] Toward a better programming

by Alexandre Bergel

> Now this is clear that Roassal is a bit reinventing Morphic to some extend but this is like that. Indeed, Roassal offers facilities that clearly looks like the ones of Morphic. However, Roassal is not meant to build GUI (for now). The primary uses of Roassal is visualizing data. And yes, you can made a small UI to drive a visualization, and the UI is best done in Roassal directly than in Morphic. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 7, 2014

Case 13007 Cannot-integrate-a-slice-with-monticello-red-square-in-the-UI

by Ben Coman

Priority 2 fix ready for review. Please come pick it apart. https://pharo.fogbugz.com/f/cases/13007/Cannot-integrate-a-slice-with-monti… cheers -ben

April 7, 2014

Re: [Pharo-dev] MC diffs are seriously broken in Pharo2.0

by Nicolas Cellier

2014-04-07 13:28 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Sorry but I do not have *any* of this problems (and I use same things as > you all the time for the vm stuff). > I wonder what happened to you to get this kind of behaviour. > Can I have your image to test it? > > Esteban > > ps: afaik, vmmaker was loading in 3.0 with some fixes, but there is still > not configuration released for it. > > Hi Esteban, The most probable explanation is that you are so used to these failures that you adopted a circumvention strategy, consciously or not. You must consider me as a newbie, and as a newbie I step where the experimented user has learned not to... Try https://pharo.fogbugz.com/f/cases/13181/MCVersion-should-NEVER-cache-a-snap… tell me if this is reproducible for you or not. > On 06 Apr 2014, at 12:36, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > I'm trying to fix some Pharo VM issues (11330), but have awfully bad > experience with Pharo2.0 tools. > > > > The autocompletion stuff is a joke, it moves the input cursor randomly > and spoils my input. That's the first thing I disable. > > > > The pharo's PolyMorphDiffTool is good looking but awfully sloooow > > It clearly does not scale (10 minutes or so to diff Eliot's branch) so I > reverted to the old diff tool. > > But of course, someone broke MCMethodDefinition>>summary (gratuitously?) > and I had to revert this method to have class names displayed again. > > > > But worse than all, there are insane caches operating in MCVersion that > drove me crazy. > > Here is the scenario: > > 1) I diff working copy against package.branchA-version.mcz > > 2) I cherry pick and install a few methods > > 3) I diff against package.branchA-version.mcz again to check if I missed > smthing > > 4) Huh? it looks like my cherry pick have not been installed??? > > Yes they were installed, but the completePackageSnapshot has been cached > in MCVersion!!! > > What a mistake! The working copy is going to evolve, caching a snapshot > of it is a DUMB thing.It means that methods that I further change in the > working copy will NEVER be taken into account next time I'll do a diff. > > So I had to change MCVersion>>changes > > ^ self completeSnapshot patchRelativeToBase: self > loadCompletePackageSnapshot > > > > This is so broken that I have to report here. > > Note that I did not check if symptoms are still in Pharo 3.0, but the > working copy scnapshot cache still is for sure! > > > > Guys, it makes me wonder, who is eating the dog food? > > Did anyone progress into developing VM in Pharo 3.0, because if I must > eat it, I'd prefer the freshest ;) > > Or if I fix some more bug, I'd like my efforts to not apply to an > obsolete version. > > >

April 7, 2014

Re: [Pharo-dev] Suggested Syntax Highlighting Features for Beginners

by GOUBIER Thierry

If we had a way to scope inside that micro-world subset, then we could simply use the scoping for that (and have syntax highlighting matching the scope of the browser showing the code). Then, once the user is deep enough, then he could be told how to reach the full scope. Or we let him find by himself, Hypercard-like :) Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de J.F. Rick [self(a)je77.com] EnvoyÃ© : lundi 7 avril 2014 16:30 Ã : Pharo Development List Objet : Re: [Pharo-dev] Suggested Syntax Highlighting Features for Beginners On Fri, Apr 4, 2014 at 8:28 PM, Pharo4Stef <pharo4Stef(a)free.fr<mailto:pharo4Stef@free.fr>> wrote: Did you also see that what I like is to make a distinction between a possible selector and a wrong one? because this is nice. Yes, that is nice. My guess is that for beginning programmers (rather than programmers new to Pharo), it might be nice to prioritize certain messages or even limit the messages to a subset initially, especially in a Microworld environment. Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

April 7, 2014