From: Adam S. <ad...@pe...> - 2002-03-19 21:02:17
|
CC'd back to the list cause it looked like a mistake that it wasn't ... > I considered using these (and l|r) but went for left|right for ease > of understanding (and remembering) on the part of the user. Also < > and > are parsed for and return an error earlier in stdlib.php (I > think). Yeah, it's hard to decide which is the most "wiki way". > Which brings up a question. This new syntax you guys are working on - > will it play nicely alongside the current syntax? Converting to/from > during import/export/upgrades may or may not be difficult, but surely > this obstacle is dwarfed by the retraining of the existing user-base, > many of whom enjoy (!) using wiki *because* they are familiar with > the simple syntax? It's hard enough getting folks to edit wiki, but > once they do, asking them to learn a new system is, in some cases, > not practical. This I can't answer as I'm not the one working on it. If I remember right the decision was that the old markup was sub-optimal and that the new markup should be implemented exclusively. > Oh yes - that was another question that's been lurking in the back of > my mind. Some of my history pages are getting pretty long and anchors > would be very useful. Yep. Moin has a TableOfContents macro that does some of what I'd like to see, but it has some pretty serious limitations as well. > On BurleyGreen.com most of the navigation on the left is an > IncludePage. This got me thinking: would be possible to create a > system which would allow content from a single page to be placed in > two or more locations in the template? > > Say in the browse.html file you had the following: > > <div class="nav"><?plugin Includepage section="Nav" ?></div> > <div class="main">$content</div> > <div class="sidebar"><?plugin Includepage section="SideBar" ?></div> > > And in the wiki-text you could put something like: > =========== > Welcome to my phpwiki-powered web site... > > ! Nav > HomePage%%% > SomePage%%% > OtherPage > > ! SideBar > [http://.../image.jpg]%%% > Caption > =========== > > You can *nearly* do this with the existing IncludePage plugin, but > the sidebar stuff will be duplicated at the bottom of the page. Can > anyone point out a way to suppress this content - with or without > hacking the source? Why not just use multiple pages eg. SideBar, NavBar, TopBar etc? That seems more flexible to me anyway? As for your question I believe there is an option to pass to the IncludePage plugin to only include "sections" which are defined by "----" within the page. Adam. |