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

Re: [Pharo-project] Error handling failure during load
by Dale Henrichs Nov. 5, 2009

Nov. 5, 2009

Bill, Have you looked at http://code.google.com/p/metacello? I don't think there's a lot of future tense writing there:). Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Stef, | | The classes in CommandShell-Piping would be better separated from | CommandShell. That said, I do not terribly much care about loading | CommandShell to get pipes - I care a lot that it won't load w/o | proceeding past two warnings followed by a debug/edit/proceed cycle. | I have no idea whether it is a true fix or not, but I commented out | the offending line and re-saved the package, only to find that it | loads w/o hassles. If it really is that simple, the repository should | be fixed. | | Re Metacello, I looked around for information, found a lot of future | tense writing that looked interesting, and went back to cleaning up my | recreation of Migrate for Pharo. The result is not as flashy as | Migrate, but it adds the search for unpackaged code that I wrote | (something I have never found missing in Dolphin given its IDE) and it | seems to simplify saving all packages of interest. | | I will keep an eye on Metacello, but I do not really need it at the | moment. Of greater concern to me is that I am dead in the water on | RC1. The SharedQueue2 bug stops me cold every time I try to build an | image, and strikes in a way that will not allow me to debug it by | normal means. Do we have a procedure for reverting to SharedQueue? | That might at least get me going. | | Bill | | | -----Original Message----- | From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of | StÃ©phane Ducasse | Sent: Thursday, November 05, 2009 1:42 PM | To: Pharo-project(a)lists.gforge.inria.fr | Subject: Re: [Pharo-project] Error handling failure during load | | | On Nov 3, 2009, at 5:17 PM, Schwab,Wilhelm K wrote: | | > Hello all, | > | > I am gradually approaching a working load "script," but I just hit a | | > new wrinkle in RC1: at some point in the process I get offered an | > emergency evaluator, which appears unable to open. There is mention | | > of looking for something in the system dictionary, and something | about | > "system error handling failed." Nothing is logged, and the image is | | > helpless at that point. Any ideas for how to debug it? | > | > Creating my own build log comes to mind; the idea would be to open/ | | > update/close each time it starts work on a new package. I can also | | > load the loader into a clean older image and see what happens. | > | > It would be _really_ nice to have a clean-loading version of OS | > Process/Command Shell. Actually, I do not need the shell at all, | but | > I do need the pipeable processes. | | damien told today that it would be nice that some CommandShell class | such as (I do not remember) StdOut/SdtIn could be packaged with | OSProcess and not with CommandShell. Or that they are separated | because people want to get them but not need the CommandShell. | | Now bill did you got a look at Metacello? | Because I'm sure it can help to maintain your packaged code. | | Stef | | | | > | > Bill | > | > | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project(a)lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] RC1 image build failure
by Schwab,Wilhelm K Nov. 5, 2009

Nov. 5, 2009

Hello all, Whatever is happening, it keeps happening, and on two different machines, but both Ubuntu 9.10, FWIW. Attached is a shot of the whatever-it's-called window; the promised emergency evaluator does not appear (not that I would know what to do with it<g>). Comparing SharedQueue with SharedQueue2 might be interesting; with luck, there will simply be a missing method?? Bill

3 7

[Pharo-project] Juan Cook has invited you to Dropbox
by Dropbox Nov. 5, 2009

Nov. 5, 2009

We're excited to let you know that Juan Cook has invited you to Dropbox! Juan Cook has been using Dropbox to sync and share files online and across computers, and thought you might want it too. Visit http://www.getdropbox.com/link/20.cqyZ1lxSZM/NjQ3MjkzODM3 to get started. - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.getdropbox.com/bl/568088f42f89/pharo-project%40lists.gforge.inri…

1 0

[Pharo-project] New Pharo based on core 10493
by Damien Cassou Nov. 5, 2009

Nov. 5, 2009

http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] Making packages shipped with Pharo ready for 1.0
by Adrian Lienhard Nov. 5, 2009

Nov. 5, 2009

