From: Mike N. <mh...@us...> - 2003-02-04 17:34:23
|
On Tue, 2003-02-04 at 09:03, Don Seiler wrote: > Well parseOutput prints the <pre> tag when it sees [code] so couldn't it > just print <pre style="code"> instead? Don, So, parseInput and parseOutput don't do what I thought they did. [code] is just a substitute for <pre>. It's not a raw edit section of the page. > On Tue, 4 Feb 2003, Mike Noyes wrote: > > > On Tue, 2003-02-04 at 07:47, Don Seiler wrote: > > > I see the [code] thing is working now. I do have couple of requests: > > > > > > 1. How about adding an entry at the top of that text area (along side the > > > bold, italic, ol, ul) for putting a [code] [/code] block in? I didn't see > > > one in the demo site. > > > > Don, > > I may be mistaken here, but shouldn't the xhtml tags inside of [code] > > derive their attributes from the theme css? So if you want a boarder > > around <pre>, you define it in the stylesheet. The only thing [code] > > should do is bypass the stripping code in parseInput. Correct? > > > > http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/core/Text.php?r=1.48 -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |