Community Scripts Initiative Launch!


We’d like to announce the public launch of our Community Scripts Initiative. Trying to explain the CSI is difficult in one post, but the idea is to start a revolution in technical community interaction. Interaction within (between technical people), and without (with users of tools). This is a large task but we have some good people behind it and really good ideas for it.

The feature of the CSI we are launching today is the Community Repositories (click here to access). CR’s are like source repositories you can make from your control panel, and are publicly viewable (though only you can check in material, others can create branches- this is a type of Distributed Version Control System and is very popular in open source communities). This is all working and in the coming weeks, remaining bugs will be ironed out and new features added. (Tutorial on setting up a Repository, with video)

So what does this do for you? Well, it creates a very easy way to set up a version control system for your personal scripts. It also publishes them if you want, so others can see and use. This kills two birds with one stone, really, and I’ve been using it for my own stuff for a month or so already. What I hope is that people will start to use it for their own and collaborative projects, and share their work, and knowledge, with the community even more.

Already on the CR, we have a series of very common and useful functions: the Function Libraries (read about them here), which are groups of functions in the public domain (so your studio won’t care about license) that are maintained by the TAO admins, so you can count on swift updates and reliable code. Any fixes requested will be done with the most speed possible. Growing these common core libraries will be a major goal of the CSI, because having a common library across all connected technical artists provides a huge boost to productivity. There is also an auto-documentation system in place. So have no fear! Take the plunge and start using the libraries, and please help create new ones! And remember, all official TAO scripts should conform to our Code Conventions and Standards.

Well this is great but may or may not be something to write home about. The CSI is more than just the CR, though, though the CR’s form a core. What we hope to roll out in coming months are much more important features and integration. For example:
Imagine you are browsing ScriptSpot, and come across a script you want to use. You download it and check it out, and make some changes. You can make a repository for your new ‘branch’ of this script. And imagine if ScriptSpot could then list your branch on the main script’s page so people can get to your page from the ‘trunk’ script. And whenever you update your script- people would be able to comment and request fixes from your ScriptSpot page- the most recent version would automatically be published. And you could allow others to publish to your own branch if you want, if your friend wants to help or make changes or well.

Well it doesn’t stop there, even. We have lots more up our sleeve (and are actively working with Chris from SS to make this a reality), and now that the CSI is launched, we’ll be asking for more help and feedback. If you are interested in helping right away, you can PM me. Or anyone can help just by participating. These things all work great on paper, but if no one uses them they will whither and die.

The sky is the limit here. For a technical and cutting edge industry, we’ve been awfully slow in embracing ‘Web 2.0’. Here is the chance to make a real change, and you can be part of it.

Other links of interest:
[li]I made a long-winded blog post about TAO, its Max-centricity, and the the future.[/li][li]All Repositories[/li][li]CSI Forum[/li][li]CSI on the Wiki[/li][/ul]

And videos make everything better, so here’s a video of how to connect to the Repositories with Mercurial installed:



BTW if anyone is interested in what we have planned for scriptspot/future expansion:

We are brewing up some awesome stuff!


Not sure if this the correct place to report bugs, but the script “” has a bug in the line 193:
it says:
local dNode = DotNetObject.ChildNodes.ItemOf index

while it should be:
local dNode = DotNetNode.ChildNodes.ItemOf index



Fixed, thanks for the heads up! Not the right thread though- there should be a thread made for it in this forum.


great initiative here. thanks!


壁球场地营造指南: 壁球是从网球派生出来的一种对着墙打的球类运动,所以又叫墙围网。 1950 年,英格兰一所名叫哈罗的学校,因运动场地小不能满足学生打网球的愿望,于是在网球场上建立起几面墙让学生对着墙打网球,后来就发展成利用三面墙的室外内球类运动。 1922 年开始的 " 拉凡姆纪念奖 " 比赛是是最早的壁球国际比赛。壁球集网球、羽毛球、乒乓球等多项运动特点于一身,对于耐力和协调性的锻炼效果非常好,娱乐性强。壁球馆占地面积小,运动环境舒适,竞技规则设计合理,已成为都市休闲健身的一种新趋势.世界壁球联合会( WSF )所规定的标准壁球馆尺寸为:单打运动场地: 长 9.75 米 宽 6.40 米 高 4.57 米;壁球双打场地: 长 9.75 米 宽 7.62 米 高 4.57 米。 体育工程壁球场地施工前对场地的要求:1、完全按照图纸要求进行土建施工。2、墙身必须符合图纸要求,如平面度在直径 3 米 圆周不超过正负 3 毫米,墙身之伸缩 缝必须平滑,不可有砂浆水泥刮痕。3、消防、装修、正式水电、油漆、天花及照明系统等,必须在墙身批挡开工前完成。4、水泥地面必须符合厂方要求:在地面同级度不可有其它砂石水泥痕迹,平整度在直径 3 米 圆周不超过 3 毫米。5、 施工墙壁应在红线下,墙面需要干燥,避免有油渍。6、球场墙壁需要清洁、干净、光滑。7、施工前必须有空调,温度大约 21℃ 左右。8、施工光线要均匀,需 500LUX 光亮度。施工中不能有其他非施工人员干扰施工。


wow… lace front wigs: make people look so different. You guys are really tempting me i’m about to order a lace wig, but these are making me want to buy full lace wigs instead and save myself some money!




happy a good lunch to you