My Java port of it is probably 1/2 weeks away from being "done" - as in, ready to release, unless I get a large amount of spare time in the next few days.prawndiddy wrote:I don't know how far along the efforts to recreate/port the randomizer are, or even how many different people are poking at it, but there's one thing I think would be really handy.
Would it be possible to recreate the XML hierarchy structure in the list of rounds within the application? What I'm envisioning is more of a collapsible tree than the current video listing. The other half of this is to use a checkbox type of interface instead of the "create your own" list. Checking a video header would check/uncheck toggle all rounds in that video, and then expanding the video would allow checking/unchecking specific rounds. Instead of the list of numbers being directly visible in the app to create a special playlist, it could import/export the checklist using the same notation. It would also make it easier to exclude a few videos that the user doesn't want, instead of having to build up from zero. Blacklist vs Whitelist, so to speak.
It probably sounds like a lot of work, but I have a feeling that most of the hard stuff is done already by reading in the XML anyway, and displaying/interfacing it the way I'm describing might not take more than a few hours with the proper forms/objects.
Eh? Thoughts?
Having a whitelist/blacklist approach to the XML is a pretty good idea, I do this myself just by keeping a folder of videos I don't want in my randomiser.
Right now, I have each videos known filenames + all rounds associated with each video. By creating a second CHDB(whitelist/blacklist) file I could probably use that DB to include / exclude the rounds you wanted. It should be do-able with a relatively minor change to the XML processing system.
If you've any other "feature" requests/suggestions post them here.
