- Pharo-dev - lists.pharo.org

[Pharo-project] I'm harvesting nicolas fixes...
by StÃ©phane Ducasse Oct. 9, 2008

Oct. 9, 2008

1 0

Re: [Pharo-project] Monticello: an idealist question
by Bill Schwab Oct. 9, 2008

Oct. 9, 2008

Dolphin has been running on Wine for a while, so get a community edition copy and give it a try. Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> pennell.david(a)gmail.com 10/9/2008 10:44 AM >>> VW runs has been on Linux since about 2001. On Thu, Oct 9, 2008 at 9:26 AM, Matthew Fulmer <tapplek(a)gmail.com> wrote: > > I really wish I could try out Dolphin and VW and see what I am > missing, but they don't run on linux. >

1 0

[Pharo-project] how to register a tool in the open menu?
by StÃ©phane Ducasse Oct. 9, 2008

Oct. 9, 2008

Hi guys does one of you know how when I load a package I can get an entry in the open... menu? Stef

3 7

[Pharo-project] Pharo one click on Win32 - VM fix available + new Freetype plugin
by Torsten Bergmann Oct. 9, 2008

Oct. 9, 2008

The Pharo one click VM for Win32 still has the full screen problem, which is already fixed for Squeak by Andreas with a newer VM. See http://bugs.squeak.org/view.php?id=6818 for details and the new sources. There is also a new build of the external Freetype Plugin. See http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-October/131889.… Thx Torsten -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

1 0

[Pharo-project] Polymorph
by Gary Chambers Oct. 9, 2008

Oct. 9, 2008

Just to let you know there are some newer versions on SqueakSource. Start of work on a "Watery 2" theme (more spotted cat like :-) ) using CompositeFillStyles with form-based graphics. A few other improvements too, check the version notes. Regards, Gary.

3 3

[Pharo-project] 10089-10090
by StÃ©phane Ducasse Oct. 8, 2008

Oct. 8, 2008

Hi 10089 fixes the bookMorph 10090 introduces a nice features added to Sunit - the possibility to store the results of tests run and to compare the results This way you can get a package and evaluate if when you run them you really broke something or improved the tests. Now the browser could take avantage of that information. Stef

1 1

[Pharo-project] Two problems yesterday
by Bill Schwab Oct. 8, 2008

Oct. 8, 2008

Hello all, After a few days of getting mostly nothing from an evolving Seaside+Apache setup, I got it running. A lot suddenly happened on two machines, and there is no telling what I might have done to cause trouble on my own. Anyway, two things deserve mention. Sorry to throw these at you, but I think I can explain one of them. The first problem might have been continuations in action. I use streams often and will somewhat frequently read files as I process them, using #ensure: to close them. It ends up looking like in := FileStream read:fileName text:true. [ "code that might raise an error" ] ensure:[ in close. ]. Despite this construction, I ended up with errors trying to open a file, and ended up closing and reopening Pharo to regain access to it. In Dolphin, that was an almost certain sign that I had not properly ensured the closing of a stream. Based on recent discussions of #terminate, I began to suspect that closing the debugger thwarted the ensure block. However, I note that [ nil halt. ] ensure:[ Transcript show:'Did it'. ]. has been doing pretty much what I expect it to do: close the debugger and the block executes. So, I suspect what in fact happened is that a continuation caused me to re-open the file before it was closed. I am starting to like Seaside, but I wish it were based on threads and synchronization objects, but that's another topic. Whether or #ensure: behaves correctly in response to #terminate is something I need to check. For now, I will probably read the file into memory and close it before Seaside gets involved. The second thing that happened was I ended up with an image in which the system browser was out of synch. Clicking on the name of one method would show source for another. When I saw that, I assumed the change log had been clobbered, but not knowing what else to do, I exited w/o saving and recreated what I had lost in the process. The recovery was probably not what you would think. I had been coding on "the other machine" (win2k3 image on a blade via remote desktop), and was trying to integrate a few things into my "real" image (on my local machine) that I did to get the Seaside app working. Somewhere in that process, the browser mess started. I did something along the lines of firing off a new browser (probably from a method I was editing) to add a new method. I have noted that Pharo gets a little upset, (correctly) warning about possible changes elsewhere. The simple explanation is that this time, it "mis-filed" what I did in that new browser. Specifically, I (most likely) overwrote everything and accepted the source of the method. Sorry for the lengthy and un-confirmed guesswork masquerading as a bug report. I'm not sure I _want_ to reproduce it :( Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

1 0

Oct. 8, 2008

Begin forwarded message: > From: "HernÃ¡n Morales Durand" <hernan.morales(a)gmail.com> > Date: October 8, 2008 8:17:40 PM CEDT > To: "The general-purpose Squeak developers list" <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] [ANN] Dependency Browser > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Dear Squeakers, > > If you ever wondered how to observe dependencies between > packages in the image, now you can use this new Dependency Browser. > Instructions for using it are in the following pages: > > Castellano : http://cs.hernanmorales.com.ar/DBrowser-es.php > FranÃ§ais : http://cs.hernanmorales.com.ar/DBrowser-fr.php > English : http://cs.hernanmorales.com.ar/DBrowser-en.php > > Regards. > > HernÃ¡n > >

1 0

Oct. 8, 2008

Hi marcus removed methodFinder and I understand the reasons (lot of list of old method selectors hardcoded and not maintained). Still I think that MethodFinder was a really cool tool. So is there somebody that would like to have a look and take an old pharo version, package MethodFinder and clean it. This would be great. Stef and Marcus

2 3

[Pharo-project] [updates] 10088
by Marcus Denker Oct. 8, 2008

Oct. 8, 2008

Issue 218: Enhancements collected by gary and simon 1. Fixed flaky borwser comment text area sometime not showing. 2. Added getArgumentPermutation to support RefactoringEngine. 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner to correctly align the first line of text when centered/justifed etc. 4. Added more constant names to Character class. 5. Modified ConnectionQueue to not accept connections when queue is full. 6. Changed GrafPort to answer a MultiDisplayScanner when appropriate (allows subclasses of MultiNewParagraph). 7. NaturalLanguageTranslator startup postion move to after PasteUpMorph since it will show a progress bar. 8. Fix to Random>>nextInt: to allow large numbers which would be out of range if using Floats (as mentioned recently on dev, use of Floats is dodgy anyway...) 9. Changed TranscriptStream>>clear to use a new buffer (was just reset which could leave a massive collection). 10. Changed RemoteString to handle concurrent processes safely. This ones particularly interesting: we were load-testing our Seaside app here and getting lots of syntax errors when hitting the image with around the 20 concurrent processes due to source file access. After this change we were hitting it with approximately 500 concurrent processes, and the failure was in the Java load tester (it timed out). Issue 224: random cleans - removeColorSwatch.1.cs: remove class ColorSwatch Issue 221: cleanup: remove methods calling isThisEverCalled - remove some methods that where deprecated in 3.9 - remove all methods with calls to #isThisEverCalled Issue 222: methods from NewCompiler - some method from newcompiler/Reflectivity that are better directly in the base (accessors, mostly) Issue 199: remove MethodFinder - finding methods by name is done by "Method Names", too - it s >1000 lines of Code. - it has a list of all selectors of a very old Squeak version. Many methods are only referenced here, thus they can not be found using the tools to find unsent mesages. postscript: Smalltalk removeClassNamed: #CardPlayer59. Smalltalk removeClassNamed: #Player58. SystemOrganization removeEmptyCategories. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

4 7