{"id":946,"date":"2009-05-06T09:00:21","date_gmt":"2009-05-06T08:00:21","guid":{"rendered":"http:\/\/www.matthijskamstra.nl\/blog\/?p=946"},"modified":"2009-05-28T23:45:53","modified_gmt":"2009-05-28T22:45:53","slug":"updated-syntaxhighlighter","status":"publish","type":"post","link":"https:\/\/www.matthijskamstra.nl\/blog\/2009\/05\/06\/updated-syntaxhighlighter\/","title":{"rendered":"Updated Syntaxhighlighter"},"content":{"rendered":"
Update #1:<\/strong> hmmmm, stupid but I write these post sometimes weeks ahead…. and this one caught up on me… The new version of SyntaxHighlighter Evolved has ActionScript support.. \ud83d\ude42<\/div>\n
Update #2:<\/strong> I could remove everything below, but I’m keeping this here, perhaps someone can use it…. and it took some time to write, so I really can’t kill my darlings.<\/p>\n

A little change I made to the new updated plugin:
\nfind the plugin-folder “syntaxhighlighter” and add the next line to “syntaxhighlighter.php”
\n[as highlight=”1,3″]
\n‘as’ \t\t\t=> ‘as3’,
\n‘as3’ => ‘as3’,
\n‘actionscript’ => ‘as3’,
\n‘actionscript3’ => ‘as3’,
\n[\/as]
\nand<\/strong> find in the plugin-folder “syntaxhighlighter”, the folder “scripts” and change the next line to “shBrushAS3.js”
\n[as wrapper=”true”]
\n\/\/ SyntaxHighlighter.brushes.AS3.aliases\t= [‘actionscript3’, ‘as3’]; \/\/ old line and the bottom of the .js file
\nSyntaxHighlighter.brushes.AS3.aliases\t= [‘actionscript3′,’actionscript’, ‘as3’, ‘as’]; \/\/ new line
\n[\/as]<\/p>\n

the new syntaxhighlighter only uses “as3<\/code>” and “actionscript3<\/code>“, and I just changed all my post to “as<\/code>”\n<\/div>\n

Update #3:<\/strong> and update the css, that made the code not wrap….
\nI removed “white-space: pre;” form “code” and now it wraps:<\/p>\n
\r\ncode  { font-family: "Courier New", Courier, monospace; font-size: 1.2em; \/*white-space: pre;*\/ color: Gray; }\r\n<\/pre>\n<\/div>\n
Today I updated my SyntaxHighlighter JavaScript package by Alex Gorbatchev<\/a> and it was not easy…<\/p>\n
I have a syntax highlighter installed on my blog to show my ActionScript source code in a nice way.
\nBut the first time I installed it, I choose a WordPress plugin which isn’t add to WordPress Plugin Directory<\/a>and doesn’t appear to be update.
\nAnd if I remember correctly, it didn’t work as it should and I had to add ActionScript. Read my previous decision here<\/a>.
\nSo I had to upgrade to SyntaxHighlighter Evolved<\/a> which of course came with some upgrading issues created by my previous install.<\/p>\n
First problem: write ActionScript.
\nActionScript is not default included in the Syntaxhighter, and you will be advised to use [ javascript ]<\/code> tag, which is a good advice since AS is almost javascript. It would make your live easier if you choose this option.
\nBut as in my last installment of syntaxhighlighter I want to use Actionscript highlighting.
\nSo there we go:
\nTo do that you need an Actionscript brush. I found two of them: cptloadtest.com<\/a> has one but it looks like its more for AS2,
\nand yourpalmark.com<\/a> which is also the one I choose, because I used his version also with my previous installment and it’s for AS3.<\/p>\n
This is what you need to do: install SyntaxHighlighter and if you choose to use [ javascript ]<\/code>
\nyour done. I was not done yet, so lets continue… Download the shBrushAS3.zip<\/a>, extract and place the shBrushAS3.js<\/code> in the correct folder on the server (in my case ...\/wp-content\/plugins\/syntaxhighlighter\/syntaxhighlighter\/scripts<\/code>). Now you need to change some code in the WordPress plugin:
\nYou can do this in WordPress itself if you have writing permission set, or you can edit the php file on your desktop…
\nyou need to add the highlighted code <\/p>\n
\r\n\/\/ Register brush scripts\r\nwp_register_script( 'syntaxhighlighter-core', plugins_url('syntaxhighlighter\/syntaxhighlighter\/scripts\/shCore.js'), array(), $this->agshver );\r\nwp_register_script( 'syntaxhighlighter-brush-actionscript3', plugins_url('syntaxhighlighter\/syntaxhighlighter\/scripts\/shBrushAS3.js'), array('syntaxhighlighter-core'), $this->agshver);\r\n<\/pre>\n
and <\/p>\n
\r\n\/\/ Create list of brush aliases and map them to their real brushes\r\n$this->brushes = apply_filters( 'syntaxhighlighter_brushes', array(\r\n\t'as'       => 'actionscript3',\r\n\t'as2'       => 'actionscript3',\r\n\t'as3'       => 'actionscript3',\r\n\t'actionscript'       => 'actionscript3',\r\n\t'bash'       => 'bash',\r\n<\/pre>\n
and now you are ready to go.<\/p>\n
I had to change some other stuff ([ source:as ]...[ \/source ]<\/code> into [ as ]...[ \/as ]<\/code> ) and it seems that my css is not playing nice with syntaxhighlighter. hmmmm this is more work then I thought it would be.<\/p>\n
I had to deactivate one plugin: autoescape<\/a> , it didn’t play nice with SyntaxHightlighter. I didn’t use it anymore, and the combination generated gibberish.<\/p>\n","protected":false},"excerpt":{"rendered":"
Update #1: hmmmm, stupid but I write these post sometimes weeks ahead…. and this one caught up on me… The new version of SyntaxHighlighter Evolved has ActionScript support.. \ud83d\ude42 Update #2: I could remove everything below, but I’m keeping this here, perhaps someone can use it…. and it took some time to write, so I […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,6,17],"tags":[39,408,155,185,186,406],"class_list":["post-946","post","type-post","status-publish","format-standard","hentry","category-as3","category-open-source-freeware","category-wordpress-plugin","tag-as2","tag-as3","tag-syntax-highlighter","tag-upgrading","tag-wordpress","tag-wordpress-plugin"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/posts\/946","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/comments?post=946"}],"version-history":[{"count":16,"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/posts\/946\/revisions"}],"predecessor-version":[{"id":1018,"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/posts\/946\/revisions\/1018"}],"wp:attachment":[{"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/media?parent=946"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/categories?post=946"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.matthijskamstra.nl\/blog\/wp-json\/wp\/v2\/tags?post=946"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}