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

[Pharo-project] Cog problems

by Igor Stasenko

I built new Cog by taking latest VMMaker-oscog.46 on MacOS VM still crashing at some random point during running all pharo-core image tests. Once i were able to run w/o crash and found following failures: MethodContextTest debug: #testClosureRestart because actually this one: MethodContextTest new privRestartBlockArgsNoRemoteTempsTest i'm not sure if this is a compiler issue (maybe it shuffling the temps) or because of Cog, which doesn't likes restarts like that :) BecomeTest>>testBecomeIdentityHash. Sometimes passes, sometimes not (try doing following in workspace): | a b | a := 'ab' copy. b := 'cd' copy. self assert: (a identityHash ~= b identityHash). a become: b. self assert: (a ~= b). self assert: (a identityHash ~= b identityHash). i'm not sure if this is a big issue.. afaik, #become: don't gives any guarantees about copying identityhash. P.S. yesterday i were able to successfully build Cog on linux using cmake configs i generating. but it crashing at first #commonReturn point, which is really weird :) I tried multiple images, same result. The crash happens in given loop: while (closure != GIV(nilObj)) { home = longAt((closure + BaseHeaderSize) + (ClosureOuterContextIndex << ShiftForWord)); closure = longAt((home + BaseHeaderSize) + (ClosureIndex << ShiftForWord)); } -- Best regards, Igor Stasenko AKA sig.

Jan. 19, 2011

[Pharo-project] About XML Support in the 1.2

by Fabrizio Perin

Hi, I have a problem with the XMLSupport version from Pharo 1.2. The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. Thanks, Fabrizio

Jan. 19, 2011

Re: [Pharo-project] RPackage

by Cyrille Delaunay

Hello, Currently I am working on integrate RPackage in pharo, and having it working in parallel of PackageInfo. What RPackage is already able to do (or at least until you find something wrong;)) is: - synchronize and initialize with the current MCPackages in the system - update itself when changes are made in the system (new category, new class, new method, ... ). Now I was wondering if there would be something to pay attention to with Monticello. Maybe when saving or importing packages to/from a repository? I don't know how monticello work, but after looking quickly, that's some thoughts I had: 1) => *Saving from the image to a repository: *How monticello know if the package we want to saved is extended by other classes? is there currently a link between Monticello and Package Info to do that? 2) => *import from a repository into the image: *How do we manage to install the extension in the right package ? For the point 1) : MCPackageManager seems to directly listen to the system events (see MCPackageManager class >> reregisterForNotificationsWith:), in a parallel direction than RPackage (with its announcements system). So I guess Monticello update itself all its packages and check itself when a protocol is added to know if it's an extension. Therefore there would be nothing to worry when replacing PackageInfo by RPackage For the point 2) : When monticello will import the code, it will create classes, create methods in some protocols (that can be extensions or not), using the system interface. Then, Normally each modification will raise the corresponding event, for which RPackage is listening to (throught the announcement system). Therefore RPackage will update itself and there would be still nothing to worry. For now the only link to make I see, is when creating or deleting a MCPackage: we have to do the same with the RPackages. This is currently done in RPackage, by listening to MC changes (look at RPackageOrganizer >> update:). PackageInfo is directly updated in the MC code instead of listening to changes. So I wonder if there is some big parts I totally forgot ? and In general if you have something in mind that should be done for RPackage? 2010/12/6 <csrabak(a)bol.com.br> > I think this small thread is an excellent example of the need we have to > implement simpler practice: > > When we announce a package or project, it would nice if the first > paragraph[s] could be a short description of what it's all about! > > We could even open another thread and agree upon a format for it, and look, > we could even have the same text in some specific attribute in the package > which could be collected, selected, etc.!! > > -- > Cesar Rabak > > > Em 06/12/2010 07:08, Tudor Girba < tudor.girba(a)gmail.com > escreveu: > Good work, Cyrille! > > For people that might not know what RPackage is, this project aims to > replace PackageInfo with a faster and cleaner implementation. At the moment, > all categories are mapped one-to-one and in the end, we would like to remove > class categories altogether. > > This infrastructure is also targeted to code browsers. > > Doru > > > On 6 Dec 2010, at 09:58, Cyrille Delaunay wrote: > > > Hello, > > > > Recently I made some improvements about RPackage. What I mainly did, is > to implement the 'SystemAnnounncements listening', to update the organizer > when the system change. With that I implemented a set of tests that should > all be green now (in RPackageMCSynchronisationTest (I should change the > name)). > > > > You can load RPackage by evaluating: > > > > Gofer new > > squeaksource: 'PharoInbox'; > > package: 'ConfigurationOfRPackage'; > > load. > > (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. > > > > (I think it should work, but squeaksource is down for now, so I was not > able to test it). > > > > In those tests I started to write some about traits, but after few, I > realized that the events emitted when a trait change are the same that the > one used for classes ? > > Then if you have some ideas about what is still missing in RPackage, tell > me, I can add it to my task list :) > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > > > >

Jan. 19, 2011

Re: [Pharo-project] list on he fly selection :)

by Tudor Girba

Could you let me know when I should try again? I am very interested in this. Cheers, Doru On 18 Jan 2011, at 21:39, Benjamin wrote: > You must have tried between two commits on squeaksource (I hope ^^) > I will refactor that because the inst var is named lastKeystrokes but the method is named lastKeyStrokes ... > > > Thanks for your feedback :) > > > > Ben > > On Jan 18, 2011, at 8:34 PM, Tudor Girba wrote: > >> I am not sure where it should work, but I tried in Pharo 1.2 and it does not work. First, there is a "self self". Second, even if I fix this one, I still get a DNU for OnTheFlySelectionPluggableListMorph>>lastKeystrokes. >> >> Cheers, >> Doru >> >> >> On 18 Jan 2011, at 20:21, StÃ©phane Ducasse wrote: >> >>> close your eyes and imagine that you can just type as to get all the methods starting with as* >>> without extra shortcut whatever.... >>> same for classes, packages... of course. >>> >>> Stef >>> >>> On Jan 18, 2011, at 4:16 PM, Alexandre Bergel wrote: >>> >>>> Just tried. I could not immediately figure out what is the difference with the "Find Class" panel (pressing Cmd-f in OB)? >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> On 18 Jan 2011, at 12:00, StÃ©phane Ducasse wrote: >>>> >>>>> Hi guys >>>>> >>>>> I'm sure that some of you will really like to type on that list and see it auto selectioning its elements.... >>>>> >>>>> Gofer it >>>>> squeaksource: 'DirtyExperiments'; >>>>> package: 'DirtyExperiments'; >>>>> load >>>>> >>>>> | test | >>>>> test := DummyTest on: (Smalltalk allClasses). >>>>> test openInWorld >>>>> >>>>> Of course I would love to have that for a lot of lists..... :) >>>>> >>>>> Thanks Benjamin for this first version :) >>>>> Stef >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Sometimes the best solution is not the best solution." >> >> > > -- www.tudorgirba.com "One cannot do more than one can do."

Jan. 19, 2011

Re: [Pharo-project] splitters in table layout

by Tudor Girba

That is strange. Are you using Pharo 1.2? Cheers, Doru On 18 Jan 2011, at 21:33, Andreas Wacknitz wrote: > > Am 18.01.2011 um 20:58 schrieb Tudor Girba: > >> Yes, you missed a changeset Gary sent in the aligning morphs thread (he actually sent two, and you should pick the second one). >> >> Cheers, >> Doru >> > Ah, thank you. I have found two messages with changesets from January 11th, 2011. > After I filein the second changeset alas I will get a DNU Morph>>doFastWindowReframe: when I move the splitter... > > Regards, > Andreas > > -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Jan. 19, 2011

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

by pharo＠googlecode.com

Comment #14 on issue 3542 by philippe...(a)gmail.com: Add SmalltalkImage>>#gcBiasToGrow: and friends to core http://code.google.com/p/pharo/issues/detail?id=3542 Has been integrated into Seaside.

Jan. 19, 2011

[Pharo-project] need a working RFB server

by sergio_101

