On 5 Feb 2000, Marcus Sundberg wrote:
> > So, you have contradict yourself. :)
>
> Huh? If you find two contradictory statements of mine in this thread
> you are welcome to show them to me.
No problem:
---------------------------------------------------------------------
Christoph Egger:
What do _you_ think what is the idea behind of the file-target?
Marcus Sundberg (1. contradictory statement):
The purpose of the file-target is to transparently render a LibGGI
application's output (=Image) to a file.
[...]
Marcus Sundberg (2. contradictory statement):
Image loading/writing should ideally be written as two libraries:
One library that does not use LibGGI and does not know about visuals.
It should dynamicly load readers/writers for different image formats,
and read images into/write imaghes from it's own simple structure
(basicly just width, height, format and a pointer to the data). It
should also be able to convert images between different formats.
The second library should be a simple glue-layer between the first
library an LibGGI. The reason to make two libraries that a generic
image loader/writer that is _not_ tied to any graphics/window system
is badly needed, and the first library will be just that.
---------------------------------------------------------------------
The contradictory is, you say in the first statement that render any
application's output, which is a Image, to a file, which is similar to
write it to a file, is the purpose of the file-target.
^^^^^
In the secondary statement you say, that Image loading _and_ _writing_
should be written as two libraries... ^^^^^^^
> > What do you think, how the application should render the output to
> > a file?
>
> If the application writer wants to create images and write them
> to disk he may use whatever method he likes. That's not what
> this thread is about.
I know, the RAW format is designed to use it to render any applications
output to fbdev devices. But couldn't it used to do that too?
> > Rendering to a file is the same as something save to a file,
> > isn't it?
>
> Not necessarily, but what has that got to do with anything?
> You are talking about making the file target read files, and I'm
> telling you it should not do that.
But why? I don't understand you, why it shouldn't do that?
Andrew has a good statement for this:
------------------------------------------------------------
Imagine this: one process using display-file to output (via mmap) a
constantly changing image to a file. Another process using
display-file to read that image (again via mmap) and displaying it.
There are no-doubt other ways of achieve the same thing, but could it
get any simpler (and more intuitive) than that ?
Cheers,
__
\/ Andrew Apted <[EMAIL PROTECTED]>
------------------------------------------------------------
Christoph Egger
E-Mail: [EMAIL PROTECTED]
