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

[Pharo-project] [update 1.4] #14326 NonInteractiveUIManager improved
by Marcus Denker Feb. 10, 2012

Feb. 10, 2012

14326 ----- Issue 5227: NonInteractiveUIManager should implement #syntaxErrorNotificationDefaultAction: http://code.google.com/p/pharo/issues/detail?id=5227 Thanks Camillo Bruni! Primarily fixed startup errors for loaded scripts - CodeLoader prints out SyntaxErrors and the filename if a script fails to load - added CommandLine UIManager which should be an interactive implementation for being used on the terminal - NonInteractiveUIManager inherits from CommandLine UIManager so that the logging facility can be shared - Cleaned up SyntaxError - added direct initializers with SyntaxErrorNotification: - properly color the displayed code - selec the error message - display the error message in the title - double click on the class name opens the debugger - Cleaned up users of SyntaxErrorNotification: - provide the code in raw format without included error message - changed the notion of headless and interactive on SmalltalkImage - headless == no display attached - noninteractive == no user input (previously the negation of headless) - added new possible commmandline option -interactive - added convenience method in String >> #lineNumberCorrespondingToIndex: used for formatting the syntax errors -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Moving parsing out of code generator in NativeBoost
by Javier PimÃ¡s Feb. 10, 2012

Feb. 10, 2012

This is mainly for Igor, but anyone interested on NB can participate. For the topic parser/code generator. I been thinking about the parts of the changes we've been talking about. The are dozens of classes that implement asNBExternalType: generator, but only string/char uses the generator, to access an instance variable and know if should use wide or byte strings/chars. In the end, I think the dependency parser->generator is artificial and should be removed (maybe by creating some "environment object") but I need to think how. But I think that we can do something in the middle meanwhile. What I'd like is the generator to take care of *only* generating code. Or at least, if that is not possible, to keep the unrelated code on it to the minimum. Specially, to move out the parts that deal with strings. It's obvious that the gen needs a parsed version of the function specs, but if most of this parsing is done outside, the best. In that direction I pushed some code which I think you'll like more this time. The idea is that the generator creates a translator object, that takes the raw func spec (stings) and with it's aid creates a new one that has the external types. The only aid the parser needs is to resolve types, because type resolving may depend on options. Then, it doesn't do it itself but uses the type resolver, because again, most of this work is to deal with strings, and doesn't need the generator directly so it can be done outside. Give the code a look, it's in better shape -- Lic. Javier PimÃ¡s Ciudad de Buenos Aires

1 0

[Pharo-project] [update 1.4] #14325
by Marcus Denker Feb. 10, 2012

Feb. 10, 2012

14325 ----- Issue 4647: Update Filesystem Dialogs to use the new FS implementation http://code.google.com/p/pharo/issues/detail?id=4647 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] ss3.gemstone.com
by Alexandre Bergel Feb. 10, 2012

Feb. 10, 2012

Hi! The main page of ss3.gemstone.com gives an "Important Announcement (September 7, 2011)". Does it make sense to have it still? The website is apparently in alpha. Isn't it ready for a release? Has anyone experienced some problem with it? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

Re: [Pharo-project] 1.4 - better from Jenkins
by Marcus Denker Feb. 9, 2012

Feb. 9, 2012

On Feb 9, 2012, at 9:23 PM, Schwab,Wilhelm K wrote: > Miguel, > > Giving you the benefit of the doubt, you misunderstand. Something did change "suddenly" in my experience and (as I ****CLEARLY**** stated in my email), it could easily be that the links on the Pharo site are stale. They are not. At least a) the link to 1.4 points to update 315, which is just 9 updates old. And for sure you would do a "load updates" anyway? The download is just a copy from the build server. (same .zip, renamed), of some days ago. This is used by jenkins. Jenkins does nothing else then "load updates" and save. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] [update 1.4] #14324
by Marcus Denker Feb. 9, 2012

Feb. 9, 2012

14324 ----- Issue 5269: Add cmd-a/cmd-A on multiple selection PluggableListMorph for select/deselect all http://code.google.com/p/pharo/issues/detail?id=5269 Issue 5268: CompiledMethod >> receiver:withArguments:executeMethod: should be in class side http://code.google.com/p/pharo/issues/detail?id=5268 Issue 5240: [ENH]: Make PluggableButtonMorph more lively http://code.google.com/p/pharo/issues/detail?id=5240 Issue 5228: MorphTreeMorph hide last element when horizontal scrollbar is shown http://code.google.com/p/pharo/issues/detail?id=5228 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Updated Configuration packages for PharoMorphicView
by S Krish Feb. 9, 2012

Feb. 9, 2012

Details are posted in: http://skrishnamachari.wordpress.com/2012/02/09/pharo-morphic-view-framewor… hopefully cleaner and easier for anyone to load and check out.. PharoMorphicView-Core-App : is a basic package and PharoMorphicView is the full pack. Trying to now wade through the Specs / Presenty / existing capabilities which I can merge with but overall very interesting first time run up with Morphic Experimental Run, but quite usable overall.... plugs in hand in glove with existing primitive morphs. Easy too to get some newbies started with Morphic UIs.. PS: Once comment was nice to hear.. Few new trainees found working in Pharo easier than starting up with VisualAge.. !..

