[cap-talk] User interface discussion, role based geometry editing

[John Carlson]

So any collaborative application would be thrown out,
because it would require more than one SmallTalk image?
Is networking inside a SmallTalk image these days?

What are they doing inside Croquet...replicating
file based formats without OCaps, or doing things the right way, with
OCap points, polygons and groups?  Where does OpenGL
or its replacement fall into this?

Sorry, I don't know SmallTalk yet.

John
On Feb 26, 2008, at 8:46 AM, David Chizmadia (Home) wrote:

> John Carlson wrote:
>>> At 09:04 PM 2/25/2008, John Carlson wrote:
>> Are these situations that neither role based nor
>> capability security has a good answer for?
>
>     Not intending to be glib, I would say that the
> answer depends on your criteria for "good".
>
>     With a couple of minutes of thought, I was able
> to envision both OCap and OCap-based RBAC designs,
> but based on some of Shap's questions I suspect that
> they might not be efficient, even if they are
> effective and easily analyzed.
>
>     My own rule of thumb for deciding whether an
> application is amenable to an OCap design is that
> if you can think of a way to implement what you want
> entirely in a SmallTalk image, then Ocaps are likely
> to be an effective approach for your application.
>
> -DMC
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk