Maybe a good step would be to make the logs easy to get to from the viewer
itself. A read chat log button, or a menu item. Then open out in the
default browser on they easy to read format. That might stop term thousand
users from freaking out when they open the file using Notepad
Am Sonntag 17 Oktober 2010 schrieb Ricky:
I agree, the XML notation is far from perfect (see some of my posts
last year about the subject,) however I consider it better than
either text or this almost-JSON notation for a variety of reasons,
all laid out in
Lance check the jira if the file ext is changes to xml it will
automatically open in IE,Firefox,Chrome,Whatever Browser they have as
default and it will display styled to look just like the plain text
old versions only underneath it will contain much more information.
Those stylesheets can also be
On 2010-10-16, at 22:57, Ricky wrote:
Assuming that the order of fields is fixed, a fair assumption as LLSD
requires it I believe, then the XSLT isn't so bad, and a prototype has
already been made.
That depends on the details of the XSL transform tool. Streaming tools preserve
order but
Typically Joe Everyguy, from my experience as an IT professional, will
just double-click (or single click depending on settings) the file
from Windows Explorer/Mac Finder. (Us *NIX folks have our own way of
looking at things...) if the file has the .xml extension it will work
correctly. If we
On 2010-10-15 19:22, Boroondas Gupte wrote:
On 10/16/2010 12:59 AM, SuezanneC Baskerville wrote:
What happened to that jira issue? It appears to have been moved to
SEC or something like that.
It has been moved to DN-179
https://jira.secondlife.com/browse/DN-179. (I guess DN stands for
On 2010-10-15, at 16:36, Ricky wrote:
All that's needed is a linked XSL stylesheet to make it just as easy
to read as the text files were.
1. It's not in XML, it's in notation format. This is a good thing, because...
2. LLSD is really badly designed from the point of XSL transformations.
WolfPup Lowenhar wrote:
Actualy the file extension change is only to chat and IM logs. And I
have already found a bug in the code!
https://jira.secondlife.com/browse/VWR-23437
the above jira is the bug and it is not being cause be my file name
modification as the mod is working fine for
Am Freitag 15 Oktober 2010 schrieb Jamey Fletcher:
WolfPup Lowenhar wrote:
Actualy the file extension change is only to chat and IM logs.
And I have already found a bug in the code!
https://jira.secondlife.com/browse/VWR-23437
the above jira is the bug and it is not being cause be
Wait, what?
The new chat/IM logs are saved in LLSD of all things?
Why? To make chat/IM history work with the display names or...what?
And there is no option to also store a .txt copy?
On Fri, Oct 15, 2010 at 08:15, Jamey Fletcher ja...@beau.org wrote:
WolfPup Lowenhar wrote:
Actualy the file
The new chat/IM logs are saved in LLSD of all things?
NOT MY CHAT LOGS! That's where I keep all my text!
I am also very interested in the purpose of this change, and if there
will be provided (by LL or a loving developer) a handy and lightweight
notepad replacement to read and search these log
On 10/15/2010 01:46, Stickman wrote:
The new chat/IM logs are saved in LLSD of all things?
NOT MY CHAT LOGS! That's where I keep all my text!
Me too - thats a change needs a backout immediately.
Whiskey Tango Foxtrot?
___
Policies and
My wife works inworld for a big estate, in sales and tenant support and staff
training, and basically EVERY CASE DOCUMENTATION is based on plaintext chat-
and IM logs. When I told her about this change earlier I almost had to tie her
down to keep her to go over to linden village with a
...@lists.secondlife.com] *On Behalf Of
*Jamey Fletcher
*Sent:* Friday, October 15, 2010 12:31 AM
*To:* opensource-dev@lists.secondlife.com
*Subject:* Re: [opensource-dev] O.O Display name code DROP!
WolfPup Lowenhar wrote:
Well folks my night is going to be interesting as now I have to hard
merge
[{TIME}] {DISPLAY NAME} ({REAL.NAME}) says: {STUFF} would have been MORE
than sufficient for logging purposes.
[01:49] TehSticks (Stickman Ingmann) says: I second this format.
Anyone see any drawbacks? Dates, maybe?
-Stickman
___
Policies and
Am Freitag, 15. Oktober 2010, 10:00:44 schrieb Rob Nelson:
So basically, LL decided to go from simply changing the formatting of
their logs to (if what I am hearing is correct), of all things, LLSD XML
notation, possibly the worst formatting of log possible?
Has ANYONE over there at LL
On Fri, Oct 15, 2010 at 2:04 AM, Lance Corrimal
lance.corri...@eregion.de wrote:
Am Freitag, 15. Oktober 2010, 10:00:44 schrieb Rob Nelson:
So basically, LL decided to go from simply changing the formatting of
their logs to (if what I am hearing is correct), of all things, LLSD XML
notation,
On Fri, Oct 15, 2010 at 7:15 AM, Jamey Fletcher ja...@beau.org wrote:
Is there actually a *reason* for this change, or is it just to screw
around in the code to do provide an opportunity for new bugs, such as
the one you found already?
I suspect the reason for the change is that with display
On 10/15/2010 2:04 AM, Lance Corrimal wrote:
Am Freitag, 15. Oktober 2010, 10:00:44 schrieb Rob Nelson:
So basically, LL decided to go from simply changing the formatting of
their logs to (if what I am hearing is correct), of all things, LLSD XML
notation, possibly the worst formatting of
OMG!?!?! THIS WILL [destroy SL economy|eat all
your cheese|kill your kittens] !!!11!!!1!
I can't believe nobody is considering the idea that
the current setting may just be an overlooking and that
the default behaviour could be restored before this
goes into production.
Opensource Obscure
I didn't know LLSD was capabable of appending,
does this new format mean that my 50 MB chat.txt
file is going to be re-written from scratch,
every time I sync it with the latest chat?
I was hoping that log files are updated very
frequently, so that if I crash I don't lose
text. But writing
On Fri, Oct 15, 2010 at 4:38 AM, Carlo Wood ca...@alinoe.com wrote:
I was hoping that log files are updated very
frequently, so that if I crash I don't lose
text. But writing several megabytes to disk
every line of chat seems unfeasible.
It's 115 bytes + display name + message per line. Just
It's 115 bytes + display name + message per line. Just where are these
several megabytes coming from?
Lack of append in LLSD. Sounds a bit extreme to me.
I prefer Opensource's line of thinking, where this is simply some sort
of oversight that can be repaired. The current format is missing
On Fri, Oct 15, 2010 at 4:53 AM, Stickman stick...@gmail.com wrote:
It's 115 bytes + display name + message per line. Just where are these
several megabytes coming from?
Lack of append in LLSD. Sounds a bit extreme to me.
The latest Snowstorm build had no trouble appending to the chat.llsd
On Fri, Oct 15, 2010 at 11:23, leliel leliel.mir...@gmail.com wrote:
On Fri, Oct 15, 2010 at 2:04 AM, Lance Corrimal
lance.corri...@eregion.de wrote:
Am Freitag, 15. Oktober 2010, 10:00:44 schrieb Rob Nelson:
So basically, LL decided to go from simply changing the formatting of
their logs
@lists.secondlife.com
Subject: Re: [opensource-dev] O.O Display name code DROP!
It's 115 bytes + display name + message per line. Just where are these
several megabytes coming from?
Lack of append in LLSD. Sounds a bit extreme to me.
I prefer Opensource's line of thinking, where this is simply some sort
On Fri, Oct 15, 2010 at 04:47:21AM -0700, leliel wrote:
On Fri, Oct 15, 2010 at 4:38 AM, Carlo Wood ca...@alinoe.com wrote:
I was hoping that log files are updated very
frequently, so that if I crash I don't lose
text. But writing several megabytes to disk
every line of chat seems
Apparently you don't chat much, mine is ten times larger over the same
period.
On 10/15/2010 7:24 AM, opensource-dev-requ...@lists.secondlife.com wrote:
My log folder is a whopping 35MB after almost 4 years.
___
Policies and (un)subscribe
On Fri, Oct 15, 2010 at 6:57 AM, Daniel danielravenn...@gmail.com wrote:
Apparently you don't chat much, mine is ten times larger over the same
period.
I only logged IMs for two years.
So my chat.txt file is 15409876 bytes and 265570 lines which gives me
an average message size of 58 bytes.
It was a JIRA from Samia Bechir https://jira.secondlife.com/browse/VWR-22940
dated from September 10
You can vote for it
GCI
- Original Message -
From: WolfPup Lowenhar
To: OpenSource Mailing List
Sent: Friday, October 15, 2010 2:58 AM
Subject: [opensource-dev] O.O Display
To: OpenSource Mailing List
Sent: Friday, October 15, 2010 2:58 AM
Subject: [opensource-dev] O.O Display name code DROP!
Well folks my night is going to be interesting as now I have to hard merge
my logging code to the new code as there are changes to the way logs are
EVEN saved .llsd instead
-22940 dated from September 10
You can vote for it
GCI
- Original Message -
From: WolfPup Lowenhar
To: OpenSource Mailing List
Sent: Friday, October 15, 2010 2:58 AM
Subject: [opensource-dev] O.O Display name code DROP!
Well folks my night is going to be interesting as now I have
September 10
You can vote for it
GCI
- Original Message -
From: WolfPup Lowenhar
To: OpenSource Mailing List
Sent: Friday, October 15, 2010 2:58 AM
Subject: [opensource-dev] O.O Display name code DROP!
Well folks my night is going to be interesting as now I have to hard merge
my
: opensource-dev@lists.secondlife.com
Subject: Re: [opensource-dev] O.O Display name code DROP!
Besides, back on Sept 2nd this was already discussed, and plans
invented.
https://lists.secondlife.com/pipermail/opensource-dev/2010-September/003162.html
All that's needed is a linked XSL
...@gmail.com
Date: Fri, 15 Oct 2010 15:23:49 -0700
To: labrat...@gmail.com
CC: opensource-dev@lists.secondlife.com
Subject: Re: [opensource-dev] O.O Display name code DROP!
Actually, IMHO that was the catalyst, not the reason. The reason was
that there needs to be a pile of information about
On 15 October 2010 15:44, Dave Booth d...@meadowlakearts.com wrote:
On 10/15/2010 17:38, Marc Adored wrote:
snip
Bollocks.
Thanks for providing a succinct example of what really isn't OK around here.
Disagreement: Fine.
Passionate argument: Fine, as long as it's civil and reasoned.
Hi All,
The chat log format change wasinitially done so we could easily add
more information in the chat logs. Now that the display name can
change it's nice to have more data like an agent_id that can be hooked
up to inspectors.
But seeing as how many people rely on easily readable text chat
Oh well so much for progress :( Is linden labs going to provide a tool
to convert current llsd logs back to plaintext?
On Fri, Oct 15, 2010 at 7:23 PM, Leyla Linden le...@lindenlab.com wrote:
Hi All,
The chat log format change wasinitially done so we could easily add
more information in the
On Fri, 15 Oct 2010 16:23:27 -0700
Leyla Linden le...@lindenlab.com wrote:
Hi All,
The chat log format change wasinitially done so we could easily add
more information in the chat logs. Now that the display name can
change it's nice to have more data like an agent_id that can be hooked
up
Marc Adored wrote:
Download a stylesheet? The file would contain a link directly to the
stylesheet and would be automatically loaded. Also I'm not sure about
your operating system but I'm pretty sure the file extension already
opens in your default browser and once the stylesheet is specified
snip
Let's see... Future Proof.
Program to read and process a text file - anywhere from a few hundred
bytes, to a small OS-wannabe like emacs. Program to process LLSD and
display it - several hundred K minimum, oh, and *REQUIRED* network
connection live so the referenced DTD can be
I'd have to say that future proof and archival safe are two separate
qualities. Logs might need to be archived, but 90% (guessing) of the
content is fluff only useful for a couple of months to a year at the
most. However, the tools that read them (such as converters /
archivers) have a much
Hi Leyla,
Glad to keep the current text format if there are no real goals for changing
it.
For one that would have broken the integrity of current log files.
On that point I would actually love to know if the filenames of IM logs is
to
eventually change, from say First Last.txt to first.last.txt
I CONTRIBUTED SOMETHING ;_;
Rob
On 10/15/2010 4:23 PM, Leyla Linden wrote:
The only difference is that
they'll include both display names and usernames, much like Rob
Nelson suggested.
- Leyla
___
Policies and (un)subscribe information available
Well folks my night is going to be interesting as now I have to hard merge
my logging code to the new code as there are changes to the way logs are
EVEN saved .llsd instead of .txt which is going to make things interesting
for me as now I have to change my history look up code for the new file
WolfPup Lowenhar wrote:
Well folks my night is going to be interesting as now I have to hard
merge my logging code to the new code as there are changes to the way
logs are EVEN saved .llsd instead of .txt which is going to make things
interesting for me as now I have to change my history look
: opensource-dev-boun...@lists.secondlife.com
[mailto:opensource-dev-boun...@lists.secondlife.com] On Behalf Of Jamey
Fletcher
Sent: Friday, October 15, 2010 12:31 AM
To: opensource-dev@lists.secondlife.com
Subject: Re: [opensource-dev] O.O Display name code DROP!
WolfPup Lowenhar wrote:
Well folks
47 matches
Mail list logo
