Hi Michael, One advantage of making it a plugin is that you could then distribute / sell the plugin as a product in itself once it is complete. This is possible with the declare route, but is much easier to achieve with a plugin.
Dave. > From: Michael Williams <[EMAIL PROTECTED]> > Reply-To: REALbasic Plugins <[email protected]> > Date: Sat, 28 Jul 2007 18:45:03 -0400 > To: REALbasic Plugins <[email protected]> > Subject: Re: Incorporating existing C/C++ libraries into an RB Project. . .? > >> >> If what you have is a shared library (dylib, DLL, ...) with a C >> interface >> then you can call it today with declares and you don't need a plug- >> in at >> all. If you don't know much about declares I recommend Charles >> Yeoman's book >> iDeclare at http://www.declaresub.com/. You need to use a plug-in when >> either the interfacing becomes complicated or all you have is >> source code to >> the library. >> >> Chris > > > Well, that's just it; I'll need it for different platforms so I'll > either 1) need to create a plugin to do what I want or 2) have to > distribute the shared library with every copy of the program which is > very prohibitive. As I stated earlier, I'm working with the FITS > file format and my plan was to make use of the following library: > http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html > > If you all could, take a look and let me know what you think. > Perhaps this is the wrong approach. Perhaps I'm missing something. > Otherwise, thanks for the great suggestions. > > Michael > > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
