On la, 2011-01-22 at 23:02 -0800, Groove wrote: > TOY sounds like a very interesting project :) > Any idea when there might be more information available and/or a > public release?
Soon I think -- one idea is that there'd be a public server out for people to test. I suspect that also for you pointing to a pile of code would not be helpful, 'cause it would be considerable work to setup and configure and it requires some extra server backends etc. And there are probably no docs for those configs. > Is the intention still to make it a free open source release? I had to ask around a bit and have some talks to get to know the current status about this. Conclusion is that the plan is indeed to have the tools as open source, but to provide it also as a service commercially for those who don't want to install & maintain etc. themselves. Also one idea in TOY development has been to be close to normal Naali development. All the basics like using web pages, drag&drop of new meshes to worlds from the web, the Mumble voice etc. have been in Naali releases for long and used in TOY pretty much as is (were developed partly as TOY work but put to mainline Naali immediately). TOY just has some additional simple content creation GUIs on top of these. One fun feature is that you can carry objects around, as a simple way to build a scene without having to know how to 3d manipulation with the normal editing tools. That is also something that we all agree that could and should be just a normal feature in default Naali, but it's not integrated over yet. Guys have now been at least experimentally porting some of the tools to work on Tundra, which is AFAIK not a big change 'cause much of them were already client side Naali things and the API on the client is side is mostly same no matter which server is used. And custom feats use ECs for storage&syncs and those work similarily in Taiga&Tundra. In that work they are ported from py to js so that they can be downloaded and executed as a part of services on the net, don't have to be bundled in Naali releases or installed with an add-on system that asks permissions from users etc. So they can be updated after deployment. (i did propose they would have used js already in the previous step, but they didn't wanna learn a new lang then, and we still don't have js bindings for all the things like webkit so probably doing in py was quicker then .. porting between py & js is usually simple so i expect we see results soon). ~Toni -- http://groups.google.com/group/realxtend http://www.realxtend.org
