log4cocoa-development — Discussion of all Log4Cocoa dev issues

[Log4cocoa-development] Re: sleeping project looking for new owner

[Ruotger S. <ro...@ma...>]

Hi Bob,

if the offer still is open, I'd be willing to do it. I wont invest  
large amounts of time but I'd maintain the project and implement all  
the features I am missing which would be:

- configuration through NSUserDefault
- "porting" unit tests to XCode's built-in SenTestingKit.framework

Roddi


> Hi,
>
> Despite my desire to get back and work some more on Log4Cocoa ---  
> it is
> unlikely for the foreseeable future.  So, I"ve decided to cast my lot
> to the wind.  If anyone has any interest in taking over this project
> (or knows someone qualified to do so), please contact me.
>
> I think I should acknowledge the reality that no development has
> occurred in over a year and that without a new leader, its unlikely
> that new development will start up again any time soon.  Thanks all  
> for
> working on it.  I did enjoy this project when I had the time.
>
>
> Thanks,
>
> -Bob

[Log4cocoa-development] Patch submitted

[Ruotger S. <ro...@ma...>]

Hi people,

I have submitted a patch that eliminates some of the compiler  
warnings. Please have a look

Thanks,
    Roddi

P.S.: I already posted this on log...@li...  
but it was meant for this list, sorry

[Log4cocoa-development] sleeping project looking for new owner

[Bob F. <chi...@ma...>]

Hi,

Despite my desire to get back and work some more on Log4Cocoa --- it is 
unlikely for the foreseeable future.  So, I've decided to cast my lot 
to the wind.  If anyone has any interest in taking over this project 
(or knows someone qualified to do so), please contact me.

I think I should acknowledge the reality that no development has 
occurred in over a year and that without a new leader, its unlikely 
that new development will start up again any time soon.  Thanks all for 
working on it.  I did enjoy this project when I had the time.


Thanks,

-Bob

[Log4cocoa-development] Documentation

[Eric W. <ew...@ny...>]

Hi,

Is there a tutorial on how to use Log4Cocoa? I don't have any experience
using Log4J so things like appenders and layouts are alien to me. I read
through the readme, but unfortunately it hasn't really helped my
understanding.

Thanks for any help,
Eric Wang

[Log4cocoa-development] status, questions, etc.

[Brendan W.M. <bmc...@sl...>]

Greetings all ...I'm noticing from the list that people are more or 
less on break from the project.

I was ecstatic to find this package, as I'm fairly new to cocoa but 
have spent alot of time in Perl and Java.  Suffice to say i'm a bit of 
a log4j junkie.

I'm wondering if there's anything I can do to help out with things; one 
of the things I'd like to do (I'm doing it on my local copy for 
simplicity) is have formats implicitly supported within the log 
messages, or at the least have L4InfoF or such methods.

Or I may be way off base and missing the fact that these are already in 
here (according to what I read you still need to pass an NSString 
stringWtihFormat, etc. into the log message).

thoughts?
---
Brendan W. McAdams
bmc...@tw...

"I am free, no matter what rules surround me. If I find them tolerable, 
I tolerate them; if I find them too obnoxious, I break them. I am free 
because I know that I alone am morally responsible for everything I 
do."				--- Professor Bernardo de La Paz
			     Robert A. Heinlein "The Moon Is A Harsh Mistress"

Re: [Log4cocoa-development] status

[Bob F. <chi...@ma...>]

On Sep 2, 2004, at 9:41 AM, Don Willems wrote:

