Adium 0.80 and plain-text logs

[cometbus]

Logs need to be searched, the Adium devs have better things to do than work on a log viewer, at least, no offense, but the log viewer is kinda needing some work. os to say text logging is not coming back and to use the log viewer to me, well, ewww.

I dont have Tiger yet, but this may be the best arguemtn to bring them back, how does Spotlight do with html files? If they are plain text, I know for sure they are going to be fine.

To be honest, I moved from other IM apps with this one issue in mind, and this is a bummer.

Why can there not be a log as plain text option? Even if you have to hack it in by editing some plist, im fine with that, this is just a big bummer.

[Catfish_Man]

Logs need to be searched, the Adium devs have better things to do than work on a log viewer, at least, no offense, but the log viewer is kinda needing some work. os to say text logging is not coming back and to use the log viewer to me, well, ewww.

I dont have Tiger yet, but this may be the best arguemtn to bring them back, how does Spotlight do with html files? If they are plain text, I know for sure they are going to be fine.

To be honest, I moved from other IM apps with this one issue in mind, and this is a bummer.

Why can there not be a log as plain text option? Even if you have to hack it in by editing some plist, im fine with that, this is just a big bummer.

Spotlight handles .html files just like .txt files. The real solution is an adium log format of some sort, which we can provide a plugin for. Improving the log format is being discussed. I would certainly expect improvements to both logging and the log viewer no matter what route ends up being chosen though.

[thewolf]

One of the reasons I moved to Adium was the text-only logging.

If that doesn't come back, I'll have to move to another AIM client that supports it.

I don't want to do that, since I love Adium, but text-only logging is a required feature for my needs.

If I had the skills, I'd code a plugin or something like that for it, unfortunately I don't know how to do that.

Thanks.

[Catfish_Man]

One of the reasons I moved to Adium was the text-only logging.

If that doesn't come back, I'll have to move to another AIM client that supports it.

I don't want to do that, since I love Adium, but text-only logging is a required feature for my needs.

If I had the skills, I'd code a plugin or something like that for it, unfortunately I don't know how to do that.

Thanks.

Well, a) good luck with your quest for an IM client that fits your needs. I hope you find one. and b) what about text logging is particularly nice for you? We're evaluation a lot of things people want, so it's useful to know why people want them.

[kap]

b) what about text logging is particularly nice for you? We're evaluation a lot of things people want, so it's useful to know why people want them.

I can view text logs at a glance, search through multiple logs at the same time in an environment that I'm comfortable in and understand the results, and can manipulate the results to almost unlimited ends.

Html logging essential locks me into using a program that can interpret the results and makes things that should be simple, like cutting and pasting segments for one, a huge pain.

[thewolf]

I can view text logs at a glance, search through multiple logs at the same time in an environment that I'm comfortable in and understand the results, and can manipulate the results to almost unlimited ends.

Html logging essential locks me into using a program that can interpret the results and makes things that should be simple, like cutting and pasting segments for one, a huge pain.

I need plain-text logs for almost the same reasons, also plain-text logs take up less disk space to store and memory to analyze.

Thanks.

[Adam Iser]

Html logging essential locks me into using a program that can interpret the results and makes things that should be simple, like cutting and pasting segments for one, a huge pain.

Copy-paste from the log viewer works very well.

[The_Tick]

I can view text logs at a glance, search through multiple logs at the same time in an environment that I'm comfortable in and understand the results, and can manipulate the results to almost unlimited ends.

Html logging essential locks me into using a program that can interpret the results and makes things that should be simple, like cutting and pasting segments for one, a huge pain.

I need plain-text logs for almost the same reasons, also plain-text logs take up less disk space to store and memory to analyze.

Thanks.

Couldn't you just use some fancy perl or regex to you know process the text and provide you with the output you desire?

[thewolf]

Couldn't you just use some fancy perl or regex to you know process the text and provide you with the output you desire?

If I had the skills to do that, I would do it for sure and make it public.

Anyway, I still didn't get the reason of removing the plain-text logging from Adium.
Was it a technical reason or what?

Please no flames, just trying to understand.

Thanks for the great product.

[The_Tick]

Couldn't you just use some fancy perl or regex to you know process the text and provide you with the output you desire?

If I had the skills to do that, I would do it for sure and make it public.

Anyway, I still didn't get the reason of removing the plain-text logging from Adium.
Was it a technical reason or what?

Please no flames, just trying to understand.

Thanks for the great product.

We're trying to improve the log viewer. In order to do this we need to drop things which do not help us at all. One of those is, you guessed it, the logging you guys are clamoring to have put back in. We've tried multiple times to pull this feature with a small but vehement group of people always asking to have it put back in.

At this point we've recognized that some things just need to go in order to move on and provide a better user experience in general. What if the log viewer could do what you guys are wanting now? You can do a quick search, and copy and paste worked correctly. Plus copy and paste in the message view could work correctly as well.

Or we can keep plain text logs.



So, as I posted earlier:

So I guess you want us to bring back something that was holding up improvements to the deficiencies of the log viewer in order to work around those deficiencies, from what you said here.

[kap]

We're trying to improve the log viewer. In order to do this we need to drop things which do not help us at all. One of those is, you guessed it, the logging you guys are clamoring to have put back in. We've tried multiple times to pull this feature with a small but vehement group of people always asking to have it put back in.

At this point we've recognized that some things just need to go in order to move on and provide a better user experience in general. What if the log viewer could do what you guys are wanting now? You can do a quick search, and copy and paste worked correctly. Plus copy and paste in the message view could work correctly as well.

Or we can keep plain text logs.

I simply don't understand why plaintext logging would hold up improving the log viewer when you could just disallow them to work with the log viewer. Keep the feature, it obviously works as-is, and then ignore it from now on while continuing to update the log viewer's deficiencies for the people who want to use it. I honestly don't understand any technical reason why this wouldn't be possible. Can you please explain it? (Again, not trying to troll or anything, I just want to understand.)

To me, using a log viewer just represents another window I have to open and play around with to get what I want, which is silly and wasteful and in the way when I already have a terminal window open that I know how to use quickly and easily. It's something already existing that fulfills the same purpose as the log viewer as well as a million other things.

Writing a script to remove the html is doable, but it seems like a waste when the application has done it flawlessly and natively in the past.

I understand you want to improve the log viewer, and there's probably a good deal of pride (good thing!) in getting it to the point where it's perfect. I personally don't have a problem with it's deficiencies, because I don't use it. I never have. Plaintext logging has allowed me to handle my data any way I please without having to resort to GUIs that just get in my way, and I really feel like that's a minor demand.

If there is focus on improving the log viewer, great, if plaintext logs are holding the goal back, just prevent them with working with it, or put a notice in the options saying they won't work with it. Whatever works. Taking away such a basic option just seems silly to me.

[The_Tick]

We're trying to improve the log viewer. In order to do this we need to drop things which do not help us at all. One of those is, you guessed it, the logging you guys are clamoring to have put back in. We've tried multiple times to pull this feature with a small but vehement group of people always asking to have it put back in.

At this point we've recognized that some things just need to go in order to move on and provide a better user experience in general. What if the log viewer could do what you guys are wanting now? You can do a quick search, and copy and paste worked correctly. Plus copy and paste in the message view could work correctly as well.

Or we can keep plain text logs.

I simply don't understand why plaintext logging would hold up improving the log viewer when you could just disallow them to work with the log viewer. Keep the feature, it obviously works as-is, and then ignore it from now on while continuing to update the log viewer's deficiencies for the people who want to use it. I honestly don't understand any technical reason why this wouldn't be possible. Can you please explain it? (Again, not trying to troll or anything, I just want to understand.)

If you didn't get it from what I said, I don't think you ever will. It's not coming back. We don't want crap options just because of a small group anymore. Get over it, move along.