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
Includes some simple Japanese localization.
Update: Recieved a request last week to update the broken uninstaller. Link above updated as of September 2008.
mootools is a spectacular little JavaScript framework, but the “tricks of the trade” you need to know to get anything done with it on a timely basis can be a bit maddening. Here are three examples:
getElementsByClassName(), but seemingly no more in v1.11. Looking ahead at subversion, lots of API changes seem to be coming down the pipe.Window.DomReady as well as Element.Selectors and it’s dependencies. (To complicate matters, Element.Selectors seems to have become a stand-alone Selectors class.)<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
If not, the accordion will not collapse properly, leaving lower panels filled with vast tracts of dead space, and you with a rising stress level, and even less hair, and all because you can’t, for the freaking life of you, figure out what is different between your freaking code, and the virtually identical freaking stuff on the freaking mootools site and in the end it turns out it’s just a freaking missing freaking doctype.
(I guess IE won’t fork over DOM support unless once declares the doctype.)
So, overall, great little JavaScript framework. But.. Freaky.