March 2015 - Pharo-dev - lists.pharo.org

[Pharo4][Reflectivity] Fix link invalidation + hook generation on MetaLink

by Marcus Denker

Hi, https://pharo.fogbugz.com/f/cases/15094/Fix-link-invalidation-hook-generati… This increment does another pass over invalidation/recompile when setting a link. - recompile AST on run:with:in - install recompiled cm - fixes for the whole mechanism add #hook and #metaAwareHook to MetaLink. After experimenting with the AST transformer, I think I will for now (for Pharo4) just do it very simple: add the resulting hook as an annotation (beforeHook) to the AST node, do name analysis on those and then visit them in the ASTTranslator to generate code. This is very easy for âbeforeâ links, and the milestone we need for Pharo4 is just before to support Breakpoints and change-notification on variable access. Having just one AST is important for text/bc to AST mappingâ¦ when transforming one needs to take care to not destroy all this meta informationâ¦ so we will postpone that to Pharo5. TODO: -> hook ASTs need to stored in an annotation after first request -> visit them in Name analysis -> visit them before visiting any noise in OCASTTranslator after that, we should be ready to load the breakpoint package. Marcus

March 8, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Thierry Goubier

Le 08/03/2015 00:37, Sven Van Caekenberghe a Ã©crit : > > > Then the problem is in the extension protocol *gofer-core-accessing - for me that is not ZnUrl itself ;-) > > That being said, I totally agree the code is ugly there, what is the solution ? > > Doing a subclass based lookup below MCRepository ? Who wants to handle this URL ? I'd like that. Simple and not very complex. I had a look into which methods I extend in Zn, and for some of them, it looks like very small changes. I'll make a slice as soon as I get to it. Thierry

March 8, 2015

Re: [Pharo-dev] Bloc Example Errors

by stepharo

Hi Sean Load the latest version. There is a Ci entry so you can download it with the Launcher. Let me know. Stef Le 8/3/15 05:26, Sean P. DeNigris a Ã©crit : > I dug into Bloc a bit and ran into a few problems with the examples... > > 1. There seems to be some problem with fonts. Right clicking on a BlMorph > gives: > <http://forum.world.st/file/n4810365/Screenshot_2015-03-07_23.png> > > 2. the svg examples e.g. #exampleSvgIcon report missing .svg files > 3. BlMorphToTestMouseEnterLeave>>#example blows up, creating a red square of > death that eats the whole screen as the mouse moves around. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Bloc-Example-Errors-tp4810365.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

March 8, 2015

Re: [Pharo-dev] Bloc Example Errors

by Sean P. DeNigris

Sean P. DeNigris wrote > I... ran into a few problems (ConfigurationOfBloc project version: '1.9') in #40540 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Example-Errors-tp4810365p4810366.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 8, 2015

Bloc Example Errors

by Sean P. DeNigris

I dug into Bloc a bit and ran into a few problems with the examples... 1. There seems to be some problem with fonts. Right clicking on a BlMorph gives: <http://forum.world.st/file/n4810365/Screenshot_2015-03-07_23.png> 2. the svg examples e.g. #exampleSvgIcon report missing .svg files 3. BlMorphToTestMouseEnterLeave>>#example blows up, creating a red square of death that eats the whole screen as the mouse moves around. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Example-Errors-tp4810365.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 8, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Sven Van Caekenberghe

