January 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] Extent a Athens surface?
by Vanessa PeÃ±a Araya Jan. 28, 2013

Jan. 28, 2013

Hi, I wanted to ask if it's possible to extent an Athens surface. If it can't be done, because as far as I understand this can't be done in Cairo, is it possible to simulate it at least? Is it possible to stop #drawDuring: and build another surface, maybe? Thanks, Vanessa.

1 0

[Pharo-project] [update 2.0] #20494
by Marcus Denker Jan. 28, 2013

Jan. 28, 2013

20494 ----- Issue 7342: RB tests assume that Object isAbstract http://code.google.com/p/pharo/issues/detail?id=7342 Issue 7335: [Bug]: Nautilus Annotation Plugin DNU http://code.google.com/p/pharo/issues/detail?id=7335 Issue 7290: Add #split: streaming protocol http://code.google.com/p/pharo/issues/detail?id=7290 Diff information: http://ss3.gemstone.com/ss/Pharo20/Regex-Core-MarcusDenker.22.diff http://ss3.gemstone.com/ss/Pharo20/Refactoring-Tests-Core-MarcusDenker.61.d… http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.402.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1291.diff http://ss3.gemstone.com/ss/Pharo20/Collections-Strings-MarcusDenker.240.diff http://ss3.gemstone.com/ss/Pharo20/Collections-Sequenceable-MarcusDenker.12… http://ss3.gemstone.com/ss/Pharo20/Collections-Abstract-MarcusDenker.196.di…

1 0

[Pharo-project] FOSDEM diner & drinks?
by Stephan Eggermont Jan. 28, 2013

Jan. 28, 2013

Hi, Craig and I plan to arrive in Brussels-Midi 12:04 on saturday. We are up for diner & drinks saturday evening, and early diner on sunday. We'd like to travel back to the Netherlands at 19.00 or so. Any ideas? I liked the place Andy showed us last year, and it is perfect for sunday evening. Cheers, Stephan

2 1

[Pharo-project] CouchDB and Pharo
by GÃ¶ran Krampe Jan. 28, 2013

Jan. 28, 2013

Hi! Just noticed your stuff: http://vinsicaves.seasidehosting.st/resources/Developing%20Applications%20w… http://www.smalltalkhub.com/#!/~jmari/SCouchDBViewServer Looks very nice! I also wrote a view server implementation a while ago - I remember I did some tricks to make Compiler deal with it properly etc. Can dig it out an email it to you, in that way I am at least sure it didn't go to waste. regards, GÃ¶ran PS. I moved on to Riak after CouchDB and now I am heavily intrigued by HyperDex and have a binding brewing using NB FFI :)

5 4

[Pharo-project] Fwd: More progress...
by Marcus Denker Jan. 28, 2013

Jan. 28, 2013

â¦ maybe others are interested. Begin forwarded message: > From: Marcus Denker <marcus.denker(a)inria.fr> > Subject: More progress... > Date: January 28, 2013 1:07:19 PM GMT+01:00 > To: "pharo-compiler(a)lists.gforge.inria.fr" <pharo-compiler(a)lists.gforge.inria.fr> > > Hi, > > Lots of progressâ¦ > > -> BC to Text mapping (highlighting in the debugger) > Instead of building the mapping in the code generator, we instead > enhanced the AST and IR to have all the right information and needed > mapping. > > This means: we can query the AST for "which statement generated the byte code at offset 24?" > Or "which BlockNode is the one for this Context?". > > The AST combined with the Scope/Var annotations and the IR contains all information needed, > and in cases where something is wrong it is easy to debug. > > -> Correct Temp Vars for Contexts (via the Scope/Var knowledge) > For accessing temps in blocks in the debugger. > Here we delegate queries to the annotated AST, this means the Debugger uses > the same data structures as the compiler when it wants to know about e.g. local temps. > > One of the nice effects is that the needed machinery is much simpler: > > DebuggerMethodMap linesOfCode 164 > DebuggerMethodMapOpal linesOfCode 62 > > it is actually so simple that in a second step, there is no need for DebuggerMethodMapOpal at all, > the code can be moved directly to better places (e.g. MethodContext). Caching is handled by ASTCache. > > -> Error Handling is working. All the error handling (Parsing and Semantic) are handled the same as > the old compiler. > > TODO > => Pass over integration. Clean up the Compiler/Parser facades. > (We will first have the whole thing to be compatible to the old from the Compiler/Parser POV, > here more cleanups are following after we have the stuff in the image) > > => Pass over the decompiler. BC->IR is working, IR->AST needs to be checked. > > => Fix all showstoppers here: http://code.google.com/p/pharo-newcompiler/issues/list > > > Marcus and Clement >