>> Yes, this is a port of Log4J.  It is basically functional and a few 
>> folks are using it.  It is missing many Appenders.  Frankly, its 
>> suffering from, Bob hasn't had any time to work on it for a while 
>> disease :-)
>
> Ah yes, I know that problem (at least if you replace 'Bob' with 
> another name ;-).
>
>> Please check it out, you can do an anonymous check out.
>
> Yes I did that.
> I first downloaded the tar file. But that release of log4cocoa was 
> missing an (for me) essential appender (the file appender). Luckily 
> the file appender is in CVS.
>
>> If you'd like to contribute, please send me a patch and I'll put it 
>> in, or if you want you can join the project.
>
> Yes, I'd like to help out.
> I'm actually working on a (very basic) log viewer for which I'll need 
> an appender that uses sockets. I may be able to use the 
> L4WriterAppender for that.
>
> If it's ok with you than you can add me to the project, my unix name 
> at sourceforge is 'wonco'.
>
> Bye,
> Don

Hello & Welcome wonco.  You've been added to the project.  Enjoy.

-Bob

Re: [Log4cocoa-development] status

[Don W. <don...@ma...>]

> Yes, this is a port of Log4J.  It is basically functional and a few  
> folks are using it.  It is missing many Appenders.  Frankly, its  
> suffering from, Bob hasn't had any time to work on it for a while  
> disease :-)

Ah yes, I know that problem (at least if you replace 'Bob' with another  
name ;-).

> Please check it out, you can do an anonymous check out.

Yes I did that.
I first downloaded the tar file. But that release of log4cocoa was  
missing an (for me) essential appender (the file appender). Luckily the  
file appender is in CVS.

> If you'd like to contribute, please send me a patch and I'll put it  
> in, or if you want you can join the project.

Yes, I'd like to help out.
I'm actually working on a (very basic) log viewer for which I'll need  
an appender that uses sockets. I may be able to use the  
L4WriterAppender for that.

If it's ok with you than you can add me to the project, my unix name at  
sourceforge is 'wonco'.

Bye,
Don


Don Willems
NICI, Cognitive Engineering - University of Nijmegen
------------------------------------------------------------------------ 
-------------------------
Montessorilaan 3, Room: B.02.02
P.O.Box 9104, 6500 HE Nijmegen, The Netherlands
phone: +31 24 3616029	 	| fax: +31 24 2616066
email: dd....@ni... 	| http://homepage.mac.com/don_willems
------------------------------------------------------------------------ 
-------------------------

Re: [Log4cocoa-development] status

[Bob F. <chi...@ma...>]

On Aug 31, 2004, at 3:49 PM, Don Willems wrote:

> Hi,

Hi,

> I stumbled on Log4Cocoa today when I was looking for logging options 
> in Cocoa.
> As this is a port of Log4J, I'm wondering which features of Log4J are 
> already included in Log4Cocoa and which features still need to be 
> ported?

Yes, this is a port of Log4J.  It is basically functional and a few 
folks are using it.  It is missing many Appenders.  Frankly, its 
suffering from, Bob hasn't had any time to work on it for a while 
disease :-)

Please check it out, you can do an anonymous check out.  If you'd like 
to contribute, please send me a patch and I'll put it in, or if you 
want you can join the project.

-Bob "still hoping to get back to this someday" Frank

[Log4cocoa-development] status

[Don W. <don...@ma...>]

Hi,

I stumbled on Log4Cocoa today when I was looking for logging options in 
Cocoa.
As this is a port of Log4J, I'm wondering which features of Log4J are 
already included in Log4Cocoa and which features still need to be 
ported?

Many thanks,
Don

[Log4cocoa-development] welcome new developer

[Bob F. <chi...@ma...>]

Hi All,

I just wanted to welcome Michael James as a new developer on Log4Cocoa. 
  He is planning on adding additional support for Pattern Layouts.

Welcome and happy coding.

-Bob

[Log4cocoa-development] Fwd: Log4Cocoa feedback

[Bob F. <chi...@ma...>]

Thanks!

The README hasn't been updated in a while.  I'd check the top of tree=20
cvs.   Michael Tsai did some work on variadic macros that was pretty=20
nice.

You probably noticed that there hasn't been any activity in a while. =20
I've been busy (had a baby, bought a house, and got busy at work :-) =20
Even though I don't know when I'd find the time, I still hope to pick=20
this up again.

Do you have any other comments or suggestions?  I'd appreciate any=20
additional feedback.


