The Specification numbers of specs created via Java Community Process: Java Specification Request, AKA JCP JSR or just JSR, are often hard to remember.
A nice description of communication problems arising from this can be found in this post in blog of Adriaan Bloem:
I’ve recently had several conversations that went something like this. A vendor told me, “we’ve added JSR-186 support,” (confusing it with JSR-168, which is not uncommon). So I replied, “you mean the JCR?” (guessing they may have meant JSR-170. ) To which they said “yes, the JSR.”
[mvmn remark: JSR-170 is Content Repository for Java, AKA Java Content Repository or JCR]
So I’ve decided to actually make a complete JSR “cheatsheet”, featuring current state of list of JSRs from JCP site.
The form of implementation was chosen as HTML/JS, “packed” as Mac OS Dashboard Widget (although it can be opened in browser as usual HTML page) – I had some free time and wanted to finally try making a dashboard widget.
And here it is: bundled and source code. And I guess you’ve noticed already the screenshot at the beginning of the post.
The widget doesn’t look very “hot” for now, and doesn’t resize, which is not very good, but it’s a very first try, so be forgiving. I might improve it in future in case somebody finds it useful (and is too lazy to fix things [him/her]self (-: ).
And a small lesson learned about widget making: the OS X Property List Editor
sucks? is tricky – when creating with it Width and Height properties in Info.plist file for your widget you might find that they don’t take effect and widget has default size. The cause of this in my case was that Property List Editor created values for those properties with type String, but they are expected to be Integer.
So open your Info.plist in text or XML editor, and if you see something like:
be sure to change it to
(and same for Width, of course).
UPD: Known issue – clicking on ">>" external links (they lead to JSR website) closes the widget )-: , but doesn’t open the browser for linked page \-: /-: .