Re: A virtual file system

I had a look at the code last night, and I've got the native file system driver working without Horde now. I agree with Alan Knowles on the returning of arrays though - and I'm also going to do some extending, because it seems to be missing some features that I think should be there - such as the isFile() call in Alan's code. It's a lot easier to work with then I'd been expecting though - thanks to the Horde developers for the code :) Do we have a decision on where the VFS code is going to be stored yet - I'd be happy to keep it in either PEAR, or Horde, although I'm not sure how keeping it on the Horde cvs server would work, if your going to be using a wrapper class to integrate the Horde code anyway, couldn't you use VFS as a dependency like you do with the Log class. My guess is that users are only going to find getting a pear module difficult once, and then they just have to repeat the same process to get the vfs one, which they'll already know how to do. Since it's Horde's code though, the final decision is with you. Jon ----- Original Message ----- From: "Mika Tuupola" <tuupola@appelsiini.net> To: "Jon Wood" <jon@jellybob.co.uk> Cc: <pear-dev@lists.php.net> Sent: Monday, September 23, 2002 10:12 AM Subject: Re: [PEAR-DEV] A virtual file system > On Fri, 22 Nov 2002, Jon Wood wrote: > > > I'm not starting again as a dig at the Horde implementation - I'd just rather > > start with a clean sheet, then re-engineer the Horde code :P > > I don't see the point of rewriting the whole thing. Just > removing the few call's to Horde specific stuff should > be enough. Horde is otherwise allready PEARified. > > -- > Mika Tuupola > http://www.appelsiini.net/~tuupola/ > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >