Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread Stéphane Ducasse
Sure have a look at SystemLogger http://smalltalkhub.com/#!/~StephaneDucasse/SystemLogger I did not check the changes made by norbert. I will work on it during xmas. Stef On Dec 3, 2013, at 11:47 AM, "p...@highoctane.be" wrote: > What's wrong with Strings anyway? But yeah, I underst

Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread Norbert Hartl
Am 03.12.2013 um 11:47 schrieb p...@highoctane.be: > What's wrong with Strings anyway? But yeah, I understand your point. > Strings are fine when you don’t need specific behavior oder structure of your log messages anymore. A conversion to string should in most cases happen as late as possible

Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread p...@highoctane.be
What's wrong with Strings anyway? But yeah, I understand your point. What I have done for my own stuff is to have a TLog aspect with info, debug, error, warn and, well, Strings. But double dispatch could take care of that, like printOn:, storeOn: etc. Do you have some code that I can look at? TL

Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread Stéphane Ducasse
On Dec 3, 2013, at 10:34 AM, p...@highoctane.be wrote: > I am working on this one. > > Don't kill the transcript, it is useful when working without a console. I will not kill it but it will just be dull outputer for my logger. In fact I'm missing a user interface (the idea was to build it with

Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread p...@highoctane.be
I am working on this one. Don't kill the transcript, it is useful when working without a console. Now, adding the features you mention is not hard. And the top right triangle menu of Transcript could get a clue from the Workspace one with a Save As entry. I once had an issue with things like (ou

Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread Stéphane Ducasse
On Dec 3, 2013, at 2:59 AM, Esteban A. Maringolo wrote: > 2013/12/2 Sean P. DeNigris : >> EstebanLM wrote >>> yes, the transcript is ThreadSafeTranscript >> >> Does "ThreadSafe" mean I don't have to wrap all my debug logging in >> "WorldState addDeferredUIMessage: [ Transcript... ]? That would

Re: [Pharo-dev] transcript is plain bad

2013-12-03 Thread Stéphane Ducasse
On Dec 2, 2013, at 8:46 PM, p...@highoctane.be wrote: > And missing a ton of methods. > > Teh StackInterpreterSimulator is agreeing with this statement. send us the ones that are missing. Please note that we should kill the transcript in the future because this is a ^%$&*((^%$* outdated way t

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Norbert Hartl
> Am 02.12.2013 um 19:56 schrieb Stéphane Ducasse : > > >> The return of the toothpick is near. o/ > > No I will finish my logger :) > From next week on I will have a little time to work on it, too. If you like we can discuss a few things and bring to some usable state. Norbert

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Igor Stasenko
On 3 December 2013 02:59, Esteban A. Maringolo wrote: > 2013/12/2 Sean P. DeNigris : > > EstebanLM wrote > >> yes, the transcript is ThreadSafeTranscript > > > > Does "ThreadSafe" mean I don't have to wrap all my debug logging in > > "WorldState addDeferredUIMessage: [ Transcript... ]? That would

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Esteban A. Maringolo
2013/12/2 Sean P. DeNigris : > EstebanLM wrote >> yes, the transcript is ThreadSafeTranscript > > Does "ThreadSafe" mean I don't have to wrap all my debug logging in > "WorldState addDeferredUIMessage: [ Transcript... ]? That would save a lot > of time :) According to the implementation it means t

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Sean P. DeNigris
EstebanLM wrote > yes, the transcript is ThreadSafeTranscript Does "ThreadSafe" mean I don't have to wrap all my debug logging in "WorldState addDeferredUIMessage: [ Transcript... ]? That would save a lot of time :) - Cheers, Sean -- View this message in context: http://forum.world.st/tran

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread p...@highoctane.be
And missing a ton of methods. Teh StackInterpreterSimulator is agreeing with this statement. On Mon, Dec 2, 2013 at 8:05 PM, Esteban Lorenzano wrote: > yes, the transcript is ThreadSafeTranscript > > > On Mon, Dec 2, 2013 at 8:00 PM, Yuriy Tymchuk wrote: > >> Buy the way, is absence of Trans

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Esteban Lorenzano
yes, the transcript is ThreadSafeTranscript On Mon, Dec 2, 2013 at 8:00 PM, Yuriy Tymchuk wrote: > Buy the way, is absence of Transcript class - ok? > > I know how it all works now, but is it ok? :) > > uko > > > On 02 Dec 2013, at 19:58, Esteban Lorenzano wrote: > > yes, please :) > > > On Mo

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Yuriy Tymchuk
Buy the way, is absence of Transcript class - ok? I know how it all works now, but is it ok? :) uko On 02 Dec 2013, at 19:58, Esteban Lorenzano wrote: > yes, please :) > > > On Mon, Dec 2, 2013 at 7:56 PM, Stéphane Ducasse > wrote: > > > The return of the toothpick is near. o/ > > No I w

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Esteban Lorenzano
yes, please :) On Mon, Dec 2, 2013 at 7:56 PM, Stéphane Ducasse wrote: > > > The return of the toothpick is near. o/ > > No I will finish my logger :) > > Stef > >

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread Stéphane Ducasse
> The return of the toothpick is near. o/ No I will finish my logger :) Stef

Re: [Pharo-dev] transcript is plain bad

2013-12-02 Thread p...@highoctane.be
The return of the toothpick is near. o/ On Mon, Dec 2, 2013 at 6:54 PM, Stéphane Ducasse wrote: > I can tell that it does not work when loading partial code because all the > compiler warnings make sure that you > cannot see anything…. > I should have pushed my logger more. :( >