RE: Buttonz and GUI

Hi Arnaud

For an immediate solution, you can remove any unwanted interface options
within a custom theme, see Doc: Styles and Themes
http://doc.tikiwiki.org/tiki-index.php?page_ref_id=151

Start with these two to address your issues...
tiki-show_page.tpl
tiki-page_bar 

I'd suggest just {* commenting out *} any elements you don't want, that way
they can be easily added back if you change your mind later.

Hope this helps!

 - jd - - -

> -----Original Message-----
> From: tikiwiki-devel-admin@... [mailto:tikiwiki-devel-
> admin@...] On Behalf Of Arnaud HERVE
> Sent: August 5, 2005 4:13 AM
> To: tikiwiki-devel@...
> Subject: [Tikiwiki-devel] Buttonz and GUI
> 
> 
> 
> Hi,
> 
> just as I am preparing to set up another tiki site for another
> organization,
> I would like to remind you that a few details -which are not that
> interesting to concentrate on - are still not finished.
> 
> For the moment Anonymous still sees History and Source buttons, even
> if the webmasters doesn't want that.
> 
> More important, Anonymous is enticed to Discuss the wiki page
> (discuss into forum feature), which ends up in an absolutely disastrous
> permission refusal page. Same for Help button on top of a few features.
> 
> I believe it is always difficult for core programmers to understand to
> what extent such petty interface details make the average user believe
> that the cms doesn't work. Same for css trouble in IE, for instance.
> 
> To make it short, I would like to be defined as a priority that the user
> should never end up on a permission refusal page, and Admin could
> make ALL buttons invisible to Anonymous.
> 
> Personnally I also believe that full control over "Created by" and stuff
> like that make a system much more enjoyable.
> 
> Last, another detail: I have fiddled with some templates like page_bar, I
> have removed the tables and stated instead in the css that the button
> links should be bordered rectangles: it works and allows more
> adaptability to such buttons bars. Therefore I believe some work on
> templates permission could also be an opportunity to remove most
> tables and state divs instead. That would also be a way to prevent table
> or cell css div to prevent the application of the specific feature div.
> 
> http://nondegaucheeuropeen.info/tiki-index.php
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> 

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf