diff options
Diffstat (limited to 'docs/Croquet-integration.html')
-rw-r--r-- | docs/Croquet-integration.html | 114 |
1 files changed, 114 insertions, 0 deletions
diff --git a/docs/Croquet-integration.html b/docs/Croquet-integration.html new file mode 100644 index 0000000..943274e --- /dev/null +++ b/docs/Croquet-integration.html | |||
@@ -0,0 +1,114 @@ | |||
1 | <html> | ||
2 | <head> | ||
3 | </head> | ||
4 | <body bgcolor="black" text="white" alink="red" link="blue" vlink="purple"> | ||
5 | <p>I just stumbled on this - <a href="http://forum.world.st/OpenCobalt-Croquet-client-for-Opensim-td622809.html">http://forum.world.st/OpenCobalt-Croquet-client-for-Opensim-td622809.html</a></p> | ||
6 | <div> | ||
7 | <p> </p> | ||
8 | <p>I'll reproduce the relevant part here -</p> | ||
9 | <pre>Rich White wrote: | ||
10 | |||
11 | > Thinking out loud regarding the feasible of a OpenCobalt /Croquet | ||
12 | > client/peer for Opensim ? | ||
13 | > | ||
14 | > * Connect to Opensim Server - much like Cobalt connects to Jabber now | ||
15 | > * Portal window opens to server - much like opening a stored file or | ||
16 | > connecting to another peer | ||
17 | > | ||
18 | > Convergence of the technologies would seem to bring the best of both | ||
19 | > "worlds" (peer/server/content) into one ecosystem. | ||
20 | > | ||
21 | > A few dangling pointers: | ||
22 | > http://opensimulator.org/wiki/OpenSim_Archives | ||
23 | > http://opensimulator.org/wiki/User_Documentation | ||
24 | > | ||
25 | > | ||
26 | > Ideas? Is a convergence possible? ... This though may be WAY off but | ||
27 | > wanted to bring it up and see what others thought. | ||
28 | > | ||
29 | > Cheers, | ||
30 | > Rich | ||
31 | > === | ||
32 | > | ||
33 | > | ||
34 | ... [show rest of quote] | ||
35 | |||
36 | Actually, I've been looking at merging SL and Croquet off and on for | ||
37 | several years, and there's far more interesting ways of merging the two | ||
38 | that can serve as a pattern for using Croquet in many situations besides | ||
39 | formal virtual worlds. | ||
40 | |||
41 | The simplest is to simply use the SL media plugin or the equivalents | ||
42 | that work with 3rd party viewers, and create a "telepresence" between | ||
43 | worlds. I.E. a simple view-only portal or 2D equivalent using VNC, with | ||
44 | or without interaction: | ||
45 | |||
46 | http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion#Media_Rendering_Plugin | ||
47 | |||
48 | This particular use can be extended to provide a service that could be | ||
49 | added to SL instant messaging, so that you could create a temporary | ||
50 | world and invite a buncha people to join you in a private 3D chat | ||
51 | island, for collaboration or simply to "hangout" without having the | ||
52 | overhead of maintaining a genuine OpenSim or SL sim. | ||
53 | |||
54 | Obviously, you can extend the concept to be an option for ANY kind of 2D | ||
55 | collaboration system, from Jabber to IRC to Google Wave to whatever. | ||
56 | Imagine having a "create Croquet island/invite people" option as | ||
57 | standard in any IRC client. | ||
58 | |||
59 | Getting back to typical virtual worlds usage, the idea of a viewer | ||
60 | plugin that leverages all of Squeak/Croquet's functionality to enhance | ||
61 | some other viewer shouldn't be sneered at. Right now, the SL viewer (for | ||
62 | example) barely provides access to raw mouse coordinates for UV tracking | ||
63 | on a texture (the current media plugin scenario), but there's no reason | ||
64 | why any arbitrary event or internet packet couldn't be intercepted and | ||
65 | shunted off to squeak for pre/post processing. | ||
66 | |||
67 | http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion#Proposed_Extension_to_Media_Plugin | ||
68 | |||
69 | |||
70 | I'm currently working on a proof of concept of this last by intercepting | ||
71 | arbitrary packets to/from the SL server/viewer using the Gridproxy | ||
72 | utility and/or injecting or pre/post processing such packets. When you | ||
73 | combine that with the ability to intercept mouse UV coordinates on a | ||
74 | texture in SL and render into said texture from Squeak/Croquet directly, | ||
75 | you get all sorts of possibilities. Add localhost/seaside into mix and | ||
76 | you've got a very powerful experimental system that can project control | ||
77 | surfaces via html on a prim, or in the SL built-in browser, or via | ||
78 | VNC-like interactions directly to a prim on the local SL viewer. | ||
79 | Combine that with broadcasting to streaming server, and you have a | ||
80 | virtual worlds whiteboard that can project into SL ala the metanomics | ||
81 | virtual lecture hall. | ||
82 | |||
83 | http://www.metanomics.net/ | ||
84 | |||
85 | |||
86 | Start interacting with internal viewer events, and you can leverage | ||
87 | physics/graphics creation/etc from the Squeak/Croquet side, and merge it | ||
88 | directly into a local SL instance for custom puppeteering with the | ||
89 | possiblilty of doing a P2P collaboration mechanima where individual | ||
90 | avatars can be controlled by a single machine using a script and/or | ||
91 | timeline control interface. The resulting avatar activity can be | ||
92 | "filmed" for mechanima, or could be uploaded to a central server for | ||
93 | rebroadcast to a virtual world audience (or both). | ||
94 | |||
95 | http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion#Puppeteering_Plugin | ||
96 | |||
97 | |||
98 | Instead of using 2D projections, you could also leverage the 3D portal | ||
99 | system of Croquet to inject 3D cenes from Croquet into a given virtual | ||
100 | world viewer, and either maintain a backk-end P2P connection between | ||
101 | participants, or shoot the composite scene to a central server in some | ||
102 | fashion using the existing virtual world protocols. | ||
103 | |||
104 | The possibilities are endless for synergy between Croquet and other | ||
105 | virtual worlds, IMHO. | ||
106 | |||
107 | |||
108 | Lawson (Saijani Kuhn in Second Life) | ||
109 | |||
110 | |||
111 | </pre> | ||
112 | </div> | ||
113 | </body> | ||
114 | </html> | ||