Hi guys This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people. Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ... How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review I think that it can be fun and motivating. So let me know because I would like to have more social coding. Stef
Hi Stef, Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial. Norbert Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
SystemLogger interests me as well. Phil On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote:
Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
Me too. I already gave a first set of feedback. As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry Doru On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <phil@highoctane.be>wrote:
SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name>wrote:
Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com "Every thing has its own flow"
Am 19.05.2014 um 14:31 schrieb Tudor Girba <tudor@tudorgirba.com>:
Me too. I already gave a first set of feedback.
publicly? Norbert
As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <phil@highoctane.be> wrote: SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote: Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
Of course, publicly. It's in the reply of the first announcement. Doru On Mon, May 19, 2014 at 2:45 PM, Norbert Hartl <norbert@hartl.name> wrote:
Am 19.05.2014 um 14:31 schrieb Tudor Girba <tudor@tudorgirba.com>:
Me too. I already gave a first set of feedback.
publicly?
Norbert
As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <phil@highoctane.be>wrote:
SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name>wrote:
Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
I am interested as well. I had some private discussions with Norbert and Doru, and I used a different approach on one of my projects very recently that I am quite happy with. BTW, I have long term plans to change ZnLogEvent... On 19 May 2014, at 14:31, Tudor Girba <tudor@tudorgirba.com> wrote:
Me too. I already gave a first set of feedback.
As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <phil@highoctane.be> wrote: SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote: Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
a blog post could help a lot because I have no clue what systemLogger suppose to do or the other things. I was actually thinking enhancing Workspace. On Mon, May 19, 2014 at 3:49 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I am interested as well.
I had some private discussions with Norbert and Doru, and I used a different approach on one of my projects very recently that I am quite happy with.
BTW, I have long term plans to change ZnLogEvent...
On 19 May 2014, at 14:31, Tudor Girba <tudor@tudorgirba.com> wrote:
Me too. I already gave a first set of feedback.
As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <phil@highoctane.be> wrote: SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote: Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
How would you like to change Workspace? Doru On Mon, May 19, 2014 at 2:56 PM, kilon alios <kilon.alios@gmail.com> wrote:
a blog post could help a lot because I have no clue what systemLogger suppose to do or the other things.
I was actually thinking enhancing Workspace.
On Mon, May 19, 2014 at 3:49 PM, Sven Van Caekenberghe <sven@stfx.eu>wrote:
I am interested as well.
I had some private discussions with Norbert and Doru, and I used a different approach on one of my projects very recently that I am quite happy with.
BTW, I have long term plans to change ZnLogEvent...
On 19 May 2014, at 14:31, Tudor Girba <tudor@tudorgirba.com> wrote:
Me too. I already gave a first set of feedback.
As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be < phil@highoctane.be> wrote: SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote: Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
I have several ideas. I would like to test them in practice to see how well they work. 1) I would like to render prints to separate area from the code area, so the user wont have to delete those prints to carry on coding. I dont know if an embeded inspector would make more sense in this case, with continuous tracking of values. 2) I would also like to render information like the super class of an object, class comment, implementors of a method, etc without having to open a system browser to do so from inside workspace. 3) Another thing is emac's like navigation around, move to next message, easy selection and generally the usual stuff one can do with emacs without having to use a mouse. 4) a History feature would also be cool, something that can track changes of a workspace and have different versions of a code. Probably there is already this feature , with the ability to recall past workspace but maybe I could polish it a bit. 5) Also I am interested in quick creation of methods and classes, select a piece of code in workspace and send it to a method directly again completely bypassing the system browser and preferably not having to pop up dialog messages. 6) Embedding widgets like sliders and knobs for quickly changing values with the mouse could be nice as well. Going to study the Moose playground as well to see how you guys hack the workspace. On Mon, May 19, 2014 at 4:00 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
How would you like to change Workspace?
Doru
On Mon, May 19, 2014 at 2:56 PM, kilon alios <kilon.alios@gmail.com>wrote:
a blog post could help a lot because I have no clue what systemLogger suppose to do or the other things.
I was actually thinking enhancing Workspace.
On Mon, May 19, 2014 at 3:49 PM, Sven Van Caekenberghe <sven@stfx.eu>wrote:
I am interested as well.
I had some private discussions with Norbert and Doru, and I used a different approach on one of my projects very recently that I am quite happy with.
BTW, I have long term plans to change ZnLogEvent...
On 19 May 2014, at 14:31, Tudor Girba <tudor@tudorgirba.com> wrote:
Me too. I already gave a first set of feedback.
As a general matter, I would be interested in: - unifying with the ZnLogEvent - Split the Log class - Possibly support Fuel serialization for each log entry
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be < phil@highoctane.be> wrote: SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote: Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
On 19/5/14 14:56, kilon alios wrote:
a blog post could help a lot because I have no clue what systemLogger suppose to do or the other things.
there is a full chapter on it. https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/590/artifac...
I was actually thinking enhancing Workspace.
On Mon, May 19, 2014 at 3:49 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
I am interested as well.
I had some private discussions with Norbert and Doru, and I used a different approach on one of my projects very recently that I am quite happy with.
BTW, I have long term plans to change ZnLogEvent...
On 19 May 2014, at 14:31, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote:
> Me too. I already gave a first set of feedback. > > As a general matter, I would be interested in: > - unifying with the ZnLogEvent > - Split the Log class > - Possibly support Fuel serialization for each log entry > > Doru > > > On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>> wrote: > SystemLogger interests me as well. > > Phil > > > On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote: > Hi Stef, > > Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial. > > Norbert > > Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>: > > > Hi guys > > > > This is a call for some of you that committed code and would like to do it with me :). > > I have some projects that I would like to push further in 4.0 and I'm thinking that > > he could be much more fun to do it with other people. > > > > Here are some topics > > - integrating the systemLogger > > - integrating/improving the new method categorizer > > - cleaning fonts > > - ... > > > > How this could work? > > We could have > > - some discussions > > - make a little roadmap > > - then we could work on the same slice and do code review > > > > I think that it can be fun and motivating. So let me know because I would like to have more social > > coding. > > > > Stef > > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"
On 19/5/14 14:31, Tudor Girba wrote:
Me too. I already gave a first set of feedback.
As a general matter, I would be interested in: - unifying with the ZnLogEvent
first we should integrate it and make sure that all the Transcript show are funnelled to the Log frameworks.
- Split the Log class
we will not split it because we iterated over the design since 8 months with norbert :)
- Possibly support Fuel serialization for each log entry Please go ahead.
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>> wrote:
SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote:
Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>:
> Hi guys > > This is a call for some of you that committed code and would like to do it with me :). > I have some projects that I would like to push further in 4.0 and I'm thinking that > he could be much more fun to do it with other people. > > Here are some topics > - integrating the systemLogger > - integrating/improving the new method categorizer > - cleaning fonts > - ... > > How this could work? > We could have > - some discussions > - make a little roadmap > - then we could work on the same slice and do code review > > I think that it can be fun and motivating. So let me know because I would like to have more social > coding. > > Stef >
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
Am 21.05.2014 um 08:24 schrieb stepharo <stepharo@free.fr>:
On 19/5/14 14:31, Tudor Girba wrote:
Me too. I already gave a first set of feedback.
As a general matter, I would be interested in: - unifying with the ZnLogEvent
If this means talking to Sven this is a definite yes. I donât think we need to unify with the current ZnLogEvent. Syncing with zinc is probably not the way to go anyway. Zinc is still an external framework (hence the namespace prefix). I did a zinc bridge which operates an a single event bridging from zinc to SystemLogger. This is not clever performance wise. A better approach is to plug into zincs LogSupport. We should hook into there so we just get the invocations from zinc and we can emit the proper SystemLogger events into the Log framework. Sven will come up with something announcement based. And that is still a task for us, too. To look where functionality of SystemLogger is doubled with announcements.
first we should integrate it and make sure that all the Transcript show are funnelled to the Log frameworks.
Yes. Maybe we need to sync our understanding of log levels first. The exchange adds a log level and adding a tag would be good, too.
- Split the Log class
we will not split it because we iterated over the design since 8 months with norbert :)
I cannot find the proposals of Doru. But Iâm interested. I splitted the Log class already into BasicLog and Log. Iâm not fully satisfied with it so ⦠My concern about the Log class is more how get it right supporting different kind of Log classes and still have a working filtering in the Logger. But that we can discuss in the groups that form I guess
- Possibly support Fuel serialization for each log entry Please go ahead.
Yes. I donât even understand what it means :) Norbert
Doru
On Mon, May 19, 2014 at 11:01 AM, phil@highoctane.be <phil@highoctane.be> wrote: SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name> wrote: Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr>:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
-- www.tudorgirba.com
"Every thing has its own flow"
As a general matter, I would be interested in: - unifying with the ZnLogEvent
SystemLogger is infrastructure low level. So I do not see why Zn and SystemLogger should be unified.
If this means talking to Sven this is a definite yes. I donât think we need to unify with the current ZnLogEvent. Syncing with zinc is probably not the way to go anyway. Zinc is still an external framework (hence the namespace prefix). I did a zinc bridge which operates an a single event bridging from zinc to SystemLogger. This is not clever performance wise. A better approach is to plug into zincs LogSupport. We should hook into there so we just get the invocations from zinc and we can emit the proper SystemLogger events into the Log framework. Sven will come up with something announcement based. And that is still a task for us, too. To look where functionality of SystemLogger is doubled with announcements.
We should pay attention that it stays small and simple.
first we should integrate it and make sure that all the Transcript show are funnelled to the Log frameworks.
Yes. Maybe we need to sync our understanding of log levels first. The exchange adds a log level and adding a tag would be good, too.
I do not get it but this is not a problem. No need to reply.
- Split the Log class
we will not split it because we iterated over the design since 8 months with norbert :)
I cannot find the proposals of Doru. But Iâm interested. I splitted the Log class already into BasicLog and Log. Iâm not fully satisfied with it so ⦠My concern about the Log class is more how get it right supporting different kind of Log classes and still have a working filtering in the Logger. But that we can discuss in the groups that form I guess I would like to stop iterating. And again we should keep the system small. I studied all the logger framework available and I think that we can look for the graal forever or get done and I want to get done because there are other many many topics that can get fixed. Right now we went from 0% to 80% and this is a good ratio. We iterated with you. Now I do not want to pass time to go to an hypothetical 85%.
- Possibly support Fuel serialization for each log entry Please go ahead.
Yes. I donât even understand what it means :) Send code!
Hi, I really do not get the tone of these replies, but perhaps my mail was not clear. So, let me start over. You asked for who is interested in joining co-coding, and I said that I am interested particularly in the area of the logger. Specifically, I would be interested in splitting the Log class into two: - a Log class holding the current class side methods - a LogEvent (or LogEntry, or LogItem or whatever other name indicating the result of a single log statement) that holds the instance side of the current Log class. As it is now, when I execute: Log critical: 'message' I get an instance of Log. This is confusing, and not needed. We can nicely get an instance of LogEvent. This will not complicate things at all. Next, I said that as we already have a Zinc logging mechanism, I would be interested in consolidating Zinc to use the new mechanism. This would also provide a case study for having explicit classes of LogEvents and see the implications of that. And finally, I mentioned the Fuel serialization. My idea was to offer a cheap way to serialize a log into a file by serializing each log entry as a fuel object, but I did not know that we already have a JSON serialization. So, this is not that much of a priority anymore. I will propose code for the splitting. Doru On Wed, May 21, 2014 at 9:05 AM, stepharo <stepharo@free.fr> wrote:
As a general matter, I would be interested in: - unifying with the ZnLogEvent
SystemLogger is infrastructure low level. So I do not see why Zn and SystemLogger should be unified.
If this means talking to Sven this is a definite yes. I donât think we
need to unify with the current ZnLogEvent. Syncing with zinc is probably not the way to go anyway. Zinc is still an external framework (hence the namespace prefix). I did a zinc bridge which operates an a single event bridging from zinc to SystemLogger. This is not clever performance wise. A better approach is to plug into zincs LogSupport. We should hook into there so we just get the invocations from zinc and we can emit the proper SystemLogger events into the Log framework. Sven will come up with something announcement based. And that is still a task for us, too. To look where functionality of SystemLogger is doubled with announcements.
We should pay attention that it stays small and simple.
first we should integrate it and make sure that all the Transcript show
are funnelled to the Log frameworks.
Yes. Maybe we need to sync our understanding of log levels first. The exchange adds a log level and adding a tag would be good, too.
I do not get it but this is not a problem. No need to reply.
- Split the Log class
we will not split it because we iterated over the design since 8 months with norbert :)
I cannot find the proposals of Doru. But Iâm interested. I splitted the Log class already into BasicLog and Log. Iâm not fully satisfied with it so ⦠My concern about the Log class is more how get it right supporting different kind of Log classes and still have a working filtering in the Logger. But that we can discuss in the groups that form I guess
I would like to stop iterating. And again we should keep the system small. I studied all the logger framework available and I think that we can look for the graal forever or get done and I want to get done because there are other many many topics that can get fixed. Right now we went from 0% to 80% and this is a good ratio. We iterated with you. Now I do not want to pass time to go to an hypothetical 85%.
- Possibly support Fuel serialization for each log entry
Please go ahead.
Yes. I donât even understand what it means :)
Send code!
-- www.tudorgirba.com "Every thing has its own flow"
Am 21.05.2014 um 14:24 schrieb Tudor Girba <tudor@tudorgirba.com>:
As it is now, when I execute: Log critical: 'message'
I get an instance of Log. This is confusing, and not needed. We can nicely get an instance of LogEvent. This will not complicate things at all.
Please take Object>>#asLog into account when doing it. Norbert
Am 21.05.2014 um 09:05 schrieb stepharo <stepharo@free.fr>:
As a general matter, I would be interested in: - unifying with the ZnLogEvent
SystemLogger is infrastructure low level. So I do not see why Zn and SystemLogger should be unified.
yep
If this means talking to Sven this is a definite yes. I donât think we need to unify with the current ZnLogEvent. Syncing with zinc is probably not the way to go anyway. Zinc is still an external framework (hence the namespace prefix). I did a zinc bridge which operates an a single event bridging from zinc to SystemLogger. This is not clever performance wise. A better approach is to plug into zincs LogSupport. We should hook into there so we just get the invocations from zinc and we can emit the proper SystemLogger events into the Log framework. Sven will come up with something announcement based. And that is still a task for us, too. To look where functionality of SystemLogger is doubled with announcements.
We should pay attention that it stays small and simple.
It is and will be an extra anyway. You load zinc, you load SystemLogger, you load the glue code between them. Nothing to bloat the core.
first we should integrate it and make sure that all the Transcript show are funnelled to the Log frameworks.
Yes. Maybe we need to sync our understanding of log levels first. The exchange adds a log level and adding a tag would be good, too.
I do not get it but this is not a problem. No need to reply.
The Log as it is at the moment contains log level and a tag. Going from a simple logCr: you have to add a log level. Not everything will be debug/trace. With the tag I meant the tag of the Log class. This is a first-class citizen for categorizing and should be something like âimageâ or even better the name of the sub-system that emitted the message. Clear now? Norbert
- Split the Log class
we will not split it because we iterated over the design since 8 months with norbert :)
I cannot find the proposals of Doru. But Iâm interested. I splitted the Log class already into BasicLog and Log. Iâm not fully satisfied with it so ⦠My concern about the Log class is more how get it right supporting different kind of Log classes and still have a working filtering in the Logger. But that we can discuss in the groups that form I guess I would like to stop iterating. And again we should keep the system small. I studied all the logger framework available and I think that we can look for the graal forever or get done and I want to get done because there are other many many topics that can get fixed. Right now we went from 0% to 80% and this is a good ratio. We iterated with you. Now I do not want to pass time to go to an hypothetical 85%.
- Possibly support Fuel serialization for each log entry Please go ahead.
Yes. I donât even understand what it means :) Send code!
Hi phil Have a look at - http://smalltalkhub.com/#!/~StephaneDucasse/SystemLogger - and the chapter :) https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccess... On 19/5/14 11:01, phil@highoctane.be wrote:
SystemLogger interests me as well.
Phil
On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote:
Hi Stef,
Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial.
Norbert
Am 19.05.2014 um 09:10 schrieb stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>:
> Hi guys > > This is a call for some of you that committed code and would like to do it with me :). > I have some projects that I would like to push further in 4.0 and I'm thinking that > he could be much more fun to do it with other people. > > Here are some topics > - integrating the systemLogger > - integrating/improving the new method categorizer > - cleaning fonts > - ... > > How this could work? > We could have > - some discussions > - make a little roadmap > - then we could work on the same slice and do code review > > I think that it can be fun and motivating. So let me know because I would like to have more social > coding. > > Stef >
great move! Iâm not available but you should blog and announce about this! guys activate your social media about this people need this kind of signal beating is their chance to get involved and get great code mentoring On May 19, 2014, at 4:10 AM, stepharo <stepharo@free.fr> wrote:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
Hi Stef (and all :)). Would be nice. Iâm anyway going to do something for Pharo and from time to time Iâm making small contributions here and there. As now Iâm working on code design/quality out of listed things I like method categoriser the most. But other options are acceptable. Uko On 19 May 2014, at 09:10, stepharo <stepharo@free.fr> wrote:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
Hi yuriy have a look at http://smalltalkhub.com/#!/~StephaneDucasse/AutomaticMethodCategorizer I should check again what I wanted to do before release and integration. The point is not to make it too complex. I would like to have much better rules and in fact I want to recategorise the complete system with them but we have to take care. Stef On 19/5/14 15:08, Yuriy Tymchuk wrote:
Hi Stef (and all :)).
Would be nice. Iâm anyway going to do something for Pharo and from time to time Iâm making small contributions here and there. As now Iâm working on code design/quality out of listed things I like method categoriser the most. But other options are acceptable.
Uko
On 19 May 2014, at 09:10, stepharo <stepharo@free.fr> wrote:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
On Wed, May 21, 2014 at 8:30 AM, stepharo <stepharo@free.fr> wrote:
Hi yuriy
have a look at
http://smalltalkhub.com/#!/~StephaneDucasse/AutomaticMethodCategorizer
I should check again what I wanted to do before release and integration. The point is not to make it too complex. I would like to have much better rules and in fact I want to recategorise the complete system with them but we have to take care.
It would be nice to have a way to add typical protocols. e.g. Doing Seaside dev, add initialization/rendering/actions/... protocols. Now, I can always copy a "template" class, but it would be nice to have. Phil
Stef
On 19/5/14 15:08, Yuriy Tymchuk wrote:
Hi Stef (and all :)).
Would be nice. Iâm anyway going to do something for Pharo and from time to time Iâm making small contributions here and there. As now Iâm working on code design/quality out of listed things I like method categoriser the most. But other options are acceptable.
Uko
On 19 May 2014, at 09:10, stepharo <stepharo@free.fr> wrote:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
I'm currently writing some roadmaps about each possible topics. I will send them when I'm done. Stef
For SystemLogger here is my roadmap steps - note that SystemLogger has a special logger that pushes strings to Transcript so we can have the same as now. - right now in Object we have crTrace crTrace: trace trace: traceCr traceCr: logCr: deprecated crLog: deprecated so we can use trace: (I do not like it that much but this is ok) - check all the Transcript left reference - convert them to use the SystemLogger probably to trace: so that after we can simply rewrite trace: - I think that it would be good to have a single entry point in Object (even at the cost to send another call to the main log recording method) - check all the log: - convert them (since a log is an entry we do not need to have explicit cr) - may be use a circular structure for holding entries because right now the logger logs as much as possible. - We should probably have different settings and the default should be circular - produce a nice transcript with structured log entries - log entries should be able to provide specific actions - for example a compiler logentry could hold a reference to the compiled method and we could ask to jump there - filter logentries - make sure that all the crLog: logCr: are nicely funnel to the systemLogger - and that everything works
I started to write to files with roadmaps so that other people can work with me :). https://github.com/pharo-project/pharo-workingRoadmaps Nicola Heiss should prepare one or two on cleaning Nautilus, Theme, and or KeyMappings Stef
Hi Stef, this is great. I would like to participate on fonts, because I want to understand how it works. I have just read https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/CleaningF... FT means FreeType? Thanks. There is a lot of issues. Where do you recommend to start? Cheers, Juraj El 19-05-2014, a las 3:10, stepharo <stepharo@free.fr> escribió:
Hi guys
This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people.
Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ...
How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review
I think that it can be fun and motivating. So let me know because I would like to have more social coding.
Stef
participants (9)
-
Juraj Kubelka -
kilon alios -
Norbert Hartl -
phil＠highoctane.be -
Sebastian Sastre -
stepharo -
Sven Van Caekenberghe -
Tudor Girba -
Yuriy Tymchuk