> "R. Alan Monroe" wrote
>> Neither of these seem like they'd scale very well (say, up to the
>> resolution of your screen, with one block per pixel). The end goal
>> is
>> just a basic do-nothing light show that simulates
>> fragmentation/defragmentation as eye candy.
> For that purpose the
"R. Alan Monroe" wrote
I was just going to start with, say, 16 or 64 "blocks", then
randomly
add and delete ficticious "files"
1. Is there some more clever way of tracking this than the very
naive
approach:
toc = {
A: [0, 1, 2],
D: [3, 4, 5, 9, 10],
C: [6, 7, 8]
} ?
Obviously yes, th
I'm trying to mentally plan out the most bare bones drive simulation
possible, but I have this nagging feeling that I'm missing something.
I was just going to start with, say, 16 or 64 "blocks", then randomly
add and delete ficticious "files" (which won't have any actual
content - I'm just trying t
