The reality is that we like to speak, walk, run around, and play with code. It’s our paintbrush, tinker toy, classical instrument, and pen. It can do things that people can take for granite or widen peoples’ eyes.

We all need to respect the programmer and give him/her a pat on the back. A raise might be nice too ;)

Yes, it’s true, we develop for ourselves, some more than others. If we want to build a god damn game engine for a calculator, by damn we will. You can’t stop us!

A toast for the digital poets!

I started off using google’s system, but found it too cumbersome. I shot straight through three more plugins tonight and found they also have strange issues. This last one I’m working with today has found all the problems I have had and made it nice to use, besides one large issue with the WordPress TinyMCE Editor.

The winner is
CodeViewer by elasticdog – http://elasticdog.com/2004/09/code-viewer/

Below is a Test Program – this is a C program and you download here to it:

1. #include <stdio.h>
2. #include <stdlib.h>
3.  
4. void main() {
5. return;
6. }
7. Download this code: test.c

I found that formatting is more important than the actual syntax highlighting. So what I’m doing is using CodeViewer for the display and will use a child extension for doing actual syntax highlighting.

GeSHi has given a wonderful attempt at writing a variable syntax highlighter. It works while in chunk-based highlighting too. GeSHi is a O(n) based parser for syntax highlighting, yet it works pretty quickly as it keeps its use of substr and preg_replace at a minimum where doing character based descent to speed up the system.

I’ve partially implemented GeSHi for line-based highlighting inside CodeViewer. You can download and compliment your wordpress installation by grabbing this tarball – Code Viewer with GeSHi Support.

To write a proper geshi supported tag, you must use the lang attribute.

1. <viewcode src="cv_geshi_example.html" lang="html" />

If you would like to see the changes I’ve made to the plugin, please see this diff below:

1. --- code-viewer.txt     Mon Aug 29 07:08:37 2005
2. +++ code-viewer.php     Sun Nov 18 09:33:15 2007
3. @@ -9,14 +9,15 @@
4. */
5.  
6. /* Configuration Settings */
7. -$default_path = "http://elasticdog.com/code/";  // the absolute path of your code folder
8. +$default_path = "http://{$_SERVER['HTTP_HOST']}/code/";  // the absolute path of your code folder
9.  
10. /* --- STOP EDITING ---  */
11. +require_once('geshi/geshi.php');
12.  
13. function code_viewer($text) {
14. global $default_path;
15.  
16. -       $count = preg_match_all('/<viewcode src="([^"]+)"(?: link="(?i:(yes|no))")?\s?\/>/', $text, $matches);
17. +       $count = preg_match_all('/<viewcode src="([^"]+)"(?: link="(?i:(yes|no))")?(?: lang="(?i:([a-z]+))")?\s?\/>/', $text, $matches);
18.  
19. for ($i = 0; $i < $count; $i++) {
20. // Determine if the specified path is absolute, or relative to the root path
21. @@ -29,6 +30,9 @@
22. $path = $default_path . $matches[1][$i];
23. }
24.  
25. +                if(strtolower($matches[3][$i]) != "") {
26. +                  $language = $matches[3][$i];
27. +                }
28. // Open the file
29. // If the file can't be found, print an error message
30. if ($lines = @file($path)) {
31. @@ -44,8 +48,11 @@
32. } else {
33. $numtabs = strlen($line) - strlen(ltrim($line));  // determine the number of tabs
34. $line = trim($line);                              // trim leading/trailing whitespace
35. -
36. -                                       $codelist .= "\t" . '<li class="tab' . $numtabs . ' ' . $toggle . '"><code>' . htmlspecialchars($line) . '</code></li>' . "\n";
37. +                                        if(isset($language)) {
38. +                                          $codelist .= "\t" . '<li class="tab' . $numtabs . ' ' . $toggle . '"><code>' . geshi_highlight($line, $language, null, true) . '</code></li>' . "\n";
39. +                                        } else {
40. +                                          $codelist .= "\t" . '<li class="tab' . $numtabs . ' ' . $toggle . '"><code>' . htmlspecialchars($line) . '</code></li>' . "\n";
41. +                                        }
42. }
43. }
44.  
45. @@ -76,4 +83,4 @@
46.  
47. add_filter('the_content', 'code_viewer', 9);
48. add_filter('the_content', 'fix_bad_p');
49. -?>
50. \ No newline at end of file
51. +?>
52. Download this code: code-viewer_geshi.diff


foreach($bastards as $retard) {
$life->addFailuresIQRates($retard->get("iq_test_scores"));
}


About ~six weeks ago we decided to expand our datacenter to a San Jose location. Mae West is our new location for current and future servers at the Blackacid Community Colocation Project(BCCP). It just so happened to be the same weekend as SHDH18. Never had a better time with a bunch of geeks and some of these guys know how to pound a beer. If you are in the bay area and you haven’t heard about this event, you are really missing out. I’m still living in Phoenix these days so its not an easy event to make. We hope to set one up in Phoenix if it appears to be a tough habit. If anyone has interest in helping out with such an event, please email me. Adios!

So whats under my dev-blurb for the last 24 hours you ask?

I loaded up FreeBSD-6.0 Release on my HP zv5410us – thanks to cokane for the help he pointed me to at defcon last year! =)

Looks like I got this blog properly working and running under my hackish design of four cols =D

I accomplished a series of annoying builds, builds, and rebuilds till I had an outcome of a
full homebrew psp development toolchain setup… not very difficult to make oopo’s script to work properly under freebsd. If you can’t figure it out, well email me or join #pspdev on freenode.

Looks great, feels great, the psp that is. I wrote a couple tests for the 1.0 psp that work as predicted ;) Simple text-based output and shapes, nothing special. I’ll try some algorithms in a bit and try out the pad!

Getting sleepy, but more stuff to do!
]]> http://blogs.blackacid.org/2006/03/31/busy-busy-and-busy/feed/ 0