[physfs] Adding Support for Custom Archives

[Oli Wilkinson]

It does sound as if you're wanting some functionality that PhysFs doesn't
offer, and didn't offer when you came across the library - namely pluggable
archivers and a C++ interface. Did you look around for any other solutions
that would fit your needs better?

And if you do make your changes, what would you do with them? Would you
release your /own/ branch of Phys? I agree that these changes would be nice,
but it sounds like you'd be better off rolling out a quick library of your
own that contains the functionality that you need rather than retro fit them
into a library that wasn't designed to support them.

Cheers

Oli


On 6 August 2010 06:47, Kip Warner <kip at thevertigo.com> wrote:

> On Thu, 2010-08-05 at 11:15 +0200, Christoph Nelles wrote:
> > Hi,
> >
> >
> > On Wed, 04 Aug 2010 18:21:56 -0700, Kip Warner <kip at thevertigo.com>
> wrote:
> > > That sounds like a great idea, but I am confronted with a dilemma. As
> > > you say, you have some things to sort out in personal life, so I don't
> > > know how long before we see a pluginable interface being available. So
> I
> > > either have to include a static snapshot into my source and patch that,
> > > or wait and use the newer 2.1 interface. Either way, they both involve
> > > some important design decisions that I need to make quickly.
> >
> > i need/want the same functionality, too. I will work on it soon (1-2
> > weeks). Currently I am busy with cleaning up the error handling stuff and
> > after finishing that, i will go on. I don't know if Ryan will like the
> > work. And in the end, if it's not becoming official, it won't solve your
> > and my problem of an independent maintenance as as library.
> >
> > Btw. Ryan is not very release happy and all non-bugfix changes have gone
> > into a development branch and i haven't seen any packages using that
> > branch. It looks like everybody is relying on the stable branches. So
> until
> > there will be a new "stable" branch, compiling your own version in may be
> > the only solution.
>
> Hey Christoph. To quote some of my friends, I'm "stoked" you're doing
> that. Majorly needed and I'm surprised a pluginable archive interface
> wasn't in there right from the get go. There isn't really any other way
> to get an obscure, ad hoc, resource format for a game engine in there.
>
> --
> Kip Warner -- Software Engineer
> OpenPGP encrypted/signed mail preferred
> http://www.thevertigo.com
>
> _______________________________________________
> physfs mailing list
> physfs at icculus.org
> http://icculus.org/mailman/listinfo/physfs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/physfs/attachments/20100806/a16a184a/attachment.htm>