Re: [JAVA3D] Changes after compilation...

2002-04-22 Thread Doug Twilleager
this method has a number of rewards. Doug. >Subject: Re: [JAVA3D] Changes after compilation... >To: [EMAIL PROTECTED] >MIME-version: 1.0 >Content-transfer-encoding: 7bit >X-Accept-Language: en-us >Delivered-to: [EMAIL PROTECTED] >User-Agent: Mozilla/5.0 (X11; U; SunOS sun

Re: [JAVA3D] Changes after compilation...

2002-04-22 Thread Kyle McDonald
to follow the > rule of restricting features at first, and then loosening up the > semantics as things progress. Java 3D is fairly innovative with > these types of features in a scene graph API, so we like to be > cautious in these grey areas. > > Doug. > > >>Subjec

Re: [JAVA3D] Changes after compilation...

2002-04-22 Thread Doug Twilleager
cs as things progress. Java 3D is fairly innovative with these types of features in a scene graph API, so we like to be cautious in these grey areas. Doug. >Subject: Re: [JAVA3D] Changes after compilation... >To: [EMAIL PROTECTED] >MIME-version: 1.0 >X-MIMEOLE: Produced By Microsoft MimeOL

Re: [JAVA3D] Changes after compilation...

2002-04-22 Thread David Grace
: [JAVA3D] Changes after compilation... The issue is not with the concept of compilation and capability bits. If you set capability bits, and compile an object, then you do have access to the things that you set with the capability bits. And, given our current set of compile optimizations, it should

Re: [JAVA3D] Changes after compilation...

2002-04-22 Thread Doug Twilleager
The issue is not with the concept of compilation and capability bits. If you set capability bits, and compile an object, then you do have access to the things that you set with the capability bits. And, given our current set of compile optimizations, it should work fine because they are all mach

Re: [JAVA3D] Changes after compilation...

2002-04-19 Thread Philip Wong
Dear Doug, sorry for being a pain. I wanted to build an infinitely scalable Java3D environment, and compilation will take so long eventually. My idea is to distribute the compilation so that it doesn't overload one computer. I am working on it using a Linux cluster. The compiled code will then be

Re: [JAVA3D] Changes after compilation...

2002-04-19 Thread Doug Twilleager
graph, and then compile it on the remote computer before displaying. Doug Twilleager Java 3D Team Sun Microsystems >Subject: Re: [JAVA3D] Changes after compilation... >To: [EMAIL PROTECTED] >Delivered-to: [EMAIL PROTECTED] >Delivered-to: [EMAIL PROTECTED] > >Thanks! > >But

Re: [JAVA3D] Changes after compilation...

2002-04-19 Thread Philip Wong
Thanks! But in that case, can i set all geometries, appearances, transform, behaviors, etc, in a branchgroup, complie it, serialize it and attach this to a locale on a different computer and render the scene from there? thanks again! pw

Re: [JAVA3D] Changes after compilation...

2002-04-18 Thread Doug Twilleager
Serializing and transmitting compiled scene graph objects is not a good idea - ie: undefined results. And, in this case, no you could not change the appearance on the second computer. It is still compiled. Doug Twilleager Java 3D Team Sun Microsystems >Subject: [JAVA3D] Changes af

[JAVA3D] Changes after compilation...

2002-04-17 Thread Philip Wong
Hi! Suppose I have a class on one computer that returns a compiled sphere as an object. This object is serialized and sent over the network to another computer. Can I change the appearance of this sphere on the second computer? thnaks! pw ===