Sorry, no posts matched your criteria.
Comments are closed.
Follow me on Twitter: @snowcrashme - be among the first ones to know what is going on!
Hot News from Twitter
- snowcrashme: 3D in the 3D Internet http://goo.gl/fb/qd5Fl #news #virtualworlds September 2, 2010
- snowcrashme: Unisfair to launch virtual classroom http://goo.gl/fb/WxznH #news #virtualworlds September 2, 2010
- snowcrashme: We all live in a virtual world http://goo.gl/fb/XxzFa #news #virtualworlds September 2, 2010
- snowcrashme: Free ‘Virtual Events For Dummies’ Now Available http://goo.gl/fb/26anJ #news #virtualworlds September 2, 2010
- snowcrashme: Latest Teleplace release supports Sharepoint http://goo.gl/fb/V8BcA #news #virtualworlds September 2, 2010

It’s seems to be a pretty simple free way to implement virtual scrum. But if you want to have a better solution than using an Excel spreadsheet to communicate information between distributed scrum teams, you can take a look on the GreenHopper product on the following web site. This is a sofware for Agile project management team.
http://www.greenpeppersoftware.com/en/
Pierre-Yves Dufour
Sofware developper
nice Post!
Hi Ralf,
nice post, just one comment. In the ’shutdown a session’ section, you use the ‘-X quit’ option. This will just close the screen session, without nicely closing the program running inside. This could possibly lead to problems.
I tend to use ‘-X eval “stuff ^Mshutdown^M”‘, but that doesn’t always work correctly either
(
Bulli
works well for me since some while…. However it´s more “pareto quility”, i agree…
but your problem will be adresses in the next post – you can inject all kind of command into screen sessions.
This was a basic starter.
Thanks for your comments !
cheers,
Ralf
nice post. Another useful thing in screen to send commands to a screensession:
cmd = “screen -S simI -p 0 -X stuff $’link-region ” + uri + “/index.php?mcr=sim2xml&ctr=hgl\n’”
On some systems the ‘$’ is not necessary though
@Jereon: right…
will go into stuff like this in the next part, should be soon..
i just noticed there was no easy to follow track from manual to automated server operation. i will present all i am running in a basic version.
cheers,
Ralf
Thanks for this promotion Jani! Stop by and see me all week for help/details my avatar is Reaction Core or Kyle Gomboy.
The conception of sleeping sim is a very fresh, and nice idea. I think the same as you. The SL architecture is not really optimal, and not enough flexible to be a platform of the future virtual reality. I really believe in MXP and the sleeping sim philosophy, what you introduced in this article. I think the MXP can help to create a web like global virtual reality architecture.
You have spoken about 2 problems of the sleeping grids: the phisics, and the scripts which have to be run in also in non obeserved state. I have no idea about phisics, but I have a possible solution to solve the problem of scripting. I think the core of the problem that LSL uses simple event handling for the “inner events” (events which comes from inside the SIM, like timer ticks). If you change these events by others which fire only when the object is observed, you can solve the problem in many cases. For example, if you want to rotate a simple cube in LSL, you do something like this:
on_timer() {
counter ++;
rotate(counter % 360);
}
It can be changed a different timer event, which fires only when the object is obesrved, and calculates the state of the object in the time of observation:
on_timer_observed(rez_time, now) {
counter = now – rez_time;
rotate(counter % 360);
}
In this second script we get the time when the script started, and the actual time, and calculates the counter, and the state of the object. The difference that in the first (standard) case, we calculates every phase of the rotation, but in the second case we put it the state which should be in, on the observetion time. The second script is equivalent like the first, but it has the advantage that it can be sleep when the object is not observed.
The more generic way to solve problems like this is creation of an “observation” event. It could be fire only when the object is observed. In this event you could set the state of the object (as I’ve shown), do a sensor scan, etc. I think it is a more cleaner solution like create many new events like “TimerIfAvatarInRegion”, “SensorIfAvatarInRegion”, etc.
It can help to make “sleepable” scripts in many cases, but not all of them. When the object interacts others when it is changing with time, the observation event is not enough. Imagine a moveing cube, which is collide another cube. If you dont observe them when they collide, they wont collide. So, the observation event is not a universal solution, but it could help to solve the “sleepable script” in many cases.
Can Naali run in a Web browser?
Can it be used to access standard OpenSim worlds?
Thanks!
– Maria