From: Micki K. <mic...@co...> - 2004-03-07 22:54:23
|
ONe other addition: to exclude the comments from the 'main' page, but have them on the 'included' pages, just use a 'section=' in the IncludePage plugin. I don't think 'section=' is active in IncludeSiteMap, but that should be easy to explore... Enjoy! Micki >For your application, make that 'h2'... > >Micki > >>Whit: >> >>I'd use IncludePage (for static includes) or IncludeSiteMap (for >>dynamic includes based on WikiBadges), and (HACK ALERT) change the >>'transclusion-title' in the stylesheet to an h1 heading. Then, >>insert a TOC and lock the main page. UnfoldSubPages should work >>similarly to IncludePage, with a defined list, not quite 'static' >>but not as dynamic as a 'WikiBadges' approach like IncludeSiteMap. >> >>Should give you a large chunk of the behavior for which you are >>searching - clickable headers that point back to the base pages, a >>locked 'book' page containing the includes, and a TOC that >>accommodates the huperlinking. >> >>What do you think? Am I missing something fundamental? >>Micki >> >>At 8:07 PM -0800 3/6/04, php...@li... wrote: >>>Message: 1 >>>Date: Sat, 6 Mar 2004 13:16:57 -0500 >>>From: Whit Blauvelt <wh...@tr...> >>>To: php...@li... >>>Subject: Re: [Phpwiki-talk] TOC headings - unique ID >>> >>>On Fri, Mar 05, 2004 at 08:33:30PM -0500, Micki Kaufman wrote: >>> > Absolutely - a unique ID in each anchor and href is critical, to >>> > differentiate form from function... >>> >>>While it's simple enough to add something either time-based on a fine-enough >>>scale or sufficiently random in the TOC context, I've been puzzling on how >>>to borrow the functionality being built for the TOC context to get the >>>following effect: having each heading accompanied by an auto-generated link >>>to a subpage (somewhat like the calendar plugin). The notion is that the >>>main page remains owned by - and only editable by - the primary author(s), >>>but the subpages are there for open comments on each of the subsections >>>(with an option to display comments and sections side-by-side). >>> >>>The stumbling block with doing this is that, while the unique ID scheme that >>>will be used in the TOC most probably will generate the IDs on-the-fly each >>>time the page is generated, the unique ID scheme required for what I'm after >>>would have to be stable so the subpage links could be consistent. To have it >>>be stable all I can think of is to write the IDs into the page body on the >>>first pass through - which seems a bit un-wiki-like and noisey. Is there a >>>solution I'm overlooking? >>> >>>Thanks, >>>Whit >> -- Micki mailto:mic...@co... |