 |
See You at JavaOne
Posted by tball on May 12, 2006 at 11:53 AM | Comments (3)
It's been a crazy couple of months, but JavaOne waits for no engineer. Most of Jackpot's new UI has been implemented and was pushed yesterday. This spec required fundamental changes in the transformation engine, which I think strengthened its design even though it impacted the schedule. It's also more Swing form coding that I have done in a long time, but thanks to Matisse I just made the JavaOne milestone.
If you are interested in Jackpot, there will be an announcement regarding it at NetBeans Day. Thursday morning I'll be presenting Creating and Deploying Custom Jackpot Queries and Transformers (TS-1278), which will describe how developers can create their own bug-searching and fixing tools and share them with others or deploy them within an engineering organization. Friday, there will be a short Jackpot demo at James Gosling's keynote. (Looking up the URL, I just found out Scott McNealy will be hosting that keynote, too. I better "kick butt", as he likes to say, during the demo!)
If you are attending JavaOne, please check out these "Jackpot sightings" if you can. If you see me rushing down the hall, join the rush and introduce yourself.
Bookmark blog post:  del.icio.us  Digg  DZone  Furl  Reddit
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
I really like the notion of Jackpot, especially the matching language for specifying source transformations. However, I'm not keen on the requirement to use NetBeans, specifically, I'd think that all such tools are inherently (or at least can be) command line tools. Is there something about Jackpot that requires a GUI?
Posted by: thalliley on July 05, 2006 at 05:57 AM
-
Jackpot needs to know specifics about the project(s), such as what their source paths are and what Java language version they compile with. Its UI uses many NetBeans components and services, which would have to be duplicated otherwise. Things such as undo/redo, preview, and individual change selection aren't possible from the command-line.
Posted by: tball on July 05, 2006 at 08:01 AM
-
Source paths, Java language version, etc. are easily passed in on the command line. I agree that undo/redo and change selection aren't possible on the command line, but preview is, as well as some notion of "level of change", for example, make all changes from a certain category.
The output of a command-line version of Jackpot could be new source files that do not replace the old ones. Rather, the user could use diffing tools and/or a Jackpot log file to understand which transformations were performed.
If you're using different sets of rulesets, then perhaps some rulesets are "safe" and could be applied in order to replace the existing source, whereas other rulesets require human intervention to accept/reject the change. Such behavior could also be command-line driven.
Is Jackpot open source?
Posted by: thalliley on July 07, 2006 at 05:24 AM
|
java.net RSS Feeds
