[vos-d] S5 and ordering listeners
Can you comment on this Peter? Let's say I want a set of listeners attached to an object to be invoked in order. Let's say that both listeners live on the same local site (process) and maybe are both associated with the same vobject. Will there be a way to do this in S5? What if the listeners are associated with metaobject types (e.g. a vobject L is linked to another vobject Source. Applying type X to L causes listener x to be created, and applying type Y casues listener y to be created, each listening to vobject Source (they find Source because it's linked to L). I always want x to be notified before y of any changes to Source. Does this make sense? -- http://interreality.org/~reed ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] thinking about a new web site
Here are some ideas I had on revamping the web site. Graphic Design -- * Change the background to white or another light color. Maybe change the main content area to a different shade too, rather than current grey. * A set of background/side illustrations, that convey some of the more general themes of VOS and Interreality -- interconected things; multifaceted stuff; distributed structures -- but also look cool and have a computer graphics style to them. Pages - It's great that the site runs on hypervos. Maybe we want to keep it, or maybe we want to switch to something else then go back to it. It would be great to have text in Vobjects that can be reused on multiple pages. One possability is to use a wiki for all the pages, and then transition back to hypervos once S5 is ready for it. We could have some pages consist of more free form brainstorming and draft documentation like the current wiki, and some pages be the more public facing webpages, but those pages could be smaller but interlinked. More detail below. If we use a wiki for the main pages, we'd need to hide all the meta wiki stuff. I'm also planning on figuring out how to set up a somewhat customized drupal site for a different project, so if that works out maybe we could use that. Sections I don't think we really need a hierarchy [with the exception of About, see below], at least for the public facing aspect. These links can be listen in a little table or grid at the top of the page, like they are now (but set in a grid so they line up nicely, perhaps with logical groping/separation). * About [See below] * Screenshots * News [redirects to forum announcements] * Download * Docs * Forums * Mailing Lists * IRC * Servers [not at first, but eventually link to running servers] * Bugz * Contact About Section - This is where we explain what the heck Interreality is, and sell it. One thing we could do is have a set of short descriptions, each aimed at a different kind of person who might be interested, or describe in general terms how you might approach solving particular problem or implementing a type of idea using VOS. Docs Here we have short articles that explain how to do specific programming tasks with VOS (howto's), as well as the reference manuals. We should probably take S5 as an opportunity to split up the reference manuals, to have one for each library. I don't know if we should just update the Creating Interreality manual, or split it up into smaller documents. I'm inclined to split it up a bit, or at least separate the VOS Design document from the more practical program/how-to manuals. ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] S5 and ordering listeners
On Mon, Oct 22, 2007 at 04:39:39PM -0400, Reed Hedges wrote: Can you comment on this Peter? Let's say I want a set of listeners attached to an object to be invoked in order. Let's say that both listeners live on the same local site (process) and maybe are both associated with the same vobject. Will there be a way to do this in S5? What if the listeners are associated with metaobject types (e.g. a vobject L is linked to another vobject Source. Applying type X to L causes listener x to be created, and applying type Y casues listener y to be created, each listening to vobject Source (they find Source because it's linked to L). I always want x to be notified before y of any changes to Source. Does this make sense? I don't really follow, no. Could you give an example? The plan for listeners is for it to be based properly on message passing between objects, rather than straight callbacks. Once messages are sent out, there isn't really a guarantee on ordering, so if you need a strong cause and effect trigger, you should probably have an intermediate object that subscribes to the primary object, does some work, and then passes it on to the next listener... Or are you trying to do some kind of filtering? I can't answer the questions without knowing what you're trying to acomplish. -- [ 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] thinking about a new web site
On Mon, Oct 22, 2007 at 07:56:09PM -0400, Reed Hedges wrote: Here are some ideas I had on revamping the web site. Graphic Design -- * Change the background to white or another light color. Maybe change the main content area to a different shade too, rather than current grey. * A set of background/side illustrations, that convey some of the more general themes of VOS and Interreality -- interconected things; multifaceted stuff; distributed structures -- but also look cool and have a computer graphics style to them. Sure. I did the current design a few years ago based on an even older design of yours (still online at http://interreality.sourceforge.net/ !!!) (we should probably take down the sourceforce page, although it is of historical interest ;-) Anyway, I don't claim to be a competent graphic designer, and the interreality.org cascading style sheet has grown completely out of control, so it is probably time to start over from scratch from a design standpoint. Anybody want to help do a new site design? Pages - It's great that the site runs on hypervos. Maybe we want to keep it, or maybe we want to switch to something else then go back to it. It would be great to have text in Vobjects that can be reused on multiple pages. Having updated the pages, I think it's worth staying with HyperVOS for now. We'll want to transition to an s5-based system eventually, but we need s5 first. If we use a wiki for the main pages, we'd need to hide all the meta wiki stuff. I've seen quite a few projects that use a more or less straight up wiki for their whole site, take http://bazaar-vcs.org/ for example. Hiding the wiki links does look more polished, though. Sections I don't think we really need a hierarchy [with the exception of About, see below], at least for the public facing aspect. These links can be listen in a little table or grid at the top of the page, like they are now (but set in a grid so they line up nicely, perhaps with logical groping/separation). * About [See below] * Screenshots * News [redirects to forum announcements] * Download * Docs * Forums * Mailing Lists * IRC * Servers [not at first, but eventually link to running servers] * Bugz * Contact That's pretty much what it is divided up into right now, minus a contact page, and no servers page since there are none. About Section/Docs -- My main concern is that so much stuff is changing, in terms of both overall goals (trying to be a more focused on addressing specific tasks) and in the specifics of the technology, its hard to write useful documentation until development has settled down a bit. -- [ 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
[vos-d] notes from IRC, pt 2
Additional notes on interreality3d gui from IRC. Participants: mm765, tetron - Had trouble moving the avatar. Determined that this probably stemmed from a combination of issues: - Initially tried to use WASD keys (typical first person shooter configuration). Interreality3D 0.1 doesn't bind these keys to movement. - The d key goes into drag and drop mode, which overrides the movement keys and is not obvious how to escape from (you hit escape). - Once figured out arrow keys for movement, reported stuttering movement. This seemed to be tied to resizing the window (?). Mentioned he was using Windows Vista -- interreality3d hasn't been tested first hand on Vista, so it may be an issue with that OS. - Reported crash when clicking on ? button, then closing the help panel. - Did not like having to push escape to cancel out of minor modes. Should at least be able to cancel mode using the same key that got into the mode. - Did not think splitting was a common enough operation to support having those buttons on the button bar. - Mentioned running out of space in the window when using the mouse to move. - Liked the ability to go back to previous views. - Suggested having view templates for set GUI configurations. I mentioned and we agreed this is the same idea as UI skins discussed previously on vos-d. - Suggested that chat view should be integrated as an overlay on the 3D view; a suggestion also put forward by winterk (I believe.) - Did not like Emacs-style multi-key chords. I pointed out that the majority of Ctrl- and Alt- prefix key shortcuts are already monopolized by the OS, other GUI controls or by convention, so there are very few shortcut keys available without getting into multi-key chords. - Agreed the the UI will probably become clearer once its purpose is clearer. Lacking the ability to do any interesting browsing or editing (which depends on the backend to supply that data) it requires a bit of imagination to see what the workflow will be like, and how a configurable UI plays into that. -- [ 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
