Absolutely agreed on the compatibility. There will be implementation
quirks worth matching, but I think in most cases code can be made to
work on both OS and SL easily enough, and will be more reliable for
the thought put into it.
If anyone has BSD licensed (because I'm not getting into rea
Good to know. As long as there's a reason, I'm happy, I just want to
make sure people have thought about it, thanks for the answer!
On 17 Jan 2009, at 07:36, Mike Mazur wrote:
Hi,
On Fri, Jan 16, 2009 at 9:46 PM, Sean Dague wrote:
J Ross Nicoll wrote:
Any chance of a number of times access
On completed functions, what appears to be constantly ignored are other area
changes or errors that will break what was a working function. This consumes a
great deal of time thinking of new methods for an equivalent and to me defeats
the purpose of a function. The number of functions in that ca
Dear Bri:
Can you offer some suggestions as to what you might propose as we move forward?
If I get your drift, you are addressing what many call "regression", and that
is important also. One of the thoughts I had on that subject was a series of
sims with scripts running 24/7 demonstrating the v
As to the SL compatibility, at this point in development running back to SL to
test is a handy tool. That also is a reason to get flow control statements
completed.
Our next meeting we will see what we can concoct as a suggestion besides
whining.
Bri
(The sailboat is not a vehicle)
- Or
Dear Bri:
I was certainly not criticizing you. I was just trying to figure out how to
best move forward. We are all volunteers and the trick is always to figure out
how to leverage all of our efforts to help each other move forward. One of the
ideas I had was to have a set of scripts running
Charles,
No criticism received. What I want to pursue is a broader test set. Owen often
constructs bizarre looking objects that only exist for test. From his kicked
ball cross, strange linked swing set to our vendor that sells you a blank box.
They exist only to test functions. We were thrilled
Reports are good on the current trunk stability, so we just tagged r8067 as
r8068. This means that r8068 is the 0.6.2 release.
A binary build is being prepared by Nebadon and will be available on the
osgrid.org and opensimulator.org web site a little bit later today.
Good work everyone for the
There is also a suite of unit tests for trunk which are tested on every
check-in of every revision. Many of the functions and other script language
features are tested there, along with other features of OpenSim. These tests
provide almost instant feedback to developers when their changes break
exi
Dear Brianna:
I struggle with these issues all the time and have been for nearly two years
now with OpenSim.
One of the things I find that helps is to concentrate on the things that are
implemented rather then the features that are not implemented. There are more
tests I can imagine that will
Yes, excellent work. Does this include the new functions added in 1.18.x
such as llGetObjectDetails(), a key addition.
On Fri, Jan 16, 2009 at 7:13 PM, Charles Krinke wrote:
> There are 27 LSL functions with no implementation left, and they are:
>
> llRotTarget, llRotTargetRemove, llLoopSoundMas
11 matches
Mail list logo
