February 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Basics...Pluggable..Morphs on change
by S Krish Feb. 6, 2012

Feb. 6, 2012

I am checking out on the basics of the PluggableTextMorph and PluggableListMorph .. and its cousins. PluggableListMorph >> changeModelSelection: anInteger setIndexSelector ifNotNil: [model perform: setIndexSelector with: anInteger]. here it is the responsibility of the model to send #changed: getIndexSelector. why..? why not a simpler generic: changeModelSelection: anInteger setIndexSelector ifNotNil: [model perform: setIndexSelector with: anInteger]. "sends the call to all dependents of the model implicitly" * model perform: #changed: with: getIndexSelector * thereof the models anywhere need not bother sending #changed: calls... ! similarly: acceptTextInModel ..... [^setTextSelector isNil or: [setTextSelector numArgs = 2 ifTrue: [model perform: setTextSelector with: acceptedText with: self] ifFalse: [model perform: setTextSelector with: acceptedText]] ] ensure: [unstyledAcceptText := nil]. * model perform: #changed with: getTextSelector* *We can avoid these in the methods if implemented across all Pluggable??Morphs * Workspace class>> openContents: aString ^ self new open; contents: aString; "funny is this itself calls #changed:" "changed: #contents;" yourself Makes common sense to me.. rather than expecting the model to explicity call #changed:..this "view" / widget knows its model and it implicitly invoking #changed: is cleaner abstraction, unless a use case exists which may break infrastructure/ whole base doing this.. This way all models associated with various Pluggable??Morphs will work perfectly fine on just a setter call without extra line being added everywhere in the application code, apps need to bother about changes to other symbol viz: updating a list selection index causes another widget to refresh its content..

3 2

[Pharo-project] Debugger filtering
by Camillo Bruni Feb. 6, 2012

Feb. 6, 2012

In the latest Pharo Release we pushed a new Setting for the Debugger: see Settings / Debugging / Filter out common message sends, when enabled the Debugger behaves a bit nicer in most cases by filtering some non-interesting contexts: - "self halt" will now open the Debugger in the sender context, not somewhere on Halt / Object - sends to Kernel Classes are not shown (like Dictionary >> #at:ifAbsent: #do: #collect: ...) - a failing TestCase will open the Debugger in the test method itself So all in all it will save you some clicks and concentrate on the important stack elements For those interested in the details or wanting to extend it see Debugger >> #shouldDisplayContext: best cami

4 3

[Pharo-project] [update 1.4] #14316
by Marcus Denker Feb. 6, 2012

Feb. 6, 2012

14316 ----- Issue 5251: Remove MCWorkingCopy from startup list http://code.google.com/p/pharo/issues/detail?id=5251 Issue 5167: Fix weak finalization thrashing - improve interrupt behavior http://code.google.com/p/pharo/issues/detail?id=5167 Issue 5224: move deprecated methods from category convenience-inspecting in ToolRegistry to deprecated14 http://code.google.com/p/pharo/issues/detail?id=5224 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.4] #14314
by StÃ©phane Ducasse Feb. 6, 2012

Feb. 6, 2012

14314 ----- - Issue 5233: Support Semantic Source Links. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=5233 Now when you press command while clicking on a class name you jump to the class :). Same for the click on a method name and instance variable. Pay attention that this change should really be changed on windows and linux. So please give us feedback. Camillo will do a fix so that menu appears on click down versus click up.

5 5

[Pharo-project] Creating a file with FS
by stephane ducasse Feb. 6, 2012

Feb. 6, 2012

