On Fri, 2009-09-25 at 07:44 +0200, Lukas Renggli wrote:
If I have a
seaside component and want to make it a page in pier, how do
I do that?
Add > Select "Component" > Select "Component Class"
there some registration process to get items to appear on that list?
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.
What if I want to make it a part of a page?
You embed it into the page with an embed-link:
A Seaside component: +/path/to/my/component+
Does this assume step 1, so that
my/component is a page (class
PRComponent) setup with an instance of my component?
I have a feeling the pier way is much different.
Judging by how
PRDistribution sets things up, it looks as if components are wrapped in
PRComponent and have a component class. But I've been unable to see
where actual rendering happens, or where state goes.
PRDistribution creates an initial model from a script. Doing it from
the web goes through a series of command objects, but in the end you
have the same model. State is stored in the components and rendering
happens in #renderContentsOn: of the components, just as in default
More precisely, I think the Magritte way is different. I think I could
subclass PRObject to create a class with instance vars dir and pattern.
On the class side implement descriptionDir and descriptionPattern (which
maybe would create the accessors if I hadn't bothered?).
But then I don't know how to hook that up so one can create an instance
through the web.
And I don't know how to change the default display (the default edit
view is probably fine) so it shows, e.g., the list of files in dir
When you referred to things being addressable through the web, in
response to my earlier question about security, I had assumed that the
components of a page were not addressable. I see now that most
components, if included through +path/component+, are addressable (and
presumably can be viewed separately if one is so inclined).
The concrete problem motivating these questions
is that I want to
display a list of files whose name match a certain pattern in a certain
directory. The pattern and the directory could be hardcoded, but it
would be more interesting if they were editable in the web.
You can do this with something like this:
Let's see if I
Do parameters like |foo=bar get translated into method calls foo: "bar"?
And |foo=bar|with=blah becomes sends of foo: "bar" and then with:
"blah", rather than foo: "bar" with: "blah"?
These are directed to my component, not the children? But the thing
with +value:children...+ is a PRPage, not my component, so that won't
work. So maybe my component should subclass PRPage?
So I create a component that implements setters for target: and select:.
When it receives select: (if I can count on the order) it clears it's
existing list of children and repopulates it with appropriate PRFile's.
And then the value:children|link will display them.
This is all likely to get more complex as I
extract relations between
files, parse the contents of the files and show information based on the
parse. But for now I'm just working on the "simple" stuff.
For this requirement you presumably require to add some code of you own.
already added some code, so maybe I don't understand.
The files in the directory may change (both the names of the files and
the contents), and so I can't use a static list.
Thanks for all your help.