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

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

by Goubier Thierry

Le 23/02/2014 11:44, MartinW a Ã©crit : > Torsten Bergmann wrote >> http://www.omgubuntu.co.uk/2014/02/locally-integrated-menus-ubuntu-14-04 >> >> http://www.youtube.com/watch?v=teAFgtHWDso > > Well, are not Smalltalks pop-up menus (i.e. the world menu and all the other > context menus) solving the problem in the most beautiful way possible? No, they're not. > I was shocked when i recently read somewhere on this list that people are > thinking about introducing menu bars in order to make everything look more > like everything else looks. One HCI principle: discoverability. How to understand it? List all the commands in smart suggestions by looking at the popup menus. > 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. You're perfectly right :). Its just wiser to be aware of popup menus limitations. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 24, 2014

Re: [Pharo-dev] iPad version does not work ?

by Esteban Lorenzano

not yetâ¦ so far I restored the build capability, not the image event handling :( (nevertheless, Iâm on it :) ) Esteban On 24 Feb 2014, at 08:00, jannik laval <jannik.laval(a)gmail.com> wrote: > Hi Esteban, > > Did you already try ? > I saw a message on the VM repo related to iOS, not sure it is for my problem. > > Cheers, > Jannik > > > 2014-01-29 17:32 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > oksâ¦ I will take a lookâ¦ as soon as I can :S > > (damnâ¦ I need to learn how to do a mitosisâ¦) > > On 29 Jan 2014, at 17:28, jannik laval <jannik.laval(a)gmail.com> wrote: > >> I confirm that it does not work: the simulator compile (but not the non-simulator). >> Then the image cannot be open: I have a white screen. >> Here is my process: >> >> === >> 1) git clone https://github.com/pharo-project/pharo-vm.git >> 2) in ./image dir prepare a VMMaker image (including download of a pharo 2.0): >> ./newImage.sh >> >> 3)open the generated.image and execute: >> === >> PharoIPhoneBuilder buildIPhone. >> â or â >> PharoIPhoneBuilder buildIPhoneSimulator. >> >> 4) Generate your iPhone image in iosbuild/resources/ >> ./generate.sh >> >> 5) In dir ./build: >> sh build.sh >> === >> >> Cheers, >> Jannik >> >> >> >> 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> >> and btwâ¦ >> >> iosbuild/resource$ ./generate.sh >> >> should generate a 1.4 image that *should* work in ipad (no idea if that will be the case, its been more than 6months since I do not test it and vm changed since then). >> >> Esteban >> >> >> On 29 Jan 2014, at 10:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> PharoIPhoneBuilder buildIPhone. >>> >>> it should generate all sources and a âbuild.shâ >>> >>> then >>> >>> build$ sh build.sh >>> >>> will generate an xcode project. >>> >>> and let me rememberâ¦ mmmâ¦ yeah, that was all :) >>> >>> >>> >>> On 29 Jan 2014, at 08:10, jannik laval <jannik.laval(a)gmail.com> wrote: >>> >>>> Hi Esteban, >>>> >>>> Hum, this means that my instructions are outdated. >>>> Where are the right instructions ? The ones on Github do not mention IOS. >>>> >>>> Cheers, >>>> Jannik >>>> >>>> >>>> 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> >>>> >>>> On 29 Jan 2014, at 00:18, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Tue, Jan 28, 2014 at 2:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> because you are not following the instructions ;) >>>>> >>>>> basicallyâ¦ you can generate them by: >>>>> >>>>> build$ ../scripts/extract-commit-info.sh >>>>> >>>>> I asked for this info last week ;-). Thanks! >>>> >>>> hey! I answered you! :P >>>> >>>> >>>>> >>>>> But this is alarming: >>>>> >>>>> McStalker.pharovm$ ./scripts/extract-commit-info.sh >>>>> readlink: ./scripts/extract-commit-info.sh Invalid argument >>>>> >>>>> I suggest changing >>>>> SCRIPT_DIR=`readlink "$0"` || SCRIPT_DIR="$0"; >>>>> to read >>>>> SCRIPT_DIR=`readlink "$0" >/dev/null` || SCRIPT_DIR="$0"; >>>>> >>>>> >>>>> Esteban >>>>> >>>>> On 28 Jan 2014, at 23:15, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>> >>>>>> Thank you, I am trying the latest one. >>>>>> >>>>>> When compiling for IOS, I have an error in sqSCCSVersion.h >>>>>> >>>>>> #include "vmVersionInfo.h" // defines REVISION_STRING >>>>>> the file is not found. >>>>>> >>>>>> Anyone knows where is this file ? >>>>>> >>>>>> Cheers, >>>>>> Jannik >>>>>> >>>>>> On Jan 28, 2014, at 8:58 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>>>>> >>>>>>> jannik the latest vm is not on gitoruous anymore but git >>>>>>> >>>>>>> >>>>>>> On 27 Jan 2014, at 22:03, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hum, have I the correct repository ? >>>>>>>> I used this one: https://git.gitorious.org/cogvm/cog-osx.git >>>>>>>> >>>>>>>> But, I just saw that this one exists: https://github.com/pharo-project/pharo-vm >>>>>>>> I should use it no? >>>>>>>> >>>>>>>> Jannik >>>>>>>> >>>>>>>> >>>>>>>> 2014-01-27 Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>>> 1.4 and 2.0 worked out of the boxâ¦ and after my latest integration, 3.0 should work too. >>>>>>>> I will take a look as soon as I have half and hour to spare. >>>>>>>> >>>>>>>> Esteban >>>>>>>> >>>>>>>> >>>>>>>> On 27 Jan 2014, at 14:27, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi list, >>>>>>>>> >>>>>>>>> Does anyone try to load Pharoon iPad ? >>>>>>>>> In the past, the version 1.4 worked with XCode 4.4. >>>>>>>>> >>>>>>>>> I just tried to recompile it with the new XCode (5.0.2). >>>>>>>>> The VM seems to work, but the pharo 1.4 image freezes. >>>>>>>>> >>>>>>>>> Any idea ? >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ~~Jannik Laval~~ >>>>>>>>> Ãcole des Mines de Douai >>>>>>>>> Enseignant-chercheur >>>>>>>>> http://www.jannik-laval.eu >>>>>>>>> http://car.mines-douai.fr/ >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> ~~Jannik Laval~~ >>>>>>>> Ãcole des Mines de Douai >>>>>>>> Enseignant-chercheur >>>>>>>> http://www.jannik-laval.eu >>>>>>>> http://car.mines-douai.fr/ >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> best, >>>>> Eliot >>>> >>>> >>>> >>>> >>>> -- >>>> ~~Jannik Laval~~ >>>> Ãcole des Mines de Douai >>>> Enseignant-chercheur >>>> http://www.jannik-laval.eu >>>> http://car.mines-douai.fr/ >>>> >>> >> >> >> >> >> -- >> ~~Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> http://car.mines-douai.fr/ >> > > > > > -- > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ >

Feb. 24, 2014

Re: [Pharo-dev] iPad version does not work ?

by jannik laval

Hi Esteban, Did you already try ? I saw a message on the VM repo related to iOS, not sure it is for my problem. Cheers, Jannik 2014-01-29 17:32 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > oks... I will take a look... as soon as I can :S > > (damn... I need to learn how to do a mitosis...) > > On 29 Jan 2014, at 17:28, jannik laval <jannik.laval(a)gmail.com> wrote: > > I confirm that it does not work: the simulator compile (but not the > non-simulator). > Then the image cannot be open: I have a white screen. > Here is my process: > > === > 1) git clone https://github.com/pharo-project/pharo-vm.git > 2) in ./image dir prepare a VMMaker image (including download of a pharo > 2.0): > ./newImage.sh > > 3)open the generated.image and execute: > === > PharoIPhoneBuilder buildIPhone. > -- or -- > PharoIPhoneBuilder buildIPhoneSimulator. > > 4) Generate your iPhone image in iosbuild/resources/ > ./generate.sh > > 5) In dir ./build: > sh build.sh > === > > Cheers, > Jannik > > > > 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> > >> and btw... >> >> iosbuild/resource$ ./generate.sh >> >> should generate a 1.4 image that *should* work in ipad (no idea if that >> will be the case, its been more than 6months since I do not test it and vm >> changed since then). >> >> Esteban >> >> >> On 29 Jan 2014, at 10:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> PharoIPhoneBuilder buildIPhone. >> >> it should generate all sources and a "build.sh" >> >> then >> >> build$ sh build.sh >> >> will generate an xcode project. >> >> and let me remember... mmm... yeah, that was all :) >> >> >> >> On 29 Jan 2014, at 08:10, jannik laval <jannik.laval(a)gmail.com> wrote: >> >> Hi Esteban, >> >> Hum, this means that my instructions are outdated. >> Where are the right instructions ? The ones on Github do not mention IOS. >> >> Cheers, >> Jannik >> >> >> 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> >> >>> >>> On 29 Jan 2014, at 00:18, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>> >>> >>> >>> On Tue, Jan 28, 2014 at 2:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: >>> >>>> because you are not following the instructions ;) >>>> >>>> basically... you can generate them by: >>>> >>>> build$ ../scripts/extract-commit-info.sh >>>> >>> >>> I asked for this info last week ;-). Thanks! >>> >>> >>> hey! I answered you! :P >>> >>> >>> >>> But this is alarming: >>> >>> McStalker.pharovm$ ./scripts/extract-commit-info.sh >>> readlink: ./scripts/extract-commit-info.sh Invalid argument >>> >>> I suggest changing >>> SCRIPT_DIR=`readlink "$0"` || SCRIPT_DIR="$0"; >>> to read >>> SCRIPT_DIR=`readlink "$0" >/dev/null` || SCRIPT_DIR="$0"; >>> >>> >>> Esteban >>>> >>>> On 28 Jan 2014, at 23:15, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>> >>>> Thank you, I am trying the latest one. >>>> >>>> When compiling for IOS, I have an error in sqSCCSVersion.h >>>> >>>> #include "vmVersionInfo.h" // defines REVISION_STRING >>>> the file is not found. >>>> >>>> Anyone knows where is this file ? >>>> >>>> Cheers, >>>> Jannik >>>> >>>> On Jan 28, 2014, at 8:58 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>>> >>>> jannik the latest vm is not on gitoruous anymore but git >>>> >>>> >>>> On 27 Jan 2014, at 22:03, jannik laval <jannik.laval(a)gmail.com> wrote: >>>> >>>> Hum, have I the correct repository ? >>>> I used this one: https://git.gitorious.org/cogvm/cog-osx.git >>>> >>>> But, I just saw that this one exists: >>>> https://github.com/pharo-project/pharo-vm >>>> I should use it no? >>>> >>>> Jannik >>>> >>>> >>>> 2014-01-27 Esteban Lorenzano <estebanlm(a)gmail.com> >>>> >>>>> 1.4 and 2.0 worked out of the box... and after my latest integration, >>>>> 3.0 should work too. >>>>> I will take a look as soon as I have half and hour to spare. >>>>> >>>>> Esteban >>>>> >>>>> >>>>> On 27 Jan 2014, at 14:27, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>> >>>>> Hi list, >>>>> >>>>> Does anyone try to load Pharoon iPad ? >>>>> In the past, the version 1.4 worked with XCode 4.4. >>>>> >>>>> I just tried to recompile it with the new XCode (5.0.2). >>>>> The VM seems to work, but the pharo 1.4 image freezes. >>>>> >>>>> Any idea ? >>>>> >>>>> -- >>>>> >>>>> ~~Jannik Laval~~ >>>>> Ãcole des Mines de Douai >>>>> Enseignant-chercheur >>>>> http://www.jannik-laval.eu >>>>> http://car.mines-douai.fr/ >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> ~~Jannik Laval~~ >>>> Ãcole des Mines de Douai >>>> Enseignant-chercheur >>>> http://www.jannik-laval.eu >>>> http://car.mines-douai.fr/ >>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> best, >>> Eliot >>> >>> >>> >> >> >> -- >> >> ~~Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> http://car.mines-douai.fr/ >> >> >> >> > > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

Feb. 24, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by Ronie Salgado

Hi! Now I have Internet access for a pair of days again. Oops, I had forgotten to commit code, which added warnings for classes starting with lowercase. Unfortunately, there is not a general automated way for dealing with classes starting, that also avoids names clashes. The only solution is to issue a warning telling the problematic class, and allow the programmer to rename it using the %rename(NewName) oldName; directive, by placing it in the interface definition file. About the newlines, I took the opportunity to add code for replacing all of them with CR, in the generated Smalltalk code. Now I remembered a hard to fix bug, with overloaded functions. Currently this uses the arguments names to generate their selector, but it does not take into account their types. The following illustrates the problem: void overloadedFunctionA(int a, int b); -> Module class>>overloadedFunctionA: a b: b void overloadedFunctionA(float a, double b); -> Module class>>overloadedFunctionA: a b: b Different signatures, but the same selector is generated. A method implementation is generated for both of them, but because they have the same selector and belong to the same class, only the last implementation can be seem, because it overwrites the previous ones. Another problem is with C++exception handling, is not implemented yet, but it is possible to support them. Best Regards, Ronie 2014-02-21 15:43 GMT-03:00 GÃ¶ran Krampe <goran(a)krampe.se>: > Hey! > > > On 02/21/2014 06:50 PM, Ronie Salgado wrote: > >> Hi there!, >> >> It is great to hear that it is being useful. Currently I am taking some >> vacations, so I will probably be without Internet access for some days. >> > [SNIP] > > > I took that kind of approach because it gives more flexibility, but it >> provides probably a reduced performance in comparison with placing the >> callouts directly in the wrapped classes. Some people that saw this when >> developing this did not like this approach. >> > > Yeah, I can see what you mean - and I think that's just fine. > > One bit tricky problem: there are classes generated starting with lower > case. That doesn't fly :) > > Also, LF instead of CRs after signatures makes NB barf when parsing. That > was easily solved with a global tr '\n' '\r' of course, the class naming is > a bit harder - need to go to the source. > > I can see if I can find that one :) > > regards, GÃ¶ran > > PS. Tried wrapping Nanomsg.org today, got so far as to start running test > code - but then it fails creating a socket - not sure why, might not be > your fault at all actually :) When it works I will blog about it. > >

