Re: Re-connecting

set a large section of disk aside for 'data' make a table of tthousands of
entries so you can never run out and asign each one a starting block number
and a size. search for a space big enough and record something there, free
the entry when it is deleted (data is still there so it can be recovered).
that should be an adequate enough file system. every time a change is made
you save the table out (how big should it be ... ?) you could give each one
a 'filetype' and write countless different programs for managing them and
filtering them in different ways. they should map to blocks and consectutive
disk sectors to make it fast and simple. 1000x faster than windows and in
kilobytes of code! you dont need folders or anything - do that kind of
organization stuff in other apps and store the orginization data in a file.
(because files don't ever move you can do this efficiently, index into it
rather than searching.)

5 words - name
1 word - type (w/ 'used' flag)
1 word - block/sector?
1 word - size
8 cells -> 32 bytes -> 10000 entries -> 320k
modern hard drives can store 320k in a split second.
back up the table to floppy now and then maybe?
overwritten file that is bigger than the original? make a new one and mark
the old one as freed. we have gigabytes to spare.


----- Original Message -----
From: "Mark Slicker" <[email protected]>
To: <[email protected]>
Sent: Tuesday, February 08, 2005 5:25 PM
Subject: Re: [colorforth] Re-connecting


> On Mon, 24 Jan 2005, Terry Loveall wrote:
>
> > The Explorer wannabe file manager has no cognate in colorForth so we
will just
> > pass on that for now. BTW Just how does one manage downloadable content,
web
> > pages, cache and hundreds of megabytes of email on colorForth?
> >
>
> One doesn't at present. If I extrapolate my experience with colorForth, I
> believe all Chuck's data (his chip designs, all colorForth code), fits
> within that first megabyte of space, so there is a 1:1 correspondence
> between the state of floppy and the first megabyte of memory. Sitting on
> the edge of the first megabyte are the stacks and floppy buffer on the
> interior and the dictionary space on the exterior. So actually Chuck uses
> less than megabyte, given my experience, probably a lot less.
>
> I think it is a reasonable assumtion, that all essential programs can
> fit in a relatively small finite ammount of space. Data is another story,
> emails individually are pretty small, when you have thousands this adds up
> to megabytes easily. And there is really no need to have every email in
> memory, memory can be better used at present. If you don't have the data
> in memory, that means it is on a disk or some permanent storage, and this
> implies some method of organization, perhaps with an indexing scheme for
> fast access.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> Main web page - http://www.colorforth.com
>
>