Did I write any magritte code?
mhh, sorry this was someone else.
Nevertheless, I do see them as tools associated with a particular
The idea being that a page may be presented as a task document
embed the tools for carrying out that task. In this case the page
be within the management area. Certainly I would expect to filter them
out of the users widgets list fairly soon.
I see, sounds like an interesting approach. Looking forward to see an
I expect to work it so that the environment provides the style for
peers and their sub-trees, but I expect that the environment itself
have its own environment, so that a user editing their environment
accidentally break the environment.
Yes, this sounds reasonable, breaking the environment and looking
yourself out of the system is too easy. Luckily there is always a
working inspector ...
User management may be a candidate for this kind of treatment,
user having responsibility for a sub-tree may put a user manager in
place for that subtree only. I beleive that xope does it this way too.
Exactly and I think the ACL security of Philippe is doing that as
well, at least this was one his of the initial requirements I
> 2. Your new persistency mechanisms looks cool. Does it work yet?
> is the performance? I am especially interested into the Magma
> implementation. Your changes add a lot of external dependencies,
> why not put the new persistency mechanisms into their own packages?
In theory Magma makes very little impact on the running application. I
was hoping that magma persistence could make it into the main
distribution and so although it may not look like it at this time I
been attempting to minimise those dependancies.
Yes, we can discuss about that. If it is reliable working it might be
a good thing in Squeak, though there were interests in porting it to
other Smalltalk dialect and a strong dependency to Magma would make a
port much harder.
If you look at PRMagmaPersistency all but one of the methods on the
class side in the category "init repository", I am currently
into the "Magma seaside" package as part of the magma control panel
Why "Magma Seaside"? Isn't it possible to implement the Magma
persistency so that it doesn't depend on Seaside, for example if only
the OmniBrowser interface is loaded? Or maybe one using a different
This would leave only one real method (#doing:commit:) in
PRMagmaPersistency (the others are stubs which could be fleshed out if
needed). I suspect it would seem somewhat overkill to have a whole
package for one class with one method.