I haven't played with it yet but Epictetus looks like a competent Java based database explorer. It is built on the Netbeans platform, but you don't need Netbeans to run it. Note though it is still early days for this application.
Why the mention? Well, I went and looked at the fuzzy little video there. No strange voice talking over it. Just MC Hammer's Can't Touch This... I was off looking for my big trousers in seconds.
Saturday, May 31, 2008
Thursday, May 22, 2008
A thought... Annotated licenses....
When mixing code libraries together, wouldn't it be neat to be able to enumerate all the licenses that applied to the code base.
How about an @License annotation?
@License(name="MyNeatLibrary",type="BSD",author="Blah Blah Inc")
@License(name="IrregularExpression Library",type="CCattrib",attrib="Fred Flintstone",attribemail="fred@example.com",attriburl="http://example.com")
At run time, the "About" dialog then scans the code base for the annotations, which would be set to runtime persist, and then display about information based on what is actually used.
It wouldn't attempt to enforce the licenses, but would allow for automatic visibility of licenses.
Of course, this would have to be done in some coordinated way to standardise the types and attributes, but it has some potential... just as long as we don't end up with per-method licenses.
[ This thought caused by following Matt Gemmell on Twitter ]
How about an @License annotation?
@License(name="MyNeatLibrary",type="BSD",author="Blah Blah Inc")
@License(name="IrregularExpression Library",type="CCattrib",attrib="Fred Flintstone",attribemail="fred@example.com",attriburl="http://example.com")
At run time, the "About" dialog then scans the code base for the annotations, which would be set to runtime persist, and then display about information based on what is actually used.
It wouldn't attempt to enforce the licenses, but would allow for automatic visibility of licenses.
Of course, this would have to be done in some coordinated way to standardise the types and attributes, but it has some potential... just as long as we don't end up with per-method licenses.
[ This thought caused by following Matt Gemmell on Twitter ]
Monday, May 05, 2008
Finally, an end of Time (and Date)
Top of the list of things that any Java developer can agree, sucks like a sucky thing from suckington, suckania, it's Date and Time. These have never got better, and like a scab have been picked at with no healing up. Well now there's JSR 310... and here's an interview at Java Lobby with the JSR leaders.
Subscribe to:
Posts (Atom)