Re: [opensource-dev] Viewer 2 beta crash osx

Well I think I just narrowed it down. I turned off streaming media and I am able to login now. I guess viewer 2 auto loads the media even if it isn't set to auto play? I should have thought of it earlier and I don't know why I didn't. I can't play streaming media in the v1.x viewers either but they

Re: [opensource-dev] Viewer 2 beta crash osx

I would attach that video, any logs you can collect, and possibly a screen of anything odd in your inventory to a jira. I might also attach some logs of a successful login in with 1.x I knwo the codebases are different, but theres always the slim hope that by comparing the two something might

[opensource-dev] Viewer 2 beta crash osx

Ok so I have been having the crashing problem on login every since viewer 2. I can still login fine with the viewer 1.x viewers but none of the viewer 2 viewers login fully they just crash. I have tried clearing cache and deleting everything blah blah even reinstalled osx and same thing. Here is a

Re: [opensource-dev] O.O Display name code DROP!

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 h

Re: [opensource-dev] Fwd: O.O Display name code DROP!

NO I completely forgot to post a JIRA entry on that! Just got it in though: https://jira.secondlife.com/browse/VWR-23451 Any useful counter-arguments/expansions can go there. :) Ricky Cron Stardust On Fri, Oct 15, 2010 at 5:46 PM, Marc Adored wrote: > Woops forgot to reply to all so it went to

Re: [opensource-dev] O.O Display name code DROP!

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

[opensource-dev] Fwd: O.O Display name code DROP!

Woops forgot to reply to all so it went to the list :P I think your post here: https://lists.secondlife.com/pipermail/opensource-dev/2010-September/003167.html Was a very good one explaining what the advantages could be. A true xml format like that would be easy to read and easy to parse. Of co

Re: [opensource-dev] O.O Display name code DROP!

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 longe

Re: [opensource-dev] LLSD logs (was: O.O Display name code DROP!)

On Fri, Oct 15, 2010 at 5:12 PM, Ricky wrote: > Ah yes, I'd forgotten that there was more than one form for LLSD... > I've only worked with the XML-style one thus far! Since, as you say, > the format is not in the XML style, then it is likely that they > hadn't. Or that they had, but chose this

Re: [opensource-dev] O.O Display name code DROP!

> > 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 retr

Re: [opensource-dev] LLSD logs (was: O.O Display name code DROP!)

Ah yes, I'd forgotten that there was more than one form for LLSD... I've only worked with the XML-style one thus far! Since, as you say, the format is not in the XML style, then it is likely that they hadn't. Or that they had, but chose this style for being more "human friendly" - like you said.

Re: [opensource-dev] O.O Display name code DROP!

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 specif

Re: [opensource-dev] Replying to OpenSource-Dev using Gmail.

The problem is the list sends the email to you from the sender not from the list so gmail replies to the person because reply replies to the sender. My other lists don't have this issue so I'm pretty sure its a setting set differently in mailman that linden might should change to make replying act

[opensource-dev] VWR-23437 / DN-179: Personal IM logs not being generated (was: O.O Display name code DROP!)

On 10/15/2010 06:57 AM, 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 > mo

Re: [opensource-dev] O.O Display name code DROP!

On Fri, 15 Oct 2010 16:23:27 -0700 Leyla Linden 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 to inspectors

Re: [opensource-dev] Replying to OpenSource-Dev using Gmail.

Thanks. Gee, it would be nice if it would work like it looks like it would work. On Fri, Oct 15, 2010 at 6:39 PM, Teravus Ovares wrote: > On that note, there's a gmail Lab feature which makes 'Reply to All' > default and makes it so you have to dig for 'Reply' when you want to reply > to some

Re: [opensource-dev] Replying to OpenSource-Dev using Gmail.

On that note, there's a gmail Lab feature which makes 'Reply to All' default and makes it so you have to dig for 'Reply' when you want to reply to someone individually off list. I use it for this e-mail address..but be careful. It might not be appropriate for every situation. -Teravus O

Re: [opensource-dev] Replying to OpenSource-Dev using Gmail.

Use reply to all it replies to the person ad cc's to the mailing list. Somehow the person in the TO field doesnt get a duplicate either like you think they would so it works perfect. On Fri, Oct 15, 2010 at 7:21 PM, SuezanneC Baskerville wrote: > I switched my listmanager settings from Digest to

Re: [opensource-dev] O.O Display name code DROP!

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 wrote: > Hi All, > The chat log format change wasinitially done so we could easily add > more information in the chat logs.  Now tha

