- Pharo-dev - lists.pharo.org

Missing documentation for Pharo Launcher on UBUNTU

by kilon alios

I am following the documentation here http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher and it sends me also there http://www.pharo-project.org/pharo-download/ubuntu then it says "Just launch the Pharo launcher image using the platform-specific VM." but there is no information how to do that. There is also no information about where Pharo Launcher installs and what files it installs. Not good :(

April 8, 2014

[Pharo3] Issue tracker status

by Marcus Denker

âMust fixâ and higher: 20 Issues, 5 of those have fixes that need reviews https://pharo.fogbugz.com/f/filters/64/3-0-TODO (this list should be empty before we release) There are overall 87 issues tagged for Pharo3: https://pharo.fogbugz.com/f/filters/99/3-0-All (We should check and un-tag all those that we want to postponeâ¦) Overall, there are 642 open issues: https://pharo.fogbugz.com/f/filters/62/All-priority We closed 2321 for Pharo3 alone. Marcus

April 8, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30815 Home: https://github.com/pharo-project/pharo-core

April 8, 2014

[pharo-project/pharo-core] fe970b: 30815

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: fe970b60a9f5801452165ad90839e7c9dc03a4f8 https://github.com/pharo-project/pharo-core/commit/fe970b60a9f5801452165ad9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-04-08 (Tue, 08 Apr 2014) Changed paths: M MonticelloFileTree-Core.package/extension/MCFileRepositoryInspector/instance/refresh.st M MonticelloGUI.package/MCFileRepositoryInspector.class/definition.st A MonticelloGUI.package/MCFileRepositoryInspector.class/instance/accessing/packageList.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/initialization/initialize.st R MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageHighlight_.st A MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageHighlight_loadedPackages_.st R MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageList.st A MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageListUpdate.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageSearchAccept_.st A Morphic-Base.package/MenuMorph.class/instance/control/deselectAndFocusOutermenuOn_.st M Morphic-Base.package/MenuMorph.class/instance/events/keyStroke_.st M Nautilus.package/AbstractNautilusUI.class/instance/private/buildPackageHierarchyFor_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script468.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30815.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Shout.package/SHParserST80.class/instance/parse support/parsingBlockarguments.st M Shout.package/SHParserST80.class/instance/scan/scanBinary.st Log Message: ----------- 30815 13080 Shout does not recognize doubled vertical bar || as a binary selector https://pharo.fogbugz.com/f/cases/13080 12178 Extended class shown twice in Browser. https://pharo.fogbugz.com/f/cases/12178 13007 Cannot integrate a slice with monticello (red square in the UI) https://pharo.fogbugz.com/f/cases/13007 13108 MNU in class menu https://pharo.fogbugz.com/f/cases/13108 http://files.pharo.org/image/30/30815.zip

April 8, 2014

Re: [Pharo-dev] Fast render of a bitmap in Athens?

by Igor Stasenko

On 7 April 2014 19:42, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 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? > > yes, converting from form to paint is slow, because it copies contents (form's bits) into new cairo surface. to speed things up , cache the result: athensCanvas pathTransform restoreAfter: [ paint := ( canvas cacheAt: self form ifAbsetPut: [ (self form asAthensPaintOn: canvas) ]). athensCanvas setPaint: paint. (and before saying draw, you have to set shape first, isn't?) athensCanvas setShape: .... athensCanvas draw ] > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Best regards, Igor Stasenko.

April 8, 2014

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

by Ben Coman

April 8, 2014

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