On Dec 10, 10:23 pm, Amit Singh <[email protected]> wrote: > I'll repeat an analogy I used earlier to help people understand *what* > MacFUSE is. > > Cocoa applications are programs. Cocoa is an API. > > Similarly, MacFUSE file systems are programs. MacFUSE is an API > (rather, a family of APIs).
I have a fairly good idea MacFUSE it is... what I *don't* know is how Aperture manages its database (well, past that it's SQLite3), given the general lack of public documentation on the Aperture internals. I'm looking for anyone who might know more about that subject. :] > Now rethink about your question. You don't "set up" MacFUSE file > systems. You (or somebody else) has to write them. That I know, too - seems like a bit of a pedantic difference to make. :P A MacFUSE filesystem that matches to SQL queries might be complex, but it doesn't seem like it would be all that hard... if you know how to do it, anyway. > Yes, it would be > pretty straightforward to write such a file system. Thanks... any more info, though? ;) I do hope to find someone with any general info about Aperture's database structure, and/or relatively non-awkward ways to use that in MacFUSE... maybe I should go post an inquiry like this somewhere more Aperture-centric. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
