- Pharo-dev - lists.pharo.org

[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

[Pharo-project] Slice and others
by StÃ©phane Ducasse Nov. 5, 2009

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

[Pharo-project] Sockets, events, semaphores, etc.
by Schwab,Wilhelm K Nov. 4, 2009

Nov. 4, 2009

Hello all, Am I falling into a bad area of the image, or does Pharo poll for socket connections? As an example, look at ConnectionQueue>>getConnectionOrNil. Even the Socket waiting methods are all time-bombed. I would expect these methods to wait on a semaphore signalled by the vm on a socket event. It is one thing to offer time-bombed options, but I see nothing event driven at present :( Am I missing something? Bill

3 3

[Pharo-project] gofer cannot load if the package name not well-formed.
by arnaud Jean Baptiste Nov. 4, 2009

Nov. 4, 2009

hi, My named is Arnaud Jean Baptiste, i work with VMMaker and, i have try to load VMMaker via Gofer on Pharo (severals versions of the image, rc, alpha, dev). and then the : when i load the VMMaker package gofer don't find any version and raise a exception. The code: Gofer new squeaksource: 'VMMaker'; addPackage: 'VMMaker'; load. raise a unbound exception. i have open a issue : http://code.google.com/p/pharo/issues/detail?id=1397 I can reproduce the problem with another project like balloon3D

4 8

[Pharo-project] anyone think buttons still too large?
by empty Nov. 4, 2009

Nov. 4, 2009

Hi, 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? Regards, emp ----- åç¡ä½ åç¡æ³ åç¡å§ -- View this message in context: http://n2.nabble.com/anyone-think-buttons-still-too-large-tp3947548p3947548… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1