Re: [opensource-dev] O.O Display name code DROP!

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 lo

Re: [opensource-dev] O.O Display name code DROP!

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 . (I guess "DN" stands for "display names".) Why we can't see that jira pro

[opensource-dev] Replying to OpenSource-Dev using Gmail.

I switched my listmanager settings from Digest to individual messages recently. I use Gmail. I just tried to reply to an OSD thread, and it appears that the mail would be going to one individual rather than to the mailing list. I didn't seem to have this problem with the list set to send digests

Re: [opensource-dev] O.O Display name code DROP!

On 15 October 2010 15:44, Dave Booth wrote: > On 10/15/2010 17:38, Marc Adored wrote: > > > > 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. Confrontational rudeness wi

Re: [opensource-dev] Project-MESH viewer

Nyx Linden wrote: > We just pulled from viewer-development yesterday actually, but we had > already released the initial beta viewer. > We try to stay reasonably up to date, but we don't merge the latest > changes every day. > > Don't worry we will stay synced! > >   -Nyx Its anyway awsome - ty an

Re: [opensource-dev] O.O Display name code DROP!

Which part is bullocks? The accurate description of how things will change or the accurate description of how things will change? Fact is it's not going to change much for anyone when its finished (assuming they are going to provide a stylesheet for it). You will still simply double click the file

Re: [opensource-dev] O.O Display name code DROP!

What happened to that jira issue? It appears to have been moved to SEC or something like that. On Thu, Oct 14, 2010 at 11:57 PM, 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.

[opensource-dev] LLSD logs (was: O.O Display name code DROP!)

On 10/15/2010 11:36 PM, Ricky wrote: > Besides, back on Sept 2nd this was already discussed, and plans > invented. > https://lists.secondlife.com/pipermail/opensource-dev/2010-September/003162.html That was more throwing ideas around than actual plans. We probably can't even be sure the display

Re: [opensource-dev] O.O Display name code DROP!

On 10/15/2010 17:38, Marc Adored wrote: Bollocks. ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges

Re: [opensource-dev] O.O Display name code DROP!

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 it will look just like a

Re: [opensource-dev] O.O Display name code DROP!

Actually its a bad move. For one: logs should NOT have fields. The display name used at the time should NOT change in the logs once someone changes their user name, which appears to be what this file format does. TWO, to require you users to download a style sheet and use a web browser to vie

Re: [opensource-dev] O.O Display name code DROP!

Speak for yourself. My drives are only 250gig and 500 gig. Even with having lost 3 years wroth of logs, in txt format, my log folders are ALREADY almost half a gig. That's in just 3 months. ... > From: kf6...@gmail.com > Date: Fri, 15 Oct 2010 14:36:06 -0700 > To: m...@inworlddesigns.com >

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 the posts. The log files just don't contain enough information, especially with Display Names. With an expanded format, such as any of LLSD/XML/JSON, you can associate all the

Re: [opensource-dev] Project-MESH viewer

But on the flipside, the Project MESH viewer has working shadows for nVidia GPU's on Mac (never happened before on any known config), and anti-aliasing's fixed. If we could get that bit out of the mesh viewer and into the 2.2 pipeline, we'd really be in great shape IMO. Trilo On Oct 15, 2010

Re: [opensource-dev] O.O Display name code DROP!

This is another change that a very small percentage of people wanted that was made without consideration to how it affects the larger community. The PROPER change should have been to add an OPTION to log to .llsd for those people making log files of Office Hours parsing log files for posting to th

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 stylesheet to make it just as easy to read as the text files were. Just using a web browser instead of a t

Re: [opensource-dev] O.O Display name code DROP!

All this panic did anyone stop to think that maybe this is part of a bigger plan? The first thing that cam to mind for me was maybe it makes it easier for programs to format them and probably better for searching and stuff (withen a program). Also maybe there are plans for a built in log viewer com

Re: [opensource-dev] O.O Display name code DROP!

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

Re: [opensource-dev] Project-MESH viewer

Yikes. It sounds like you think I was complaining. not at all. Just encouraging a little. ponzu On Fri, Oct 15, 2010 at 1:29 PM, Oz Linden (Scott Lawrence) < o...@lindenlab.com> wrote: > On 2010-10-15 13:07, Ponzu wrote: > > I tried this viewer last night. As I am sure you Lindens know, it

Re: [opensource-dev] Project-MESH viewer

We just pulled from viewer-development yesterday actually, but we had already released the initial beta viewer. We try to stay reasonably up to date, but we don't merge the latest changes every day. Don't worry we will stay synced! -Nyx On 10/15/2010 01:29 PM, Oz Linden (Scott Lawrence) wrot

