[wp-hackers] Plugin to post source code needs testing

[Viper007Bond]

1. I've had bad experiences with other server side highlighting plugins for
WordPress before. They often get manged by WordPress. That one sounds decent
though, minus the "lang" attribute (then again, this one is forced to use
"name" due to the JS package). To be honest though, I'd probably have used
server side highlighting as well if I had been starting from scratch and not
just overhauling an existing plugin.

2. Oh.

3. Get a faster browser / see #1.

On 9/10/07, Otto <otto at ottodestruct.com> wrote:
>
> On 9/9/07, Viper007Bond <viper at viper007bond.com> wrote:
> > As for GeSHi, that's server side. This plugin relies entirely on
> Javascript
> > to do the highlighting and box. It makes it much easier to be honest,
> plus
> > it works better for text readers.
>
> 1. How does it make it easier? I use WP-Syntax and just add wrappers
> around my code that look like <pre lang="php">...</pre> and it just
> works. I don't see that that is any easier to do than add [sourcecode]
> wrappers. As far as implementation, you upload the plugin and activate
> it. Can't get much simpler.
>
> 2. WP-Syntax generates completely valid XHTML and CSS for the code,
> any text reader will read it just fine.
>
> 3. Using a server side system like GeSHi seems like a better solution
> to me. For one thing, you don't have the page render the code first in
> plain ugly black text and then suddenly have it jump to nice and
> colored once the javascript kicks in.
>
> I gotta say that while this is an interesting approach, the server
> side approach is a better one which just makes more sense. So I'll
> stick to WP-Syntax.
>
> -Otto
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Viper007Bond | http://www.viper007bond.com/