Thanks,
Bob Frank


Begin forwarded message:

> From: Martin H=E4cker <don...@we...>
> Date: February 25, 2004 6:19:45 PM CST
> To: chi...@ma...
> Subject: Log4Cocoa feedback
>
> Hi there!
>
> I just discovered your framework and immediately "stumbled" upon the=20=

> readme and the fact that you have to wrap the calls to the=20
> logger-macro in extra parentheses if you have a comma in there.
>
> Well, just the night before I did some preprocessor hacking to get rid=20=

> of exactly this requirement for a different project. :)
>
> What do you think, could this be useful?
>
> cu Martin
> --=20
> dont.wanna.tell
> [ot]coder - hehe=

[Log4cocoa-development] mea culpa: official hiatus

[bob f. <chi...@ma...>]

Hi all,

For a variety of reasons I didn't get much work done on Log4Cocoa this 
summer (even testing Michael's vardiac macros).

I do plan to do substantial more work on Log4Cocoa, but am totally 
swamped with work and personal issues for at least the next month 
(selling house & moving).  If anyone would like to be added as a 
commiter and would do some work on Log4Cocoa, please contact me.


Thanks,
Bob

Re: [Log4cocoa-development] it work for me.

[bob f. <chi...@ma...>]

my 2 cents. configuration should easy, but flexible.  I always assumed 
we'd be using NSUserDefaults and/or accepting arguments from the 
command line.  My thoughts:

1) From the command line you should be able to specify a config file 
that will be used instead of NSUserDefaults, also, you should be able 
to specify either on the command line or in the config file that it 
should be saved as the new NSUserDefaults config.

2) if we don't store the config info in NSUserDefaults, at a minimum we 
should store the location of the config file, and I would suggest 
looking for the config file to be specified in:
	a) command line
	b) NSUserDefaults
	c) NSGlobalDomain (maybe there is a generic config for this 
server/machine);
	d) if these fail, then perhaps, also look in well defined locations, 
for example
		1) in the app wrapper
		2) ~/Library/Application Support/AppName/Log4Cocoa.xml
		3) /Library/Application Support/AppName/Log4Cocoa.xml
		4) use default mode (i.e. set root loger to either info or debug? & 
log somewhere reasonable: probably console or a maybe a file)?
	- these are just examples, maybe this is too many places to search and 
will confuse people, but I'd like to make it easy to deploy on a server 
and also have individual users debug with their own logging configs.

3) Extra Credit:  if we want to get tricky, we could have multiple 
configs saved in NSUserDefaults, and from the command line or 
NSUserDefaults.  For example: the entire config could be 
useLoggingProfile = default | production | development | staging, etc . 
. . . . Just some random musings.

4) maybe it would also make sense to save the filename, path, & 
timestamp of the file that we got the config from so we can easily 
reload if we want (maybe it'd be automatic or a config option ... 
"reload config").



-Bob

PS: this is really musing for the final design . . . . *definitely* not 
the first pass, the first approach would be to get something working 
:-).  BTW: w/r/t/ file formats, I vote we only accept XML or Apple 
.plist file formats, later if someone is feeling adventurous they could 
make a converter for the java properties format (I'm not inclined to do 
so).

On Thursday, July 10, 2003, at 01:58 AM, Chris Hanson wrote:

> On Wednesday, July 9, 2003, at 12:18  PM, Michael Tsai wrote:
>> Personally, I think it should match Cocoa as much as possible.
>
> As do I.
>
> I think NSUserDefaults is the way to go for Log4Cocoa; it gets us so 
> much for free, I think we'd be crazy not to use it.  It even lets us 
> do things like override settings just by running an application at the 
> command line.
>
> The question is, should there just be one Log4Cocoa key in an 
> application's defaults that all the potential Log4Cocoa settings would 
> live under?
>
>   -- Chris
>
> -- 
> Chris Hanson, bDistributed.com, Inc.  |  Email: cm...@bD...
> Custom Application Development        |  Phone: +1-847-372-3955
> http://bdistributed.com/              |  Fax:   +1-847-589-3738
> http://bdistributed.com/Articles/     |  Personal Email: cm...@ma... 

[Log4cocoa-development] Variadic Macros

[Michael T. <mj...@c-...>]

Hi,

I'm attaching a diff showing the changes that I made. (My SourceForge
account, michaeltsai, isn't a member of the project.)

L4Logger.h - The log4* macros are now variadic. If the message is a
    string, it is assumed to be a format and you can add additional
    arguments at the end. If the message is not a string, the extra
    arguments are ignored. I didn't touch the deprecated L4* macros.

L4Logger.m - The macros all funnel through the new log4Log function,
    which is defined here.

L4LevelTest.m - There's a simple method here just to exercise the
    macros. It doesn't actually use ObjcUnit to do any assertions.

Log4Cocoa.pbproj/project.pbxproj - Sets CC to /usr/bin/gcc-3.3. I'm not
    sure why, but without this it wouldn't compile on my machine.

L4SimpleLayout.m - This is unrelated to the variadic macros. I revised
    -format: to be faster and (I think) clearer.

-- 
Michael Tsai                                 <http://www.c-command.com>

Re: [Log4cocoa-development] it work for me.

[Michael T. <mj...@c-...>]

On 7/10/03 at 2:58 AM, Chris Hanson <cm...@bd...> wrote:

> I think NSUserDefaults is the way to go for Log4Cocoa; it gets us so
> much for free, I think we'd be crazy not to use it.

Yeah.

> The question is, should there just be one Log4Cocoa key in an
> application's defaults that all the potential Log4Cocoa settings
> would live under?

I'd like it to be easy to use the command-line overrides by setting the
executable arguments in Project Builder. A single key would mean less
typing because we wouldn't have to unique the subkeys. OTOH, multiple
keys might make it easier to switch options on and off (by clicking the
checkboxes). And with a single key, all the settings in the
registration domain get overridden if you specify the key on the
command-line. That'd be a pain.

What advantages did you have in mind for using a single key?

--Michael

Re: [Log4cocoa-development] it work for me.

[Chris H. <cm...@bd...>]

On Wednesday, July 9, 2003, at 12:18  PM, Michael Tsai wrote:
> Personally, I think it should match Cocoa as much as possible.

As do I.

I think NSUserDefaults is the way to go for Log4Cocoa; it gets us so 
much for free, I think we'd be crazy not to use it.  It even lets us do 
things like override settings just by running an application at the 
command line.

The question is, should there just be one Log4Cocoa key in an 
application's defaults that all the potential Log4Cocoa settings would 
live under?

   -- Chris

-- 
Chris Hanson, bDistributed.com, Inc.  |  Email: cm...@bD...
Custom Application Development        |  Phone: +1-847-372-3955
http://bdistributed.com/              |  Fax:   +1-847-589-3738
http://bdistributed.com/Articles/     |  Personal Email: cm...@ma...

Re: [Log4cocoa-development] it work for me.

[Michael T. <mj...@c-...>]

On 7/9/03 at 12:20 PM, bob frank <chi...@ma...> wrote:

> How important do you think it is to match the Log4J config file
> format exactly? Or the XML config file format exactly?

Personally, I think it should match Cocoa as much as possible. If
someone's really interested in using the Java file formats, they could
write a configurator, right?

--Michael

Re: [Log4cocoa-development] it work for me.

[bob f. <chi...@ma...>]

Hello.

>> 2/ How can we have a file output ?
>
> I think you can do this by setting the root logger to use an 
> L4WriterAppender, but I've not tried this yet.

In progress right now.  I think the L4WriterAppender in CVS might work, 
but I forget what version is in there.  Also, I've been cleaning up 
that so I could implement a sub-class "rolling style" appender too, and 
should have them checked in together in a week or so.

>> 3/ Is like with Log4Java it's possible to have a little config file 
>> near the application to change the debug level ?
>
> I don't think that's implemented yet.

Correct.  But, its high on the todo list.  Here's an open question:    
How important do you think it is to match the Log4J config file format 
exactly? Or the XML config file format exactly?

The reason I'm asking is that since we're "cocoa-ifying" it, we're 
getting close to a point where we can start to leverage Cocoa features 
to make it more useful to the Cocoa developer.  I don't have anything 
specific in mind with configuration options . . . yet.  But, I've been 
thinking that tweaking the file format slightly would be helpful.

Re: [Log4cocoa-development] it work for me.

[Michael T. <li...@mj...>]

On Sunday, July 6, 2003, at 12:15  PM, Jacques wrote:

> 1/
> My log look like :
> INFO - 10931DPGroupBrowserController.m:95) -[DPGroupBrowserController
> notificationReceived:] - in notification received
>
> What are the number 10931 and 95 (the first number change, the second
> doesn't).

The 10931 is the number of milliseconds since the program started. The 
95 is the line number of the log statement in 
DPGroupBrowserController.m.

> 2/ How can we have a file output ?

I think you can do this by setting the root logger to use an 
L4WriterAppender, but I've not tried this yet.

> 3/ Is like with Log4Java it's possible to have a little config file 
> near
> the application to change the debug level ?

I don't think that's implemented yet.

-- 
Michael Tsai                                 <http://www.c-command.com>

[Log4cocoa-development] it work for me.

[Jacques <ja...@fo...>]

Hi every body,

I am happy.

Now Log4Cocoa work for me. :-)

I have just some little questions :

1/
My log look like :
INFO - 10931DPGroupBrowserController.m:95) -[DPGroupBrowserController
notificationReceived:] - in notification received

What are the number 10931 and 95 (the first number change, the second
doesn't).

2/ How can we have a file output ?

3/ Is like with Log4Java it's possible to have a little config file near
the application to change the debug level ?

Thanks in advance,
Jacques
-- 
LANGUE : organe sexuel dont certains dégénérés se servent pour parler.
               P. Desproges

Re: [Log4cocoa-development] Compiler Version

[Michael T. <li...@mj...>]

On Thursday, June 26, 2003, at 12:00  AM, Michael Tsai wrote:

> Is there some kind of hidden setting in the project file to turn off 
> newer compiler features? I started adding the variadic macro stuff, 
> but it isn't letting me use the new feature where ,## lets you have 
> zero arguments for the format string.

I still don't know what was wrong, but it's at least working now 
(letting me use the newer compiler features). What I did was set CC in 
the expert settings to /usr/bin/gcc-3.3. This shouldn't make a 
difference, because /usr/bin/gcc is 3.1, which does support the 
features. And I've never needed to set manually set CC in my other 
projects. But for now I'm just glad that it works. :)

-- 
Michael Tsai                                 <http://www.c-command.com>

Re: [Log4cocoa-development] Compiler Version

[Michael T. <li...@mj...>]

On Wednesday, July 2, 2003, at 12:07  PM, bob frank wrote:

> Did you solve this?

No. I tried building the project on a machine that still had the old 
dev tools (GCC 3.1), but that didn't help. I don't know what's left to 
try aside from recreating the project from scratch.

-- 
Michael Tsai                                 <http://www.c-command.com>

Re: [Log4cocoa-development] Compiler Version

[bob f. <chi...@ma...>]

Hi,

Sorry I didn't get back to you sooner.  Did you solve this?  I'm 
totally swamped catching up from last week.  If you're still having 
problems, I'll have some time to help you out later next week.

Please keep me posted on any progress you make along these lines.

Thanks,
Bob



On Wednesday, June 25, 2003, at 11:00 PM, Michael Tsai wrote:

> Hi,
>
> Is there some kind of hidden setting in the project file to turn off 
> newer compiler features? I started adding the variadic macro stuff, 
> but it isn't letting me use the new feature where ,## lets you have 
> zero arguments for the format string. So this:
>
> 	log4Debug(@"Set Log Level to Debug for Log message test.");
>
> is telling me that I'm missing an argument, with log4Debug defined as:
>
> 	#define log4Debug(message, args...) // etc.
>
> It doesn't like other newer GCC features like the ?: operator, which I 
> used in this code from L4SimpleLayout that I was speeding up:
>
> - (NSString *) format: (L4LoggingEvent *) anEvent
> {
> 	return [NSString stringWithFormat:@"%@ - %ld %@:%@) %@ - %@",
> 				[[anEvent level] stringValue],
> 				[anEvent millisSinceStart],
> //				[anEvent fileName] ?: @"",
> 				[anEvent fileName] ? [anEvent fileName] : @"",
> //				[[anEvent lineNumber] stringValue] ?: @"",
> 				[anEvent lineNumber] ? [[anEvent lineNumber] stringValue]: @"",
> //				[anEvent methodName] ?: @"";
> 				[anEvent methodName] ? [anEvent methodName] : @"",
> 				[anEvent renderedMessage]];
> }
>
> When I added the same files to one of my other projects, they compiled 
> fine. As far as I can tell, the settings in Project Builder that would 
> matter are the same, but I must be missing something.
>
> --Michael
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting 
> Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly 
> Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Log4cocoa-development mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cocoa-development
>

---
Bob Frank
bo...@ap...
(312) 902 - 7393

[Log4cocoa-development] Compiler Version

[Michael T. <li...@mj...>]

Hi,

Is there some kind of hidden setting in the project file to turn off 
newer compiler features? I started adding the variadic macro stuff, but 
it isn't letting me use the new feature where ,## lets you have zero 
arguments for the format string. So this:

	log4Debug(@"Set Log Level to Debug for Log message test.");

is telling me that I'm missing an argument, with log4Debug defined as:

	#define log4Debug(message, args...) // etc.

It doesn't like other newer GCC features like the ?: operator, which I 
used in this code from L4SimpleLayout that I was speeding up:

- (NSString *) format: (L4LoggingEvent *) anEvent
{
	return [NSString stringWithFormat:@"%@ - %ld %@:%@) %@ - %@",
				[[anEvent level] stringValue],
				[anEvent millisSinceStart],
//				[anEvent fileName] ?: @"",
				[anEvent fileName] ? [anEvent fileName] : @"",
//				[[anEvent lineNumber] stringValue] ?: @"",
				[anEvent lineNumber] ? [[anEvent lineNumber] stringValue]: @"",
//				[anEvent methodName] ?: @"";
				[anEvent methodName] ? [anEvent methodName] : @"",
				[anEvent renderedMessage]];
}

When I added the same files to one of my other projects, they compiled 
fine. As far as I can tell, the settings in Project Builder that would 
matter are the same, but I must be missing something.

--Michael

Re: [Log4cocoa-development] new tarball

[bob f. <chi...@ma...>]

Good idea.

I just added "l4Logger" in the NSObject additions category.  I'll 
remove the "logger" methods before 1.0, but I left them in for the 
moment, in case they're being used anywhere.

So, for now there is a #warning there to remind me to remove them 
(sorry about all the spew this generates in compiles).

-Bob

On Monday, June 16, 2003, at 10:15 AM, Michael Tsai wrote:

> On Sunday, June 15, 2003, at 11:17  PM, bob frank wrote:
>
>> Also, I've settled on final names for the convenience macros 
>> "log4Warn(), etc....", the old names are still there so nothing 
>> should break, but I'd like to remove them before we get to 1.0.  This 
>> will avoid possible collisions.  Frankly, I think a collision with 
>> logWarn is unlikely, but after talking to a few people at work I 
>> decided that the paranoid approach is generally the best.
>
> Yeah, actually I think we should be paranoid about the method names in 
> the NSObject category, too. That wouldn't impact readability, since 
> people will be using the macros.
>
> -- 
> Michael Tsai                                 <http://www.c-command.com>
>
>

---
Bob Frank
bo...@ap...
(312) 902 - 7393