FreeLists / openbeosstorage / [openbeosstorage] Re: More stuff to implement [was: Re: latestupdate]

[Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>]

On Mon, 29 Apr 2002, Ingo Weinhold wrote:

> Oh, I forgot to mention, the other day, when I took a look in the BeBook,
> I encountered BAppInfo. It's not listed anywhere, is it?

This should read BAppFileInfo.

I'm afraid there are some other things that we will have to implement:

* class BResourceStrings

* functions declared in Alias.h:

  - resolve_link(): Certainly traverses symbolic links.
    I guess, to implement it some code from BEntry::set() can be moved.
    But I'm unsure about the boolean `block' argument. Any ideas?

  - read/write_alias(): Also have a `block' parameter. But I don't even
    know what these function are for at all. Something about symbolic
    links?

ResourceStrings.h and Alias.h are the only "new" files I found in the
be/storage headers dir. So I hope there should be no more surprises of 
this kind in the future. :-)

CU, Ingo

PS: I crawled a bit in the resources of some applications and I'm afraid,
that the whole thing is a bit weird... at least not as straight forward as
I thought it would turn out to be. There seems to be a bunch of rubbish
at the beginning of the resources section. The count of the resources and
the offsets and sizes of the resources' data can be found in there, but I
have no clue about the stuff around these. The remainder of the file is
quite straight forward again: the resources' data without padding followed
by a table with the type, ID and name of each resource.

I will write a little command line tool to play around with some test
data. Hopefully I can figure out how everything works.