Hi FS users I'm puzzled by FS api. I want to create a file in a directory so I did | wk | wk := FSFilesystem disk workingDirectory. (wk / 'CSS2') ensureDirectory worked Now I looked at ensureFile and I do not understand the code ensureFile "Create if necessary a file for the receiver." self writeStream close. Because I would like to be able to write in the file and now I do not see why closing it is good. Would be good to add comments to FSReference>>writeStreamDo: doBlock ifPresent: presentBlock "Create a file if not present and execute doBlock (with a stream) as argument, if the file is present execute the presentBlock." ^ self isFile ifTrue: [ presentBlock value ] ifFalse: [ self writeStreamDo: doBlock ] FSReference>>writeStreamIfPresent: presentBlock "Return a writestream on the receiver if it does not already exist or execute the presentBlock with no argument" ^ self isFile ifTrue: [ presentBlock value ] ifFalse: [ self writeStream ] I do not get why we do not get as argument to the presentBlock the file itself? I added method commentsâ¦. as usual. :( Camillo could you have a look at such comments and commit them? I published the package to the fs package. Would be good to cross check and that I add it in 1.4 Stef

4 3

[Pharo-project] FOSDEM devroom
by Stephan Eggermont Feb. 6, 2012

Feb. 6, 2012

Yesterday we had a nice day filled with great presentations. Getting to Brussels the day before proved to be a challenge, as the Dutch railways showed to have lots of trouble with 3 cm of snow and a cold night. Andy showed us a good place to eat and talk near the Central Station. In the end all presenters managed to be on time and the whole day ran smoothly. As the devroom was the second day of FOSDEM, we thought it wise not to start too early. That was a good idea, as the ULB was still very quiet when Norbert showed us how to create REST/json/xml based services. Markus followed with the Pharo Vision. Gradually more people came to the devroom until the jQueryMobile presentation was so filled that we had to refuse people entering the room. The Amber presentation also attracted a lot of people new to smalltalk. The ability to create a fast feedback cycle apparently is a major issue for javascript developers. The progress made since ESUG2011 is impressive. The next subjects (working with many cores, making smalltalk fast, spoon) still attracted over 40 participants. The introduction to smalltalk attracted quite a lot of young developers. Some remarks by participants: - a consistent set of keybindings, allowing switching between windows is essential (a developer who has trouble using a mouse for longer periods); - current developers are no longer used to free floating windows, it doesn't matter if it is better, to attract new people you need to remove barriers to entry (a freepascal maintainer); - I would have expected to have started with the basics (we focused on the things we experienced as difficult and different, using the different inspectors and browsers to navigate a large codebase, debugger driven development) And some reminder for ourselves - Tests for the domain model are not enough to ensure that the whole application works correctly; - Throw away old builds; - Check if there are enough power strips. I very much liked talking to people otherwise only known from the mailing lists and the cross-pollination between the different dialects. I would have liked to have more time for discussions. A lunch break might be a good idea. And finally a remark for next years devroom manager: don't expect to see much from FOSDEM :) Stephan Eggermont

1 0

[Pharo-project] About linkedlist
by StÃ©phane Ducasse Feb. 6, 2012

Feb. 6, 2012

Hi I was thinking that linkedList is really not to be used by something else than the scheduler (remember the problem we got with change == into something else). So I was wondering if it would not be simpler/safer to design a generalPurpose fast/robust LinkedList too? Stef

10 24

[Pharo-project] ConfigurationOfSIXX status?
by Schwab,Wilhelm K Feb. 6, 2012

Feb. 6, 2012

Does anyone know the status of the SIXX configuration. I can't get it to load. In general, what does it mean when Gofer doesn't? I hate to repeat myself, but silent failures are one of the worst things a computer can do, and I'm getting them (often). Bill

1 0

[Pharo-project] Report from FOSDEM please! :)
by GÃ¶ran Krampe Feb. 6, 2012

Feb. 6, 2012

...I want to hear how darn cool it was and how droves of new Smalltalkers got "reborn" :) regards, GÃ¶ran

1 0

[Pharo-project] Alternative to MC for upload?
by Schwab,Wilhelm K Feb. 6, 2012

Feb. 6, 2012

Hello all, I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community. In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me. Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool? Bill

6 19