As, hopefully, being discussed on TaviTodo/NewCssStructure the main structure of 'Tavi pages are going to change. Along with this change I also would like to make some changes in which elements to use for the different containers. Today these containers are hardcoded into the code, and I want some of them to change. And these changes are presented here on this page.

Todays elements

toolbar_top

Today the toolbar top consists of: 

WikkiTikkiTavi | RecentChanges | Tavi/ SubPage/ Path/ | Preferences

where the path is only visible when viewing TaviSubPages. And when editing a page there is the addition of a SaveButton and PreviewButton above the textarea box.

toolbar_bottom

The bottom consists on a normal page of:

EditLink | HistoryLink 
Modification-info
Search: <input-field>

(and on this site some logos as well)

On the edit pages this changes to:

Summary of change: <input-field>
Add document to category: <input-field>
HistoryLink

The new version

In the new version I picture this controlled by a set of variables, as given in example below:

  $ViewToolbarTop = "MainPage | RecentChanges | $SubPath | %Preferences%";
  $EditToolbarTop = "%SaveButton% | %PreviewButton% | %Preferences%";
  $SubPath = " $%path%/ [| %child%/] ";   => which would be translated into i.e My/ Longish/ SubPath/
  $ViewToolbarBottom = "EditLink | HistoryLink \\ %modification-info% \\ %search-form%";
  $EditToolbarBottom = "%comment-form%\\%category-form%";

I guess most of this is intuitive to understand, and the syntax are not fixed (yet). But as you might see such a scheme would facilitate changing top or bottom toolbars to one likeing. If one wants to add a link, then add a link. If one want to add usual text, add text. If one wants to use a special element, use a given syntax. Add line breaks could be done, say using "\\".

I've proposed a syntax for the special elements, but this is just a sketch. But as a starter I see the following lending them self for inclusion as special elements:

%preferences%
Used as todays elements. Changes according to whether one has set the preferences or not. Could easily be extended to contain login-information
%search-form%
Should contain "Search: <input-field>". See also %extended-search%
%comment-form%
Should contain "Summary of change: <input-field>".
%category-form%
Should contain "Add document to category: <input-field>".
%modification-info%
A template stating last change of pages, and maybe version?
%save-button%
A button having the save link
%preview-button%
A button having the preview link
%edit-transcluded-link%
A new form and a select list, to be used if the page has transcluded stuff in it. Then the link would appear, with a selection list of all transcluded pages. Then it's possible to go directly to edit a transcluded page. This link could be added, at will, either to the normal view or just to the edit view of a page.
%extended-search-form%
Not in use today, but maybe in version 0.25. Intended to replace the simple search form with the following: 
 <select name="searchtype=">
   <option value="simple" selected>Simple search    </option>
   <option value="linksto">        Links to        </option>
   <option value="advanced">       Advanced search</option>
   <option value="titlesearch">    TitleSearch </option>
 </select> : <input-field>
This allows for one entry field, but multiple search options. The simple search is the one used today. Links to locates pages linking to the given page title. Advanced Search could have extra matching abilities, wildcard perhaps? TitleSearch could be a easy interface to the TaviMacros/TitleSearch.
%formatting-guide%
A simple div containing a brief introduction to the formatting rules.

An example based on new style

One could use: 

 $EditToolbarTop = " %preferences% ";
 $EditToolbarBottom = "%comment-form% \\ %category-form% \\ %SaveButton% %PreviewButton% %HistoryLink% %edit-transcluded-link% \\ %formatting-guide%";

which then would be displayed as:

Your name is EvenHolen
  ---------------------------------------
  | Text of                             |
  | page                                |
  | goes here                           |
  ---------------------------------------
Summary of change: <input-field>
Add document to category: <input-field>
[[Save]] [[Preview]] ViewHistory  Edit <list of all transcluded pages>
------------------------------------------------
| ''italics'' '''bold''' {{monotype}}          |
| ==Main heading ==   === Sub Heading 2 =      |
| Lists: *bulleted #numbered  ;definition:list |
------------------------------------------------

Run discussion

EvenHolen: Is this useful, or is it just me who wants stuff like this? I think this would meat some of the demands for changing the look and feel of a 'Tavi installation, and together with TaviTodo/NewCssStructure this opens for an exciting new world. (And with file upload-possibilities for new css-files, I think this would rock the sky...)

EvenHolen: If having that %edit-transcluded-link% it would seriously ease the edit operation of transcluded pages. People would then go to edit a page, discover that what they wanted to edit is transclued, and then just choose the transcluded page from the list, and press the edit button... Hmm... I think I like my own thinking! ;-)

Hi Even. I'm not sure if I quite follow all you thinkings ;) But You have come up with great ideas before so I look forward to see this :) I just hope that no changes, change the behaviour and config of Tavi to much, for newcommers, since that's the reason I prefer Tavi over ie. php-wiki... Tavi was much easier to adjust to my needs. And I kinda like this plain environment. I have of course changed the CSS on my page and now that I know alot more about CSS I too would love to have advanced CSS. But I think the default should be as easy as possible. I also Agree with AaronLaw (TaviTodo/NewCssStructure) The pages should look ok on non CSS user agents. And as I understand, The user may change it with his/her own Preferences, I guess you want the same.