[CompInaBox-discuss] FloorCraft 0.1.2 released and bundled...

[Eric D N. <nie...@MI...>]

I released FloorCraft 0.1.2 last night.

Changelog:
- Added Ability to reorder sessions via a move up/down interface
- Improved the jar file to be double clickable on machines with Java 5.0 VM's as
default
- Fixed an event deletion bug
- Fixed a few loss of selection bugs

If you have played with FloorCraft, please let me know your feedback.  I'm
hoping to move out of "Pre-Alpha" and into "Alpha" status in another few
releases.  Following is my planned roadmap:

Version 0.1.3: (Funtionality)
-- set an actual (clock) time for the start of the day (done in CVS)
-- change the estimated size of an event.
-- all open bugs at bundling time

Version 0.1.4: (Interface Rafactoring)
Here's my list of minimal required UI improvements:
-- Collapse the double lists (Session and Event) to a tree view

Version 0.1.5: (Respond to some keyboard events)
-- Map the Menu "Deletes" to "del"/"backspace" key presses in the
tree view

Version 0.1.6: (Context Menus)
-- Context menus in the tree view for rename, change event size
-- Possible removal of said actions from main menu

Version 0.2.0 Alpha:
-- Fix some of the sizing and labeling issues of components.

Would you think at that point I can start asking some of my more
techno-friendly comp-organizers to play with it?

Things that I know I need soon, but maybe not before I let some
organizers play with it:
-- Style/dance filtering, suggested by Tuan (Ie in the Event creator dialog,
when you select Smooth, then non-smooth dances should disappear and the
remaining dances should be ordered in normal smooth dance order)

-- Expose selected "constants" for tweaking -- especially heat size, and awards
time (offer radio box selection for "Numbers only", "Numbers and Names",
"Number, Names, and Affiliations" with appropriate mappings into times)

-- Possibly convert the model dialog for Event Creation to modelless
for easier entry of multiple events -- need to make sure that a good feedback
channel is retained for indicating that the event has been added, so people
don't add like 50 copies of the same event...

-- Printing the schedule.

-- Event ordering -- currently it organizes by rounds, but within the rounds the
events are in arbitrary (normally insertion) order.  It doesn't know anything
about the ordering of levels or dances yet.

Eric