May 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Adding "Extended Search" to OB context menu

by Mariano Martinez Peck

On Mon, May 9, 2011 at 1:57 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Sure, that can be done. > > The point is that the RB code menu is fully implemented in OB now. > Thanks Lukas. I am not sure if you understand my question. I am not doing anything at all with RB. So I don't see how this is related to do a right click in the code pane. I attach two screenshots, "oldOB" and "newOB". What I am asking is to have the "extended search" or the "method soruce with it" from "oldOB". thanks in advance Mariano > Previously OB just used the menu provided by Pharo, what caused all > kinds of problems. "Method source with it" was never an operation > backed by OB. > > Lukas > > On 9 May 2011 11:46, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > Hi Lukas, > > > > do you think it would be possible to use what is currently selected in > > the code pane to set the default value of the 'Refactor -> Search > > code' window? > > > > > > ---------- Forwarded message ---------- > > From: Mariano Martinez Peck <marianopeck(a)gmail.com> > > Date: Mon, May 9, 2011 at 10:56 AM > > Subject: Re: [Pharo-project] Adding "Extended Search" to OB context menu > > To: Pharo-project(a)lists.gforge.inria.fr > > > > > >> Have you tried 'Refactor -> Search code' ? > > > > Thanks Damien. But that's something completely different. What I want > > to do is to select text, right button, method source with it. That's > > all. > > > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Lambdas are relegated to relative obscurity until Java makes them > > popular by not having them." James Iry > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] How to load Nautilus?

by Benjamin

I use it to develop since a month maybe :) It's stable, maybe a bit slow with a non cog VM (a new UI is now available and will be used by default in the next release). Right now, if you load it, if in the world menu you click on Nautilus, you will have the under dev UI, but if you select Nautilus as default browser, you will have the "stable" UI (yes I know, it's a bit stupid, I will change that right now) Ben On May 9, 2011, at 4:30 PM, Alexandre Bergel wrote: > Benjamin, are you using Nautilus to develop? Is it stable now? > > Alexandre > > > > On 9 May 2011, at 10:07, Benjamin wrote: > >> Thanks a lot, it's cool :) >> >> >> I want to know how to do that ;) >> >> >> Ben >> >> On May 9, 2011, at 4:04 PM, Marcus Denker wrote: >> >>> >>> On May 9, 2011, at 3:13 PM, Benjamin wrote: >>> >>>> Now ConfigurationOfNautilus loads RPackage. >>>> >>>> On the last 1.3 core image: >>>> >>>> Gofer new >>>> squeaksource: 'Nautilus'; >>>> package: 'ConfigurationOfNautilus'; >>>> load. >>>> >>>> ConfigurationOfNautilus loadDefault >>> >>> There is now a Hudson Project: >>> >>> https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/ >>> >>> The latest image zipped is always here: >>> >>> https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/lastSuccessfulBuild/art… >>> >>> >>> >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

May 9, 2011

Re: [Pharo-project] How to load Nautilus?

by Alexandre Bergel

Benjamin, are you using Nautilus to develop? Is it stable now? Alexandre On 9 May 2011, at 10:07, Benjamin wrote: > Thanks a lot, it's cool :) > > > I want to know how to do that ;) > > > Ben > > On May 9, 2011, at 4:04 PM, Marcus Denker wrote: > >> >> On May 9, 2011, at 3:13 PM, Benjamin wrote: >> >>> Now ConfigurationOfNautilus loads RPackage. >>> >>> On the last 1.3 core image: >>> >>> Gofer new >>> squeaksource: 'Nautilus'; >>> package: 'ConfigurationOfNautilus'; >>> load. >>> >>> ConfigurationOfNautilus loadDefault >> >> There is now a Hudson Project: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/ >> >> The latest image zipped is always here: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/lastSuccessfulBuild/art… >> >> >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 9, 2011

Re: [Pharo-project] How to load Nautilus?

by Benjamin

Thanks a lot, it's cool :) I want to know how to do that ;) Ben On May 9, 2011, at 4:04 PM, Marcus Denker wrote: > > On May 9, 2011, at 3:13 PM, Benjamin wrote: > >> Now ConfigurationOfNautilus loads RPackage. >> >> On the last 1.3 core image: >> >> Gofer new >> squeaksource: 'Nautilus'; >> package: 'ConfigurationOfNautilus'; >> load. >> >> ConfigurationOfNautilus loadDefault > > There is now a Hudson Project: > > https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/ > > The latest image zipped is always here: > > https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/lastSuccessfulBuild/art… > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

May 9, 2011

Re: [Pharo-project] How to load Nautilus?

by Marcus Denker

On May 9, 2011, at 3:13 PM, Benjamin wrote: > Now ConfigurationOfNautilus loads RPackage. > > On the last 1.3 core image: > > Gofer new > squeaksource: 'Nautilus'; > package: 'ConfigurationOfNautilus'; > load. > > ConfigurationOfNautilus loadDefault There is now a Hudson Project: https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/ The latest image zipped is always here: https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/lastSuccessfulBuild/art… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 9, 2011

[Pharo-project] compiled VM with Alien for JNIPort

by laurent laffont

Hi, is there a compiled VM available with Alien for OSX ? I want to use JNIPort. Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

May 9, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

Another that....all those incorrect compiled method has the same: they miss the bytecode 120 (self return), and they ALL have the same last byte: 32. what that 32 can be? I don't know... On Mon, May 9, 2011 at 3:27 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Ok, the problem is the following. Check my screenshot of the previous mail. > Left is incorrect, right is correct. > As you can notice, the "correct" CompiledMethod finishes with a bytecode > "return self" and number 78. This bytecode is missing in the "incorrect" CM. > And, the first byte in method trailer in the incorrect CM is 120. Guess > what? 16r78 -> 120. So...the incorrect CM interpret that byte as trailer > instead of bytecode. > Now, if you ask to the incorrect CM: "trailer data", you get, of course, > 120. > > If you see > > sourcePointer: ptr > > self clear. > data := ptr. > "see if we can encode pointer using 4-byte trailer" > kind := (ptr between: 16r1000000 and: 16r4FFFFFF) > ifTrue: [ #SourcePointer ] ifFalse: [ #VarLengthSourcePointer ]. > > > You can guess that ptr is 120, hence it sets #VarLengthSourcePointer > > Now...two problem bugs: > > 1) how can these CM be generated???? Compiler bug? > > 2) where are they kept that I cannot garbage collect them ?? > > Cheers > > Mariano > > > > On Mon, May 9, 2011 at 2:50 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Mon, May 9, 2011 at 12:48 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> the one to the left seems like broken. it not ends with return self. >>> >>> >> yes, exactly. That one on the left is the one that trailer kind answers >> #VarLengthSourcePointer >> the right is the correct one. >> >> You can also notice that the one of the left in addition to not having the >> last bytecode (self return), it has only 2 bytes for the trailer. >> >> Anyway, regardless of how such CM could have been generated, I CANNOT find >> who is pointing to them. They appear only in PharoDev and I cannot find any >> pattern between them :( >> >> :( >> >> On 9 May 2011 11:22, Mariano Martinez Peck <marianopeck(a)gmail.com> >>> wrote: >>> > >>> > >>> > On Mon, May 9, 2011 at 10:53 AM, Mariano Martinez Peck >>> > <marianopeck(a)gmail.com> wrote: >>> >> >>> >> >>> >> On Mon, May 9, 2011 at 10:27 AM, Nicolas Cellier >>> >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> >>> >>> Hi Mariano, >>> >>> you should try these two things before repeating yourself: >>> >>> >>> >>> (CompiledMethod allInstances select: [:each | each trailer kind = >>> >>> #VarLengthSourcePointer] ) first trailer kind. >>> >>> >>> >>> | temp | >>> >>> temp := (CompiledMethod allInstances select: [:each | each trailer >>> >>> kind = #VarLengthSourcePointer] ) first. >>> >>> temp == (temp methodClass >> temp selector) >>> >>> >>> >> >>> >> Thanks Nicolas. Yes, in fact all of you were right. They are not the >>> same >>> >> CM instance. They are different. >>> >> It is wierd that they are only present in Pharo1.3: >>> >> >>> >> >>> >> ((CompiledMethod allInstances select: [:each | each trailer kind = >>> >> #VarLengthSourcePointer] ) ) size >>> >> ->>> 11 >>> >> >>> >> And in Pharo 1.2, cero and and 1.1.1, 2. >>> >> >>> >> I am trying to inspect pointers to them to see who is pointing to >>> >> them...but I cannot find anything :( >>> >> >>> >> I will continue.... >>> >> >>> > >>> > More data: there are only these kind of compiled methods in the dev >>> image. >>> > Not in core. >>> > >>> > In addition, if I do: ScriptLoader new cleanUpForRelease, then inspect >>> > ((CompiledMethod allInstances select: [:each | each trailer kind = >>> > #VarLengthSourcePointer] ) ) >>> > >>> > and then I click on the first element in the inspector.... VM CRASH!!! >>> with >>> > both, InterpreterVM and CogVM. >>> > >>> > I can see the difference in the trailer of the CMs (I attach >>> screenshot), >>> > but still cannot find who is pointing to that weird instances :( >>> > >>> > grrr... thanks for the help >>> > >>> > >>> > >>> >> >>> >> thanks >>> >> >>> >> >>> >> >>> >>> It may be possible that CompiledMethod>>printString is lying to >>> you... >>> >>> >>> >>> Nicolas >>> >>> >>> >>> 2011/5/9 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> >>> > >>> >>> > >>> >>> > On Mon, May 9, 2011 at 6:14 AM, Igor Stasenko <siguctua(a)gmail.com> >>> >>> > wrote: >>> >>> >> >>> >>> >> On 9 May 2011 00:52, Mariano Martinez Peck <marianopeck(a)gmail.com >>> > >>> >>> >> wrote: >>> >>> >> > Hi guys, Maybe it is too late and I am not seeing something >>> >>> >> > obvious...so >>> >>> >> > another look is really appreciated. If I do: >>> >>> >> > >>> >>> >> > (CompiledMethod allInstances select: [:each | each trailer kind >>> = >>> >>> >> > #VarLengthSourcePointer] ) first >>> >>> >> > ---> (CodeLoader class>>#initialize "a >>> CompiledMethod(311951360)") >>> >>> >> > >>> >>> >> > But then: >>> >>> >> > >>> >>> >> > (CodeLoader class >> #initialize) trailer kind >>> >>> >> > ----> #SourcePointer >>> >>> >> > >>> >>> >> > WHYYY?? why it is answering #SourcePointer instead of >>> >>> >> > #VarLengthSourcePointer ?? >>> >>> >> > >>> >>> >> > grrr how can that be possible??? It happens the same to each of >>> the >>> >>> >> > CompiledMethods I select as #VarLengthSourcePointer. When I >>> then >>> >>> >> > ask >>> >>> >> > the >>> >>> >> > #kind they always answer #SourcePointer instead of >>> >>> >> > #VarLengthSourcePointer >>> >>> >> > >>> >>> >> is it same compiled methods? >>> >>> >> Because it is absolutely normal if they using different source >>> >>> >> pointer. >>> >>> >> >>> >>> > >>> >>> > I didn't understand your question. Yes, it is exactly the same >>> >>> > CompiledMethod. >>> >>> > Look, if I do: >>> >>> > >>> >>> > (CompiledMethod allInstances select: [:each | each trailer kind = >>> >>> > #VarLengthSourcePointer] ) first >>> >>> > >>> >>> > I get >>> >>> > ---> (CodeLoader class>>#initialize "a CompiledMethod(311951360)") >>> >>> > >>> >>> > So...it means that such CompiledMethod answers >>> #VarLengthSourcePointer >>> >>> > when >>> >>> > send "trailer kind". Ok? >>> >>> > >>> >>> > But immediatly after, if I ask the trailer kind to the SAME >>> compiled >>> >>> > method: >>> >>> > >>> >>> > (CodeLoader class >> #initialize) trailer kind >>> >>> > >>> >>> > I get >>> >>> > ----> #SourcePointer >>> >>> > >>> >>> > WHYYY?? why it is answering #SourcePointer instead of >>> >>> > #VarLengthSourcePointer ?? >>> >>> > >>> >>> >> >>> >>> >> > thanks in advance, >>> >>> >> > >>> >>> >> > -- >>> >>> >> > Mariano >>> >>> >> > http://marianopeck.wordpress.com >>> >>> >> > >>> >>> >> > >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> -- >>> >>> >> Best regards, >>> >>> >> Igor Stasenko AKA sig. >>> >>> >> >>> >>> > >>> >>> > >>> >>> > >>> >>> > -- >>> >>> > Mariano >>> >>> > http://marianopeck.wordpress.com >>> >>> > >>> >>> > >>> >>> >>> >> >>> >> >>> >> >>> >> -- >>> >> Mariano >>> >> http://marianopeck.wordpress.com >>> >> >>> > >>> > >>> > >>> > -- >>> > Mariano >>> > http://marianopeck.wordpress.com >>> > >>> > >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

Ok, the problem is the following. Check my screenshot of the previous mail. Left is incorrect, right is correct. As you can notice, the "correct" CompiledMethod finishes with a bytecode "return self" and number 78. This bytecode is missing in the "incorrect" CM. And, the first byte in method trailer in the incorrect CM is 120. Guess what? 16r78 -> 120. So...the incorrect CM interpret that byte as trailer instead of bytecode. Now, if you ask to the incorrect CM: "trailer data", you get, of course, 120. If you see sourcePointer: ptr self clear. data := ptr. "see if we can encode pointer using 4-byte trailer" kind := (ptr between: 16r1000000 and: 16r4FFFFFF) ifTrue: [ #SourcePointer ] ifFalse: [ #VarLengthSourcePointer ]. You can guess that ptr is 120, hence it sets #VarLengthSourcePointer Now...two problem bugs: 1) how can these CM be generated???? Compiler bug? 2) where are they kept that I cannot garbage collect them ?? Cheers Mariano On Mon, May 9, 2011 at 2:50 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > > > On Mon, May 9, 2011 at 12:48 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> the one to the left seems like broken. it not ends with return self. >> >> > yes, exactly. That one on the left is the one that trailer kind answers > #VarLengthSourcePointer > the right is the correct one. > > You can also notice that the one of the left in addition to not having the > last bytecode (self return), it has only 2 bytes for the trailer. > > Anyway, regardless of how such CM could have been generated, I CANNOT find > who is pointing to them. They appear only in PharoDev and I cannot find any > pattern between them :( > > :( > > On 9 May 2011 11:22, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> > >> > >> > On Mon, May 9, 2011 at 10:53 AM, Mariano Martinez Peck >> > <marianopeck(a)gmail.com> wrote: >> >> >> >> >> >> On Mon, May 9, 2011 at 10:27 AM, Nicolas Cellier >> >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> >> >>> Hi Mariano, >> >>> you should try these two things before repeating yourself: >> >>> >> >>> (CompiledMethod allInstances select: [:each | each trailer kind = >> >>> #VarLengthSourcePointer] ) first trailer kind. >> >>> >> >>> | temp | >> >>> temp := (CompiledMethod allInstances select: [:each | each trailer >> >>> kind = #VarLengthSourcePointer] ) first. >> >>> temp == (temp methodClass >> temp selector) >> >>> >> >> >> >> Thanks Nicolas. Yes, in fact all of you were right. They are not the >> same >> >> CM instance. They are different. >> >> It is wierd that they are only present in Pharo1.3: >> >> >> >> >> >> ((CompiledMethod allInstances select: [:each | each trailer kind = >> >> #VarLengthSourcePointer] ) ) size >> >> ->>> 11 >> >> >> >> And in Pharo 1.2, cero and and 1.1.1, 2. >> >> >> >> I am trying to inspect pointers to them to see who is pointing to >> >> them...but I cannot find anything :( >> >> >> >> I will continue.... >> >> >> > >> > More data: there are only these kind of compiled methods in the dev >> image. >> > Not in core. >> > >> > In addition, if I do: ScriptLoader new cleanUpForRelease, then inspect >> > ((CompiledMethod allInstances select: [:each | each trailer kind = >> > #VarLengthSourcePointer] ) ) >> > >> > and then I click on the first element in the inspector.... VM CRASH!!! >> with >> > both, InterpreterVM and CogVM. >> > >> > I can see the difference in the trailer of the CMs (I attach >> screenshot), >> > but still cannot find who is pointing to that weird instances :( >> > >> > grrr... thanks for the help >> > >> > >> > >> >> >> >> thanks >> >> >> >> >> >> >> >>> It may be possible that CompiledMethod>>printString is lying to you... >> >>> >> >>> Nicolas >> >>> >> >>> 2011/5/9 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> > >> >>> > >> >>> > On Mon, May 9, 2011 at 6:14 AM, Igor Stasenko <siguctua(a)gmail.com> >> >>> > wrote: >> >>> >> >> >>> >> On 9 May 2011 00:52, Mariano Martinez Peck <marianopeck(a)gmail.com> >> >>> >> wrote: >> >>> >> > Hi guys, Maybe it is too late and I am not seeing something >> >>> >> > obvious...so >> >>> >> > another look is really appreciated. If I do: >> >>> >> > >> >>> >> > (CompiledMethod allInstances select: [:each | each trailer kind >> = >> >>> >> > #VarLengthSourcePointer] ) first >> >>> >> > ---> (CodeLoader class>>#initialize "a >> CompiledMethod(311951360)") >> >>> >> > >> >>> >> > But then: >> >>> >> > >> >>> >> > (CodeLoader class >> #initialize) trailer kind >> >>> >> > ----> #SourcePointer >> >>> >> > >> >>> >> > WHYYY?? why it is answering #SourcePointer instead of >> >>> >> > #VarLengthSourcePointer ?? >> >>> >> > >> >>> >> > grrr how can that be possible??? It happens the same to each of >> the >> >>> >> > CompiledMethods I select as #VarLengthSourcePointer. When I then >> >>> >> > ask >> >>> >> > the >> >>> >> > #kind they always answer #SourcePointer instead of >> >>> >> > #VarLengthSourcePointer >> >>> >> > >> >>> >> is it same compiled methods? >> >>> >> Because it is absolutely normal if they using different source >> >>> >> pointer. >> >>> >> >> >>> > >> >>> > I didn't understand your question. Yes, it is exactly the same >> >>> > CompiledMethod. >> >>> > Look, if I do: >> >>> > >> >>> > (CompiledMethod allInstances select: [:each | each trailer kind = >> >>> > #VarLengthSourcePointer] ) first >> >>> > >> >>> > I get >> >>> > ---> (CodeLoader class>>#initialize "a CompiledMethod(311951360)") >> >>> > >> >>> > So...it means that such CompiledMethod answers >> #VarLengthSourcePointer >> >>> > when >> >>> > send "trailer kind". Ok? >> >>> > >> >>> > But immediatly after, if I ask the trailer kind to the SAME compiled >> >>> > method: >> >>> > >> >>> > (CodeLoader class >> #initialize) trailer kind >> >>> > >> >>> > I get >> >>> > ----> #SourcePointer >> >>> > >> >>> > WHYYY?? why it is answering #SourcePointer instead of >> >>> > #VarLengthSourcePointer ?? >> >>> > >> >>> >> >> >>> >> > thanks in advance, >> >>> >> > >> >>> >> > -- >> >>> >> > Mariano >> >>> >> > http://marianopeck.wordpress.com >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> >> >>> >> >> >>> >> -- >> >>> >> Best regards, >> >>> >> Igor Stasenko AKA sig. >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Mariano >> >>> > http://marianopeck.wordpress.com >> >>> > >> >>> > >> >>> >> >> >> >> >> >> >> >> -- >> >> Mariano >> >> http://marianopeck.wordpress.com >> >> >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] How to load Nautilus?

by Benjamin

Now ConfigurationOfNautilus loads RPackage. On the last 1.3 core image: Gofer new squeaksource: 'Nautilus'; package: 'ConfigurationOfNautilus'; load. ConfigurationOfNautilus loadDefault It works ^^ Ben On May 9, 2011, at 11:51 AM, Mariano Martinez Peck wrote: > > > On Mon, May 9, 2011 at 11:46 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > On May 7, 2011, at 10:46 PM, Mariano Martinez Peck wrote: > >> I took the latest PharoCore 1.3 and evaluated: >> >> Gofer new >> squeaksource: 'Nautilus'; >> package: 'ConfigurationOfNautilus'; >> load. >> >> >> ConfigurationOfNautilus project lastVersion load >> >> >> But it says >> >> This package depends on the following classes: >> SystemAnnouncer >> You must resolve these dependencies before you will be able to load these definitions: >> GroupAnnouncer >> >> >> Select Proceed to continue, or close this window to cancel the operation. >> >> >> >> Then after in the load, I have a DNU in MCWorkingCopy >> modified: aBooleanm, because MonticelloAnnouncer is nil (not defined) >> >> So....how I am supposed to load Nautilus? > > Nautilus is based on RPackage so: > > - dl PharoCore 1.3 from Hudson > - load RPackage 3.0 > - load Nautilus (stable or default, should be the same) > > Here it works > > > But the idea is that it works outside your pc ;) > > So...if Nautilus is based on RPackage, then you must add it to ConfigurationOfNautilus as a depdeny. Otherwise, I cannot guess that you need RPackage. If fact, I didn'tknow until now. > I don't know where RPackage is, nor which group should I load. > > :) > > > >> >> And if I want the integration with Refactoring Browser, OCompletion, Shout, etc, what should I do? load those packages and magically Nautilus will work ? > > OCompletion and Shout normally impact only the textMorph. > I haven't test OCompletion (I do not use it, but I will do it right now), but for Shout, load the Shout package, and no, it's not magic, but Nautilus works. > > ok cool > > > For refactoring browser, since Nautilus is based on BrowserEnvironment, it should work too. But I have to check and steal some menu's entries from OB. > > > Cool. I think this is really important :) > >> What happens if I load Nautilus in a dev image? > > No idea, let's try :) > > > Ben > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 9, 2011

[Pharo-project] [update 1.3] #13186

by Marcus Denker

13186 ----- Issue 3233: Tests for WeakSet Issue 4169: FlatMessageListBrowser has undeclared ivar title -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 9, 2011