Regarding my comment on the blog, I was trying to stay technically correct and not say it's impossible, but since there is a question of the feasibility I'm going to go ahead and say it's "impossible". Even if you were able to restrict all of the SketchUp tools down to the bare basics, 1) you wouldn't be able to use most of the functionality of prims because the way the Second Life engine handles cuts, hollows, twists, etc. is very unique to it's own engine and would need to be mimicked in whatever target platform you're looking at. And 2) SketchUp would still use it's own format for storing things which is a completely different line of thinking from how SL looks at objects. My guess is that the best building tools will be a standalone program written from the ground up, there's already C# code in the open source metaverse project to faithfully render prim.blender format xml files in to something like you'd see in SL, we just need some building tools added on. Again much easier said than done but that would be worlds easier than trying to support SketchUp, to put things in perspective.

C.J. Adams-Collier wrote:
Speaking of the prims exporter, could the contents of the following
elements be lowercased?  I can treat them as boolean if they're "true"
and "false" rather than "TRUE" and "FALSE".

<states>
<physics params="">FALSE</physics>
<temporary params="">FALSE</temporary>
<phantom params="">FALSE</phantom>
</states>

If not, it can be worked around.  It would just be easier if it were a
bool rather than a string :)

Cheers,

C.J.


I could fix it on our end, but the current version of prim.blender writes them uppercase and other possible utilities might follow suit, so you'd have to plan for the worst case scenario anyways.

John

_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
http://www.libsecondlife.org/

Reply via email to