Feb. 24, 2014

SysLogSender / UDP

by Pharo4Stef

Hi all Iâm integrating the SysLogSender of Goran as an extension of SystemLogger and my system gets blocked when I try to send something. I just did the same as in the original version (and know nothing about upd and port). I suspect that on mac is not working the same. https://developer.apple.com/library/mac/documentation/macosx/conceptual/bps… Does any of you have some ideas? my code look like that: | logger | logger := SysLogSender new addHost: 'localhost' port: 514. Log dispatcher addLogger: logger. Log dispatcher startAllLoggers. send: message to: host port: port "Send formatted UDP message to host and port." | sock | sock := Socket newUDP. sock setPeer: NetNameResolver localHostAddress port: port. sock sendData: message. sock waitForSendDoneFor: Socket standardTimeout. sock close Stef

Feb. 23, 2014

Re: [Pharo-dev] Morphic UI designer

by Pharo4Stef

> Hi Steff, > > may I ask why Phobos is not considered as a good candidate as a basis for an interface designer? Because not all the UI should require XULRunner and a web browser. > I have experience with PARTS (which is the best application in the field I have ever seen in ST environment) and I believe that it could be used as a basis for tools of this kind. We would love to have such kind of UI Builder. It will happen but some people have to do it first. > If anyone is interested in PARTS (included in VSE ST) as a model, I will be pleased to send it. Is it not protected from a license point of view. >

Feb. 23, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

I would define > OPALCompilationLogEvent as a subclass of Log and add the information it wants and special behavior identify borken method. I added a description to the chapter and I updated the class comments to reflect that. Stef On 23 Feb 2014, at 19:00, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 23.02.2014 um 18:54 schrieb Pharo4Stef <pharo4Stef(a)free.fr>: > >> >>> But I understand, that is not my point. >> >> Yes I saw it after sending and reading the other mails. >> This part was made by norbert and it was not obvious to me. >> Iâm adding the example to the chapter right now. >> > If it wasnât obvious can you give an example how the OPALCompilationLogEvent would work. Maybe we still have a dissonance here. Is OPALCompilationLogEvent a subclass of Log or ist the log message from opal put into the message of a log or even done with extension? > > Norbert >> >> >>> You just need to add a clear example to the docs to make your point, because now you don't, everything is just old school string messages. >>> >>> On 23 Feb 2014, at 18:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>> >>>> >>>> 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

Re: [Pharo-dev] SystemLogger unrevealed :)

by Norbert Hartl

Am 23.02.2014 um 18:54 schrieb Pharo4Stef <pharo4Stef(a)free.fr>: > >> But I understand, that is not my point. > > Yes I saw it after sending and reading the other mails. > This part was made by norbert and it was not obvious to me. > Iâm adding the example to the chapter right now. > If it wasnât obvious can you give an example how the OPALCompilationLogEvent would work. Maybe we still have a dissonance here. Is OPALCompilationLogEvent a subclass of Log or ist the log message from opal put into the message of a log or even done with extension? Norbert > > >> You just need to add a clear example to the docs to make your point, because now you don't, everything is just old school string messages. >> >> On 23 Feb 2014, at 18:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> >>> >>> 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

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

> But I understand, that is not my point. Yes I saw it after sending and reading the other mails. This part was made by norbert and it was not obvious to me. Iâm adding the example to the chapter right now. > You just need to add a clear example to the docs to make your point, because now you don't, everything is just old school string messages. > > On 23 Feb 2014, at 18:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> >> 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

Re: [Pharo-dev] SystemLogger unrevealed :)

by Sven Van Caekenberghe

But I understand, that is not my point. You just need to add a clear example to the docs to make your point, because now you don't, everything is just old school string messages. On 23 Feb 2014, at 18:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > 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