anyone know where i can find one? there used to be one here: http://source.lukas-renggli.ch/unsorted but it looks like it's down.. thanks! -- ---- peace, sergio photographer, journalist, visionary http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 19, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Comment #5 on issue 3545 by sean.p.d...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 Relationship to Project: * all the flexibility of multiple worlds (except there is no UI for now, maybe later we add a menu option, thumbnails, whatever * none of the complexity / issues Code statistics: * Changes to PasteUpMorph # methods added: 2 # lines per method: 5.5 # lines of longest method: 7 * 1 Class added: WorldManager # methods: 10 # lines per method: 2.3 # lines of longest method: 7 # methods with no senders: 5 <-- maybe we should remove these, but I wasn't sure what Jochen's intention was and wanted to hear from him before I removed them. Maybe some/all are intended as an API? - one single-line class method to access singleton Open questions: * should worlds be named, or numbered (like Mac Spaces), or both? Either way, maybe that attribute (or both) should be encapsulated in PasteUpMorph. But it's working, so we might as well play with it. * should methods with no senders (WorldManager>>switchToWorldNamed:, #createWorldNamed:, #switchToWorldNamed:, switchToWorldNamed:ifAbsent:, #worlds) be removed. Code used to collect statistics: | methodSizes numMethods lpm | methodSizes := WorldManager methodDictionary values collect: [ :m | m linesOfCode - 1 ]. numMethods := WorldManager methodDictionary size. "10" lpm := (methodSizes sum / numMethods) asFloat. "2.3" methodSizes max. "7" WorldManager methodDictionary values collect: [ :m | m linesOfCode - 1 ]. (WorldManager methodDictionary keys select: [ :s | (SystemNavigation default allSendersOf: s) isEmpty ]) size. "5"

Jan. 18, 2011

Re: [Pharo-project] Unsubscribing for Announcements

by Schwab,Wilhelm K

Take a look in this thread: http://thread.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/15001/focus=1… ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Tudor Girba [tudor.girba(a)gmail.com] Sent: Tuesday, January 18, 2011 2:52 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Unsubscribing for Announcements Who defended what status quo? The WeakAnnouncement are already on the agenda for 1.3. Cheers, Doru On 18 Jan 2011, at 20:40, Schwab,Wilhelm K wrote: > Of course. But when the status quo has been robustly defended, it seems reasonable to lobby for change as a start. > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Tuesday, January 18, 2011 2:22 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Unsubscribing for Announcements > > Yes but having good weakstructure will not arrive by accident. > > > On Jan 17, 2011, at 4:34 PM, Schwab,Wilhelm K wrote: > >> Two comments: >> >> (1) there needs to be a way to unregister interest; >> (2) the registrations need to be weak so that (1) is largely optional. >> >> If Dolphin has a weakness, it is that failure of an MVP triad to open can leave the system in a confused state. Morphic appears to be a little more robust about that, though in fairness, I do not push Pharo's GUI nearly as hard as I have Dolphin's. If in doubt, some type of #ifCurtailed: or similar protection around the assembly of a complex morph might be a good idea. >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [sean(a)clipperadams.com] >> Sent: Monday, January 17, 2011 1:18 AM >> To: pharo-project(a)lists.gforge.inria.fr >> Subject: [Pharo-project] Unsubscribing for Announcements >> >> I really like Announcements! It's so much easier to update complex GUIs when >> you can pass state :) >> >> I hit one glitch when unsubscribing... The CollaborActive book suggests >> unsubscribing in #delete. For complex UIs, this doesn't seem to work >> because #delete is only called for the one morph that was deleted, not for >> its submorphs (which may need to unsubscribe). >> >> I tried this: >> MyMorph>>delete >> super delete. "Must come first. Deleting a submorph before self = >> emergency evaluator" >> aSubmorphThatNeedsToUnsubscribe delete. >> >> SubmorphMentionedAbove>>delete >> self inventory announcer unsubscribe: self. >> super delete. >> >> >> But it seems like a lot of work and coupling. Is there no hook that is >> guaranteed to be called when a morph is going away - i.e. it or a morph in >> the owner chain is being deleted? >> >> Thanks. >> Sean >> -- >> View this message in context: http://forum.world.st/Unsubscribing-for-Announcements-tp3220751p3220751.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- www.tudorgirba.com "Every thing has its own flow."

Jan. 18, 2011

Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

by pharo＠googlecode.com

Comment #6 on issue 3471 by laurent....(a)gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 Issue 3517 has been merged into this issue.

Jan. 18, 2011