[opensource-dev] Directory named $(CONFIGURATION) (was: No rule to make target)
On 11/09/2010 08:12 AM, Ricky wrote: Trying to compile viewer_development a60d3b118c76 (tip as of the time of this message) I get the following error: make[2]: *** No rule to make target `sharedlibs//PROJECT_llmath_TEST_llbboxlocal', needed by `llmath/PROJECT_llmath_TEST_llbboxlocal_ok.txt'. Stop. The folder linden/indra/sharedlibs/ contains the following: $(CONFIGURATION) Debug RelWithDebInfo Release Resources Looks like a misconfig in the build system; I don't think that there should be a folder named $(CONFIGURATION) in that directory. Maybe someone typed single quotes when they intended to use double quotes? Maybe caused by changesets 2626 http://bitbucket.org/lindenlab/viewer-development/changeset/7428efe715e1#chg-indra/cmake/Linking.cmake_newline25/2627 http://bitbucket.org/lindenlab/viewer-development/changeset/c72a96980f2e#chg-indra/cmake/Linking.cmake_newline25? Though those are one year old, now. So if it's them, Mac builders should be having this problem ever since 2.0 ... Cheers, Boroondas ___ 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] Request for feedback - Preferences Cleanup
I think of it as frsutrate. I especially like it when they don't know I have block/mute/ignore them. On Mon, Nov 8, 2010 at 6:18 PM, Yoz Grahame y...@lindenlab.com wrote: ... or Esbee's original suggestion, Block, which is easily the most common term for this across social software UIs. I just checked as many IM apps as I could find: Skype, AIM, iChat, ICQ, MSN, Adium and Twitter all use Block, Y!M seems to alternate between Block and Ignore. On 8 November 2010 12:02, Andromeda Quonset andromedaquon...@gmail.comwrote: I hadn't thought of mute that way. Perhaps ignore would be better. Or NULL. At 11:22 AM 11/8/2010, you wrote: That mute button sometimes does the opposite of what mute means in SL. On the telephones in my house and on my Android, mute turns off the *microphone*, not the incoming sound. (Ditto for some other apps I've seen, such as GoToMeeting. Hold is the closest analogue, which turns off both directions.) I'm guessing this is probably the source of some of the confusion. Celi On Fri, Nov 5, 2010 at 5:43 PM, Andromeda Quonset andromedaquon...@gmail.com wrote: FWIW, I would also like to see the return to Mute instead of Block. With all due respect to your user testing, the telephone on my desk has a Mute button, not a Block button, and I consider it a very heavily used communications tool. Perhaps there should be an option in preferences for setting the label for this function to either Mute or Block, as that would keep all of your users happy. Thank you At 09:10 AM 11/5/2010, Sarah (Esbee) Kuehnle wrote: Thanks for the feedback everyone. I'm working on some updates to the pdf right now and will send that out for further review later today! I can't promise all the suggested additions will go into the prefs, but I'll definitely look at each one as I'm making updates. A few responses to those who's provided feedback so far: @Marine - 1) The text chat logs have been fixed in 2.3 beta. 2) We changed the label from Mute to Block early on in V2 because our user testing indicated new users were confused about what Mute means and understood Block because it's used commonly in other communication tools. @GeneJ - That for the reminder on that typo. It was pointed out in my OH the other week and I needed a good kick to remember to fix it! :) @Wolfpup - We're just talking about skinning for now. In the meantime, I'm just gathering color options in one place. But you're right - future skinning preferences will likely require a restart before changes would take effect. @Erin - I've taken note of your request for the numerical debug settings for sculpties. I'm not sure they make sense in this preference cleanup I'm doing now, but will be useful when I can focus my team on a sprint focused on content creation as some point in the near future. As far as local lights go, they've actually been added back in on the Mesh Project Viewer ( SH-157 https://jira.secondlife.com/browse/SH-157) (which will eventually be added into the main Second Life Viewer). I'll take a look at the other tickets you referenced today. @Hitomi - Thanks for the additional settings. I'll review these this morning and see what makes sense to incorporate. That's a great list! More updates from me soon! --Esbee On Thu, Nov 4, 2010 at 6:50 PM, WolfPup Lowenhar wolfpu...@earthlink.net wrote: I keep seeing people talking about user readable chat logs and from what I’m seeing in the current dev builds the logs are already back to plain text. I’m currently working on a feature that is dealing with chat and group/personal IM logs. From: opensource-dev-boun...@lists.secondlife.com [ opensource-dev-boun...@lists.secondlife.com mailto:opensource-dev-boun...@lists.secondlife.comopensource-dev-boun...@lists.secondlife.com] On Behalf Of Hitomi Tiponi Sent: Thursday, November 04, 2010 4:37 PM To: Opensource_dev Subject: Re: [opensource-dev] Request for feedback - Preferences Cleanup Thanks for the Preferences mock-up (must say that I rather like the anime look of them :)) - some really sensible stuff there. Suggestions (all currently in Debug Settings): Chat - adjustable life and fade times for Startup, IM and Group popups - I find they are too short for me to spot sometimes Chat - Add in spinners to alter the number of times that IM tabs flash and the rate at which they flash at Advanced - Move 'UI Size' slider to Graphics as KL and myself have done - it fits more naturally there Graphics-Hardware - allow forcing on of Antialiasing (as the Viewer GPU presets often gets this wrong) or better still fix the presets :) Move View - put in spinners for amount of head movement Move View - Checkbox to allow double-click point-move in-world as an alternative to double-click teleport (which is welcome) Move View - Checkbox for 'Number keys move avatar' Privacy - Check-box to select option to also create user-readable chat logs (as others
Re: [opensource-dev] Log file names (was: Request for feedback - Preferences Cleanup)
I think the filename needs to be based on the unique account name, with any periods (.) replaced by underscore (_). The display names can change weekly, and as you note it would be much more difficult to track based on display name. Q On Nov 8, 2010, at 11:45 AM, Oz Linden (Scott Lawrence) wrote: On 2010-11-08 11:10, Sarah (Esbee) Kuehnle wrote: Thanks again for all your feedback. I've made some updates to the design deck (see attached). I'm going to create subtasks underneath STORM-31 for the new preferences and get these updates rolling with the team! :) Cheers, Esbee PS - Please feel free to keep feedback coming On the Privacy tab, you ask Is this a timestamp in the log or in the filename?... I think that once we've integrated STORM-102 (a final test build for that is running now), we'll actually have two checkboxes there. A new test build for that is available now (fresh off the server) at [1]. Add timestamp Add datestamp to log file name The first one controls whether or not lines in the log file have timestamps on them, and the second appends a datestamp: For person-to-person chat, the datestamp is -MM (year and month) For local chat, the datestamp is -MM-DD (year month and day) One issue on STORM-102 that probably needs discussing... the present person-to-person chat log file name is First Last[-datestamp].txt where First and Last are the real account names. If a person has a Display Name set, that name is not used when constructing the file name: instead the real first and last names for the account are used for the log file name. The Display name does appear (followed by the userid first.last in parens) in the log text content. This seems potentially confusing to me, especially if the only name I ever use for someone is the Display Name. It seems to me that either: the Display Name should be used (if I remember talking to Joe Somebody, that's the log file name I'd be most likely to look for), which would mean that each DN value would produce a separate log even if I had conversations with the same user with different DNs, or the userid (first.last) should always be used for the log file name. [1] http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/oz_viewer-storm-102/rev/214097/index.html ___ 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
[opensource-dev] Log file names: considering a corner case (was: Log file names)
On 11/09/2010 04:39 PM, Kent Quirk (Q Linden) wrote: The display names can change weekly, and as you note it would be much more difficult to track based on display name. Even worse when it'd happen (though probably much less likely to occur), two people might have the same display name at the same time, and you might happen to chat with both in personal IMs during that time. So two concurrent but separate discussions would end up intermixed in the same log file if filenames were display name based. For the (probably rare) cases when you want to re-read all messages that reached you during a given time interval, rather than single discussion 'threads', merging logs of several discussions a posteriory (using the logged timestamps) isn't more difficult than splitting a mixed log (using logged account names). Cheers, Boroondas ___ 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] Log file names (was: Request for feedback - Preferences Cleanup)
Maybe is the right time to implement in LSL sort of llKey2Name, save logs and other using the UUID and cache the display name (at least 1 change per week us allowed, caching username and display name should solve ??? Problem, falling back on cached if trouble) -- Sent by iPhone Il giorno 09/nov/2010, alle ore 16:39, Kent Quirk (Q Linden) q...@lindenlab.com ha scritto: I think the filename needs to be based on the unique account name, with any periods (.) replaced by underscore (_). The display names can change weekly, and as you note it would be much more difficult to track based on display name. Q On Nov 8, 2010, at 11:45 AM, Oz Linden (Scott Lawrence) wrote: On 2010-11-08 11:10, Sarah (Esbee) Kuehnle wrote: Thanks again for all your feedback. I've made some updates to the design deck (see attached). I'm going to create subtasks underneath STORM-31https://jira.secondlife.com/browse/STORM-31for the new preferences and get these updates rolling with the team! :) Cheers, Esbee PS - Please feel free to keep feedback coming On the Privacy tab, you ask Is this a timestamp in the log or in the filename?... I think that once we've integrated STORM-102 (a final test build for that is running now), we'll actually have two checkboxes there. A new test build for that is available now (fresh off the server) at [1]. - Add timestamp - Add datestamp to log file name The first one controls whether or not lines in the log file have timestamps on them, and the second appends a datestamp: For person-to-person chat, the datestamp is -MM (year and month) For local chat, the datestamp is -MM-DD (year month and day) One issue on STORM-102 that probably needs discussing... the present person-to-person chat log file name is First Last[-datestamp].txt where First and Last are the real account names. If a person has a Display Name set, that name is not used when constructing the file name: instead the real first and last names for the account are used for the log file name. The Display name does appear (followed by the userid first.last in parens) in the log text content. This seems potentially confusing to me, especially if the only name I ever use for someone is the Display Name. It seems to me that either: 1. the Display Name should be used (if I remember talking to Joe Somebody, that's the log file name I'd be most likely to look for), which would mean that each DN value would produce a separate log even if I had conversations with the same user with different DNs, 2. or the userid (first.last) should always be used for the log file name. [1] http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/oz_viewer-storm-102/rev/214097/index.html ___ 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 ___ 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
[opensource-dev] support related userstory...
As a user, I would expect if i log itno the secondlife website and then try to get some live support, it would then automatically connect me under the account I am logged into the website under and not any of say the last 4 or five accounts that logged in from this computer... Is that really too much to ask for? ___ 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] support related userstory...
On 2010-11-09 12:04, Erin Mallory wrote: As a user, I would expect if i log itno the secondlife website and then try to get some live support, it would then automatically connect me under the account I am logged into the website under and not any of say the last 4 or five accounts that logged in from this computer... Is that really too much to ask for? But, alas, the web site and the support infrastructure are not a part of the open source offering, so while there may be considerable merit to your idea, it is out of scope here... ___ 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] Directory named $(CONFIGURATION) (was: No rule to make target)
On Tue, Nov 9, 2010 at 1:04 AM, Boroondas Gupte slli...@boroon.dasgupta.chwrote: On 11/09/2010 08:12 AM, Ricky wrote: Trying to compile viewer_development a60d3b118c76 (tip as of the time of this message) I get the following error: make[2]: *** No rule to make target `sharedlibs//PROJECT_llmath_TEST_llbboxlocal', needed by `llmath/PROJECT_llmath_TEST_llbboxlocal_ok.txt'. Stop. The folder linden/indra/sharedlibs/ contains the following: $(CONFIGURATION) Debug RelWithDebInfo Release Resources Looks like a misconfig in the build system; I don't think that there should be a folder named $(CONFIGURATION) in that directory. Maybe someone typed single quotes when they intended to use double quotes? Maybe caused by changesets 2626http://bitbucket.org/lindenlab/viewer-development/changeset/7428efe715e1#chg-indra/cmake/Linking.cmake_newline25 /2627http://bitbucket.org/lindenlab/viewer-development/changeset/c72a96980f2e#chg-indra/cmake/Linking.cmake_newline25? Though those are one year old, now. So if it's them, Mac builders should be having this problem ever since 2.0 ... Cheers, Boroondas Speaking as the author of the offending changesets (sorry!). I'd strongly recommend buiding using the xcode generator instead of makefiles on Mac. This is not the only place we make this assumption in our cmake scripts. Anyways, for now our builds pretty much assume Mac == Xcode. In theory, that'd be good to fix, but I don't really have time to look into it now. If there are enough people interested in this we should get a story written for adding support for the makefile generator on mac, and then I can fill in the details there for how it should be done. -Brad ___ 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] Directory named $(CONFIGURATION) (was: No rule to make target)
Just a note -- since the XCode tools are free, high quality, and supported, Linden Lab is unlikely to put any significant prioritization into making other toolsets work on the mac. If someone else wants to add such support without breaking what we have, then we won't gratuitously break it, but we're probably never going to test it. Q On Nov 9, 2010, at 2:16 PM, Brad Kittenbrink (Brad Linden) wrote: Speaking as the author of the offending changesets (sorry!). I'd strongly recommend buiding using the xcode generator instead of makefiles on Mac. This is not the only place we make this assumption in our cmake scripts. Anyways, for now our builds pretty much assume Mac == Xcode. In theory, that'd be good to fix, but I don't really have time to look into it now. If there are enough people interested in this we should get a story written for adding support for the makefile generator on mac, and then I can fill in the details there for how it should be done. ___ 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
[opensource-dev] Xcode can't parse project file
To add to my journey here, now that I know I need to use Xcode when compiling on a Mac, I did the following: cmake -G Xcode . xcodebuild And I get the following errors: 2010-11-09 20:21:30.629 xcodebuild[35776:80b] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary. 2010-11-09 20:21:30.749 xcodebuild[35776:80b] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary. 2010-11-09 20:21:30.767 xcodebuild[35776:80b] Unexpected character / at line 1 xcodebuild: Error: couldn't load project /Users/ricky/Development/SecondLife/viewer-development/indra/SecondLife.xcodeproj Thinking that this was simply because my Linux-based mind was too stuck in the terminal, I tried to open the project file by double-clicking it in Finder. Xcode opened and I got the message Unable to Open Project: Project ..indra/SecondLife.xcodeproj cannot be opened because the project file cannot be parsed. So I sank myself even deeper into Userland and tried opening Xcode first, then using File:Open to load the project. And it loaded. And it is now trying to compile. So... What's the diff?! Why didn't the first two methods work? I'm not even sure that there should even BE a difference in the last two techniques! Ideas? Ricky Cron Stardust Developing for Mac and wondering why I keep hitting walls everywhere I move... ___ 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
