25 Sep
2009
25 Sep
'09
7:16 p.m.
On Fri, 2009-09-25 at 18:22 +0200, Lukas Renggli wrote:
I tried adding users; that seemed to reuse the
existing user list.
At
the same time, I didn't see a direct way to
add a user; that is, I
had
to add the list, and then hit the add button of
the list.
I do not understand. From a web interface point of view, I thought there
would be a way to
add a new user directly. As far as I can tell, there isn't.
It seems one must first create a Pier Users component, and then work
within it.
I was a little surprised the Pier Users component seemed to use the
existing users list, rather than create a new one.
From a development point of view, I was a little
puzzled. I can see
there is a PUUser object, which class side description* methods.
I
think that means it's setup for Magritte. So I thought that might be
sufficient to make it possible to create one from the web.
Also, I'm confused about the roles of components and models.
I see now that there is a PUUsersWidget; I think this is what I added.
It does not hold a user list, but references it with
members
^ self context kernel users
I think what this means is that I could produce a quick and dirty widget
that was also a model (holds directory and pattern for files, knows how
to figure out which files are relevant), or I could have an explicit
Magritte object with the model. But then do I need another widget to
display the magritte object, e.g., for editing the instance variables?