RE: [PEAR-DEV] Package Proposal: File_MacBinary

I don't see why I couldn't add the functionality. Of course, there are variants, I might start off only by supporting the ability to write MacBinary I files, but I don't see the point just yet unless I have more votes. The need to write to class was based off the fact that the macutils package isn't that great. In addition, end-users that upload files from Fetch or some other client using "MacBinary" format fail to work correctly in the *NIX environment without first being extracted into the data fork. > -----Original Message----- > From: Martin Jansen [mailto:mj@php.net] > Sent: Saturday, May 10, 2003 4:29 AM > To: Patrick O'Lone > Cc: pear-dev@lists.php.net > Subject: Re: [PEAR-DEV] Package Proposal: File_MacBinary > > > On Fri May 09, 2003 at 08:3241PM -0500, Patrick O'Lone wrote: > > I've written a class that can extract the resource and data > forks from > > a MacBinary file. It can also detect MacBinary files via a static > > method without the use of mime_content_type(). In addition, > there are > > methods for outputting both the data and resource forks to > disk. The > > resource fork can be returned as an array describing what > data exists > > in the resource fork header. > > > > The package would be released on the PHP License. To view > the source, > > see: > > > > http://www.townnews.com/contrib/MacBinary.html > > Do you think that there will be a way to *write* this > information into a MacBinary file one day? In that case, your > package should be either prepared for that API-wise or it > should be called File_MacBinary_Read. > > Otherwise I'm +1 on this. > > -- > - Martin Martin Jansen > http://martinjansen.com/ > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >