Re: [Phpwiki-talk] simplify default template

[Reini U. <ru...@x-...>]

Jeff Dairiki schrieb:
> On Sun, 15 Sep 2002 21:26:24 +0100
> Reini Urban <ru...@x-...> wrote:
>>I now committed it now to CVS.
> 
> As I think I said, I, at least, don't like it.
> 
> If I had to pick one out of (Info, Diff, PageHistory) to leave
> on the main page I'd definitely pick PageHistory.  Most of the 
> Info stuff is just not interesting to most readers.
> 
> If you're reading a page, what are you most likely to want to
> know about that page:
> 
>   Who wrote it (both the latest version, and who's contributed
>   to the page the most)  
> 
>   When it was written (when were the bulk of the changes made
>   to the page?) (when was the most recent change?)
> 
>   What changes were made?
> 
> Who cares how may words are on the page (the viewers already
> looking at the page)?  The hit count may be
> of interest, but probably only to the pages author.  What markup
> version?  Only someone who's going to edit the page cares, and
> they'll find that out when they try to edit it.
> Everything else on the Info page (and much more) is available
> on the PageHistory page...
> 
> 
>>How about changing the pagename "FindPage" => "Search" on the default 
>>template? (German: "Suche")
> 
> 
> A little confusing.  I would think "Search" would be the submit
> button for the quick search form.  "FindPage" serves the function
> that on most web pages is labeled "Advanced Search".

Why not call it then pgsrc/AdvancedSearch and add a RedirectTo FindPage?

> Also FindPage is a wiki link (to the page FindPage).  Are you planning
> on renaming pgsrc/FindPage to pgsrc/Search?  I don't think it's 
> worth the trouble.

Yes, this was my idea.

> In the end either is okay, but I would vote for the status quo,
> because it's the status quo.  (If you move the page FindPage to Search,
> it just creates a little more pain for everyone who upgrades their
> PhpWiki.)
> 
> 
>>Of course one can create his own navbar.tmpl template version.
> 
> Of course.  So there's no need to keep mucking with the stock one. :-)
> 
> Leaving too many buttons in the stock template is probably better
> than too few (within limits, of course) -- at least people will
> see what's possible, and it's much easier to figure out how to
> delete them from the templates than it is to figure out how to
> add them back....

Okay. I'll revert.

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/