The problem I always run into with 3rd party plugins is when there is
a conflict that disables two plugins working together and you are
left at a stand-still. I've been in the "buyer beware" mode too many
times, but for the most part I would rather that they sold a dylib/
dll and a set of declares to use them. I realizes that a compiled
plugin is safer for the plugin vendor, but we all frequently have to
deal with what is best for the customer is not always what is best
for the vendor.
The real benefit of a dylib/dll solution is that it is many times a
drop-in replacement to a compiled project rather than a recompile
from RB.
No offense against the plugin vendors out there - I have had good
experiences too - Einhugur is a really good example of a set of
plugins I will never go without.
I'm working on the weekend, and I am not in the mood to be flamed for
the above -- please be kind :)
C.
On Feb 3, 2007, at 12:36 PM, Terry Ford wrote:
On Feb 3, 2007, at 9:17 AM, Chris Halford wrote:
I am absolutely willing to do this. I'm just under the impression
that someone else has already done this and might be willing to
share the knowledge.
There has been discussion in this area but I don't recall any
resolution other than MBS plugins.
The nice thing about it, as Norman stated, you don't have to bloat
your program with all of the plugins. Only the used ones get
compiled AFAIK. Also Christian can help with using them. It's all a
matter of what you value most; Time or ease of use.
-Terry
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
