Re: [vos-d] Upcoming changes: factory, actions.
Ken Taylor wrote: Cool! I was actually thinking the other day that being able to select and inspect objects in Ter'Angreal would be useful and not super-difficult to implement on the current architecture. I like the ui:actions object as a sort of scripting approximation, though i'm assuming it will probably be supplanted by a more general user-scriptable-actions mechanism in future versions. Yes. It's meant to also complement server-side scripts. E.g. you make a script that can be triggered by some random message you invent. Then you can add an action that will let the user send that message with a button click. What also would be neat is an advanced mode which allows you to edit the properties on objects directly (assuming you have permission) -- including adding new child objects. Allow this to be done on the sector (or a sub-space of the sector, once that is added to a3dl), and you have basic real-time geometry building. Yes, we need that. I've been thinking about that a lot. We had a simple one back in the day, just did a few 3D properties. I think what we'll try to do is have a little editing pane/dialog in TerAngreal, but it will be provided by a library, so we will also have a more complex standalone editor too. This is another place that OTDs could be useful: if the object editor knows what types of properties to expect, then it can create useful GUI controls for them in a generic manner. Of course, before allowing all users the ability to add objects, it would be good to hack in some quotas/limits and auto-destruction of old objects, lest your server grind to a halt from a malicious user. But perhaps I'm thinking too far ahead at the moment ;) Yeah, I think we'll worry about that later. I'm pretty sure we'll be able to implement all kinds of quota or throttling access control behaviors in server plugins in the future, when they become neccesary, as long as we keep Identities in use, and also perhaps more robust/certain remote-site identification that might be coming in s5 IIRC?? Reed ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] How to host a product design dinner party
Check this out: http://earlystagevc.typepad.com/earlystagevc/ The most recent post about Web 2.0 talks about how he thinks the next big thing is going to be interoperability. He mentions it more in the context of web services, but in fact many web services are a step backwards in terms of transparency, as a monolithic function-call API reveals little about the underlying structure of the data you are querying. VOS as a platform for interoperability has a lot of potential. What's unique, I think, is we're concerned with interoperability on multiple levels, thinking outside the web (HTTP/HTML) box, and application focused, so instead of fuzzy-headed theory or design by committee but we're actually trying to make it work for us in practice. Walking into a presentation and saying A focus of the VOS platform will be on interoperability with existing systems makes people ears perk up, probably because the strategy for 99% of systems is platform lock-in. Since we're open source, we have no motivation to create lock-in, and ironically lack of lock-in becomes our own advantage. Also, last night I came up with a new analogy for VOS: XML for Objects Meaning, essentially, in the way that XML provides a meta-syntax for documents and enables a galaxy of tools and applications that can process them, VOS could provide a meta-framework for applications to interact, and similarly enable a galaxy of tools and applications that can interoperate with them. On Tue, Mar 20, 2007 at 11:13:09AM -0400, Reed Hedges wrote: http://headrush.typepad.com/creating_passionate_users/2007/03/how_to_host_a_p.html -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] How to host a product design dinner party
On Wed, Mar 21, 2007 at 04:07:10PM -0400, Reed Hedges wrote: Walking into a presentation and saying A focus of the VOS platform will be on interoperability with existing systems makes people ears perk up, Right, though that's a hard thing to promise. Maybe we're willing to make VOS interoperable with other systems as required, and here are a few we've already done: x, y, z. To add the it's-not-cookie-cutters part: you can organize your data in whataver way fits with your need, and while this requires a bit more work to actually do that, all the features and tools and other automatic bits will still work. It's true. The advantages to VOS seem to be that it gives you a have-your-cake-and-eat-it-too approach to data structures; you can smoosh several data models together into the same logical object on the fly. Among other things this means that you can avoid slicing whereby data specific to one data model is lost in translation because the target data model doesn't support it and doesn't have room for it. In the VOS case, you translate what you can into standard object types, but can also attach your extended data and leave it there until you need it later when writing out the data to the original format. Now, this isn't perfect (there could be data dependencies which arn't maintained if the standard data is changed without updating the extended data) but it's light years better than what most people are doing. Also, last night I came up with a new analogy for VOS: XML for Objects Meaning, essentially, in the way that XML provides a meta-syntax for documents and enables a galaxy of tools and applications that can process them, VOS could provide a meta-framework for applications to interact, and similarly enable a galaxy of tools and applications that can interoperate with them. It's an OK analogy but only if you don't then start applying assumptions to VOS based on what XML is for and what it's restrictions are. Right. I'd only use this analogy with someone who already has a vague idea that VOS is about communicating objects and not documents. -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
