Search results

• Content Creation Improvement Informal User Group/Archive/July 10th, 2012 Meeting
  | our discussions from last week mostly looked at how this could work with regards to content | It would be nice if you could have access to the morphs through LSL.
  116 KB (17,286 words) - 17:30, 10 July 2012
• Simulator User Group/Transcripts/2012.04.20
  [16:03] <font color=#005ab5><b>Moundsa Mayo</b><nowiki>: Physics, vehicles, LSL equivalency</nowiki></font> [16:05] <font color=#005ab5><b>Moundsa Mayo</b><nowiki>: And some long-time LSL functionality is not there, and may never be, since indivduals decide what
  55 KB (8,889 words) - 17:24, 20 April 2012
• Doc Team/2010-08-04
  ...r with SLA is the inane questions that are asked, and then get turned into discussions ...th internal technical documentation at all? My interest is specifically in design documentation.
  134 KB (16,823 words) - 14:21, 4 February 2011
• User talk:Rand Linden
  <lsl>float float_value = whatever; }</lsl>
  41 KB (6,551 words) - 22:40, 10 May 2012
• User:Zero Linden/Office Hours/2009 Jan 27
  * [13:33] [[User:Saijanai Kuhn|Saijanai Kuhn]]: Latif, Agent Domain design allowed for multiple layers of trust. HG seems to assume one size fitgs all ...toir|Kyrah Abattoir]]: my question was what happen when an asset coded in lsl enter in a grid that run a C# script engine, the scripts stop working? are
  45 KB (6,909 words) - 09:11, 27 July 2010
• User:Andrew Linden/Office Hours/2009 10 01
  ...aine Dinova|Morgaine Dinova]]: Andrew: going way back to the original OGP discussions in AWG, the items on the interest list were expected to be controllable thr ...onetorus Habilis]]: well, cant you override the normal cam behaviour with lsl ?
  56 KB (7,279 words) - 22:57, 14 November 2009
• User:Andrew Linden/Office Hours/2010 02 23
  ...ding:0 3px;"|I'm guessing it's about the same, and probably more of an API design issue |width=100% style=" padding:0 3px;"|I haven't been involved in discussions about it so beyond that I'm really guessing about it
  101 KB (12,615 words) - 13:06, 23 February 2010
• Community Tools User Group/19-May-2011
  |width=100% style="padding:0 6px;"|@ Youri, you mean like the LSL Library? |width=100% style="padding:0 6px;"|LL itself should start their own LSL library, its a lot easier to find for new residents
  236 KB (29,300 words) - 14:04, 19 May 2011
• WindLight/Office Hours/2007-12-13
  Tao Takashi: LSL access might also be cool<br> Jeremy Linden cheers for LSL access.<br>
  41 KB (7,031 words) - 11:15, 6 May 2019
• Simulator User Group/Transcripts/2013.07.02
  ...r been thoughts of supporting FIPA-ACL and KQML for bots? Perhaps bridging LSL with these two languages?</nowiki></font> ...ll' - what is the bug? What is it doing wrong, is it doing things wrong in LSL or PHP?</nowiki></font>
  69 KB (11,030 words) - 13:35, 2 July 2013
• Talk:Sculpted prim
  == LSL functionality? == Was wondering if there are plans to put in an LSL function to allow swapping out of the sculpt texture. This would be a nice
  102 KB (17,168 words) - 18:53, 25 September 2011
• User:Andrew Linden/Office Hours/2010 06 18
  |width=100% style=" padding:0 3px;"|I dunno... it has been argued that LSL is the lifeblood of SL content... I think I agree. |width=100% style=" padding:0 3px;"|I need to talk about the fate of LSL with Kelly Linden again. He was making some rounds internally trying to bol
  195 KB (24,186 words) - 12:45, 22 June 2010
• Mesh/Archive/2012-09-10
  |width=100% style="padding:0 6px;"|Not excactly thought thru - or deliberate design? |width=100% style="padding:0 6px;"|for example on the LSL wiki, people may well contribute more information in comments that they use
  137 KB (17,529 words) - 11:15, 22 October 2012
• User:Nyx Linden/Office Hours Transcript 2010-09-29
  |width=100% style=" padding:0 3px;"|Reed: the design is a proposal right now, we're working on coding it up before we can test i |width=100% style=" padding:0 3px;"|Thats more of a viewer design issue isn't it?
  238 KB (29,841 words) - 05:17, 30 September 2010

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)