Questions

I have been having a look around pier for a few days, I am a beginner at
this so please bear with me.

Is there a way to have a flat wiki? It appears that new pages are
instanciated as children by default. This appears to mean that it would
be difficult to recreate the kind of c2.com wiki in which a web of new
pages are created at the same level. Is there an option somewhere?

I am wondering what the design decisions are on this score, it would be
interesting to understand the reasoning.

The Settings command is not working for me, can anyone enlighten me as
to what it does?

Although I like the heirarchy very much, I think I would like the option
of building a virtual heirarchy via tagging as well as an explict
heirarchy via administrative moving within an otherwise flat wiki
namespace. I have an implementation of tiddlywiki that does this. If a
page is tagged with a tag it becomes a content item in the tag-page. So
tagging a page "User" would make that page a child of users.

I havent quite got my head around the hidden pages. How does one create
a new environment in a subwiki?

In zope, (a four letter word!) if I remember correctly a SecurityManager
can be installed at any level in the heirarchy. It looks to me like
there could be /environment /style /security items at all levels. (how
about /.environment /.style /.background /.security) would this be
possible?

I think that all squeak project creators should be encouraged to write a
dissertation. I found Lukas' paper to be excellent.

Thank you very much

Keith



               
___________________________________________________________
All New Yahoo! Mail – Tired of Vi@gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Hi Keith,

> Is there a way to have a flat wiki? It appears that new pages are
> instanciated as children by default. This appears to mean that it  
> would
> be difficult to recreate the kind of c2.com wiki in which a web of new
> pages are created at the same level. Is there an option somewhere?

Pier is more of a content management system (CMS) than a Wiki, that's  
why it allows to structure the data. Of course you could restrict  
that pages can only be added to the root, but that would require a  
few changes to the code.

> The Settings command is not working for me, can anyone enlighten me as
> to what it does?

It changes the settings of instances of PRComponent, e.g. go to the  
environment and check the settings for the widgets there. The reason  
to have the settings separate form the edit command is because the  
settings depend on the component class that is actually selected.

> Although I like the heirarchy very much, I think I would like the  
> option
> of building a virtual heirarchy via tagging as well as an explict
> heirarchy via administrative moving within an otherwise flat wiki
> namespace. I have an implementation of tiddlywiki that does this. If a
> page is tagged with a tag it becomes a content item in the tag-
> page. So
> tagging a page "User" would make that page a child of users.

That would be an interesting extension indeed.

> I havent quite got my head around the hidden pages. How does one  
> create
> a new environment in a subwiki?

Copy the existing environment to a new location.

There is currently no way to create hidden pages from the Web  
interface. You have to use the inspector to do that manually.

> In zope, (a four letter word!) if I remember correctly a  
> SecurityManager
> can be installed at any level in the heirarchy. It looks to me like
> there could be /environment /style /security items at all levels. (how
> about /.environment /.style /.background /.security) would this be
> possible?

Have a look at the ACL security package, it goes a bit more into this  
direction. As far as I know it is possible to assign users/groups  
only to be valid in a certain sub-tree.

I also thought about having that $. for hidden structures, aka Unix,  
however I tried to avoid naming conventions as much as possible. If  
there would be a good taging system we could even avoid to have an  
'environment' page with a specific name.

> I think that all squeak project creators should be encouraged to  
> write a
> dissertation. I found Lukas' paper to be excellent.

Thank you!

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

> Have a look at the ACL security package, it goes a bit more into this
> direction. As far as I know it is possible to assign users/groups
> only to be valid in a certain sub-tree.

Nope this was never done because we never came up with good
semantics.What happens if something (user, group, ...) is already
defined in a subtree/supertree? Does it matter where you login? What
happens if you leave your tree? Stuff like that.

In general it would be interesting it you could combine the different
security methods but this is not possible at the Moment.

Philippe

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki