- Pharo-dev - lists.pharo.org

Re: [Pharo-project] New much faster Pharo based on 10379
by David RÃ¶thlisberger July 18, 2009

July 18, 2009

> OK then we should ask david if > - he addressed the check removal > - found the problems with the menus? The check removal I addressed, but the menu problems not yet. I will be away the next three weeks, I can't work on this during that period. But I will look at it when I'm back (Aug 10). But I really suggest to not load OB-Enhancements if you do not want to use the package browser at all. David > On Jul 18, 2009, at 11:00 AM, Lukas Renggli wrote: > >>> can you disable the annotation pane too? >> >> Yeah, the annotation pane is extremely slow. I never use it myself. >> >>> Could you also load the packageBrowser so that we can pick the other >>> one too? >> >> I don't think that would work with the code that is used in the image >> Damien created. The OB code in this image does not contain the slow >> extra checks that were hacked into the core code to make the package >> browser functioning. Furthermore the normal browser is not really >> useable if the package browser is loaded, because menu items are >> missing and strangely positioned to the point it is not useable >> anymore. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

2 1

[Pharo-project] LocaleTest >> #testIsFontAvailable failing
by Philippe Marschall July 18, 2009

July 18, 2009

Hi LocaleTest >> #testIsFontAvailable is raising an exception in my image. The problem is that LanguageEnvironment >> #isFontAvailable sends #fallbackFont to a LocigalFont which does not understand this message. The #realFont of the logical font is a FreeTypeFont which doesn't understand #fallbackFont as well. Cheers Philippe

2 1

[Pharo-project] optimizing select:thenCollect:
by StÃ©phane Ducasse July 18, 2009

July 18, 2009

Hi all apparently Collection>>select: selectBlock thenCollect: collectBlock "Utility method to improve readability." ^ (self select: selectBlock) collect: collectBlock so it would be good to avoid to do two passes on the same collection. Any takers? Stef

9 24

[Pharo-project] Seaside for html generation
by Schwab,Wilhelm K July 18, 2009

July 18, 2009

Hello all, I am loading a fair amount of code into Pharo, trying to get something working. SIF has worked well so far. The system in question will be Seaside based, but it will start life as a glorified spam generator :) Its operator will use some Seaside forms to tell the system about new data, edit the data to eliminate human errors, and then tell it to send emails based on the remaining data. The emails will be just complicated enough to benefit from html formatting. Yes, the users should be told only to visit the site to retrieve their electronic lashes via Seaside, but that will not happen over night - they haven't thought of it yet ;) The _real_ reason is that I still have to sort out the authentication mechanism. The dumb question: can I simply create a WACanvas, send some messages, and get the rendered html? Any ugly side effects of doing that? I ask because I have code for Dolphin that does the job, but it seems silly to load it into an image with Seaside. Bill

2 2

[Pharo-project] questions - class variable convention & Magritte arrays?
by Cameron Sanders July 18, 2009

July 18, 2009

-- Three questions regarding implementing singletons: 1. the convention is to use an initial cap for class variable names, correct? (even though it is not required...) 2. Magritte will likely be used. And I have not dug too deeply. My current (temporary/stepping stone) class is Object subclass: #FaFnBasicKeyLabelAssociations instanceVariableNames: '' classVariableNames: 'TheSingleton' poolDictionaries: '' category: 'FA-FinanceMeta' But I realized that I need even more information than (the basic) Magritte in some cases, and the "Fn" part of the name up above is really referring to financial series (multi-year data). The length of the series varies (depending on what is available). So the question is: does magritte have any capabilities (classes) for handling list display/edit as well as SQL access? Or is that something I will need to build? [And a "yes, read the manual, you idiot!" answer is helpful!] Thanks in advance, Cam

1 0

[Pharo-project] Save and quit vs. Save - a clue to performance???
by Schwab,Wilhelm K July 17, 2009

July 17, 2009

Hello all, I've noticed something that seems unusual to me. Choose save and quit, and the writing cursor appears, disappears, and the image is almost immediately gone after that happens. Choose save, and the cursor appears, sticks around for about the same amount of time as for save and quit (this part is a little bit of a stretch), and then the image becomes unresponsive for (depending) one or more seconds. Anything? When combined with comments people have made about the event loop, I wonder whether the system idles when it should not, or something like that??? Sorry if this is a wild goose chase. Bill

3 13

[Pharo-project] What is the story for fasterSets
by StÃ©phane Ducasse July 17, 2009

July 17, 2009

Hi guys what is the conclusion for the faster sets? Stef

3 3

July 17, 2009

> > > what is the status of the integration of these changes? > > Stef > > On Oct 1, 2008, at 10:53 PM, Damien Pollet wrote: > >> Hi list, we (with Stef) are browsing Kernel-Extensions, here are some >> notes for discussion, as we think there is stuff that should be >> merged >> in Pharo. >> >> Null and Split-Join could be packaged on their own since they are >> well-defined features. >> >> Most of the cleanup methods make sense, but what's the difference >> between cleanUp and freeSomeSpace ? >> >> AppRegistry class >> removeObsolete >> "AppRegistry removeObsoleteClasses" >> self registeredClasses copy do:[:cls| >> (cls class isObsolete or:[cls isBehavior and:[cls isObsolete]]) >> ifTrue:[self unregister: cls]]. >> self subclasses do:[:cls| cls removeObsolete]. >> >> Behavior class >> flushObsoleteSubclasses >> "Behavior flushObsoleteSubclasses" >> ObsoleteSubclasses finalizeValues. >> >> Behavior >> sourceMatchesBytecodeAt: >> >> Class class >> freeSomeSpace >> "Fix some problems with classes. Use Smalltalk allClassesDo: since it >> does not use the subclass list, which we may be modifying during this >> iteration" >> Smalltalk allClassesDo: [:ea | >> ea fixObsoleteSuperclass. >> ea removeDuplicateSubclassEntries] >> >> Collection >> contains: should probably be standardized as part of >> the STEPS project >> Collection >> reject:thenDo: and select:thenDo: should be >> included and similar enumerations reimplemented in this way too >> >> SystemDictionary >> forgetClass: aClass logged: aBool >> badly >> named but interesting >> "Delete the class, aClass, from the system. >> Note that this doesn't do everything required to dispose of a >> class - >> to do that use Class>>removeFromSystem." >> >> aBool ifTrue: [SystemChangeNotifier uniqueInstance classRemoved: >> aClass fromCategory: aClass category]. >> SystemOrganization removeElement: aClass name. >> self removeFromStartUpList: aClass. >> self removeFromShutDownList: aClass. >> self removeKey: aClass name ifAbsent: []. >> DataStream classRemoved: aClass. >> self flushClassNameCache >> >> SystemDictionary >> globals needs to pay attention that compiled >> methods share the associations >> >> Number >> to: stop do: aBlock displayingProgress: aString would >> be >> probably nicer with the block argument last >> >> >> === To discuss: >> >> Collection >> removeAll: comment should explain in which cases >> it is useful >> "the slow way" >> ^ self removeAllSuchThat: [ :each | true ] >> >> SequenceableCollection >> <= smells funnyâ¦ what is it useful for ? >> SequenceableCollection >> replacing:with: replaces in place, not >> obvious from the name >> the stream methods like putOn: â¦ convenience ? are they coherent ? >> >> String >> withoutTrailing: probably makes sense but then this is >> mostly useful for line breaksâ¦ why not a #trimLinebreak >> >> Set >> likeOrAdd: ok but then that should be available for any >> collection (and renamed addIfAbsent:) >> "Include newObject as one of the receiver's elements, but only if >> not already present. Answer the oldObject." >> >> >> === Useless: >> >> ProtoObject >> iconOrThumbnailOfSize: >> Object >> askFor: and askFor:ifDefault: that's a workaround >> >> Object >> deprecated is already here >> Object >> log should be packaged in a logging package since it's a >> convenience method >> >> SequenceableCollection >> copyReplacing:with: just to type one >> space less ? >> >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > >

2 1

[Pharo-project] WAKom
by Robert Sirois July 17, 2009

July 17, 2009

WAKom doesn't work in Pharo? I believe I have the correct image and VM: I'm getting the following from 'WAKom startOn: 9050': 'BlockClosure(Object)>>doesNotUnderstand: #newProcessWithBindings:' Thanks, RS _________________________________________________________________ Lauren found her dream laptop. Find the PC thatâs right for you. http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290

3 3

[Pharo-project] FillInTheBlankMorph and SimpleButtonMorph
by Alexandre Bergel July 17, 2009

July 17, 2009

This trigger an error when using FillInTheBlank for exemple. Doit: FillInTheBlankMorph request: 'enter something' creating an empty method updateVisualState: in SimpleButtonMorph seems to solve the problem although. Issue #957 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1