Re: [opensource-dev] Project-MESH viewer

On 2010-10-15 13:07, Ponzu wrote: > I tried this viewer last night. As I am sure you Lindens know, it is > based on a version of viewer-development that is many days old. (Some > complaint, huh?) > Could perhaps someone help the Mesh team pull the most relevant > changesets from viewer-dev s

[opensource-dev] Project-MESH viewer

I tried this viewer last night. As I am sure you Lindens know, it is based on a version of viewer-development that is many days old. (Some complaint, huh?) Could perhaps someone help the Mesh team pull the most relevant changesets from viewer-dev so their next release lacks the more annoying pro

[opensource-dev] You are not alone 8-) (was Re: Corrupted OpenGL & Hard Crash

Something similar happened to me last night, and I doubt it was overheating. Mesh Viewer. Bizarro graphics and then a total OS X lock up. Had to finally cycle power. next try, similar, but before the lockup I got into preferences and changed graphics from High to Med. After that, things worked

Re: [opensource-dev] Corrupted OpenGL & Hard Crash

I apologize! I forgot that a great many people don't have the luxury of high speed internet. Which is why I'm responding to the list: hopefully others who might makes the same mistake either here or elsewhere can learn from my mistake... Ricky Cron Stardust PS: As an (lame) excuse: I daily have

[opensource-dev] Canceled Today - Snowstorm Sprint Review Meeting

Good morning all, Sprint 5 has been focused on overall stabilization of the current Viewer 2.2 Beta. As such, we have no new user stories that require product review and discussion, so I'm canceling today's Sprint Review meeting. We'll still get together on Monday for the Sprint Retrospective and

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 6:57 AM, Daniel 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. The 115 bytes for llsd wo

Re: [opensource-dev] O.O Display name code DROP!

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 informati

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 5:29 AM, Carlo Wood wrote: > On Fri, Oct 15, 2010 at 04:47:21AM -0700, leliel wrote: >> On Fri, Oct 15, 2010 at 4:38 AM, Carlo Wood wrote: >> > I was hoping that log files are updated very >> > frequently, so that if I crash I don't lose >> > text. But writing several mega

Re: [opensource-dev] O.O Display name code DROP!

On 10/15/2010 06:53, Stickman wrote: > If it's not, the Lindens should be waking up soon and see a huge > thread of people screaming that the sky is falling and put some > authority down on the situation. Looking forward to it, those clouds > are looking awfully close. The sky may not be falling

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 04:53:05AM -0700, Stickman wrote: > If it's not, the Lindens should be waking up soon and see a huge > thread of people screaming that the sky is falling and put some > authority down on the situation. HAHAHA (not) As if they care. You still don't know them do you? -- Ca

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 04:47:21AM -0700, leliel wrote: > On Fri, Oct 15, 2010 at 4:38 AM, Carlo Wood 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. >

Re: [opensource-dev] O.O Display name code DROP!

As I am testing the viewer the .llsd files to append with no issues on that part. From: opensource-dev-boun...@lists.secondlife.com [mailto:opensource-dev-boun...@lists.secondlife.com] On Behalf Of Stickman Sent: Friday, October 15, 2010 7:53 AM To: leliel Cc: opensource-dev@lists.secondlife.co

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 11:23, leliel wrote: > On Fri, Oct 15, 2010 at 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

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 4:53 AM, Stickman 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 file the Disp

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 of oversight that can be repaired. The current format is missing i

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 4:38 AM, Carlo Wood 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 where are the

Re: [opensource-dev] O.O Display name code DROP!

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 several

Re: [opensource-dev] O.O Display name code DROP!

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 _

Re: [opensource-dev] O.O Display name code DROP!

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 formatt

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 7:15 AM, Jamey Fletcher 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 names, the na

Re: [opensource-dev] O.O Display name code DROP!

On Fri, Oct 15, 2010 at 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

Re: [opensource-dev] O.O Display name code DROP!

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

Re: [opensource-dev] O.O Display name code DROP!

On 15 oct. 2010, at 10:45, Stickman wrote: >> "[{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? > +1 ! No need

Re: [opensource-dev] O.O Display name code DROP!

> "[{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 (un)

Re: [opensource-dev] O.O Display name code DROP!

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 looked at the sheer amount of overhead LLSD produces? We'll have

Re: [opensource-dev] O.O Display name code DROP!

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 shotgun..

Re: [opensource-dev] O.O Display name code DROP!

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 (un)s