On Tue, Dec 12, 2006 at 11:51:42AM +0100, Karsten Otto wrote:
> Hi all,
>
> it seems like I finally begin to understand what this view issue is
> all about... One more point for clarification please:
>
> Are view parameters mandatory or optional?
I think that depends on the sitution. For a so
Right. I code in MySQL at my workplace, so I know a bit about what you're
talking about. You're using it very widely, however...
(Not to throw you offtrack or distract you from working on VOS, but you're
losing me more and more with this thread)
""an area of interest "view" is a subset of all th
On Tue, Dec 12, 2006 at 01:06:20PM -0700, S Mattison wrote:
> Don't forget Aspect Ratio/Field of View, and Near/Far clipping planes. Can't
> have a camera without all the bells and whistles. ;)
>
> But I think I see what you mean. Groups of objects, or some such, are
> considered 'views'? So a 'ca
Don't forget Aspect Ratio/Field of View, and Near/Far clipping planes. Can't
have a camera without all the bells and whistles. ;)
But I think I see what you mean. Groups of objects, or some such, are
considered 'views'? So a 'camera view' would be the collection of preset or
active cameras in a w
Your view is a filtered subset of the topic :-)
I mean views in an abstract sense of a filtered or transformed version
of some underlying data set. So in our examples, an area of interest
"view" is a subset of all the avatars in the entire world, an revision
control "view" is the state of the
I'm not sure if my view of this topic is correct. By 'views', do you mean
the server controls how the client's camera should act within that world?
This makes sense. Even if you are doing a "straightforward world
connection".
In a world like Counterstrike, you are placed into a 'free 3d-watch' ca
On Tue, Dec 12, 2006 at 07:23:05AM -0500, Reed Hedges wrote:
>
> How is this different than the way things currently are?
It's not, except that s5 uses 32 bit identifiers as the "canonical name"
of a vobject rather than arbitrary strings.
> Are you proposing to require that all objects except o
Peter Amstutz wrote:
> I'm not really comfortable with using the access control system for
> this, though, since security policies (or capabilities!) define what you
> *can't* see, whereas a view filters out what you *don't want* to see.
> Access control is also a very blunt instrument, since y
How is this different than the way things currently are?
Are you proposing to require that all objects except one special root
have at least one parent? Or just to encourage that practice for most
objects?
Reed
Peter Amstutz wrote:
> I just wanted to float another idea for a change in s4 to
Hi all,
it seems like I finally begin to understand what this view issue is
all about... One more point for clarification please:
Are view parameters mandatory or optional?
A mandatory view could be assigned to a user by the site, and thus
act in a similar way as access control, i.e. restric
Am 11.12.2006 um 19:03 schrieb Peter Amstutz:
> I'm thinking that it would be useful to have a well defined root,
> similar to the unix file system root, and for vobjects on the site
> to be
> treated sort of like inodes. This has a few advantages: it is simpler
> to "mount" conventional filesy
11 matches
Mail list logo
