[openbeos] Re: File format support in Haiku
- From: Ar18@xxxxxxxxxxx
- To: openbeos@xxxxxxxxxxxxx
- Date: Thu, 05 Apr 2007 02:31:04 +0000
> The Annotated BeBook is here
> (as long as beunited.org is still around):
> http://beunited.org/bebook/The%20Translation%20Kit/index.html
>
> The intro page link is bad, but it's there too:
> http://beunited.org/bebook/The%20Translation%20Kit/Translation%20Kit%20Intro.htm
Good, that would be very helpful.
> This may not be easily understood unless you've got some programming
> skills, but it's the only document AFAIK that tells the whole story or
> what's possible and what's not possible, for a Haiku application
> programmer, and Haiku apps, with the current API.
I admit that I don't have the programming skills for this, but I would like to
help out in other ways and maybe get some new people involved in the file
format translation for Haiku (and maybe other areas). Would this be acceptable?
> About a wish list,
Those are a lot of concepts to hash out. The questions is, is Haiku even ready
for new developers to come in and begin working on support for new file types
or do we need to settle on any changes that will need to be made to future
version of Haiku's translation kit first? (I forsee the need to re-evaluate
the whole translation kit concept to see if it needs to be re-done in any way.)
If the answer is the later, what can be done about this? Could something be
started to discuss and work this out? Would it even be appropriate to do at
this time?
> You can embedd any data in the resource section of the executable file,
> or directly in the source code. If the applications takes add-ons,
> those can contain additional data in whatever format. There are classes
> in the current API that allow displaying images and, I believe, simple
> vector graphics, as well as playing sounds (without any visible
> controls though, AFAIK), but it's not like embedding files in word
> processing documents or in web pages. Replicants -could- be used for
> this -- a "fat", contained(?), kind of data insertion -- embedding data
> with a rudimentary, possibly standardized set of controls, GUI and/or
> non-GUI controls. I'm not a huge fan of that idea myself, for Haiku,
> but I suppose it can be done. Applications would have to have support
> added, to be able to be hosts to embedded content of the kind I
> interpret you as asking for, but I don't think there's a solution that
> will instantly open up any given (old) application, without editing its
> source and rebuilding it, to arbitrary, safe-ish, content embedding.
> But I welcome any experimentation.
The idea could be thrown out if it's no good.... Up to you all. :)
> /Jonas Sundström.
Thanks again.
Other related posts:
