On 11/2/2011 5:24 PM, Kieron Wilkinson wrote:
(Kieron replying to someone else)
The GUI was designed to be extremely easy to use, even
for
non-technical people such as those in libraries and archives. There
are advanced features, but they are mostly hidden unless specifically
wanted. I think it turned out pretty well, if I do say so myself. Some
examples:
http://www.softpres.org/kryoflux:ui:stream-plot
http://forum.kryoflux.com/viewtopic.php?f=2&t=262
As it happens, even though I wrote the graphical user interface, I
didn't need to know anything about how to talk to the hardware. The
GUI just uses the existing software supplied. Anyone could have done
it really.
Hi.
I find it interesting what different (fairly independently developed)
designs have in common for this type of job of reading floppies. ie, How
did other smarter-than-me people accomplish the same task? Was my
solution better or worse?
I built an open source(java client software) and open hardware (HDL
released) solution for reading amiga floppy disks, and it was(is?) a
whole lot of fun developing it. Learning both the amiga-specific stuff
and the technology stuff.
My blog is at
http://techtravels.org/amiga/amigablog/ which is ATM being
reworked(but completely online and available), again. I'm starting to
add some generic FPGA notes, examples, etc.
I played with a few different microcontroller designs (using a 50mhz
Parallax SX, which was really well suited to the task) and then
eventually a Xilinx FPGA approach.
When I saw your links above, they reminded me of my analysis of my amiga
floppy data on my posts here
http://techtravels.org/?p=362
and
http://techtravels.org/?p=263
These are obviously generated outside of my client software, but could
be integrated with a little work.
Based on the number of unique non-search-engine hits my blog has taken
over the years, there is a fair number of people who dabble in this
stuff. I get email every few months about a new project from someone
working on the task.
Your screen shots look pretty sweet.
Thanks
Keith