I don’t get to spend as much time as I’d like on the Collaborative for Croquet, but I’m still pleased with progress on our software. A lot of people are trying it out from all around the world (ain’t the Internet grand?), and it’s standing up pretty well. Time to clarify expectations. (The punchline at the end is that you have use the latest version.)
Tag: application toolkit
“Well, no one told me about her… She's not there…” (The Zombies)
Getting nothing but a red screen at CroquetCollaborative.org? Here’s why.
Croquet keeps track of everything ever created, so that anyone can tell each object to do stuff. Most of the demo applications in the current SDK keep track as long as they are running. That creates a problem for our KidsFirst Application Toolkit demo,
and its public space at the Collaborative for Croquet. The public space is meant to be a long-lived environment, in which you can come and create (or destroy) stuff and rearrange it, and come back later to see things as you left them (perhaps evolved by someone else).
So we resort to a very old programming technique. And if you’re a developer, we need your help!
The Collaborative For Croquet
We’ve got a bunch of Croquet stuff going on. We have the KidsFirst project in early education. There are a few folks who would like to work with the KidsFirst project as educators, academics, etc., but who need an entity to work with. We also have a fairly traditional open-source development project for the software used by KidsFirst, called the KAT: KidsFirst Application Toolkit.
And we REALY, REALLY, REALLY want a place that people can just connect to and try Croquet. To interact with others through Croquet. To come back another day and have some hope of finding the same 3d world, evolved though it may be, but still maybe having some of the same things that had been put there in the previous visit. A little open-source 3D-direction-manipulation real-time collaborative place on the Internet.
And so we have formed “The Collaborative For Croquet”.
Check it out at: CroquetCollaborative.org.
The KAT
Our KidsFirst project includes a great deal of what we’ve learned about Croquet. We’re making all the code available through the CroquetSource code repository, as part of the Contributions collection of code that will be distributed in the forthcoming Croquet release. (This repository is available to developers ahead of release, as part of what David Reed calls “Invention in public.” For info on updating, see this movie and this discussion thread. There will also be a new image distribution shortly.)
We call this code the KAT – KidsFirst Application Toolkit. It fits over all the other Croquet SDK code without changing it. All the KAT-specific classes begin with K – partly for the KidsFirst project that informs its development, and partly as homage to Alan. As the code matures, you may or may not see some of the KAT code migrate down to the base classes from which it inherits. (For historical reasons, the name of the Monticello package is “Wisconsin.” This may change.)
-
“Well, no one told me about her… She's not there…” (The Zombies)
Getting nothing but a red screen at CroquetCollaborative.org? Here’s why.
Croquet keeps track of everything ever created, so that anyone can tell each object to do stuff. Most of the demo applications in the current SDK keep track as long as they are running. That creates a problem for our KidsFirst Application Toolkit demo,
and its public space at the Collaborative for Croquet. The public space is meant to be a long-lived environment, in which you can come and create (or destroy) stuff and rearrange it, and come back later to see things as you left them (perhaps evolved by someone else).
So we resort to a very old programming technique. And if you’re a developer, we need your help!
The Collaborative For Croquet
We’ve got a bunch of Croquet stuff going on. We have the KidsFirst project in early education. There are a few folks who would like to work with the KidsFirst project as educators, academics, etc., but who need an entity to work with. We also have a fairly traditional open-source development project for the software used by KidsFirst, called the KAT: KidsFirst Application Toolkit.
And we REALY, REALLY, REALLY want a place that people can just connect to and try Croquet. To interact with others through Croquet. To come back another day and have some hope of finding the same 3d world, evolved though it may be, but still maybe having some of the same things that had been put there in the previous visit. A little open-source 3D-direction-manipulation real-time collaborative place on the Internet.
And so we have formed “The Collaborative For Croquet”.
Check it out at: CroquetCollaborative.org.
The KAT
Our KidsFirst project includes a great deal of what we’ve learned about Croquet. We’re making all the code available through the CroquetSource code repository, as part of the Contributions collection of code that will be distributed in the forthcoming Croquet release. (This repository is available to developers ahead of release, as part of what David Reed calls “Invention in public.” For info on updating, see this movie and this discussion thread. There will also be a new image distribution shortly.)
We call this code the KAT – KidsFirst Application Toolkit. It fits over all the other Croquet SDK code without changing it. All the KAT-specific classes begin with K – partly for the KidsFirst project that informs its development, and partly as homage to Alan. As the code matures, you may or may not see some of the KAT code migrate down to the base classes from which it inherits. (For historical reasons, the name of the Monticello package is “Wisconsin.” This may change.)