problem reloading structures in plugin o3d

[j brandon keith]

hi...this is to report a plugin-o3d problem building on linux. After
syncing I type gypbuild and get:

jbk@jbk-laptop:~/workspace/o3d$ gclient sync

________ running 'svn update /home/jbk/workspace/o3d/o3d' in
'/home/jbk/workspace/o3d'
At revision 56602.
Syncing projects: 102% (48/47), done.
jbk@jbk-laptop:~/workspace/o3d$ cd o3d/
jbk@jbk-laptop:~/workspace/o3d/o3d$ ls
base buildRecord.txt compiler core event
gypbuild.py o3d_assets samples statsreport v8
bitmap cg_to_glsl conditioner DEPS
google_update import plugin serializer tests
breakpad codereview.settings converter DEPS_chrome gypbuild
installer PRESUBMIT.py skia third_party
build collada_edge converter_edge documentation
gypbuild.bat nbguidgen README standalone utils
jbk@jbk-laptop:~/workspace/o3d/o3d$ ./gypbuild
make -C ../.. O3D_All
make[1]: Entering directory `/home/jbk/workspace/o3d'
Makefile:296: native_client/src/shared/imc/google_nacl_imc.target.mk:
No such file or directory
Makefile:297: native_client/src/shared/imc/libgoogle_nacl_imc_c.target.mk:
No such file or directory
Makefile:298: native_client/src/shared/imc/run_sigpipe_test.target.mk:
No such file or directory
Makefile:299: native_client/src/shared/imc/sigpipe_test.target.mk: No
such file or directory
Makefile:300: native_client/src/shared/platform/platform.target.mk: No
such file or directory
Makefile:301: native_client/src/shared/platform/platform_tests.target.mk:
No such file or directory
Makefile:302: native_client/src/trusted/gio/gio.target.mk: No such
file or directory
make[1]: *** No rule to make target
`native_client/src/trusted/gio/gio.target.mk'. Stop.
make[1]: Leaving directory `/home/jbk/workspace/o3d'
make: *** [all] Error 2
Traceback (most recent call last):
File "/home/jbk/workspace/o3d/o3d/gypbuild.py", line 291, in <module>
main(sys.argv)
File "/home/jbk/workspace/o3d/o3d/gypbuild.py", line 288, in main
GypBuilder(args[1:])
File "/home/jbk/workspace/o3d/o3d/gypbuild.py", line 270, in __init__
func(targets, options)
File "/home/jbk/workspace/o3d/o3d/gypbuild.py", line 193, in Dobuild
self.Execute(['make', '-f', solution])
File "/home/jbk/workspace/o3d/o3d/gypbuild.py", line 52, in Execute
self.builder.Execute(args)
File "/home/jbk/workspace/o3d/o3d/gypbuild.py", line 282, in Execute
raise RuntimeError("FAILED: " + " ".join(args))
RuntimeError: FAILED: make -f o3d_all.Makefile

I use plugin version because our clients mostly use IE and plugin
works there. Also, I'm only trying to get an updated version of the
library because I've run into a bug when I try to reload a structure
into the plugin. It fails to uninitialize. For example, the
following:

function uninit() {
if (g_client) {
g_client.cleanup();
}
}

doesn't work. I've created a demo page to showcase the failure here:

http://atomicviewer.appspot.com/vimmplugin

when one clicks on the second material, for example, it doesn't load
but instead posts a popup:

ERROR: Invalid object; perhaps it's been destroyed already?

After fooling around a little with the o3d javascript I believe it may
be an o3d bug. Please let me know if there's an easy fix or
workaround.

Thanks,

Brandon Keith
Senior Postdoctoral Scholar
California Institute of Technology
Pasadena, CA

ps: is there an easier way than building from source to get the latest
plugin version library of o3d? It wasn't immediately obvious on the
website (http://code.google.com/apis/o3d/)

[brandon]

Just reposting this in case anyone has had epiphanies about why o3d
doesn't reload correctly--be sure to see the demo:

http://atomicviewer.appspot.com/vimmplugin

pertinent part of original message:

I've run into a bug when I try to reload a structure
> into the plugin.  It fails to uninitialize.  For example, the
> following:
>
> function uninit() {
>   if (g_client) {
>     g_client.cleanup();
>   }
>
> }
>
> doesn't work.  I've created a demo page to showcase the failure here:
>
> http://atomicviewer.appspot.com/vimmplugin
>
> when one clicks on the second material, for example, it doesn't load
> but instead posts a popup:
>
> ERROR: Invalid object; perhaps it's been destroyed already?
>
> After fooling around a little with the o3d javascript I believe it may
> be an o3d bug.  Please let me know if there's an easy fix or
> workaround.
>
> Thanks,
>
> BrandonKeith
> Senior Postdoctoral Scholar
> California Institute of Technology
> Pasadena, CA