KryoFlux GUI - How does it look?

All news about KryoFlux go here.
User avatar
mr.vince
Posts: 2125
Joined: Tue Oct 05, 2010 5:48 pm

Re: KryoFlux GUI - How does it look?

Post by mr.vince »

Very nice! And look... it's running on a Mac, too!

User avatar
Malvineous
Posts: 156
Joined: Sun Oct 31, 2010 10:57 pm
Location: Brisbane, Australia
Contact:

Re: KryoFlux GUI - How does it look?

Post by Malvineous »

Looks fancy! A couple of questions/suggestions:

Can you perform calibration/testing through the GUI? (dtc -c1 and -c2)

Are you able to adjust all the parameters that dtc has? If, for example you want to override something to create a sort of custom disk format. If so, can you save these for easy future access, or is the idea to post here to get them added to the GUI/dtc, so everyone knows there's a new format?

Perhaps instead of "MFM sector image" you could put something like "MFM sector image (standard PC floppy)" just to make it that bit easier on those less familiar with all the formats. Out of curiosity, are these formats hard coded or are you reading them from dtc's help output? Just wondering whether you would need an updated GUI to go with an updated dtc if more disk formats were added.

With the coloured squares, I take it green means successfully read, perhaps there is a red for failure, and does grey mean unformatted? It might be good to add another colour (if you haven't already) for 'inaccessible', which could be used to colour tracks that can't be reached (e.g. tracks 82 and 83 on a maxtrack=81 drive.) Perhaps a square with lines through it or something. This would also make it very clear that you may not be dumping the whole disk.

Might also be nice to have a tooltip appear when you hover over each square to tell you what the colour means, especially to explain why your drive can't access tracks past its maxtrack.

One last suggestion - it might be nice to monitor how long it's taking to read each track and average it out to give an estimated number of minutes+seconds until completion.

User avatar
karadoc
Posts: 139
Joined: Sun Oct 31, 2010 9:12 pm

Re: KryoFlux GUI - How does it look?

Post by karadoc »

Firstly, thanks for your feedback!

Yes, you definitely will be able to do calibration through the UI, but we've not added that yet.

As to your other questions, maybe the "image profile" configuration screen will help explain a few things:
Screen shot 2010-11-27 at 23.13.18.png
Screen shot 2010-11-27 at 23.13.18.png (88.54 KiB) Viewed 5228 times
The basic concept is this:
1) At startup, the UI runs DTC to find out all the "image types" supported, as you suspected.
2) It then (if you don't have anything else configured) initialises your starting set of "image profiles" (shown above).
3) You can then add/copy/rename image profiles, where you can give them a custom name and associate them with an image type, you either keep the defaults or can customise them.
4) The drop-down you see on the main screen is for the configured image profiles, not the image types.

So an "image type" is the code you specify with DTC with the -i switch, and an "image profile" is a bunch of settings that correspond to a set of DTC parameters, including the image type, and a user-configured name - we just generate the initial default set.

Colours: Yes, green is good, red is bad, grey is unformatted, blue is currently being dumped, and white is tracks that have not been dumped yet. There may also be other colours soon, to correspond with flags you occasionally see in DTC output where, for example, DTC found extra data that cannot be represented by the selected sector image, or various other conditions (these flags are not done yet, but are pretty simple to add). And indeed, we intended to do exactly as you suggest - giving more information (including what the colour means) on a track when you hover over it.

Estimated completion time - that is a great idea, we'll do that, thanks.

loedown
Posts: 5
Joined: Sun Nov 28, 2010 11:28 am

Re: KryoFlux GUI - How does it look?

Post by loedown »

Information is good, the more the better with options for turning off the stuff you don't want to see.

I haven't played with DTC yet because I have grand plans for my Kryoflux. I like the idea of autonumbering for auto dumps and perhaps the ability to be able to read disk names off the disks directly?

loedown
Posts: 5
Joined: Sun Nov 28, 2010 11:28 am

Re: KryoFlux GUI - How does it look?

Post by loedown »

Malvineous wrote:Are you able to adjust all the parameters that dtc has? If, for example you want to override something to create a sort of custom disk format. If so, can you save these for easy future access, or is the idea to post here to get them added to the GUI/dtc, so everyone knows there's a new format?
Template is the word you are looking for ;)

User avatar
karadoc
Posts: 139
Joined: Sun Oct 31, 2010 9:12 pm

Re: KryoFlux GUI - How does it look?

Post by karadoc »

I am keen on having stuff turned stuff off that you don't need. The interface is intended to be suitable for non-technical librarians and archivists to use, so the "default" view should definitely be as simple as possible.

Getting disk name sounds neat. If anyone wants to code that up for us (in Java or Scala), feel free and we can get that in earlier than we would find the time for...

Auto-numbering: Is that so you can do a big batch and process them later? We were thinking of letting people enter meta-data *while* the dumping is being done, does that remove the need for auto-numbering?

Thanks for the feedback!

User avatar
karadoc
Posts: 139
Joined: Sun Oct 31, 2010 9:12 pm

Re: KryoFlux GUI - How does it look?

Post by karadoc »

As per the announcement in this post:
viewtopic.php?f=2&t=72#p502

The relavent package is here: http://releases.softpres.org/kryoflux/DTC_1.0b10.zip
Or the full package with driver is here: http://releases.softpres.org/kryoflux/k ... 1.0b10.zip

Please post any problems or suggestions in this thread.

We've started small in this version of the GUI. We'd rather get it out for you sooner and have a small set of features than you have to wait longer for it. We have lots of plans though, so if you have suggestions, we would be very pleased to hear them.

It's also worth noting than the UI has been designed for libraries and archives, for people who are not so familiar with the technical details. We will be adding more advanced features, but they are likely to be hidden by default (it will of course remember your chosen view).

It's still rather experimental at the moment, and has only been tested on a few machines. It currently works with 32 and 64-bit Linux (thanks to Adam Nielsen for the DTC port) and Windows (other platforms are pending), so any feedback is appreciated.

To use, simply make sure you have the latest version of Java (java.com), download the UI package, and just double-click on the JAR file.

tect
Posts: 33
Joined: Thu Nov 04, 2010 7:58 pm

Re: KryoFlux GUI - How does it look?

Post by tect »

Great work!!!

Thanks a lot for this nice Christmas present! The GUI looks and works very good already and is really simple to use! :D

As already suggested here, more dumping information would be helpful in a future release, especially if write support will be implemented: for example for dumping Amiga disks, dtc should indicate tracks in wich weak bit or longtrack protection is used. Then you know that a special test of the written disk (or far more in the future: the dumped ipf file) is necessary.

Regarding "mass dumping": Inserting the meta data while dumping is a great thing, I think you shoud give it a try.
But for dumping software with multiple disks it would be good to have an option to autonumber dump files while keeping the rest of the meta data fo all disks identical.
Also an option to flag dumps with errors would be good (for example a starting _ERR_<filename>) and to list the damaged tracks in the meta data or in a text file. But all this is luxury ;)

User avatar
karadoc
Posts: 139
Joined: Sun Oct 31, 2010 9:12 pm

Re: KryoFlux GUI - How does it look?

Post by karadoc »

Excellent. Thanks for the feedback.

Giving more information - on reading, indicating things like weak bits and such on dumping requires analysation and some grunt work, and I am not sure we can easily do that, as we would have to do some analysis on the fly. We are planning to add density and timing distribution charts, so you will be able to see some more information like that though. For writing, it should be possible, as the analysation has already been done - we'll look into that. We certainly need to show more information about the different sorts of errors that can happen (e.g. format verification failed, format was fine but sector image cannot represent that configuration, etc.), and that is certainly on the plan - currently it just groups them by severity shows it as a colour (green - good, yellow - non-serious or wrong parameters used, red - bad data).

Metadata. Yes, we have some good plans on that. We're hoping to allow people to define their own template (needed by libraries and archives, who have their own standards), and we at SPS have our own too of course. We'll take that template and use it to generate the user interface fields. As you say, it would be nice to allow people to fill this in as the disk is being imaged.

Auto-numbering sounds neat. I also like the point about keeping the metadata around for a number of disks. We'll have to think about how that is going to work, I'm sure we can find a way of dealing with "collections" in a nice way.

Naming the file as bad is an excellent idea, as is listing the bad tracks in the metadata file... We'll definitely do that. Lots of things to do of course, so I can't say how long it will take to work all this out...

Post Reply