Recent changes - Search:




Updates

Club Activities Project Notes

Team: Webteam Task list Roles Technology: PmWiki Links Development notes Website: About All recent changes Site map


This project was completed, but not judged suitable for use on the TTC website.

Recipies should not generate formatting, but should simply provide css hooks through classes. eg

(:select table=t1 select=f1,f2,f3 ... class=nm:) generates a table, say
<table class="nm-table">
<col class="nm-f1"><col class="nm-f2"><col class="nm-f3">
<thead>
  <th>f1 title</td>   <th>f2 title</td>   <th>f3 title</td> 
</thead>
<tr class="nm-row">
  <td> ... etc
</table>
  • We are having real trouble creating css hooks, we have tried installing the css recipe and integrating things that way and also creating standalone css and calling those files with out success, do you have any tips or direction for us
    • the fundamental css file is \ttc\public_html\pmwiki\pub\skins\ttc\pmwiki.css. It is used in general to override the default pmwiki styles. This css file includes
      • the pmwiki css file
      • further ttc css files
    • ttc css styles are found in the root (public_html) directory
@import url("/pmwiki/pub/skins/pmwiki/pmwiki.css");
@import url("/ttc.css");
@import url("/ttc2.css");
  • I suggest you place your css in a new css file and include it, or add to ttc2.css
    not sure what you mean about css recipe, but the above should solve your problem, if not show me a few files.
  • We have tried to add our table class to the ttc2.css and also created a new css and imported as you have, but we are having trouble applying the styles to the wiki pages, how do you actually apply the css classes and divs to the pmwiki. Are there any examples in the ttc site of you applying different styles from your ttc.css on the fly or additional pmwiki markup to apply the css styles??. We will email you the css files we have created and go from there. Thanks

It should be possible to restore previous data entered, to preserve the wikiness of the feature. This could be by using the wiki feaures in some way, or instead treating all edits as additions to the database, and preserving a timestamp, author, and comment for each change made, and then providing a mechanism thru the modification process the view and restore previous changes. No data would be deletable by users, simply versioned or hidden away

  • new club home page will be TTC.HomePage
  • new clubnight page will be TTC.Tuesday - Was there a version of this wiki page in the TTC site you gave us? There is a TTC.Tuesday file in the wiki.d directory of the zip file I provided you.

Make even fields such as names and heading a decent length, eg 300 chars in length. Selection parameters could be such as

  • all future activities
  • next tuesday activity (parameter driven to swap over at, say, 9pm)
  • activities in next time period (eg week, month)

Have a flag per row that specifies if row is to be 'displayable'

Page last modified on 2007 Nov 27 15:20  

Edit - History - Recent changes - Wiki help - Search