On Wed, Jun 27, 2007 at 12:29:43PM +0200, Karsten Otto wrote:
> This sounds like a radical redesign... so far we had a single local  
> vobject acting as a sequencer for multiple remote vobjects.  
> Obviously, you have something new in mind. Please tell us more :-)

My feeling is that this would be like an optional add-on to a vobject. We would
still have the single master local object with remote proxies (that's still one
logical option; it's the libvos API that calls the remote objects as "objects"
not "proxies" and gives them the same interface).  Replication means making
copies of local objects and moving them to different sites, but keeping them in
sync behind the scenes, so a change to one copy gets reflected in the other
copy.   This requires the locking mechanism during that synchronization; locking
would be generally useful as well, even if you're just talking to one object as
a client, not a replicator

IS this kind of thing what you are thinking of Pete?

> > I've put together a mockup screenshot here:
> > http://interreality.org/~tetron/terangreal%20mockup.png
> >
> Looks like Safari! :-)
> I thought you wanted something different than a web browser? In  

Yes, I would skip the "back" and "forward" buttons, and the big bookmark
buttons. 

> particular, what use are Tabs here? After all, interacting with a 3D  
> world is about immersion, i.e. you interact with only one virtual  
> reality. 

Well, we could do what some web browsers do, which is hide the tabs UI if
there's only one tab.  You might want to be working in multiple worlds.
SOmetimes immersion can be a pain because it forces the world metaphor on you.
LEt's say your lurking in one world waitingc for people to arrive, but also
participating in the other. Or you are moving objects back and forth between
worlds.  Maybe one of your tabs is the local world within terangreal (i.e. the
one that terangreal starts up in that has some instructions in it)  that you're
using as a scratch space to create objects, then moving them to the other when
done.

> Apart from that, it looks like you intend the interface to be purely  
> 2D. Why restrict ourselves to that? Why not a separate 3D overlay,  
> driven by a VOS graph in the same manner as the main 3D world? We  

I agree, having the ability for the client to display local 3D stuff for UI
purposes might be neat, but there's some stuff that just gets hard in 3D. I
think it's a good idea to start off with typical WIMP graphics (using wxWidgets)
so that we can make something useful at something faster than our current
glacial pace.  If GUI elements are somewhat modular as Pete seems to be
suggesting (I.e. action/mode X means load GUI panes Z and Y) then we can
eventually replace 3D versions if we want, down the road.

> Well, URLs were originally never intended to be visible in the  
> original browser concepts. 

True, but they turned out to be useful :) IN our case, you will only see the top
level world URL (unless you specifically ask for a particular Vobject's URL).

> IMO the entire top half including bookmark buttons sould be the  
> display part of a tool plugin, just like everything else, and should  
> only show up if you select this particular tool.

I agree (though we might want to keep some stuff just built in to terangreal if
it doesn't really need to be a plugin).

> If so, I am not sure what the mode stack in your mockup is for.

Yeah, nont sure about this either. Is it a history of modes you used to be in?

> 
> Sounds fine, the only problem I see is how to determine that the user  
> is done with the current tool/minor mode. There sould be a consistent  
> and obvious way for the user to signal that. The current mode should  
> only be effective in the "main" part of the browser, with an  
> unobtrusive reserved "mode selection" area that is always available  
> and re-grabs mouse/keyboard bindings if you move the mouse over to it  
> or hit ESC or something.

Well, is this what the mode stack window is for? I think various tools could
trigger mode transitions (bound to keys, mouse buttons, other input devices).
Anyway, we can just put them all in a menu too so you can always have access to
any of them as well.



_______________________________________________
vos-d mailing list
[email protected]
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d

Reply via email to