August 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] What is the plan with Pharo changes?
by Mariano Martinez Peck Aug. 4, 2012

Aug. 4, 2012

Hi guys. PLEASE: I DON'T WANT TO START A WAR. I am just concerned about Pharo and it's future. I am totally in favor of making progress even if it breaks compatibility. I am all in favor of having to spend time and effort in updating projects to use latest Pharo changes. Today I faced a couple of problems with Metacello and Pier. Most problems were related to: 1) SystemChangeNotifier -> SystemAnnouncer 2) FileDirectory -> FileSystem so...after a couple of fixes, I was able to make them both to work in last Pharo version. So, DO NOT GO OFFTOPIC please. My question is, how can we make sure that we are not all trying to updated existing packages? I mean, I have updated Metacello (a part of it) and Pier. So what do we do? where do I commit without affecting all those not using Pharo 2.0 ? how can others take advantage of it? thanks guys. -- Mariano http://marianopeck.wordpress.com

6 18

Re: [Pharo-project] [Seaside] Re: [Metacello] What is the plan with Pharo changes?
by Dale Henrichs Aug. 4, 2012

Aug. 4, 2012

Philippe, Cami provided a port of FileTree to Pharo-2.0 within an hour... Getting FileTree to run is not the issue ... for me ... FileTree was written to be very _dependent_ on FileDirectory and needs to be rewritten... I think the Pharo folks are correct that most applications will not be hit nearly as hard by the removal of FileDirectory. Dale ----- Original Message ----- | From: "Philippe Marschall" <philippe.marschall(a)gmail.com> | To: "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org> | Cc: Pharo-project(a)lists.gforge.inria.fr | Sent: Saturday, August 4, 2012 10:27:42 AM | Subject: Re: [Pharo-project] [Seaside] Re: [Metacello] What is the plan with Pharo changes? | | On Sat, Aug 4, 2012 at 11:21 AM, Mariano Martinez Peck | <marianopeck(a)gmail.com> wrote: | > Hi all. I am answering to all together: | > | > Stef: Yes, I imported and loaded the Pier of DBX website in Pharo | > 2.0 with | > seaside and magritte. With 5 minutes of opening debuggers and | > change things | > I was able to correctly make it work (at least, my app, I didn't | > run all | > tests to see). | > | > Dale: We don't want to just help you with "hacks", that why I send | > this | > email and several others, to see what others think so that can find | > better | > and non-hacky solutions. So, let's try to find good solutions: | > | > 1) does it help if we put back FildeDirectory and we remove it | > later ? so | > that you have time to update Metacello and that we can still use | > Metacello | > :) | > 2) for the SystemChangeNotifier does it make sense to delegate to | > the | > closures? [ xx ] valueWithoutSystemNotifications. Or we add a | > #doSilently: | > and we add a MetacelloPharo20Platform that overrides the behavior. | > 3) as Janko said, what about improving/using Grease/Sport for this | > purpose? | > do they provide something for this? could this be added? | > 4) Should we integrate Metacello in the image with our changes | > until you | > have time and find a good solution that works everywhere? Maybe if | > we do 1) | > it is not very necessary. | > | > Thanks for considering this a friendly and positive thread. | | So instead of lamenting the state of the world I went ahead and wrote | some code. To find out what breaks in Seaside I created new packages | for every Pharo package that didn't work. So I ended up with: | | - Grease-Pharo20-Core | - Grease-Tests-Pharo20-Core | - Seaside-Pharo20-Core | - Seaside-Tests-Pharo20-Core | - Javascript-Pharo20-Core | | You can find them in the Seaside 3.1 repository [1]. I'm not really | sure this was a clever idea but it sounded better than writing a long | mail. | | Things I ran into: | - file system (obviously) | - SystemAnnouncer | - BlockContext is gone | - extension methods are now present on String | - different Float number printing | | File system and SystemAnnouncer are only used by file library. | | Right now two tests fail because the GRPackage dependencies are | inconsistent due to a mix of Pharo and Pharo20 packages. The rest | seems to work, also functionally. | | Things I didn't test or even load: | - OB tooling | - Slime/SLint tooling | | [1] http://www.squeaksource.com/Seaside31 | | Cheers | Philippe | _______________________________________________ | seaside mailing list | seaside(a)lists.squeakfoundation.org | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |

1 0

Re: [Pharo-project] 'self halt' safety net
by Fernando Olivero Aug. 4, 2012