> On 07 Mar 2015, at 21:10, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 07/03/2015 20:10, Sven Van Caekenberghe a Ã©crit : >> >>> On 07 Mar 2015, at 19:41, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>> >>> For example, the following would work : >>> >>> Gofer it >>> url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; >>> package: 'HelloWorld'; >>> load >>> >>> Adding that type of Url in both Gofer and Metacello requires overrides in Zn and Metacello: ugly :(:( >> >> I created an issue to study what (if anything) has to change to ZnUrl in order to help here: >> >> https://pharo.fogbugz.com/f/cases/15090/ZnUrl-should-be-able-to-better-supp… > > Thanks. > >> However, the parsing works fine & correct: >> >> 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git' asZnUrl >> >> which leads me to suspect the problem is in usage. > > Well, I use ZnUrl to decode gitfiletree: urls, so I'm sure I choose a correct url scheme :) The only extension needed is the dispatch on the scheme of the url: what ZnUrl can dispatch is hardcoded as a case switch. > > Thierry Then the problem is in the extension protocol *gofer-core-accessing - for me that is not ZnUrl itself ;-) That being said, I totally agree the code is ugly there, what is the solution ? Doing a subclass based lookup below MCRepository ? Who wants to handle this URL ? Sven

March 7, 2015

Re: [Pharo-dev] Delay issues

by Max Leske

> On 07 Mar 2015, at 19:59, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Max, > > on another Ubuntu 14.10 machine, I have no issue as well. I'm starting to suspect an ubuntu upgrade effect on one of the system libs or the kernel. ouch :) > > Would you have the time to see where one of those tests fail? Any one would probably tell me something. Sorry, I forgot. The problem seems to be that the issue tests are located in directories which do not contain a .git directory. Thus the git commands fail. Fuel file of the stack: https://www.dropbox.com/s/4dzst3cdgupcnr7/Debugger-Stack-MCFileTreeGitRepos… <https://www.dropbox.com/s/4dzst3cdgupcnr7/Debugger-Stack-MCFileTreeGitRepos…> Stack trace: MCFileTreeGitRepository class(Object)>>error: [ c := PipeableOSProcess command: self gitCommand , ' ' , aCommandString environment: nil workingDir: (MCFileTreeFileUtils current directoryPathString: aDirectory) input: nil output: nil error: nil errorPipelineStream: nil. r := c output. "Force the command to terminate." c succeeded ifFalse: [ | errorString | errorString := c errorUpToEndOfFile. errorString notEmpty ifTrue: [ self error: 'Git error: ' , errorString ]. r := '' ] ] in MCFileTreeGitRepository class>>runOSProcessGitCommand:in: in Block: [ ... BlockClosure>>ensure: MCFileTreeGitRepository class>>runOSProcessGitCommand:in: MCFileTreeGitRepository class>>runGitCommand:in: MCFileTreeGitRepository>>gitCommand:in: MCFileTreeGitRepository>>gitVersions MCFileTreeGitRepository>>loadAncestry [ :bar | anAncestry := self loadAncestry. 1 to: entries size do: [ :i | (entries at: i) in: [ :entry | | entryVersions v | entryVersions := OrderedCollection new. commitIDs := self gitVersionsForPackage: entry name. [ commitIDs atEnd ] whileFalse: [ | logSize commitID author position message dateAndTime | (commitIDs match: 'log size ') ifFalse: [ self error: 'Unable to find git data in input' ]. logSize := Integer readFrom: commitIDs. commitIDs next. position := commitIDs position. commitID := ByteArray readHexFrom: (commitIDs upTo: $|) trimBoth. author := (commitIDs upTo: $|) onlyLetters. dateAndTime := DateAndTime fromString: (commitIDs upTo: $|). message := (commitIDs next: logSize + 1 + position - commitIDs position) convertFromSystemString. entryVersions add: (GitFileTreePackageEntry on: entry name id: commitID author: author message: message timeStamp: dateAndTime) ]. v := 1. entryVersions size to: 1 by: -1 do: [ :j | (entryVersions at: j) buildInfoWith: entryVersions startingAt: j + 1 version: v ancestry: anAncestry. v := v + 1 ]. allNames addAll: entryVersions ]. bar value: i ] ] in MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... BlockClosure>>cull: [ result := block cull: self ] in [ self prepareForRunning. [ result := block cull: self ] on: JobNotification do: [ :notification | notification handle: self ] ] in Job>>run in Block: [ result := block cull: self ] BlockClosure>>on:do: [ self prepareForRunning. [ result := block cull: self ] on: JobNotification do: [ :notification | notification handle: self ] ] in Job>>run in Block: [ ... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MCFileTreeGitRepository>>loadAllFileNames MCFileTreeGitRepository>>allFileNames MCFileTreeGitRepository>>readableFileNames MCFileTreeGitRepository(MCFileBasedRepository)>>allVersionNames [ self allVersionNames ] in MCFileTreeGitRepository(MCFileBasedRepository)>>goferReferences in Block: [ self allVersionNames ] BlockClosure>>on:do: MCFileTreeGitRepository(MCFileBasedRepository)>>goferReferences [ aRepository goferReferences asSortedCollection asArray ] in Gofer>>basicReferencesIn: in Block: [ aRepository goferReferences asSortedCollection a...etc... BlockClosure>>on:do: Gofer>>basicReferencesIn: [ self basicReferencesIn: aRepository ] in Gofer>>allResolvedIn: in Block: [ self basicReferencesIn: aRepository ] [ self at: key put: aBlock value ] in Dictionary>>at:ifAbsentPut: in Block: [ self at: key put: aBlock value ] Dictionary>>at:ifAbsent: > > Thierry > > Le 07/03/2015 18:07, Max Leske a Ã©crit : >> >>> On 06 Mar 2015, at 17:21, Thierry Goubier <thierry.goubier(a)gmail.com >>> <mailto:thierry.goubier@gmail.com>> wrote: >>> >>> >>> >>> 2015-03-06 16:17 GMT+01:00 Max Leske <maxleske(a)gmail.com >>> <mailto:maxleske@gmail.com>>: >>> >>>> >>>>> On 06 Mar 2015, at 16:08, Thierry Goubier >>>>> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> 2015-03-06 15:43 GMT+01:00 Max Leske <maxleske(a)gmail.com >>>>> <mailto:maxleske@gmail.com>>: >>>>> >>>>> >>>>>> On 06 Mar 2015, at 15:35, Thierry Goubier >>>>>> <thierry.goubier(a)gmail.com >>>>>> <mailto:thierry.goubier@gmail.com>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> 2015-03-06 15:21 GMT+01:00 Max Leske <maxleske(a)gmail.com >>>>>> <mailto:maxleske@gmail.com>>: >>>>>> >>>>>> >>>>>>> On 06 Mar 2015, at 14:56, Thierry Goubier >>>>>>> <thierry.goubier(a)gmail.com >>>>>>> <mailto:thierry.goubier@gmail.com>> wrote: >>>>>>> >>>>>>> Ok. It's not an image problem. It seems to be a vm >>>>>>> problem or an ubuntu problem. >>>>>>> >>>>>>> (vm and vmLatest from get.pharo.org >>>>>>> <http://get.pharo.org/> have that, the vm in the pharo >>>>>>> launcher seems to work fine, and I haven't seen any >>>>>>> problem with Pharo3 ? Ubuntu 14.10 64bits). >>>>>>> >>>>>> >>>>>> Ok, so we need to find the VM version that breaks >>>>>> OSProcessâ¦ >>>>>> >>>>>> >>>>>> I tried to rebuilt a vm from the git for pharo-vm, and it >>>>>> failed at the end of the process... lots of incorrect >>>>>> function redefinitions in cogit.c, if it says anything. >>>>> >>>>> Yes, I know that. Itâs a problem with gcc. To fix it and get >>>>> a working VM you can use the following: >>>>> >>>>> /* pre-empty some preprocessor variables used in >>>>> srv/vm/cogit.h, cointer.h, etc */ >>>>> # define NoDbgRegParms >>>>> # define NeverInline >>>>> >>>>> >>>>> In which header do you add that? >>>> >>>> >>>> src/vm/cogit.h >>>> src/vm/cointerp.h >>> >>> and src/vm/gcc3x-cointerp.c >>> >>> >>> Thanks, it worked. For the compilation, I mean. (the two .h happily >>> contain code to define those two macros ??) >>> >>> Ok, conclusion with a brand new VM: stuck at the very first test. The >>> worst result of all :( >>> >>> Thierry >> >> >> I ran your tests a couple of times and didnât see any hangs or crashes >> (although most of the tests failed). This is on OSX 10.10.2. >> >> output: >> >> 'Running tests in 1 Packages' >> MCGitFileTreeIssue139Test>>#testWrite >> [FAIL] >> MCGitFileTreeIssue139Test>>#testLoad >> [FAIL] >> MCGitFileTreeIssue139Test>>#testWriteNRead >> [FAIL] >> MCGitFileTreeIssue139Test>>#testRepository >> [FAIL] >> MCGitFileTreeIssue146Test>>#testWrite >> [FAIL] >> MCGitFileTreeIssue146Test>>#testWriteNRead >> [FAIL] >> MCGitFileTreeIssue147Test>>#testWriteNRead >> [FAIL] >> MCGitFileTreeIssue26Test>>#testWriteNRead2 >> [FAIL] >> MCGitFileTreeIssue26Test>>#testWrite >> [FAIL] >> MCGitFileTreeIssue26Test>>#testLoad >> [FAIL] >> MCGitFileTreeIssue26Test>>#testWriteNRead >> [FAIL] >> MCGitFileTreeIssue33Test>>#testWrite >> [FAIL] >> MCGitFileTreeIssue33Test>>#testLoad >> [FAIL] >> MCGitFileTreeIssue33Test>>#testWriteNRead >> [FAIL] >> MCGitFileTreeIssue33Test>>#testRepository >> [FAIL] >> MCGitFileTreeIssue69Test>>#testLoad >> [FAIL] >> MCGitFileTreeIssue72Test>>#testLoad >> [FAIL] >> MCGitFileTreeIssue72Test>>#testWriteNRead >> [FAIL] >> MCGitFileTreeLoaderTest>>#testBaseLoadRepository >> [FAIL] >> MCGitFileTreeLoaderTest>>#testCypressCuisLoad >> [FAIL] >> MCGitFileTreeLoaderTest>>#testIssue74 >> [FAIL] >> MCGitFileTreeLoaderTest>>#testTargetLoad >> [FAIL] >> MCGitFileTreeLoaderTest>>#testTargetLoadRepository >> [FAIL] >> MCGitFileTreeLoaderTest>>#testBaseLoad >> [FAIL] >> MCGitFileTreeLoaderTraitsTest>>#testLoad >> [FAIL] >> MCGitFileTreeTests>>#testStoreReadGitFileTree >> [31/31] >> Finished running 31 Tests > >

March 7, 2015

Re: [Pharo-dev] [Pharo-users] Reading an SQL db on OS X

by Alexandre Bergel

Hi Pierce! Yes, it works!!!! The fullpath name has indeed to be provided. Was hard to guess this. Thanks!!!!! Alexandre > On Mar 7, 2015, at 3:09 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Wed, Mar 04, 2015 at 05:18:57PM -0500, Alexandre Bergel wrote: >> I would like to read a SQL .db file. The page >> http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3 mention how to do this on >> Windows and Linux, but not on OSX. What should I do to read a SQL file on OS >> X? I tried google, but it did not work. > > Do it the same way on OSX as on Windows and Linux. On OSX you need to supply a > full path name to the DB file. This is due to weirdness in Pharo.app; search > this list's archives for a recent discussion. > > I wrote NBSQLite3 on OSX and tested on Linux. I don't use Windows. Subsequently > Torsten moved NBSQLite3 to STH. Seems Torsten uses Linux and Windows, so now we > have the 3 main platforms covered. :-) > > You may also want to check out http://www.samadhiweb.com/NBSQLite3.html. > > Pierce > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Thierry Goubier

Le 07/03/2015 21:10, Sean P. DeNigris a Ã©crit : > Thierry Goubier wrote >> Both are one and the same, but created via two different approaches. > > I was confused because they appear differently in MC Browser (one shows the > directory the other the github url) Yes, this is something I should improve. Thierry

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Sean P. DeNigris

Thierry Goubier wrote > Both are one and the same, but created via two different approaches. I was confused because they appear differently in MC Browser (one shows the directory the other the github url) ----- Cheers, Sean -- View this message in context: http://forum.world.st/GitHub-Easiest-Way-to-Load-a-Project-update-tp4810309… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 7, 2015