What the.. This is annoying. And all I wanted to do was write a hack to see my AdSense pittance from within WordPress.
BlackBerry Simulator mysteriously dying every time you try to fire it up on Vista? Same here. It’s a good thing I’ve become a compulsive reader of release notes. From the the latest JDE 4.6.0 docs:
If you install the BlackBerry® Java® Development Environment on a computer with Windows Vista™, if Use Account Control is turned on, launching the BlackBerry® Smartphone simulator might produce error messages and the simulator might not start.
Read: Simulator will definitely not start. And of course they mean User Access Control. How-To Geek has an easy way to kill UAC here.
Mika Tuupola has come up with an elegant logging mechanism that has already found its way into the official PEAR::Log package.
It’s a snap to use. Simply instantiate a “Firebug” log as such:
$log = &Log::singleton('firebug', '', 'PHP', array('buffering' => true), PEAR_LOG_DEBUG);
Output will then go to your Firebug console window:
$log->log('Debug lorem ipsum.', PEAR_LOG_DEBUG);
$log->log('Info wisi enim ad minim veniam', PEAR_LOG_INFO);
$log->log('Warning est usus legentis in', PEAR_LOG_WARNING);
$log->log('Error est notare quam', PEAR_LOG_ERR);
To split output to both the default error log as well as the Firebug console, build a “composite” log:
$log = &Log::singleton('composite');
$logFile =& parent::singleton('error_log', PEAR_LOG_TYPE_SYSTEM, 'to error log', array(), PEAR_LOG_DEBUG);
$logFire =& parent::singleton(’firebug’, ”, ‘to firebug’, array(’buffering’=>true), PEAR_LOG_DEBUG);
$log->addChild($logFile);
$log->addChild($logFire);
I was surprised to receive a support request last week for the Mantis State Plugin. Given that the thing wouldn’t allow itself to be uninstalled, I figured it was time to release an update.
Version 0.0.4 includes clearer severity output, issue details on mouseover, and an attempt to better visualize date ranges within the state matrix.
Oh, and it can now be uninstalled.
It’s an Emacs weekend here at blog.arithm.
I was recently asked if it was possible to do remote PHP debugging with Emacs. We’re talking about Emacs, so the answer is: Of course! How to do it:
debugclient somewhere in your path. (Here Emacs is running on Windows, so I just threw it into the C:\WINDOWS\ directory.) Make sure the executable is named “debugclient” and not “debugclient-0.9.0″ or whatever.Now, assuming you already have xdebug plugged into PHP, modify php.ini or an .htaccess file with the following settings:
xdebug.remote_enable = true xdebug.remote_handler = dbgp xdebug.remote_host = your_client_ipFor security reasons it’s wiser to do this via .htaccess on directories that permit only authenticated access.
To debug, ask Emacs to listen for connections by going into GEBEN Mode with Meta-x geben. You should see “xdebug started.” in the status row at the bottom of the Emacs window.
Run your PHP script with the xdebug switch on, eg.
http://www.example.com/script.php?XDEBUG_SESSION_START
If everything is setup correctly, Emacs will load the source of script.php (be wary of security!) and allow you to step through the code.
Available commands are:
spc step into/step over
i step into
o step over
r step out
b set a breakpoint at a line
u unset a breakpoint at a line
g run
q stop
Some gotchas: I’ve noticed the GEBEN expects the first keystroke to be “space”; often it will freeze otherwise. GEBEN may also run into problems on certain session-related PHP commands.
Happy debugging!
Despite all the nice things I said about TOAD last year, I thought I should mention that I find myself still using DBVisualizer almost exclusively.
Although TOAD has some really powerful features, DBVisualizer is just so easy to use.. that it’s a difficult habit to break.
I couldn’t seem to find a good breakdown on this anywhere and had to see what would happen trial and error.
readonly="1" will show a standard form element, however it will not be editable. Data will, however, be submitted.disabled="1" will gray-out the form element. Data will not be submitted with the rest of the form.At least, this is what Firefox does.
More notes to self.
Fancy shmancy init scripts aside, this is the fastest way to get a Subversion server up and running:
/usr/bin/svnserve --daemon --root /var/svn
root is the directory housing one’s repositories; looks something like this:
/var/svn/
conf/
project1/
project2/
repos/
Make sure the svn port 3690 is open.
This is one of those things I have to do once every so often and that I can never freaking remember how to do.
# svnadmin create /path/to/repositoryname
$ svn import /tmp/project svn://url.com/repositoryname -m "initial freaking import"
$ svn checkout svn://url.com/repositoryname
That’s it! See the Quick Start in the online book if you need to mess around with branches and tags and the like.
For the longest time now I’ve wanted a view in Mantis that could show me, at a glance, what’s receiving attention and what’s falling through the cracks.
Vincent Debout has recently released an excellent plugin manager for Mantis; so I’ve attempted to whip something up. The Mantis State plugin contains a matrix view listing out issues in left-to-right, top-to-bottom in order of last update. Font size indicates priority. Blinking issues are severe.
Right now this probably works well for smaller projects, but could get difficult to view with a large number of issues. Would be nice if Mantis’ current filtering system could plug into this.
You can see from this sample view that one of our projects has a number of items reported sometime back that are not getting looked at. Oops.
If you’d like to test it out, feel free to download an early alpha version here: Mantis State Plugin (6.21 KB)
Includes some simple Japanese localization.
Update: Recieved a request last week to update the broken uninstaller. Link above updated as of September 2008.
online
