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

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

On 23 Feb 2014, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 23 Feb 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: > >> One of the core ideas is âlogging objects and not stringsâ. > > I am missing a clear example of that though. sven when opal is writing to the transcript that there is an undeclared or a shadow I want to get a OPALCompilationLogEvent that I can query and ask to jump in the broken code. > I am wondering what the expect interface is, how difficult/easy it is to fit in a new object as log (event). In SystemLogger you have self handleConvertedLogEvent: (self convert: aLogEvent) and convert: can do what ever we want to convert an object into a string. Stef

Feb. 23, 2014

list all projects at smalltalk hub

by Nicolai Hess

Stupid question, but how can I list all projects at smalltalk hub? At the moment, it only shows a list of recently created projects. nicolai

Feb. 23, 2014

Re: [Pharo-dev] PharoChangesCondenser

by Marcus Denker

On 22 Feb 2014, at 20:14, Camillo Bruni <camillobruni(a)gmail.com> wrote: > We need guinea-pigs for https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn… > > I rewrote the changes condenser from scratch in a couple of methods: > - probably the same speed as before > - increased safety: source pointer switching only happens after ALL sources are exported > - massively reduced complexity by using real objects Wow, very good! Marcus

Feb. 23, 2014

Re: [Pharo-dev] Log of the february dev meeting

by ClÃ©ment Bera

Hello, 2014-02-23 14:51 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi! > > What is PharoS? > For marketing, Cog VM => Pharo VM Stack VM => PharoS VM > > Alexandre > > > Le 22-02-2014 Ã 7:44, Pharo4Stef <pharo4Stef(a)free.fr> a Ã©crit : > > > > HI guys > > > > we did not have a full team meeting since nov so here is the log of the > one feb 2014. > > > > 17 February 2014 > > > > > > TODO for 3.0 > > ------------ > > > > - [todo] 17 issues left > > - [todo] Rpackage > > - [todo] classBuilder > > - [todo] VM > > - [todo] new pharo web sites > > - [todo] pharo list of changes > > > > - [no progress] > > OPAL methods withoutsource > > stalled > > unclear who is creating method without source. > > > > - [Todo ] SmalltalkInbox for projects > > > > > > - [Todo] > > Web site > > Pharodoc web site > > Association > > > > - [30] MetacelloRepository > > > > > > > > > > > > Todo for 40 > > ---------- > > > > - [40] NativeBoost on PharoS > > > > - [40] Kill Package Info > > - Rpackage iteration under way > > > > - [40] TxModel > > - (done) refactoring immutable position selection > > - (done) visual is working > > - scrolling should be added > > - (done) page up down should be added > > - morph widget > > - finish > > - (done) Study Rubric > > > > - [40] NewInterpreter > > NewSpec interpreter > > two days of work > > should be integrated in this iteration > > > > - [40] bugs from the image > > > > - [40] NativeBoost with new ASMJIT version > > > > - [40] New look and feel - November > > > > - [40] SystemEvents > > > > - [40] Display VM Guile and Esteban are killing globals > > > > > > > > Stef > >

Feb. 23, 2014

Re: [Pharo-dev] Log of the february dev meeting

by Sven Van Caekenberghe

On 23 Feb 2014, at 14:51, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > What is PharoS? The non-JIT version of Cog, AKA the Stack VM, a modern version of the old VM. > Alexandre > >> Le 22-02-2014 Ã 7:44, Pharo4Stef <pharo4Stef(a)free.fr> a Ã©crit : >> >> HI guys >> >> we did not have a full team meeting since nov so here is the log of the one feb 2014. >> >> 17 February 2014 >> >> >> TODO for 3.0 >> ââââââ >> >> - [todo] 17 issues left >> - [todo] Rpackage >> - [todo] classBuilder >> - [todo] VM >> - [todo] new pharo web sites >> - [todo] pharo list of changes >> >> - [no progress] >> OPAL methods withoutsource >> stalled >> unclear who is creating method without source. >> >> - [Todo ] SmalltalkInbox for projects >> >> >> - [Todo] >> Web site >> Pharodoc web site >> Association >> >> - [30] MetacelloRepository >> >> >> >> >> >> Todo for 40 >> âââââ >> >> - [40] NativeBoost on PharoS >> >> - [40] Kill Package Info >> - Rpackage iteration under way >> >> - [40] TxModel >> - (done) refactoring immutable position selection >> - (done) visual is working >> - scrolling should be added >> - (done) page up down should be added >> - morph widget >> - finish >> - (done) Study Rubric >> >> - [40] NewInterpreter >> NewSpec interpreter >> two days of work >> should be integrated in this iteration >> >> - [40] bugs from the image >> >> - [40] NativeBoost with new ASMJIT version >> >> - [40] New look and feel - November >> >> - [40] SystemEvents >> >> - [40] Display VM Guile and Esteban are killing globals >> >> >> >> Stef >

Feb. 23, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Sven Van Caekenberghe

