Another Croquet-based project has been launched this week. Cobalt is the first such coding project to be done by Duke University, which is also the home of the Croquet Consortium.
Tag: jasmine
I Can't Quit You Brie, So I'm Gonna Put You Down For a While
(Sorry, Willie Dixon.)
I haven’t been working on our Brie user-interface framework for a while now. We took it to a certain early level in Jasmine Croquet, in which we pretty solidly worked out user interface conventions, internal infrastructure, and the basic direct-manipulation philosophy.
Although not terribly novel (we stole liberally from David Smith, David Unger/Randall Smith, David Place/Pat O’Keefe, and, running out of Davids, Stallman/Sussman), Brie was still fairly advanced and abstract research, and we had more immediate work to do: Dormouse and the Croquet SDK release, and several projects using them. Brie had been sustained with financial support from NICT which has come to a pause. A great friend and entire world’s best salesman and demo-jock for Croquet went to Duke. So nothing got done on Brie following C5 ’06.
Brie has not yet been integrated with the current Croquet SDK. It still needs a lot of work in both the graphics and the API between private and replicated Croquet. It might be most efficient to let some dust settle here: Josh is working on new Croquet graphics, Andreas is working on 2D interfaces, and David Smith is working on the task/interactor model.
But the main thing is that I’m starting another project that I’m very excited about (more about this later), so I know that I won’t have time to work on Brie for a while. Fortunately, I do think that, say, phase III or so of the new project will be a driver for pulling Brie out of the closet again.
News from the Metaverse
Key invitation-only conference on the future of collaborative virtual worlds.
A Microsoft blogger, with pictures
A key thread in all this seems to be a desire for an open-source framework that works. It looks like the only concerns voiced about Croquet for this was a mistaken impression about the licensing. (See the comments in the “Good blog”, above.)
BTW, We’re still trying to set up cool demos over the now-released Croquet Software Developers Kit. The demo at Metaverse was actually the demo we produced at the University of Wisconsin for C5 ’05 in Kyoto, which was built over the Jasmine proof-of-concept. The current release is so much better, but lacking in some of the visible bells and whisles. We’re working on it…
Collateral
It’s been heads-down hard work around here ever since OOPSLA in October. Haven’t even filed my expense report yet. (Coding is more fun.) So I’m pretty late in posting that…
Summer Heat
I have no news. Or too much.
I thought summer was supposed to be “off season” in academia, but things have been incredibly busy. Some of the stuff we’ve been doing:
What Is It About Immersive 3D?
When something new comes along, we tend to describe what it is. If it’s something important, it takes a while to figure out why it’s important – what it is that is really different. The description of what something is tends to be somewhat dry and technical and it misses the point. For example, a telegraph is an encoder and a decoder in an electric circuit. But couriers and semaphores involve coders and decoders, and other stuff has had electric circuits. What was important about the telegraph was that it provided instantaneous long-distance communication. This is also what was important about its successors like the telephone and radio, even though the descriptions of what each is are quite different than that of the telegraph. It’s not as simple as describing what a new invention does for people. Quite often we don’t know how it will be used.
Since I first heard about Croquet, I’ve been trying to figure out what is really important about the immersive 3D that everyone first notices about it. I think I now have an idea. It turns out that the “immersive” part is key.
Inventing the Future: learning the system
Dear Diary,
I’m off to Japan Tuesday for the big conference. Better take a snapshot of what I’ve been doing, because I expect my world to change by the time I get back. My first six weeks on this radical Croquet project were spent with very general learning of what’s what. Drinking knowledge from a firehose. For the next six we’ve been prototyping some of the features from conference papers written by my boss, Julian, and his counterpart at U. Minnesota. We’re going to demo these at the conference, and we go on right after Alan Kay’s keynote address. Yikes. Good thing Julian gives great demos! I imagine the conference organizers know that and put him in that slot accordingly. (Cast of characters here).
[details below the fold]
Inventing the Future: Jasmine release
Croquet is still being designed. Personally, I’d like to see something useable this summer, but that remains to be seen.
There is a “developer’s version” available now, called Jasmine, but there’s some confusion as to what Jasmine is in relation to the real thing. I’m going to try to straighten that out here.
-
I Can't Quit You Brie, So I'm Gonna Put You Down For a While
(Sorry, Willie Dixon.)
I haven’t been working on our Brie user-interface framework for a while now. We took it to a certain early level in Jasmine Croquet, in which we pretty solidly worked out user interface conventions, internal infrastructure, and the basic direct-manipulation philosophy.
Although not terribly novel (we stole liberally from David Smith, David Unger/Randall Smith, David Place/Pat O’Keefe, and, running out of Davids, Stallman/Sussman), Brie was still fairly advanced and abstract research, and we had more immediate work to do: Dormouse and the Croquet SDK release, and several projects using them. Brie had been sustained with financial support from NICT which has come to a pause. A great friend and entire world’s best salesman and demo-jock for Croquet went to Duke. So nothing got done on Brie following C5 ’06.
Brie has not yet been integrated with the current Croquet SDK. It still needs a lot of work in both the graphics and the API between private and replicated Croquet. It might be most efficient to let some dust settle here: Josh is working on new Croquet graphics, Andreas is working on 2D interfaces, and David Smith is working on the task/interactor model.
But the main thing is that I’m starting another project that I’m very excited about (more about this later), so I know that I won’t have time to work on Brie for a while. Fortunately, I do think that, say, phase III or so of the new project will be a driver for pulling Brie out of the closet again.
News from the Metaverse
Key invitation-only conference on the future of collaborative virtual worlds.
A Microsoft blogger, with pictures
A key thread in all this seems to be a desire for an open-source framework that works. It looks like the only concerns voiced about Croquet for this was a mistaken impression about the licensing. (See the comments in the “Good blog”, above.)
BTW, We’re still trying to set up cool demos over the now-released Croquet Software Developers Kit. The demo at Metaverse was actually the demo we produced at the University of Wisconsin for C5 ’05 in Kyoto, which was built over the Jasmine proof-of-concept. The current release is so much better, but lacking in some of the visible bells and whisles. We’re working on it…
Collateral
It’s been heads-down hard work around here ever since OOPSLA in October. Haven’t even filed my expense report yet. (Coding is more fun.) So I’m pretty late in posting that…
Summer Heat
I have no news. Or too much.
I thought summer was supposed to be “off season” in academia, but things have been incredibly busy. Some of the stuff we’ve been doing:
What Is It About Immersive 3D?
When something new comes along, we tend to describe what it is. If it’s something important, it takes a while to figure out why it’s important – what it is that is really different. The description of what something is tends to be somewhat dry and technical and it misses the point. For example, a telegraph is an encoder and a decoder in an electric circuit. But couriers and semaphores involve coders and decoders, and other stuff has had electric circuits. What was important about the telegraph was that it provided instantaneous long-distance communication. This is also what was important about its successors like the telephone and radio, even though the descriptions of what each is are quite different than that of the telegraph. It’s not as simple as describing what a new invention does for people. Quite often we don’t know how it will be used.
Since I first heard about Croquet, I’ve been trying to figure out what is really important about the immersive 3D that everyone first notices about it. I think I now have an idea. It turns out that the “immersive” part is key.
Inventing the Future: learning the system
Dear Diary,
I’m off to Japan Tuesday for the big conference. Better take a snapshot of what I’ve been doing, because I expect my world to change by the time I get back. My first six weeks on this radical Croquet project were spent with very general learning of what’s what. Drinking knowledge from a firehose. For the next six we’ve been prototyping some of the features from conference papers written by my boss, Julian, and his counterpart at U. Minnesota. We’re going to demo these at the conference, and we go on right after Alan Kay’s keynote address. Yikes. Good thing Julian gives great demos! I imagine the conference organizers know that and put him in that slot accordingly. (Cast of characters here).
[details below the fold]
Inventing the Future: Jasmine release
Croquet is still being designed. Personally, I’d like to see something useable this summer, but that remains to be seen.
There is a “developer’s version” available now, called Jasmine, but there’s some confusion as to what Jasmine is in relation to the real thing. I’m going to try to straighten that out here.