phpwebsite-developers

[Phpwebsite-developers] pagemaster and [code]

[Don S. <do...@se...>]

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.

2. Placing the code statements in a box.  like here:
https://sourceforge.net/docman/display_doc.php?docid=9960&group_id=13751

Which is done with inline CSS:
<pre width="72"
style="background-color: Gainsboro; padding: 2mm; border-style: ridge">
bash$ which ssh
bash$ which cvs
</pre>

Perhaps we need to have the themes define a "code" style, so they can 
handle color changes etc. accordingly.

Thanks to Mike Noyes for the links and tips.

Don.

Re: [Phpwebsite-developers] pagemaster and [code]

[Mike N. <mh...@us...>]

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/

Re: [Phpwebsite-developers] pagemaster and [code]

[Don S. <do...@se...>]

Well parseOutput prints the <pre> tag when it sees [code] so couldn't it 
just print <pre style="code"> instead?

Don.

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
> 
> 

Re: [Phpwebsite-developers] pagemaster and [code]

[Mike N. <mh...@us...>]

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/