On Dec 10, 2005, at 1:14 PM, Jonathan Jones wrote:
That's an important distinction. Is the chat code going to be integral
to the VOS protocol, or is it going to be relegated to the role of a
standard plugin?
Jonathan, there are two aspects to doing chat in VOS. One is the
Talkative vobject
Hmm OK thinking about this a bit more.
I don't really think that Talkative and client actions should be
conflated at the Vobject level. Instead, I suggest modifying that
aspect of actions like this: The server could provide (a) seperate
MetaObject(s) to which the client can send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to talk a little bit about what I mean when I say I want VOS to
be the 3D web.
I don't mean that VOS neccesarily use any web technologies, I mean that
VOS has a similar scope: in the way that the web has come to utterly
dominate
And so says Peter Amstutz on 12/12/05 05:10...
Probably spam or an email virus? I know mailman strips off attachments
over 40k, so there may have been an incriminating payload which was
dropped. I certainly didn't send out these empty emails. In fact, this
is exactly the reason why I GPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, in order for Ter'Angreal (the VOS Browser) to be able to reconfigure
itself for new applications, I see a few of fundamental operations that
are required: binding keys to actions, binding mouse events to actions,
and having the ability to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now for the third installment in our groundbreaking series on where to go
the VOS UI :-)
One difficulty I've been mulling over for a while is the fact that while
VOS is focused on providing a unified view of the world which is
consistent across