1 0

[Pharo-project] Feedback on Pharo 1.4 Debugger
by Ben Coman Feb. 9, 2012

Feb. 9, 2012

The debugger in Pharo 1.4 is looking very nice - cleaner and easier to follow. I wonder if the following might be an additional improvement... If you consider a class has a method subpart which has a block subpart, then the "natural flow" of these would continue from left to right. Referring to [1] - having the "Block" text on the left breaks this sense of "flow". What I've drawn in [2] feels more natural to me. Possible advantages: * It is easier to see the five SystemReporter items line up. * Balances brevity with giving a bit of context to distinguish nested blocks. [1] NewDebuggerStackView(1).png (attached) [2] NewDebuggerStackView(2).png (attached) cheers, -ben

2 1

[Pharo-project] Smalltalk on Bacon conf?
by Janko MivÅ¡ek Feb. 9, 2012

Feb. 9, 2012

Hi guys, Maybe this two day conference "by developers for developers" is another opportunity to show strengths of Smalltalk? Bacon http://devslovebacon.com/ BACON is a two-day, two-track technology conference on things developers love. 20-21 April, 2012 London. Thirty-two tasty sessions on topics including web development, machine learning, astronomy, and electronic music. Call for speakers Bacon is a conference by developers for developers. We are looking for a wide range of talks that focus on things developers love, whether digital or analogue. Are you a developer by day and electronic music superstar by night? Have you been working on some super interesting code and want to share your findings? Each speaker will have half an hour to deliver their talk and to gain the eternal admiration and adoration of their peers. Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

1 0

[Pharo-project] FSFilesystemTest>>testReferenceTo fails on Windows
by Ben Coman Feb. 9, 2012

Feb. 9, 2012

I have loaded ConfigurationOfFilesystem v2.0.3 into Pharo-1.3-13315 on Windows 7. All tests are green except FSFilesystemTest>>testReferenceTo which hard codes the unix root folder... self assert: (filesystem referenceTo: '/') isRoot. However, guessing at the semantics of isRoot, simply changing this to... self assert: (filesystem referenceTo: 'C:\') isRoot. is not sufficient since... FSAbsolutePath>>isRoot ^ self size = 0 has size = 1. Looking into this further, it appears that the test for absolute path is incorrect in FSWindowStore>>pathFromString: aString. It is not the drive letter and colon that make it an absolute path, but whether the third character is a slash as well. Consider this sequence from a new command window ... C:\> mkdir C:\TestC1 C:\> cd TestC1 C:\TestC1> E: E:\> mkdir C:TestC2 E:\> C: C:\testC1> cd \testC1\testC2 C:\testC1\testC2> Definitively... [1] "Section 'Fully Qualified vs. Relative Paths' >> If a file name begins with only a disk designator but not the backslash after the colon, it is interpreted as a relative path to the current directory on the drive with the specified letter. " [1] http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%… Without knowing the design philosophy or architecture of FS I'll just wildly speculate on on implementation.... by FSDiskStore having an instance variable "volume." For Unix this would remain empty. For Windows this would be 'C:' or 'D:' (without the slash). Then once this volume is stripped from the front of the path, the super method could be used, and (^ self size = 0) in FSAbsolutePath>>isRoot would be true. For example... FSWindowStore>>pathFromString: aString | class | class := ((aString at: 1) isLetter and: [(aString at: 2) = $:]) ifTrue: [ volume := (aString at: 1) asString , ":" . ^ super pathFromString: (aString copyFrom: 3 to: (aString size)). ] ^ super pathFromString: aString. FSStore>>pathFromString peek = $/ would also need to be replaced by peek = self delimiter. OR... perhaps... FSDiskStore>>pathFromString: aString self volumeFromString: aString. super pathFromString: ( aString copyFrom: (self volume size) + 1 to: (aString size) ). FSDiskStore>>volume volume ifNil: [ volume := '' ]. FSDiskStore>>volumeFromString ^self. FSWindowStore>>volumeFromString: aString ((aString at: 1) isLetter and: [(aString at: 2) = $:]) ifTrue: [ volume := (aString at: 1) asString , ":" . ] "also handle UNC volumes here" Also are UNC paths under consideration? Here the volume '\\server\share' might be extracted from the front of the path and isRoot would be True at this location. From [1] ... "The "\\?\" prefix can also be used with paths constructed according to the universal naming convention (UNC). To specify such a path using UNC, use the "\\?\UNC\" prefix. For example, "\\?\UNC\server\share", where "server" is the name of the computer and "share" is the name of the shared folder. These _ prefixes are not used as part of the path itself. _ " Anyway, that is as far as I can take it. Obviously lots of implications I haven't considered. Hope this helps. cheers, -ben

1 2