December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] getting rid of Symbol >> new: ?
by StÃ©phane Ducasse Jan. 20, 2010

Jan. 20, 2010

> From: Sheridan Mahoney <sheridan(a)sheridan-mahoney.com> > Date: December 3, 2009 11:04:19 PM GMT+01:00 > To: pharo-project-bounces(a)lists.gforge.inria.fr > Subject: Re: getting rid of Symbol >> new: ? > Reply-To: sheridan(a)sheridan-mahoney.com > > > A colleague and I are investigating the ImageSegment class and its methods, we came across an issue I would like to get external opinions on. Newbie alert, BTW (at least one of us, no names mentioned...). Also, this is not a problem that will affect many users, but it is familiarizing us with the check-in process, slices, etc. While working on ImageSegment tests, we discovered a problem on trying to load segments that had Symbols in the root array. It is possible to create 2 ByteSymbols with the same sequence of characters. :( In trying to track down how this is possible, we came across a side issue, that ByteSymbol new: had the capacity to create multiple new ByteSymbols with the same number of nil characters (as in, initialized with nil). We want to dissallow Symbol new: , which would cause people to use one of the nicer methods for Symbol/ByteSymbol creation (namely, one which checks that the sequence of characters doesn't already exist, as part of the creation process). We have a fix we want to check in, but currently it breaks a test case in the SymbolTest class, which is checking that new: works. We also changed the intern: method on the class side of Symbol to use basicNew: instead of new: . Are there reasons to keep 'Symbol new:' , that outweigh the reasons to get rid of it? > Many thanks, > and Cheers, > Sheri Mahoney

8 31

[Pharo-project] Refactoring Browser depenences
by Mariano Martinez Peck Jan. 12, 2010

Jan. 12, 2010

Lukas: I am doing a Metacello ConfigurationOfRefactoringBrowser and I see I need these three packages for pharo: AST-Core Refactoring-Core Refactoring-Spelling Now, my question is, do you know the depences between them ? Rught now I noticed Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core There are more ? and dependences with external packages? Thank you. Mariano

3 16

[Pharo-project] [BUG] Bitmap DejaVu Sans / WideString
by Lukas Renggli Jan. 11, 2010

Jan. 11, 2010

Bitmap DejaVu Sans displays WideStrings in unpredictable ways. Looks like there is a bug in StrikeFont? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

3 3

[Pharo-project] Core font
by Torsten Bergmann Jan. 11, 2010

Jan. 11, 2010

The squeak trunk has a nice looking default font compared to pharo core (without Freetype). Wasnt that related to some Cuis changes that were also integrated into Pharo already? Any chance we can get that too? Just curious... Thx Torsten -- DSL-Preisknaller: DSL Komplettpakete von GMX schon fÃ¼r 16,99 Euro mtl.!* Hier klicken: http://portal.gmx.net/de/go/dsl02

5 4

[Pharo-project] Pharo for Professional Development
by Bart Gauquie Jan. 11, 2010

Jan. 11, 2010

Dear all, I've been using Squeak before, now I'm using Pharo. Its still 'hobby' usage. However, on my firm, we have a lot of working groups in which we investigate new technologies. We mainly use Java / .Net. I've initiated a working group around Smalltalk/Seaside. And chose Pharo as a smalltalk platform/dialect, mainly because its free and adaptable. I'm a fan of it, but my colleagues of it have some doubts about it. I know that its not finished yet, and that a lot of improvements are ongoing. The main 'complaint' about Pharo is that the environment is not stable. In a lot of the tools you get exceptions, errors, it breaks something, stuff like that. Thats a shame off course. I expect in an environment that everything just works. We are using Eclipse in our day to day work; nowadays, Eclipse is quite fast and is reliable. Pharo is more or less fast enough, but still not reliable. There are too much 'dead links', messageNotUnderStoods I mean. For instance on latests browse package is not working on the Class Browser. On the Pharo 1.0 branch, there are also dead links here and there. So therefore my question: I highly support that Pharo wants to innovate ; BUT as a developer I first expect that every tool works perfectly, that I can trust it. Furthermore, since Smalltalk environment is written in itself, I expect that every tool is also thoroughly unit tested to avoid regression on the tools. I don't know if it is possible to test the Morphic windows in Pharo. Rephrasing: I think we should focus a lot on making the current system stable, and keeping it stable; and focus on fixing bugs asap (and not just quickly fixing the bug, first at least write a test for it). All these new stuff like NewCompiler, Settings, in the 1.1 are very valuable stuff to add; but we should really keep focusing on stability. I'm saying this because, what I've noticed is that my colleagues are trying the other smalltalks like Cincom; the only reason that that they are doing this , is because the environment is not stable enough: I suspect that a lot of other people are also doing this? I've noticed that there are quite some regression bugs (for instance: http://code.google.com/p/pharo/issues/detail?id=349) it worked in version x but now is not working anymore. If you have a lot of these, you lose a lot of time. I'd rather make one slow step forward, instead of rushing forward and having to back up. Furthermore I still had some other tools I found very useful in my day to day work that I'm missing in Pharo - Proper keyboard shortcuts: see other thread, did not have time yet to put something on wiki - History of a file: you can always check the local history of a file (comparable with the versions of a message in Pharo), but you can in the same view also see the version of the file on the repository - regardless which versioning system you're using. And quickly open these versions, select 2 of these versions and compare them with each other. This is very valuable tool if you're developing with a lot of people on the same to see every version created and quickly be able to compare them. Is there such functionality in Pharo ? - ... Any thoughts on this? Kind Regards, Bart -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein Gravitation is not responsible for people falling in love. - Albert Einstein

15 43

[Pharo-project] Pharo-beginner mailing list ?
by StÃ©phane Ducasse Jan. 11, 2010

Jan. 11, 2010

Hi all I remember that the squeak-beginner mailing-list (our ideas) was a huge success since it enabled people to ask questions and have less mails. So a question to you: do you think that it would be good to have a pharo-beginner mailing list? Stef

13 26

[Pharo-project] Pharo testers.... WE NEED YOU!!!
by Mariano Martinez Peck Jan. 8, 2010

Jan. 8, 2010

Ok, you already know the idea. Damien, or the person that build the next Pharo dev and web images will send those Pharo beta testers a private email with the link to download the image. No ANN and now update is done yet to the website. Then the betatesters use that image as much as possible for a couple of days. Report bugs if necessary and if it is ok, the image is released. Regarding the list of beta testers would be perfect if we cover the combination of OS (Linux, Mac, Windows) and the browser (OB, O2). But we cannot pretend too much. Take into account that not all the people can work with a new image very easily because they have to migrate data ...etc..Others can just download the project from MC and start to work :) So...here is the list, if you offer yourself, it would be cool to know: OS, VM version, Dev or Web, browser you usually work, 32 o 64 bits, I will then collect this and I will put it in the wiki. - Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, Dev, OB, 32 bits - Stan Shepherd WHO ELSE IS IN THE LIST ?? cheers and happy new year!!

15 33

[Pharo-project] Simple question about NewInspector
by Mariano Martinez Peck Jan. 7, 2010

Jan. 7, 2010

Hi Frederic. I am trying to see if it make sense to create a metacello configuration for NewInspector. The only external (not in PharoCore) dependency I saw using the DependencyBrowser is RoelTyper, which is used in the class NICompiledMethodNode >> configuration you use the class TypeCollector which is from RoelTyper. So, the question is, is this dependency correct? I ask because I took a PharoCore image, load NewINspector WITHOUT RoelTyper and it "seemed" to work. Thank you very much. Mariano

4 6

[Pharo-project] Beginner question :) search and replace in String
by Adrian Kuhn Jan. 7, 2010

Jan. 7, 2010

Method finder does not find a method for 'foobarqux' . 'bar' . 'XYZ' . 'fooXYZqux' and stupid me couldn't find a method on String either. How to get this done? +10 internets for solution with regex. --AA

8 25

[Pharo-project] ImageSegment fixes in Inbox
by Mariano Martinez Peck Jan. 5, 2010

Jan. 5, 2010

Hi! After several days of surfing the beatiful ImageSegment code, I fixed several issues. I commit to Inbox the SLICE-FixesToImageSegment. This are the changes in my commit: - Removed Beeper beepPrimitive from ImageSegment >> install - Fix to writeToFile. See issue 1204 http://code.google.com/p/pharo/issues/detail?id=1204 - Now ImageSegment >> discoverActiveClasses answer the number of them - New method ImageSegment >> unActiveClasses - Fix to ImageSegment >> swapOutInactiveClasses. I have to hold the allSymbols and to exclude the Multilingual and Kernel package from the swap. This should fix issues 1203 and 1204. - The errors for wrong states now print the current state and also the expected one. - Fix issue 207. Take a clean image and evaluate: Smalltalk at: #MDFaultDict put: Dictionary new. Then | count | count := ImageSegment discoverActiveClasses. Transcript show: 'Classes forced: ', count asString. Do something And finally evaluate | count | count := ImageSegment activeClasses size. Transcript show: 'Classes active ', count asString. or | count | count := ImageSegment unActiveClasses size. Transcript show: 'Classes active ', count asString. Whit this, there is no trace. Even if puting the dictionary. A simple hack to see this is to change activeClasses to use recoverFromMDFaultWithTrace instead of recoverFromMDFault If you do that, you will be able to inspect Smalltalk at: #MDFaultDict I also fixed the swapOutInactiveClasses. The image have several emergency windows before this.

2 4