Its been quite some time & I’ve received quite a lot of eMails from people asking me when the v2.0 Final of iG:Syntax Hiliter will be released.
Firstly I’d like to express my gratitude to people who’ve taken few moments out of their busy schedule to try & implement my plugin & who are interested in it. Thanks guys, you are the best. 😉
Secondly, I’d like to tell them to hold their horses. I finally got down to drafting & writing the plugin yesterday(well, day before yesterday as its past 12 midnight now), as I’ve been busy as hell off late. You’ll be surprised to know that I’ve completely(about 99%) re-written the plugin code so now its all encapsulated in a class which you can use as it is in your projects to hilite the code, you just need to call the respective hilite function & pass it the code to hilite. But the CODE Tags won’t be available, so to use them also, you’ll need the whole code of the plugin minus the WP filter calls at the end.
Thirdly, this is going to be a massive update, so I’d urge all users to upgrade to v2.0 Final, when it comes out(hopefully this weekend, I’ve got 4 consecutive holidays coming). 😀 Besides that, the results so far look really good.
In the versions released till date, you have had the generic CODE tags for hiliting CODE that doesn’t have any specific tags. But these CODE tags just wrapped your CODE in a CODE Box without any line numbering etc. But now in v2.0 Final, you’ll have Line Numbering in Generic CODE boxes also. 😀 Didn’t I say things are not going to be same!! 😉
So everyone will find something to their appetite. 😀 😉
I’ve spilled enough beans & any more & I might as well hand out the plugin right now(I’d love to but I fear the brickbats that you’ll throw at me for giving out an un-finished & highly crash prone plugin to you). 😀
But keep in mind that the Plugin hasn’t been finalised yet, so there’s an outside possibility that something mentioned here might not be in the public release & its definite that a lot of things not mentioned here will be in the public release. 😀
So, till the moment arrives, keep your hats on….. 😉
Have you seen this?
An obvious quick hack, but I can’t believe how many hits it’s giving me…
Nah, I haven’t seen it & now that I’ve seen it, I can’t understand it. 🙁
But as far as I can make out it, its a plugin for Blog:CMS. 😀
Good for you!! 😉 And I recommended my plugin & GeSHi to Dennis & he’s using it at ezFAQs. 😉
Aah, I thought that was a plugin for WP 😉
Well, the code is written in English & the class extends NucleusPlugin & as far as I know, only the plugins meant for NucleusCMS & Blog:CMS use that class for plugins.
And since that blog is running Blog:CMS, I made an educated guess that its a plugin for Blog:CMS. 😀
While I’m around, no one is going to create a WP plugin using GeSHi. There’s no need for duplicacy. There are still lot of other important issues to tackle, so the guys should spend their time in tackling one of them rather than duplicating my work. 😉
I suggest that you implement some sorta caching if you can: I’ve done that for the phpBB mod to experience huge speed increases.
phpBB doesn’t have a cacheing facility, so you had to implement the cacheing. But WordPress has an excellent plugin called Staticize by Matt. 😀 Now, you tell me, do I really have to duplicate work when there’s an excellent solution available? 😉
Sure phpBB has caching, it’s just not turned on by default 😉
Just make sure that calls to parse_code only happen when they *have* to (if your caching doesn’t do this already).
Well, I haven’t tried my plugin with Staticize but as far as I know, Staticize stores the final output, after all plugins & filters have been applied, in text files, so the next time it shows the content from text files, no filters are applied. But I’ll look into it. 😉
Perhaps you should suggest it as part of your mod, rather than re-doing it if it’s already done. Just a quick note, like “you may notice speed issues with this mod – use ths Staticize mod to resolve them” or similar.
Yep, that can be done. I’ll put it in the manual, though I haven’t myself tried out my plugin with Staticize. So I’ll try it out & then put it in the manual. 😀 😉