[wp-hackers] Need code syntax highlighting plugin testing/feedback please

[Viper007Bond]

Correct. You can paste your code directly into TinyMCE and it should display
normally.

On Fri, May 30, 2008 at 2:51 PM, Jorge Peña <jorgepblank at gmail.com> wrote:

> So it works with TinyMCE without having to switch to source/code view?
>
> I wonder why someone hasn't created a TinyMCE plugin for syntax
> highlighting. Maybe one clicks a button which opens a pop up where the
> code is pasted, and only something like [code-listing-#] where # is
> the number of the code listing. Then when the post is, well, posted,
> it interprets that as the code using some type of filter (Of course
> that would mean that the code would have to be inserted into a
> database on its own). Pretty complicated but it's the only way I can
> imagine being able to use syntax highlighting plugins with TinyMCE, or
> does anyone else know another way?
>
> On Fri, May 30, 2008 at 1:37 AM, Viper007Bond <viper at viper007bond.com>
> wrote:
> > If anyone's looking for something to do, I'd appreciate this plugin being
> > tested, especially by those using TinyMCE:
> > http://wordpress.org/extend/plugins/chili-code-highlighter/
> >
> > It's similar to the SyntaxHighlighter plugin I helped write (
> > http://wordpress.org/extend/plugins/syntaxhighlighter/ ) but it uses WP
> 2.5
> > shortcodes (with some hackery for pre-10 running) and a jQuery plugin
> called
> > "Chili" which is crazy fast. Chili also doesn't require invalid XHTML,
> > unlike SyntaxHighlighter which does sadly.
> >
> > It does lack the cool line numbering, etc. of SyntaxHighlighter, but it
> > wouldn't be too hard I'd image to extend this plugin to add that if it
> > becomes a majorly wanted feature.
> >
> > I have yet to port over the kses handling (so users without the
> > unfiltered_html cap can post code), but the rest should hopefully work
> fine.
> >
> > I'm also all ears on any coding ideas anyone has to offer if someone can
> > think of a better way to do what I did -- having my shortcode run
> > pre-wpautop() and pre-wptexturize() to avoid either function mucking up
> my
> > code. There are tickets open on that BTW. I also had to use some wrapper
> > functions so I could figure out what tag I was on (there's a ticket for
> that
> > too).
> >
> > Thanks! :)
> >
> > --
> > Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



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