4 4

[Pharo-project] [Issue Tracker] Failing Tests in 2.0
by Marcus Denker Jan. 28, 2013

Jan. 28, 2013

Failing test in 2.0: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=2.0%20status=F… I added all failing tests from Jenkins to the tracker. https://ci.inria.fr/pharo/view/Pharo-2.0/job/Pharo-2.0-Tests/

1 0

Re: [Pharo-project] Fwd: More progress...
by Fernando Olivero Jan. 28, 2013

Jan. 28, 2013

Hi Marcus, this are great news! For the less-knowledgable in OPAL, were can we read more about it? Fernando On Mon, Jan 28, 2013 at 1:15 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Yes ! > > Looking forward to itâ¦ > > On 28 Jan 2013, at 13:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > â¦ maybe others are interested. > > > > Begin forwarded message: > > > >> From: Marcus Denker <marcus.denker(a)inria.fr> > >> Subject: More progress... > >> Date: January 28, 2013 1:07:19 PM GMT+01:00 > >> To: "pharo-compiler(a)lists.gforge.inria.fr" < > pharo-compiler(a)lists.gforge.inria.fr> > >> > >> Hi, > >> > >> Lots of progressâ¦ > >> > >> -> BC to Text mapping (highlighting in the debugger) > >> Instead of building the mapping in the code generator, we > instead > >> enhanced the AST and IR to have all the right information > and needed > >> mapping. > >> > >> This means: we can query the AST for "which statement > generated the byte code at offset 24?" > >> Or "which BlockNode is the one for this Context?". > >> > >> The AST combined with the Scope/Var annotations and the IR > contains all information needed, > >> and in cases where something is wrong it is easy to debug. > >> > >> -> Correct Temp Vars for Contexts (via the Scope/Var knowledge) > >> For accessing temps in blocks in the debugger. > >> Here we delegate queries to the annotated AST, this means the > Debugger uses > >> the same data structures as the compiler when it wants to > know about e.g. local temps. > >> > >> One of the nice effects is that the needed machinery is much > simpler: > >> > >> DebuggerMethodMap linesOfCode 164 > >> DebuggerMethodMapOpal linesOfCode 62 > >> > >> it is actually so simple that in a second step, there is no need > for DebuggerMethodMapOpal at all, > >> the code can be moved directly to better places (e.g. > MethodContext). Caching is handled by ASTCache. > >> > >> -> Error Handling is working. All the error handling (Parsing and > Semantic) are handled the same as > >> the old compiler. > >> > >> TODO > >> => Pass over integration. Clean up the Compiler/Parser facades. > >> (We will first have the whole thing to be compatible to the > old from the Compiler/Parser POV, > >> here more cleanups are following after we have the stuff > in the image) > >> > >> => Pass over the decompiler. BC->IR is working, IR->AST needs to > be checked. > >> > >> => Fix all showstoppers here: > http://code.google.com/p/pharo-newcompiler/issues/list > >> > >> > >> Marcus and Clement > >> > > > > >

1 0

[Pharo-project] [update 2.0] #20493
by Marcus Denker Jan. 28, 2013

Jan. 28, 2013

20493 ----- Issue 7336: ReleaseTest is run double http://code.google.com/p/pharo/issues/detail?id=7336 Issue 7310: PickListModel should be improved http://code.google.com/p/pharo/issues/detail?id=7310 Postscript: SystemNavigation new instanceSideMethodsWithNilKeyInLastLiteral do: [ :thisShouldNotBeAStringButAMethod | | method classAndSelector | classAndSelector := ' ' split: thisShouldNotBeAStringButAMethod. method := (Smalltalk at: classAndSelector first asSymbol) methodNamed: classAndSelector second asSymbol. method recompile. ]. Diff information: http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.495.diff http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-MarcusDenker.83.diff http://ss3.gemstone.com/ss/Pharo20/RPackage-Tests-MarcusDenker.105.diff

1 0

Jan. 28, 2013

Hi guys we want to do a poll for two options for the pharo conference so do you know a free service for organizing that? Stef

3 2

Jan. 28, 2013

Hi Is there a way to specify the equivalent of project loadType: #'atomic'. at the level of an expression such as: (ConfigurationOfMoose project version: '4.7-flat') load while this loadType propagated to the projects? I saw that on a MetacelloMCVersion that there is a loaderPolicy instance variables and setters but there is no comment I have no idea what it is. It would be good to comment for real classes of the infrastructure we use. Of course MetacelloLoaderPolicy is not commented either. Sad. So apparently a MetacelloLoaderPolicy hold a loadDirective which can be a MetacelloLinearLoadDirective Stef

1 0