From: Micki K. <mic...@co...> - 2004-03-01 18:31:06
|
Reini: The CreateToc looks good! I'm gonna test it on erratic section patterns (! with !! but no intermediate !!, etc.) Yes, the anchors are an important next step. Joby - maybe your code could be helpful! Rocking job! Micki At 10:25 AM -0800 3/1/04, php...@li... wrote: >Message: 11 >Date: Mon, 01 Mar 2004 19:19:43 +0100 >From: Reini Urban <ru...@x-...> >To: php...@li... >Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings) > >Joby Walker schrieb: >> I implemented a table of contents in my fork of Phpwiki as a function of >> using headings ('!'). So if in your page you have: > >Like the CreateToc plugin I just checked in :) >Can I see your source? >For now I didn't change the pagecache, so there are no anchors (a name) >for the links. > >> !!! Major Section >> !! minor section >> ! sub section >> ! another sub section >> !! another minor Section >> ! sub section >> !!! Last major Section >> >> The following TOC would be generated: >> >> * Major Section >> * minor section >> * sub section >> * another sub section >> * another minor section >> * Last major section >> >> I used unordered lists so that we can control the numbering, but it >> would be easy to change it to an ordered list. >> >> jbw >> >> Reini Urban wrote: >> >>> I would do it this way: >>> >>> ! any page content >>> <?plugin AnyPlugin ?> >>> ! more headers >>> <?plugin AutoToc ?> >>> nothing really important here at the footer >>> >>> AutoToc sees the HTML tree from the previous plugin's and page >>> content, and modifies it accordingly by recursively stepping through >>> the tree. >>> >>> This seems to be fun to code and the most painless solution. >>> (I am a former lisp programmer :) >>> >>> Micki Kaufman schrieb: >>> >>>> What if we approached it differently: >>>> >>>> 1. The plugin is an include of the basepage, but only the headings. >>>> Each is formatted with an anchor href, according to a nomenclature to >>>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4, >>>> etc.). Since one recursive include is allowed, this should be >>>> possible (except for TextFormattingRules). >>>> >>>> 2. The page belowis rendered as usual, but the presence of the >>>> AutoToc modifies the display so that the sections are rendered out >>>> with invisible anchor tags, named using the exact same nomenclature >>>> as in 1. >>>> >>>> This way you don't need two passes, or jscript. >>>> >>>> A known limitation: any !'s above the plugin declaration would >>>> perhaps not have anchors, since they'd be rendered before the >>>> appearance of the declaration. >>>> >>>> What do you think? >>>> Micki >>>> >>>>> Message: 9 >>>>> Date: Wed, 25 Feb 2004 00:53:29 +0100 >>>>> From: Reini Urban <ru...@x-...> >>>>> To: php...@li... >>>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto >>>>> IncludeHeadings) >>>>> >>>>> Micki Kaufman schrieb: >>>>> > I frequently have use for a bunch of named links - to function >>>>> like an >>>>> > online table of contents. >>>>> > >>>>> > For an example, see the beginning of the latest build's >>>>> > PhpWikiAdministration. >>>>> >>>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?> >>>>> >>>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator. >>>>> The only problem is that such targets must provide the appropriate >>>>> <a name=""> tags and gyriations as in PhpWikiAdministration. >>>>> >>>>> > Would be great to be able to insert a code like %%TOC%% or the >>>>> > equivalent, and have a series of links display based on heading >>>>> 1, 2 and >>>>> > 3. Named links aren't as important here, because one can use the >>>>> desired >>>>> > text for the headings themselves. >-- >Reini Urban >http://xarch.tu-graz.ac.at/home/rurban/ > > > > >--__--__-- > >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > >End of Phpwiki-talk Digest -- Micki mailto:mic...@co... |
From: Micki K. <mic...@co...> - 2004-03-01 18:32:40
|
Forgot to mention. One thing I really liked in Reini's 'pre-spec' was the 'headers' option in: >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?> With that, one can create Toc's of 'questions' on the page below, and ignore intermediate headings - this would be great for online frequently asked questions, etc. Looking forward! Micki > > >Reini: > >The CreateToc looks good! I'm gonna test it on erratic section >patterns (! with !! but no intermediate !!, etc.) > >Yes, the anchors are an important next step. Joby - maybe your code >could be helpful! > >Rocking job! >Micki > >At 10:25 AM -0800 3/1/04, php...@li... wrote: >>Message: 11 >>Date: Mon, 01 Mar 2004 19:19:43 +0100 >>From: Reini Urban <ru...@x-...> >>To: php...@li... >>Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings) >> >>Joby Walker schrieb: >> > I implemented a table of contents in my fork of Phpwiki as a function of >> > using headings ('!'). So if in your page you have: >> >>Like the CreateToc plugin I just checked in :) >>Can I see your source? >>For now I didn't change the pagecache, so there are no anchors (a name) >>for the links. >> >> > !!! Major Section >> > !! minor section >> > ! sub section >> > ! another sub section >> > !! another minor Section >> > ! sub section >> > !!! Last major Section >> > >> > The following TOC would be generated: >> > >> > * Major Section >> > * minor section >> > * sub section >> > * another sub section >> > * another minor section >> > * Last major section >> > >> > I used unordered lists so that we can control the numbering, but it >> > would be easy to change it to an ordered list. >> > >> > jbw >> > >> > Reini Urban wrote: >> > >> >> I would do it this way: >> >> >> >> ! any page content >> >> <?plugin AnyPlugin ?> >> >> ! more headers >> >> <?plugin AutoToc ?> >> >> nothing really important here at the footer >> >> >> >> AutoToc sees the HTML tree from the previous plugin's and page >> >> content, and modifies it accordingly by recursively stepping through >> >> the tree. >> >> >> >> This seems to be fun to code and the most painless solution. >> >> (I am a former lisp programmer :) >> >> >> >> Micki Kaufman schrieb: >> >> >> >>> What if we approached it differently: >> >>> >> >>> 1. The plugin is an include of the basepage, but only the headings. >> >>> Each is formatted with an anchor href, according to a nomenclature to >> >>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4, >> >>> etc.). Since one recursive include is allowed, this should be >> >>> possible (except for TextFormattingRules). >> >>> >> >>> 2. The page belowis rendered as usual, but the presence of the >> >>> AutoToc modifies the display so that the sections are rendered out >> >>> with invisible anchor tags, named using the exact same nomenclature >> >>> as in 1. >> >>> >> >>> This way you don't need two passes, or jscript. >> >>> >> >>> A known limitation: any !'s above the plugin declaration would >> >>> perhaps not have anchors, since they'd be rendered before the >> >>> appearance of the declaration. >> >>> >> >>> What do you think? >> >>> Micki >> >>> >> >>>> Message: 9 >> >>>> Date: Wed, 25 Feb 2004 00:53:29 +0100 >> >>>> From: Reini Urban <ru...@x-...> >> >>>> To: php...@li... >> >>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto >> >>>> IncludeHeadings) >> >>>> >> >>>> Micki Kaufman schrieb: >> >>>> > I frequently have use for a bunch of named links - to function >> >>>> like an >> >>>> > online table of contents. >> >>>> > >> >>>> > For an example, see the beginning of the latest build's >> >>>> > PhpWikiAdministration. >> >>>> >> >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?> >> >>>> >> >>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator. >> >>>> The only problem is that such targets must provide the appropriate >> >>>> <a name=""> tags and gyriations as in PhpWikiAdministration. >> >>>> >> >>>> > Would be great to be able to insert a code like %%TOC%% or the >> >>>> > equivalent, and have a series of links display based on heading >> >>>> 1, 2 and >> >>>> > 3. Named links aren't as important here, because one can use the >> >>>> desired >> >>>> > text for the headings themselves. >>-- >>Reini Urban >>http://xarch.tu-graz.ac.at/home/rurban/ >> >> >> >> >>--__--__-- >> >>_______________________________________________ >>Phpwiki-talk mailing list >>Php...@li... >>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk >> >> >>End of Phpwiki-talk Digest > -- Micki mailto:mic...@co... |
From: Micki K. <mic...@co...> - 2004-03-02 03:01:01
|
More CreateToc feedback: 1. the toc should indent to represent the heading depth. I know it's annoying, because level 3 headings (!!!) would get no indent, level 2 headings (!!) would get one indent, and level 1 headings (!) would get 2... 2. We may want to allow folks to have the output as a bulleted or non-bulleted list. Great job! Micki > > >Forgot to mention. One thing I really liked in Reini's 'pre-spec' >was the 'headers' option in: > >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?> > >With that, one can create Toc's of 'questions' on the page below, >and ignore intermediate headings - this would be great for online >frequently asked questions, etc. > >Looking forward! >Micki > >> >> >>Reini: >> >>The CreateToc looks good! I'm gonna test it on erratic section >>patterns (! with !! but no intermediate !!, etc.) >> >>Yes, the anchors are an important next step. Joby - maybe your code >>could be helpful! >> >>Rocking job! >>Micki >> >>At 10:25 AM -0800 3/1/04, php...@li... wrote: >>>Message: 11 >>>Date: Mon, 01 Mar 2004 19:19:43 +0100 >>>From: Reini Urban <ru...@x-...> >>>To: php...@li... >>>Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings) >>> >>>Joby Walker schrieb: >>> > I implemented a table of contents in my fork of Phpwiki as a function of >>> > using headings ('!'). So if in your page you have: >>> >>>Like the CreateToc plugin I just checked in :) >>>Can I see your source? >>>For now I didn't change the pagecache, so there are no anchors (a name) >>>for the links. >>> >>> > !!! Major Section >>> > !! minor section >>> > ! sub section >>> > ! another sub section >>> > !! another minor Section >>> > ! sub section >>> > !!! Last major Section >>> > >>> > The following TOC would be generated: >>> > >>> > * Major Section >>> > * minor section >>> > * sub section >>> > * another sub section >>> > * another minor section >>> > * Last major section >>> > >>> > I used unordered lists so that we can control the numbering, but it >>> > would be easy to change it to an ordered list. >>> > >>> > jbw >>> > >>> > Reini Urban wrote: >>> > >>> >> I would do it this way: >>> >> >>> >> ! any page content >>> >> <?plugin AnyPlugin ?> >>> >> ! more headers >>> >> <?plugin AutoToc ?> >>> >> nothing really important here at the footer >>> >> >>> >> AutoToc sees the HTML tree from the previous plugin's and page >>> >> content, and modifies it accordingly by recursively stepping through >>> >> the tree. >>> >> >>> >> This seems to be fun to code and the most painless solution. >>> >> (I am a former lisp programmer :) >>> >> >>> >> Micki Kaufman schrieb: >>> >> >>> >>> What if we approached it differently: >>> >>> >>> >>> 1. The plugin is an include of the basepage, but only the headings. >>> >>> Each is formatted with an anchor href, according to a nomenclature to >>> >>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4, >>> >>> etc.). Since one recursive include is allowed, this should be >>> >>> possible (except for TextFormattingRules). >>> >>> >>> >>> 2. The page belowis rendered as usual, but the presence of the >>> >>> AutoToc modifies the display so that the sections are rendered out >>> >>> with invisible anchor tags, named using the exact same nomenclature >>> >>> as in 1. >>> >>> >>> >>> This way you don't need two passes, or jscript. >>> >>> >>> >>> A known limitation: any !'s above the plugin declaration would >>> >>> perhaps not have anchors, since they'd be rendered before the >>> >>> appearance of the declaration. >>> >>> >>> >>> What do you think? >>> >>> Micki >>> >>> >>> >>>> Message: 9 >>> >>>> Date: Wed, 25 Feb 2004 00:53:29 +0100 >>> >>>> From: Reini Urban <ru...@x-...> >>> >>>> To: php...@li... >>> >>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto >>> >>>> IncludeHeadings) >>> >>>> >>> >>>> Micki Kaufman schrieb: >>> >>>> > I frequently have use for a bunch of named links - to function >>> >>>> like an >>> >>>> > online table of contents. >>> >>>> > >>> >>>> > For an example, see the beginning of the latest build's >>> >>>> > PhpWikiAdministration. >>> >>>> >>> >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?> >>> >>>> >>> >>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator. >>> >>>> The only problem is that such targets must provide the appropriate >>> >>>> <a name=""> tags and gyriations as in PhpWikiAdministration. >>> >>>> >>> >>>> > Would be great to be able to insert a code like %%TOC%% or the >>> >>>> > equivalent, and have a series of links display based on heading >>> >>>> 1, 2 and >>> >>>> > 3. Named links aren't as important here, because one can use the >>> >>>> desired >>> >>>> > text for the headings themselves. >>>-- >>>Reini Urban >>>http://xarch.tu-graz.ac.at/home/rurban/ >>> >>> >>> >>> >>>--__--__-- >>> >>>_______________________________________________ >>>Phpwiki-talk mailing list >>>Php...@li... >>>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk >>> >>> >>>End of Phpwiki-talk Digest >> -- Micki mailto:mic...@co... |
From: Reini U. <ru...@x-...> - 2004-03-02 18:29:06
|
I fixed now CreateToc to link to the headers and optionally link back to the TOC. I had to pass the preparsed markup through a lot of expand calls to the plugin as $dbi->_markup (hack alert), but I didn't have to change any user-dependent argument numbers and now we are able to see the markup as XmlElement tree and even change it. The nesting is not implemented yet and the DHTML expand/collapse also not. And the worst: I couldn't find the problem in the section extracter, with the hairy regex yet. Maybe we have to get rid of the regex and use the new preparsed tree to get at the section borders. It's already parsed anyway. Micki Kaufman schrieb: > More CreateToc feedback: > > 1. the toc should indent to represent the heading depth. I know it's > annoying, because level 3 headings (!!!) would get no indent, level 2 > headings (!!) would get one indent, and level 1 headings (!) would get 2... > > 2. We may want to allow folks to have the output as a bulleted or > non-bulleted list. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Whit B. <wh...@tr...> - 2004-03-04 19:05:46
|
On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote: > I fixed now CreateToc to link to the headers and > optionally link back to the TOC. Nice addition. One thing the current scheme misses is when two different headings have the same subheading. So if you have a page with sections like: Category One Examples Categore Two Examples - the two Examples subcategories try to set up links to the headers like: <li><a href="InPage#Categoryx20.1" class="named-wiki" title="InPage">Category 1</a></li> <li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li> <li><a href="InPage#Categoryx20.2" class="named-wiki" title="InPage">Category 2</a></li> <li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li> which both assigns the same link to two locations, but throws an error: PHP Warnings lib/plugin/CreateToc.php (In template 'browse') (In template 'savepage') (In template 'body') (In template 'html'):77: Notice[1024]: Heading <h3> Examples </h3> not found Whit |
From: Joby W. <joby@u.washington.edu> - 2004-03-04 19:12:52
|
Nice catch. This could be resolved by appending an (invisible) index number to every TOC link/anchor. jbw Whit Blauvelt wrote: > On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote: > >>I fixed now CreateToc to link to the headers and >>optionally link back to the TOC. > > > Nice addition. > > One thing the current scheme misses is when two different headings have the > same subheading. So if you have a page with sections like: > > Category One > Examples > > Categore Two > Examples > > - the two Examples subcategories try to set up links to the headers like: > > <li><a href="InPage#Categoryx20.1" class="named-wiki" title="InPage">Category 1</a></li> > <li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li> > <li><a href="InPage#Categoryx20.2" class="named-wiki" title="InPage">Category 2</a></li> > <li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li> > > which both assigns the same link to two locations, but throws an error: > > PHP Warnings > > lib/plugin/CreateToc.php (In template 'browse') (In template 'savepage') (In template 'body') (In template 'html'):77: Notice[1024]: Heading <h3> Examples </h3> not found > > Whit > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Reini U. <ru...@x-...> - 2004-03-05 10:46:49
|
Joby Walker schrieb: > Nice catch. > This could be resolved by appending an (invisible) index number to every > TOC link/anchor. yes, CreateToc is not quite stable enough. I'll have more time on sunday for this and more. > Whit Blauvelt wrote: >> On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote: >> >>> I fixed now CreateToc to link to the headers and >>> optionally link back to the TOC. >> >> >> >> Nice addition. >> >> One thing the current scheme misses is when two different headings >> have the >> same subheading. So if you have a page with sections like: >> >> Category One >> Examples >> >> Categore Two >> Examples >> >> - the two Examples subcategories try to set up links to the headers like: >> >> <li><a href="InPage#Categoryx20.1" class="named-wiki" >> title="InPage">Category 1</a></li> >> <li><a href="InPage#Examples" class="named-wiki" >> title="InPage">Examples</a></li> >> <li><a href="InPage#Categoryx20.2" class="named-wiki" >> title="InPage">Category 2</a></li> >> <li><a href="InPage#Examples" class="named-wiki" >> title="InPage">Examples</a></li> >> >> which both assigns the same link to two locations, but throws an error: >> >> PHP Warnings >> >> lib/plugin/CreateToc.php (In template 'browse') (In template >> 'savepage') (In template 'body') (In template 'html'):77: >> Notice[1024]: Heading <h3> Examples </h3> not found >> >> Whit >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: IBM Linux Tutorials >> Free Linux tutorial presented by Daniel Robbins, President and CEO of >> GenToo technologies. Learn everything from fundamentals to system >> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >> _______________________________________________ >> Phpwiki-talk mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Reini U. <ru...@x-...> - 2004-03-09 13:11:46
|
> Joby Walker schrieb: >> Nice catch. >> This could be resolved by appending an (invisible) index number to >> every TOC link/anchor. Reini Urban schrieb: > yes, CreateToc is not quite stable enough. > I'll have more time on sunday for this and more. CreateToc is now finished. Instead of "x20." I used "_" for spaces. This is not reversible, but anchors doesn't need to be reversed. >> Whit Blauvelt wrote: >> >>> On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote: >>> >>>> I fixed now CreateToc to link to the headers and >>>> optionally link back to the TOC. >>> >>> >>> >>> >>> Nice addition. >>> >>> One thing the current scheme misses is when two different headings >>> have the >>> same subheading. So if you have a page with sections like: >>> >>> Category One >>> Examples >>> >>> Categore Two >>> Examples >>> >>> - the two Examples subcategories try to set up links to the headers >>> like: >>> >>> <li><a href="InPage#Categoryx20.1" class="named-wiki" >>> title="InPage">Category 1</a></li> >>> <li><a href="InPage#Examples" class="named-wiki" >>> title="InPage">Examples</a></li> >>> <li><a href="InPage#Categoryx20.2" class="named-wiki" >>> title="InPage">Category 2</a></li> >>> <li><a href="InPage#Examples" class="named-wiki" >>> title="InPage">Examples</a></li> -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |