- Pharo-dev - lists.pharo.org

[Pharo-project] CI server down?

by Sebastian Nozzi

I cannot access: http://ci.lille.inria.fr/pharo/ (anyone has nagios on that? ;-)

Dec. 2, 2012

Re: [Pharo-project] just help :)

by Mariano Martinez Peck

On Fri, Nov 30, 2012 at 10:06 AM, Sebastian Nozzi <sebnozzi(a)gmail.com>wrote: > 2012/11/30 Marcus Denker <marcus.denker(a)inria.fr>: > > On Nov 29, 2012, at 11:55 PM, dimitris chloupis <thekilon(a)yahoo.co.uk> > > wrote: > > > > * Framework for seamless data/object-synchronization. I suggested this a > > while ago, didn't get much response. I don't blame anyone, there is not > much > > need for this right now. What I would want is to be able to modify > certain > > objects in my image, while offline, and connect to the Internet, and > these > > objects be synchronized between other images. This way Internet-enabled > apps > > could be built on top of Pharo in a better way that web-apps are built > now > > (because, in Pharo you can not hit F5 and get fresh data ;-). But this is > > low-priority for me." > > > > This is a hard problemâ¦ but if would be nice to have, yes. > > I think it would make a nice research project ;-) > > Maybe as an extension(*) to Fuel/Tanker? > I guess Fuel/Tanker also has to deal with conflicts, right? > > Right. This already happens and Fuel deals with some of them. > > > * - "Extension" or "on-top-of" > > -- Mariano http://marianopeck.wordpress.com

Dec. 2, 2012

Re: [Pharo-project] [[ false ] whileFalse: [ ]] in workspace

by Guillermo Polito

Hi! I've hacked a fix, but I don't know if it is correct... can somebody check it so I make a Slice? Guille On Sun, Dec 2, 2012 at 8:56 PM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > Ok, I've found the cause :). > > From update 20043: > > Issue 5744: Clean up Temp Embedding 2): DoIts > http://code.google.com/p/pharo/issues/detail?id=5744 > > > - Doits are now compiled with source embedded > - embedding sources for doits pretty prints from AST as doits are compiled > specially (with a return added) > > CompiledMethod: > > - remove blockExtendsToTempsMap: Not needed anymore, all calls go the > MethodNode > - remove #copyWitTempsFromMethodNode: All senders use #copyWithSource > - remove #holdsTempNames. Temp name embedding not needed > - add isDoit > - schematicTempNamesString always returns the schematic string > representation of all temps > - tempNames forwards to methodNode > - remove tempNamesString. Concatenate yourself if you need that. > > Debugger>>selectedMessage asks the selectedContext directly for the > source. No need for the methodMap. > > DebuggerMethodMap > > - no special handling of methods that encode temps. Just as for methodNode > always. > > MethodNode > > - generateWithSource. embedd pretty printed code in case of doit > - remove generateWithTempNames > > In general: rewrite code to use #generateWithSource > > > On Sat, Dec 1, 2012 at 6:24 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Sebastian >> >> I can tell you that what you did is **useful** because we are all working >> like mad >> and such kind of help is really welcome. >> >> Stef >> >> On Dec 1, 2012, at 3:24 PM, Sebastian Nozzi wrote: >> >> > It's the #7076. >> > >> > 2012/11/29 Camillo Bruni <camillobruni(a)gmail.com>: >> >> perfect! can you open a bug report with this information? :) >> > >> >> >> >

Dec. 2, 2012

Re: [Pharo-project] DynamicVariable>>value:during:

by Sven Van Caekenberghe

Yes, I think so too, but maybe there was some reason for not doing it ? On 02 Dec 2012, at 20:52, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hey guys, > > would not make much much more sense if we return the result of evaluating the block when we use dynamic variables? > > Here is the patch I'm using these days: > > DynamicVariable>>value: anObject during: aBlock > > | p oldValue result | > p := Processor activeProcess. > oldValue := (p psValueAt: index) ifNil: [self default]. > [ > p psValueAt: index put: anObject. > result := aBlock value. > ] ensure: [ > p psValueAt: index put: oldValue > ]. > > ^ result -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 2, 2012

Re: [Pharo-project] [[ false ] whileFalse: [ ]] in workspace

by Mariano Martinez Peck

On Sat, Dec 1, 2012 at 6:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Sebastian > > I can tell you that what you did is **useful** because we are all working > like mad > and such kind of help is really welcome. > > +9999 > Stef > > On Dec 1, 2012, at 3:24 PM, Sebastian Nozzi wrote: > > > It's the #7076. > > > > 2012/11/29 Camillo Bruni <camillobruni(a)gmail.com>: > >> perfect! can you open a bug report with this information? :) > > > > > -- Mariano http://marianopeck.wordpress.com

Dec. 2, 2012

Re: [Pharo-project] [[ false ] whileFalse: [ ]] in workspace

by Guillermo Polito

Ok, I've found the cause :). >From update 20043: Issue 5744: Clean up Temp Embedding 2): DoIts http://code.google.com/p/pharo/issues/detail?id=5744 - Doits are now compiled with source embedded - embedding sources for doits pretty prints from AST as doits are compiled specially (with a return added) CompiledMethod: - remove blockExtendsToTempsMap: Not needed anymore, all calls go the MethodNode - remove #copyWitTempsFromMethodNode: All senders use #copyWithSource - remove #holdsTempNames. Temp name embedding not needed - add isDoit - schematicTempNamesString always returns the schematic string representation of all temps - tempNames forwards to methodNode - remove tempNamesString. Concatenate yourself if you need that. Debugger>>selectedMessage asks the selectedContext directly for the source. No need for the methodMap. DebuggerMethodMap - no special handling of methods that encode temps. Just as for methodNode always. MethodNode - generateWithSource. embedd pretty printed code in case of doit - remove generateWithTempNames In general: rewrite code to use #generateWithSource On Sat, Dec 1, 2012 at 6:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Sebastian > > I can tell you that what you did is **useful** because we are all working > like mad > and such kind of help is really welcome. > > Stef > > On Dec 1, 2012, at 3:24 PM, Sebastian Nozzi wrote: > > > It's the #7076. > > > > 2012/11/29 Camillo Bruni <camillobruni(a)gmail.com>: > >> perfect! can you open a bug report with this information? :) > > > > >

Dec. 2, 2012

[Pharo-project] DynamicVariable>>value:during:

by Sebastian Sastre

Hey guys, would not make much much more sense if we return the result of evaluating the block when we use dynamic variables? Here is the patch I'm using these days: DynamicVariable>>value: anObject during: aBlock | p oldValue result | p := Processor activeProcess. oldValue := (p psValueAt: index) ifNil: [self default]. [ p psValueAt: index put: anObject. result := aBlock value. ] ensure: [ p psValueAt: index put: oldValue ]. ^ result

Dec. 2, 2012

Re: [Pharo-project] Open Source and Constraints | Documentation is King

by Frank Shearar

On 2 December 2012 18:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Well written: > > http://kennethreitz.org/open-source-and-constraints.html > > I also find that writing documentation (minimal method/class comments or longer standalone documents) improves coding, because you take another perspective. I wouldn't value it above tests though. "I'm designing an API and experience for myself and others as developers." That's exactly why I write tests in the first place: you write the tests to design the API. And hopefully the tests serve as good examples of how to use the API. (If they aren't good examples, you're writing your tests wrongly.) frank > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Dec. 2, 2012

[Pharo-project] Open Source and Constraints | Documentation is King

by Sven Van Caekenberghe

Well written: http://kennethreitz.org/open-source-and-constraints.html I also find that writing documentation (minimal method/class comments or longer standalone documents) improves coding, because you take another perspective. I wouldn't value it above tests though. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 2, 2012

Re: [Pharo-project] Getting started with Athens

by StÃ©phane Ducasse

>> >> >>> Stef, >>> >>> With Ze great Stef? Incredible, indeed :) >>> I'll start putting down my questions and learning then. Can you tell me when you will be starting? I'll start the one for Roassal soon. >>> >> >> I will also ask tristan to join because he will work on athens for a large industrial :). >> >> Stef >> >> > Would that touch on implementing any industrial communications protocols, like Modbus[1]? I plan to try implementing Modbus next year after I get a few other things out of the way. > > [1] http://en.wikipedia.org/wiki/Modbus "Simple and robust, it has since become a de facto standard communication protocol, and it is now amongst the most commonly available means of connecting industrial electronic devices." Without a project behind I do not think that we cant decently implement protocol Now if people give a try and we see what it isâ¦ We have OSC and TUIO already Stef

Dec. 2, 2012