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

iPad version does not work ?

by jannik laval

Hi list, Does anyone try to load Pharoon iPad ? In the past, the version 1.4 worked with XCode 4.4. I just tried to recompile it with the new XCode (5.0.2). The VM seems to work, but the pharo 1.4 image freezes. Any idea ? -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

Jan. 27, 2014

Re: [Pharo-dev] Source city

by Diego Lont

And of course I forgot to checkâ¦ new chance for a fixed configuration On Jan 27, 2014, at 2:20 PM, Diego Lont wrote: > Hi all, > > I wanted to try out source city in Moose 5.0. The current pharo version there is Pharo3.0 (Latest update: #30714), so note before loading you need to install the slice that belongs to issue 12488. So somewhere regressions occurred. > > But after installing this slice, you still have to fix the configuration. I attached a fixed configuration, as I am not allowed to put it in the right spot. If someone could upload this, I would be much obliged. > > Cheers, > Diego > <ConfigurationOfSourceCity-DiegoLont.4.mcz>

Jan. 27, 2014

Source city

by Diego Lont

Hi all, I wanted to try out source city in Moose 5.0. The current pharo version there is Pharo3.0 (Latest update: #30714), so note before loading you need to install the slice that belongs to issue 12488. So somewhere regressions occurred. But after installing this slice, you still have to fix the configuration. I attached a fixed configuration, as I am not allowed to put it in the right spot. If someone could upload this, I would be much obliged. Cheers, Diego

Jan. 27, 2014

Re: [Pharo-dev] strange error in latest 3.0 -

by Martin Dias

On Mon, Jan 27, 2014 at 7:10 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I opened an issue: > https://pharo.fogbugz.com/f/cases/12731/Traits-modifications-cause-a-DNU > > I marked it as a show stopper because right now you cannot load a package > with Traits in the image. > > I am not sure about triggering the event for subclasses, but I can > certainly understand that it can be useful for tools. However, the problem > is that we are trying to figure out isPropagation after we trigger it, > instead of doing it while triggering for a subclass. So, one possibility > would be to distinguish between ClassModified and SuperclassModified. I > tried to search in the code quickly but could not locate the exact place. I > will try again later if nobody beats me to it. > +1 I think not much people is interested in SuperclassModified. ClassModified is the more interesting one. It requires, for example, the browser to be refreshed, the package to be marked as dirty, or the change to be logged. But SuperclassModified... ?

Jan. 27, 2014

[ci server][3.0] #cleanUpForRelease done on server again

by Marcus Denker

Hi, The job https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/ now does a #cleanUpForRelease using ImageCleaner. This used to be done on update, but that is not good as when people load updates they do not want the side effects of a release clean (mostly, deleting all change set information). So I added command line support for ImageCleaner last week and now that it is in the image, I added this line to the build script: ./pharo Pharo.image clean ârelease This will be used with the next update (#724) The command might be interesting for others, here is the description from the class comment: Usage: clean [ --release ] --release do #cleanUpForRelease --production do #cleanUpForProduction Documentation: This allows to run the ImageCleaner from the commandLine. With no special option it runs Smalltalk cleanUp: true. Usage: pharo Pharo.image clean pharo Pharo.image clean --release

Jan. 27, 2014

Re: [Pharo-dev] process to collaborate on cleaning morphic

by J.F. Rick

On Sun, Jan 26, 2014 at 9:48 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > 3. possible remove the concept of mouse and keyboard focus entirely. This > is > what Self does and it seems much cleaner. There would just be mouse and > keyboard subscribers and a Morph, let's say a text editor, would "take > focus > away from itself" e.g. when there was a mouseDown outside it's bounds > Interesting. One thing to consider is support for (or non-exclusion of) soft keyboards. In a tabletop setup, you could have multiple keyboards, each with a different focus (or list of subscribers). Same thing for mouse input. There could be systems with more than one mouse or, more likely, multi-touch input. I've been using Squeak / Pharo for fairly novel devices for some time and having the flexibility to augment the events, etc. has been really useful. Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Jan. 27, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 27, 2014

[pharo-project/pharo-core] eff618: 30723

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: eff618ddf0d6217fc06c43073d32502349a75fa2 https://github.com/pharo-project/pharo-core/commit/eff618ddf0d6217fc06c4307… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-27 (Mon, 27 Jan 2014) Changed paths: M Nautilus.package/PackageTreeModel.class/instance/help-text/helpTextFor_.st M RPackage-Core.package/RPackage.class/instance/accessing/addClass_.st A RPackage-Core.package/RPackage.class/instance/private/basicImportClass_.st M RPackage-Core.package/RPackage.class/instance/private/importCategory.st A RPackage-Core.package/RPackage.class/instance/private/importClass_.st A RPackage-Core.package/RPackage.class/instance/private/moveClass_fromPackage_toTag_.st A RPackage-Core.package/RPackage.class/instance/private/moveClass_toTag_.st M RPackage-Core.package/RPackageTag.class/instance/accessing/addClass_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemClassAddedActionFrom_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemClassRecategorizedActionFrom_.st A RPackage-Tests.package/RPackageTagTest.class/README.md A RPackage-Tests.package/RPackageTagTest.class/definition.st A RPackage-Tests.package/RPackageTagTest.class/instance/running/tearDown.st A RPackage-Tests.package/RPackageTagTest.class/instance/tests/testAddClass.st A RPackage-Tests.package/RPackageTagTest.class/instance/tests/testAddClassFromTag.st A RPackage-Tests.package/RPackageTest.class/README.md A RPackage-Tests.package/RPackageTest.class/definition.st A RPackage-Tests.package/RPackageTest.class/instance/running/tearDown.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testAddClass.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testAddClassFromTag.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script376.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30723.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30723 12719 Creating Unnamed Package Kills Nautilus https://pharo.fogbugz.com/f/cases/12719 12718 rpackage not reorganising properly moved classes https://pharo.fogbugz.com/f/cases/12718 http://files.pharo.org/image/30/30723.zip

Jan. 27, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Sebastian Sastre

+1 any reason to not make it public in youtube? On Jan 27, 2014, at 1:24 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Pharo4Stef wrote >> Should put them on youtbue but I dod not how. > > I'm still having problems viewing the second one. Will you host it somewhere > else pleeeeease? I want to learn!!! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Two-videos-to-explain-what-we-do-when-integrating-a-f… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 27, 2014

Re: [Pharo-dev] bugs with blocks

by Camille Teruel

On 27 janv. 2014, at 10:44, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 27 janv. 2014, at 09:28, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> Hello, >> >> I don't think this line was there by mistake. In some cases, the activePC with this code is lower than the startpc and then the debugger shows an error 'no ast node found at this pc' and cannot properly highlight the current executed code because the pc is outside the method bytecode. > > Ok, thanks ClÃ©ment. > So shouldn't it be: activePC <= self home startpc ifTrue: [ activePC := pc ] since self may be the context of a block? We looked at the issue with ClÃ©ment and we agreed on adding #home. Fix in inbox. Nicolai what do you think? > >> I remember adding this line as a hack to fix a bug report.... But I don't remember any more... >> >> Here's an extract from my blog post, at that time the method had not this line, and we added it due to a bug report: >> >> in a debugger, the context on the top of the stack does not highlight the same way other contexts does. In fact, the top context highlights the instruction in source code that *will* be executed in the next step. On the contrary, all the other contexts highlights the instruction in source code that *has been* executed previously. That means that you need to take care about that in the mapping to highlight the correct range. >> >> Right now we had to keep the old mapping API so there is a method named rangeForPC:contextIsActiveContext: that has a boolean as second argument. With this boolean you know if you need to look for the range of the current pc (first argument) of the previous pc of the first argument. On the old mapping, they needed the exact pc for their pc to abstract pc mapping. So they needed a method previousPCFor: to handle the case of multiple byte code instructions. But we donât care, as the pc will be used in the scan of instructionForPC:, so we just need to do pc â 1. >> >> The result is : >> >> DebuggerMethodMapOpal>>#rangeForPC: aPC contextIsActiveContext:contextIsActive >> "return the debug highlight for aPC" >> | pc | >> pc := contextIsActive ifTrue: [aPC] ifFalse: [aPC - 1]. >> ^ (methodNode sourceNodeForPC: pc) debugHighlightRange >> RBMethodNode>>#sourceNodeForPC: anInteger >> ^ (self ir instructionForPC: anInteger) sourceNode >> >> IRMethod>>#instructionForPC: aPC >> 0 to: -3 by: -1 do: [ : off | >> (self firstInstructionMatching: [:ir | ir bytecodeOffset = (aPC - off) ]) ifNotNil: [:it |^it]] >> >> >> >> 2014/1/27 Camille Teruel <camille.teruel(a)gmail.com> >> >> On 27 janv. 2014, at 08:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> >>> On 26 Jan 2014, at 10:08, Camille Teruel <camille.teruel(a)gmail.com> wrote: >>> >>>> [ [ ] ] >>>> prints: >>>> [ ] >>>> instead of: >>>> [ [ ] ] >>>> >>>> and >>>> [ :arg | [ arg ] ] >>>> prints: >>>> DoIt >>>> ^ [ :arg | [ arg ] ] yourself >>>> instead of: >>>> [ :arg | [ arg ] ] >>>> >>>> >>>> Apparently it's the print that is not correct because of problem in #sourceNode. >>>> Any clue? Marcus? ClÃ©ment? >>> >>> Other than âthe devil is in the detailsâ (this is all far too complex for my taste, implementation wiseâ¦) >>> >>> Can you add an issue? My problem is that i have no time right now to even think about itâ¦ >> >> My problem is that I found a fix with try-and-fail without really understanding the code. >> I just found that problematic examples were passing through that condition whereas non problematic examples were not. >> I looked at the versions and though that you may have left this line by error. >> I removed it and so far, it *seems* to work. So the fix is there but I have no clue if it's correct or not. >> Here it the case: https://pharo.fogbugz.com/f/cases/12732/sourceNode-broken >> >>> >>> Marcus >> >> >

Jan. 27, 2014