Aug. 4, 2012

What about a Nautilus plugin, that allows browsing all the methods that send #halt, #flag:,#log:? (the "development" messages). Since finding all the halts, doesn't seem something that needs to be performed all the time, an optional Nautilus plugin would suffice. Fernando On Sat, Aug 4, 2012 at 3:02 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Mariano Martinez Peck wrote >> >>> Another thought, are there any plans for a "breakpoint" facility, so that >>> I don't dirty a package by only inserting 'self halt' to aid debugging. >> it already exists. Right click on a method -> Add breakpoint >> > > I, too would love to have the features you suggest. However, as it stands, I > would strongly advise against using breakpoints (someone definitely let me > know, maybe this is not still a problem in 2.0). In my experience, they are > incredibly buggy. Historically: > * if you add a breakpoint in one tool, and try to disable it in another, it > may still be active; and who remembers what tool they enabled it in??? > * there is very little feedback as to when a breakpoint is enabled > - no icon in the browsers > - the menu item was "toggle breakpoint" instead of dynamically "enable" > vs. "disable" > > In all, I found it very confusing to figure out when a breakpoint was > enabled, and how to disable. Of course, anyway, these are not breakpoints as > typically offered by an IDE, which can be attached to any statement, but > only at the method level. > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/self-halt-safety-net-tp4643012p4643070.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

3 2

[Pharo-project] LaTeX formula in Smalltalk
by Hilaire Fernandes Aug. 4, 2012

Aug. 4, 2012

Hello, Java has JLatex a self sufficient package to render latex formula. Is there any interest for a such think in Smalltalk? I guess most part of it could be portable. Thanks Hilaire

2 1

[Pharo-project] RPackageOrganizer does not unregister when we unload MC ?
by Mariano Martinez Peck Aug. 4, 2012

Aug. 4, 2012

RPackageOrganizer default packages select: [:each | each name = 'HistoryCollection'] -> an Array(a RPackage(HistoryCollection)) (MCPackage named: 'HistoryCollection') workingCopy unload. RPackageOrganizer default packages select: [:each | each name = 'HistoryCollection'] -> an Array(a RPackage(HistoryCollection)) I would expect the last line to answer empty... is this a bug? -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] ScriptManager MNU #yellowButtonMenu
by Ben Coman Aug. 4, 2012

Aug. 4, 2012

Using latest ConfigurationOfScriptManager-tbn.21, right clicking in the code window brings up a MNU #yellowButtonMenu. The same occurs with ScriptManager-Core-GuillermoPolito.15 listed in Pharo1.4 Configuration Browser. Given that this is one of the "trusted" configurations, should the issue be logged in the Pharo tracker, or elsewhere?

1 0

[Pharo-project] Completion
by Camillo Bruni Aug. 4, 2012

Aug. 4, 2012

I don't particularly like the current completion mechanism in pharo: - the OCompletion (or what it is called) only displays a limited number of selectors - the second completion (which is complete!) using CMD-Q is in many cases more helpful Could we combine these two? Simply concatenate the two lists and we're done! Where is the place to look for that? best cami

4 6

Aug. 3, 2012

Hi guys I would like to raise this issue while this is calm and that the servers are working. What do we do to replicate our servers: ss3 and smalltalkHub I asked nicolas and christophe to check because the original plan (I still like it) is to host SmalltalkHub servers on INRIA infrastructure and the plan was to replicate it in three nodes of the server rooms across the country. Now we could have a mirroring also between such server and the one hosted by nicolas company. I will start to migrate all my projects from Squeaksource. Stef

2 1

[Pharo-project] Memory usage
by jannik.laval Aug. 3, 2012

Aug. 3, 2012

Dear pharoers, We are loading really big models in the Moose software analysis platform. This generate a lot of small objects and with the biggest model, we approach the limit of 2Gb of the VM. Is it possible for anyone who knows the VM to add extra memory space ? Going to 4Gb or maybe 8Gb would be a great thing. Thank you for your help. Cheers, --- Jannik Laval

8 26

Aug. 3, 2012

http://code.google.com/p/pharo/issues/detail?id=6519 I really love seeing that happens. Thanks camillo! I like that because I spent time cleaning OCompletion to avoid duplication and being able to load it with ECompletion, Esteban did a pass and made my work working and now you give the final touch. I think that this is a good illustration of the power of improving infrastructure step by step and being able to build on the previous step. Stef

1 0