Customizing Pier
Locked
 
|
Greetings,
I am just starting to poke around Pier and I am trying to figure out how to hide the "Views" menu from a non-admin user. I can change the permissions for "Other" so that there are no menu choices under the "Views" menu but the box with the word "Views" still appears. I would like this to not be shown. How can this be done? Just to clarify, what I mean by the "Views" menu is the menu on the left hand side. There are three menus on the lhs: Views, Commands and Navigation. I want the Views menu to not appear at all. Thanks, Frank _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Hi,
Go to the Commands widget and then access Settings. This will allow you to put away the View from the list of available commands. Cheers, Doru On Aug 31, 2008, at 4:35 PM, Squeaker wrote: > Greetings, > > I am just starting to poke around Pier and I am trying to figure out > how > to hide the "Views" menu from a non-admin user. > > I can change the permissions for "Other" so that there are no menu > choices under the "Views" menu but the box with the word "Views" still > appears. I would like this to not be shown. How can this be done? > > Just to clarify, what I mean by the "Views" menu is the menu on the > left > hand side. There are three menus on the lhs: Views, Commands and > Navigation. I want the Views menu to not appear at all. > > Thanks, > Frank > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com www.tudorgirba.com/blog "Beauty is where we see it." _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Tudor Girba wrote:
> Go to the Commands widget and then access Settings. This will allow > you to put away the View from the list of available commands. > Thanks for the help. I was able to do what you suggested but what I wanted to accomplish is to have the entire Views box on the sidebar not appear. Maybe I can pose a different question: How do I get the entire sidebar to not appear? I see in a previous email that Lukas provided this hint: > If you have loaded Pier-Security you can set the view > permissions of the side-bar to the admin only. This > means you remove all the permissions from Group and > Others of the side-bar page. In this case it won't > be displayed. But I not clear on how to access the page that sets the permissions for the side-bar page. Thanks again, Frank _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
I would like to send you my pdf, but I cant attach it. I will get it to you somehow.
On Mon, Sep 1, 2008 at 8:54 AM, Squeaker <[hidden email]> wrote:
-- David Zmick /dz0004455\ http://dz0004455.googlepages.com http://dz0004455.blogspot.com _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
In reply to this post by squeakman
Hi again,
I do not know exactly what your settings are, but I guess you have somewhere in your environment "Views" as an explicit string followed by something like "+views+" that embeds the views widget. The Unix security can only be applied on a structure (e.g., page, widget, file). So, what you should do is to create a page that says "Views +views+", embed this page into the environment, and then set the rights for this page like you did for the widget only. Does this help? Cheers, Doru On Sep 1, 2008, at 3:54 PM, Squeaker wrote: > Tudor Girba wrote: >> Go to the Commands widget and then access Settings. This will allow >> you to put away the View from the list of available commands. >> > > Thanks for the help. > > I was able to do what you suggested but what I wanted to accomplish is > to have the entire Views box on the sidebar not appear. > > Maybe I can pose a different question: How do I get the entire > sidebar > to not appear? I see in a previous email that Lukas provided this > hint: > >> If you have loaded Pier-Security you can set the view >> permissions of the side-bar to the admin only. This >> means you remove all the permissions from Group and >> Others of the side-bar page. In this case it won't >> be displayed. > > But I not clear on how to access the page that sets the permissions > for > the side-bar page. > > Thanks again, > Frank > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com www.tudorgirba.com/blog "Beauty is where we see it." _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Tudor Girba wrote:
> Hi again, > > I do not know exactly what your settings are, but I guess you have > somewhere in your environment "Views" as an explicit string followed > by something like "+views+" that embeds the views widget. > > The Unix security can only be applied on a structure (e.g., page, > widget, file). So, what you should do is to create a page that says > "Views +views+", embed this page into the environment, and then set > the rights for this page like you did for the widget only. > > Does this help? > > Cheers, > Doru > Thanks that has helped me a bit in putting the pieces together. Is there documentation somewhere that explains the things that you can add to your page, e.g., +Views+, +Sidebar+, +header+ etc? Cheers, Frank _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
> Is there documentation somewhere that explains the things that you can
> add to your page, e.g., +Views+, +Sidebar+, +header+ etc? These are all pages, components, files, blogs, posts, ... that are part of your Pier setup. +Views+ means to embed the structure named "Views" that is a child of the current page. You can also use more complicated absolute or relative paths to reach any other structure within your kernel: +/+ to embed the root page +/information/license+ to embed the license +..+ to embed the parent structure etc. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
Lukas Renggli wrote:
>> Is there documentation somewhere that explains the things that you can >> add to your page, e.g., +Views+, +Sidebar+, +header+ etc? > > These are all pages, components, files, blogs, posts, ... that are > part of your Pier setup. +Views+ means to embed the structure named > "Views" that is a child of the current page. You can also use more > complicated absolute or relative paths to reach any other structure > within your kernel: > > +/+ to embed the root page > +/information/license+ to embed the license > +..+ to embed the parent structure > etc. > > Cheers, > Lukas > Ok, the light is going on! Finally. Of course I have more questions. My experimenting leads me to believe that there is one Design for the entire kernel, is this true? I am hoping that I can customize the design on a per page basis as opposed to having one global design. Another question: How does one go about creating a new kernel? Many thanks, Frank _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
>> +/+ to embed the root page
>> +/information/license+ to embed the license >> +..+ to embed the parent structure >> etc. >> >> Cheers, >> Lukas >> > > Ok, the light is going on! Finally. Good. ;-) > Of course I have more questions. My experimenting leads me to believe > that there is one Design for the entire kernel, is this true? No. The page "/environment" defines the default design (it is sort of a meta-page for Pier). In the settings of the root page you see that the environment is set to "/environment". > I am hoping that I can customize the design on a per page basis as > opposed to having one global design. Now you can copy the default environment, modify it and go to a different page. In the settings of this other page you select the copied environment. Here you go, now you have two different designs. Child structures will inherit the design of their parent, if the structure does not define the design. > Another question: How does one go about creating a new kernel? Evaluating PRPierFrame initialize will guide you through the process of creating a new kernel and register it as a Seaside entry point. You might want to have a look at that code, to see how it exactly works (essentially it just creates an instance of PRKernel, creates a new Seaside application and tells it to use the new kernel instance). Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
The Pier-PersistencyManager has a UI for adding kernels
Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
|
|
i really wish i wasnt so busy, i have pdf i would love to put somewhere, put i just dont have time!
On Tue, Sep 2, 2008 at 5:37 PM, Keith Hodges <[hidden email]> wrote: The Pier-PersistencyManager has a UI for adding kernels -- David Zmick /dz0004455\ http://dz0004455.googlepages.com http://dz0004455.blogspot.com _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
«
Return to Magritte, Pier and Related Tools
|
1 view|%1 views
| Free forum by Nabble | Edit this page |