Re: [Filecaddy-developers] Updates!

[David J. K. <dke...@ko...>]

I think you're trying to do too much with the plug-in architecture. You're
trying to create an extensible file system but VFS is *already* extensible.
For example, if you want an NFS or FTP module, why wouldn't you just write
it as a filesystem module that plugs into the VFS manager so that all
applications (not just FileCaddy) can use it?

Also, the more complex the plug-in architecture, the less likely developers
will be to write plug-ins. I know that what you have so far doesn't seem all
that complicated to you, but the fact is most PalmOS developers are *not*
expert C coders and I guarantee that what you're proposing will severely
limit who can and will write plug-ins. Even the simple plug-in architecture
for FAFileMover (simple as it was) was too complicated for few developers
that I approached with it.

Unfortunately, I don't have much time for FileCaddy these days (I'm
desperately trying to find enough paid work to keep Kopsis afloat) so I'll
leave the decision of how to proceed up to you.

-- 
    - Dave Kessler
      President - Kopsis, Inc.
      http://kopsisengineering.com


On Tue, Sep 10, 2002 at 12:03:42AM +0000, Matthew Bevan wrote:
> Woh, long time no C...VS update, eh?
> 
> As much as I love flossing my cat, the time for updates is neigh.  I've been 
> working a bunch on the plugin archatecture, and have put together a spiffy 
> makefile and code example that should, in theory, work.  Just need to make 
> some test programs so I get a full grasp of how to do this...
> 
> I'll be posting an update to the website so people know we're still alive and 
> working, as well as the plugin code example and some docs on how to write a 
> plugin that does spiffy things.  Any input on how to do the plugin system 
> would be really handy about now.  What follows are some preliminary ideas...
> 
> Plugins will have one main function exported - PlugInMain - which gets passed 
> a pointer to the following structure: