| From: | Jesse McClusky |
| Date: | 6 Sep 2000 at 03:28:38 |
| Subject: | Re: AMIOPEN: AmiPak |
> From: "Zoltan Hunt" <zhunt@newmedarc.com>
>
> Just a side point here, but didn't Fleecy say that the new
AmigaOS/DE/OE(?)
> wouldn't have any files?
Sort of.
> Instead there is a system of services. Now I'm not sure how exactly you
have
> a system without files, but I'm sure we'll find out.
I can explain a *little* bit. Basically, the idea is that the user should
not
be the one worrying about what filesystem(s) they are currently using, or
what limitations it/they has/have. They shouldn't have to worry about
where they stored something. Neither should the app programmer have
to worry about those things. The only people that should are the OE
coders.
I know I'm not giving you much, but that's the main idea behind it.
Taken at a higher level of abstraction, all a filesystem is is a way to
determine the difference between two files of the same name, and
for the human user to apply some sort of meaningful (to them)
conceptual ideas to one or more chunks of data. The user could
care less *how* exactly those are handled, and thus the app
programmer shouldn't have to care how those are handled, just
that they are.
Trust me, it does work how it's going to be implemented.
And it will cut a huge (or at least nice) chunk of development
time out for almost every piece of software written.
> What I'm thinking is that AmiPak might become a service, i.e. a
file-thingly
> comes along and it asks for something to decode it, there are several file
> processors around and AmiPak (which also handles .zip files I believe) is
> picked, it decodes and so on.
Something like that, yes. (:
I personally like to look at it more as "actions available for a type of
data".
That way there any program can "mix-and-match" at will, without having
to know or care about the details.
Jesse
Subscribe/Unsubscribe: open-request@amiga.com
Amiga FAQ: http://www.amiga.com/faq.html