On 23 Feb 2014, at 14:30, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 23.02.2014 um 14:07 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> >> On 23 Feb 2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 23.02.2014 um 13:32 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>>> >>>> On 23 Feb 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>>> One of the core ideas is âlogging objects and not stringsâ. >>>> >>>> I am missing a clear example of that though. I am wondering what the expect interface is, how difficult/easy it is to fit in a new object as log (event). >>> >>> The âmessageâ instVar in Log is supposed to be any object not just strings. So the easiest way to âlogâ your object is >>> >>> myObject asLog emit >>> >>> What it does is to wrap a Log class around myObject being the message then. The creation of the Log class is dispatch through myObjects class so every business object can decide its own preferred log vehicle which can act as a bridge between special log objects and common log behavior. >>> >>> Does that answer your question? >> >> More or less, I think I understand. Is this what you do yourself or is that how SystemLogger works ? What I meant is that this needs to be added to the documentation since it is so crucial to the 'not strings but real objects' mantra, and right now it is not explained well. >> > This is how SystemLogger works. > So this is missing in the documentation? I need to read again and will add this. It wonât just be the next days because Iâm on vacation then. By explained I mean, an example, all the examples now are with plain strings...

Feb. 23, 2014

Re: [Pharo-dev] Log of the february dev meeting

by Alexandre Bergel

Hi! What is PharoS? Alexandre > Le 22-02-2014 Ã 7:44, Pharo4Stef <pharo4Stef(a)free.fr> a Ã©crit : > > HI guys > > we did not have a full team meeting since nov so here is the log of the one feb 2014. > > 17 February 2014 > > > TODO for 3.0 > ââââââ > > - [todo] 17 issues left > - [todo] Rpackage > - [todo] classBuilder > - [todo] VM > - [todo] new pharo web sites > - [todo] pharo list of changes > > - [no progress] > OPAL methods withoutsource > stalled > unclear who is creating method without source. > > - [Todo ] SmalltalkInbox for projects > > > - [Todo] > Web site > Pharodoc web site > Association > > - [30] MetacelloRepository > > > > > > Todo for 40 > âââââ > > - [40] NativeBoost on PharoS > > - [40] Kill Package Info > - Rpackage iteration under way > > - [40] TxModel > - (done) refactoring immutable position selection > - (done) visual is working > - scrolling should be added > - (done) page up down should be added > - morph widget > - finish > - (done) Study Rubric > > - [40] NewInterpreter > NewSpec interpreter > two days of work > should be integrated in this iteration > > - [40] bugs from the image > > - [40] NativeBoost with new ASMJIT version > > - [40] New look and feel - November > > - [40] SystemEvents > > - [40] Display VM Guile and Esteban are killing globals > > > > Stef

Feb. 23, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Norbert Hartl

Am 23.02.2014 um 14:07 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 23 Feb 2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 23.02.2014 um 13:32 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> >>> On 23 Feb 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> One of the core ideas is âlogging objects and not stringsâ. >>> >>> I am missing a clear example of that though. I am wondering what the expect interface is, how difficult/easy it is to fit in a new object as log (event). >> >> The âmessageâ instVar in Log is supposed to be any object not just strings. So the easiest way to âlogâ your object is >> >> myObject asLog emit >> >> What it does is to wrap a Log class around myObject being the message then. The creation of the Log class is dispatch through myObjects class so every business object can decide its own preferred log vehicle which can act as a bridge between special log objects and common log behavior. >> >> Does that answer your question? > > More or less, I think I understand. Is this what you do yourself or is that how SystemLogger works ? What I meant is that this needs to be added to the documentation since it is so crucial to the 'not strings but real objects' mantra, and right now it is not explained well. > This is how SystemLogger works. So this is missing in the documentation? I need to read again and will add this. It wonât just be the next days because Iâm on vacation then. thanks, Norbert

Feb. 23, 2014

Re: [Pharo-dev] [OT] Where should menues go ...

by GermÃ¡n Leiva

http://www.codinghorror.com/blog/2006/08/fitts-law-and-infinite-width.html On Sun, Feb 23, 2014 at 12:10 PM, Benjamin < Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > On 23 Feb 2014, at 11:44, MartinW <wm(a)fastmail.fm> wrote: > > > The difference of Pharo (and it's UI!) was what lured me into it, not what > constituted a barrier :) And while i would also make a case for difference > only for it's own sake, i think there are very good reasons for the pop-up > menus. > > > They are very good reasons for popup menus. > > The work menu is not one of them > > Popup menus should (mainly) be used to propose contextual options. > Now take a random menu in Pharo, and look for the items > that applies only in the current context. > > That's also the reason why the menu are far too long. > > > Ben > -- GermÃ¡n Leiva LeivaGerman(a)gmail.com

Feb. 23, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Sven Van Caekenberghe

On 23 Feb 2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 23.02.2014 um 13:32 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> >> On 23 Feb 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> One of the core ideas is âlogging objects and not stringsâ. >> >> I am missing a clear example of that though. I am wondering what the expect interface is, how difficult/easy it is to fit in a new object as log (event). > > The âmessageâ instVar in Log is supposed to be any object not just strings. So the easiest way to âlogâ your object is > > myObject asLog emit > > What it does is to wrap a Log class around myObject being the message then. The creation of the Log class is dispatch through myObjects class so every business object can decide its own preferred log vehicle which can act as a bridge between special log objects and common log behavior. > > Does that answer your question? More or less, I think I understand. Is this what you do yourself or is that how SystemLogger works ? What I meant is that this needs to be added to the documentation since it is so crucial to the 'not strings but real objects' mantra, and right now it is not explained well. > Norbert > >

Feb. 23, 2014