Just to fill you in – this blog is by no means dead, I just haven’t had the time to write up new updates, especially now that I’ve given my notice of resignation. Had a few major disputes with management, but I should get things straightened out within a week or two.
In the meantime, I’ve updated the Wideimage project code, so now the unsharp filter actually works. We’ve moved the code base to Sourceforge due to some problems we’ve had with Google Code hosting, so you should update your SVN checkouts to the new location, since this is where we’ll commit any new changes to the Wideimage codebase.
Anyways, wish me luck.
There’s a WideImage wiki at http://wideimage.sourceforge.net/.
Well, not a very good turnout, but still, here are the results:
- Proof of concept – 50%
- Work in progress – 25%
- Advanced topics – 25%
And yes, sadly, those numbers are accurate. And yes, they do add up exactly. And yes, 4 of you voted.
But it does give me a slight hint about what to write about, so I’ll try and focus more on those points in the future.
Sorry for the constant back-and-forth switching between Wordpress themes, but it seems that whenever I find a suitable theme that has a variable width for displaying long lines of code, it invariantly breaks one of the plugins or Google Analytics acts up.
In any case, don’t worry, all the content’s still there.
Well, until I’ve resolved some issues regarding the code highlighting plugin, I’ve decided to present you with a quick poll on just what topics I should tackle on this blog.
Whether it be Symfony specifics, like manipulating requests and responses, internals and other whatnots or just writing about cool new ways on how to use Symfony, take your pick!
Plus, I’ve got a brand new project in the pipeline that I’ll blog about as events unroll – the project itself will be a free online service, complete with all the accompanying Web 2.0 buzzwords.
Finally found a plugin that’s made to work with Markdown in WordPress – link.
Just have to wait for the admins to install the thing.
UPDATE: Seems there’s a problem with the included PEAR class package – Text/Highlighter, which is used for code highlighting, is an old version and written for PHP4, and if you don’t have PEAR included in your path somewhere, it fails when it tries to pull in
PEAR.php. Says it works for PHP4 and 5, but still, have to figure out just what it needs from
Well, it’s seems there’s no way around the double html entity escaping in WordPress MU with Markdown Extra, which makes posting any kind of code containing HTML entities a nightmare.
I’m looking for a solution to get around this weird behaviour, but I’m stumped as to just what to do. In the meantime, I’ll be posting PHP code using the
[?php ?] tags to get around the dissapearing markup problem, but object-related stuff (like ->) are still likely to show up as literal html codes.
One way I was thinking of circumventing this problem is to have my code hosted elsewhere, then display it using CodePress. Although it’s primarily a code editor, it might get around some of the shortcomings and provide code highlighting for code examples.