storing images thumbnails as pseudo files?

storing images thumbnails as pseudo files?

[Pysiak Satriani]

Hello,

suppose pseudo files, file-as-directory are on my r4 partition and are usuable.

Does namesys' vision allow things like storing image thumbnails "inside the file
itself" ?

Example using jpgtn (jpgtn creates thumbnails of jpg files)

// create 150px thumbnail
$ jpgtn -s 150 -H test.jpg

// move the thumbnail "into" the file
$ mv tn_test test.jpg/thumbs/150px

// the same but a 100px thumbnail
$ jpgtn -s 100 -H test.jpg
$ mv tn_test test.jpg/thumbs/100px

Then I could write HTML code like this:

<a href="test.jpg"><img src="test.jpg/thumbs/150px" /></a>

This idea came to me because of a project that has to create many thumbnails
for many files. That requires to make a naming scheme, parse filenames and
don't make one mistake. If I could do things this way it would be much
easier and elegant to do.

But that's just an idea from someone not really knowledgible enough in
the area.

Best regards,
Maciej Soltysiak

Re: storing images thumbnails as pseudo files?

[David Masover]

Pysiak Satriani wrote:
> Hello,
> 
> suppose pseudo files, file-as-directory are on my r4 partition and are usuable.
> 
> Does namesys' vision allow things like storing image thumbnails "inside the file
> itself" ?

Ultimately, yes.  Currently, I don't know.

The most common use of pseudofiles, for instance, is to access metadata 
we already have.  For instance, Reiser4 stores file permissions the same 
way as anyone else, but you can access foo/..pseudo/rwx.

That's an example.  I haven't been in this community for a year or more, 
so I have no idea what the delimiter is.

For now, I don't think you can have arbitrary normal files within files, 
just metadata that has a plugin already.  You might try something like 
this, though:


$ mkdir -p .thumbs/test.jpg

// create 150px thumbnail
$ jpgtn -s 150 -H test.jpg

// move the thumbnail "into" the file
$ mv tn_test .thumbs/test.jpg/150px

// the same but a 100px thumbnail
$ jpgtn -s 100 -H test.jpg
$ mv tn_test .thumbs/test.jpg/100px


Ultimately, the Namesys vision would allow for something like this to 
happen:

$ cp /mnt/camera/test.jpg .

Then your link would look something like this:

<a href="test.jpg"><img src="test.jpg/.../thumbs/150px.png" /></a>

The thumbnail would be generated by the FS (probably by calling jpgtn or 
a similar tool) the first time it was accessed, then cached until disk 
space is needed for something else.

The rest of the kernel development list seems to believe that such 
functionality would be better achieved by hacking glibc or Apache to 
emulate that, rather than having it be a feature of the filesystem itself.

Disclaimer:  I don't speak for Namesys, and I don't work here.  While 
I'm pretty confident I understand their vision, the final word on 
anything Reiser is always from Hans Reiser.

Re: storing images thumbnails as pseudo files?

[Hans Reiser]

David Masover wrote:

> Disclaimer:  I don't speak for Namesys, and I don't work here.  While
> I'm pretty confident I understand their vision, the final word on
> anything Reiser is always from Hans Reiser.

David described my views pretty well, and saved me much typing.:)

Re: storing images thumbnails as pseudo files?

[Pysiak Satriani]

Hello Hans,

Saturday, July 22, 2006, 2:46:55 AM, you wrote:

> David Masover wrote:

>> Disclaimer:  I don't speak for Namesys, and I don't work here.  While
>> I'm pretty confident I understand their vision, the final word on
>> anything Reiser is always from Hans Reiser.

> David described my views pretty well, and saved me much typing.:)
:-) Hehe. David, Hans, thanks for your answers.
Now I'm really looking forward to r4.

--
Maciek

Re: storing images thumbnails as pseudo files?

[Hans Reiser]

Pysiak Satriani wrote:

>Hello,
>
>suppose pseudo files, file-as-directory are on my r4 partition and are usuable.
>
>Does namesys' vision allow things like storing image thumbnails "inside the file
>itself" ?
>
>Example using jpgtn (jpgtn creates thumbnails of jpg files)
>
>// create 150px thumbnail
>$ jpgtn -s 150 -H test.jpg
>
>// move the thumbnail "into" the file
>$ mv tn_test test.jpg/thumbs/150px
>
>// the same but a 100px thumbnail
>$ jpgtn -s 100 -H test.jpg
>$ mv tn_test test.jpg/thumbs/100px
>
>Then I could write HTML code like this:
>
><a href="test.jpg"><img src="test.jpg/thumbs/150px" /></a>
>
>This idea came to me because of a project that has to create many thumbnails
>for many files. That requires to make a naming scheme, parse filenames and
>don't make one mistake. If I could do things this way it would be much
>easier and elegant to do.
>
>But that's just an idea from someone not really knowledgible enough in
>the area.
>
>Best regards,
>Maciej Soltysiak
>
>
>
>
>  
>
What you describe is the vision we are trying for.