Hi, I've more closely looked at the failing tests and undeclared references in the Pharo image. The test result is 14 expected failures, 34 failures, 54 errors, 2 unexpected passes. Considering that the Pharo-core ships with all tests green, this situation needs to be fixed. I urge the package maintainers to closely look at the list below and provide fixes and cleanups of their code. There are also 9 tests failing from Pharo-core. I will take care of those. Nil ----- - Sends deprecated message: #findLastOccuranceOfString:startingAt: - A test opens a workspace that says: "Squeak is a beautiful language. Look at http:\\www.squeak.org ..." - Another test opens another workspace - NSBuffer has method that references an undeclared variable 'collection' - undeclared reference to GradientFillMorph, StringSocketStream - Total failing tests: 10 - Total tests with errors: 11 ECompleteion ------------ - 7 tests failing - 2 errors O2 -- - #dropOnClass: references InputSensor (this class does not exist anymore!) - 15 undeclared references to OB* classes, to non-existent variable hasChanges, modifiedTimeStamp, smartGroup, and sensor - 11 failing tests - >30 tests with errors OB ------ - undeclared references: HttpResponse, Json, JsonObject - #dropOnClass: references InputSensor (this class does not exist anymore!) NewInspector ------------ - undeclared reference automaticallyHideIfNoChild - NewInspector DNU #inspect (sent in #testSymbolTableM6812) Shout ----- - undeclared variable sourceMap RB -- - undeclared reference to RBBasicLintRuleTest and RBTransformationRuleTest Pharo-core tests failing ------------------------ - FontTest>>testFallback (assumes different font, to be removed) - FontTest>>testParagraphFallback (assumes different font, to be removed) - FontTest>>testResetAfterEmphasized (assumes different font, to be removed) - StandardSystemFontsTest>>testRestoreDefaultFonts (assumes different font, to be removed) - TestIndenting>>testNewLineStartsIndentedWhenWrapped (assumes different font, to be removed) - TestIndenting>>testSetUp (assumes different font, to be removed) - LocaleTest>>testIsFontAvailable (some Japanese font checking that fails with DejaVu, to be removed) - testFinalizationOfEquals (was on my to do list, but works again: remove expected failure tag) - testObsoleteClasses: again includes classes from MC and others (have to be checked) MorphExamplesAndDemos --------------------- - undeclared references to DescriptionForPartsBin and ScreeningMorph Cheers, Adrian BTW, Damien, do we know for each package who the maintainer is? Does each package have one?

8 15

[Pharo-project] anyone think buttons still too large?
by Stephan Eggermont Nov. 5, 2009

Nov. 5, 2009

> From: empty <emptist(a)googlegroups.com> > I tried to install version 1 rc to find the buttons still too large. > > If you look at the whole class browser the first things you see are > those > big blue buttons. I'd prefer they not so big and colorful. > > Anyone have the same feel? Yes, I even played around with a painting tool and started digging around in Toolbuilder, OmniBrowser and PolyMorph. Let me just say that I really, really, really like Glamour. See issue 909 Stephan Eggermont

2 1

[Pharo-project] stupid but very intrigued question
by Esteban Lorenzano Nov. 5, 2009

Nov. 5, 2009

Hi, I was downloading a new pharo-core image (to load some iphone development tools into it), and I see the pharo-core alpha for 1.1... and the image size diference is SO BIG, that I wonder why... What is droped to get an image so small? Cheers, Esteban

3 2

[Pharo-project] Underscore assignments
by Torsten Bergmann Nov. 5, 2009

Nov. 5, 2009

+1 -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

8 16

Nov. 5, 2009

Hi guys I would like to generalise the slice ideas so that even if you publish a single package change you use a slice because I'm spending time to look for these simples changes in single packages. What do you think? Stef

4 6

[Pharo-project] A couple more thoughts about Announcements
by Igor Stasenko Nov. 5, 2009

Nov. 5, 2009

As far as i can see there is no 'capture' scenario, i.e. tell announcer to not broadcast the announcement to all subscribers, but only exclusively to a single one, who requested the capture. In AXAnnouncements there is an 'interception' , using which you can achieve the similar result, except that interceptor is added to each subscription, meaning that you will receive intercepted announcement + additional data as many times as the number of subscriptions registered. Such scenario, as capturing events used heavily in UI, but not only by UI of course. So, suppose we made a Sensor which using announcer to broadcast its events. And there are cases, when you need to get an exclusive capture of all (or specific kind of events) for a single subscriber, without letting them handled using normal flow, until some condition met, when you are releasing capture. Two examples: - mouse capture usually, when you start dragging the stuff, you start capturing mouse events, and release the capture once mouse button released. All widgets, over which you dragging a mouse, should not receive any mouse events, or receive a different event such as 'draggedOver' etc - keyboard focus pass all keyboard events directly to widget which currently has focus - some code examples, by using brute force establishing a loop which consuming all sensor events until mouse button released or key pressed. All of these cases can be supported by adding few things to announcer: - tell announcer to insert a subscriber at the starting of the subscribers list (instead at the end), so it will be first who receive the announcement - make announcer to stop broadcasting announcement down the list, if particular subscription returns false as result of #handle: - when you unsubscribe, things get back to normal without any extra effort and voila.. we can implement a mouse capture, keyboard focus, filtering and event transforming scenarios. -- Best regards, Igor Stasenko AKA sig.

1 0