You can reuse plug-ins from built apps. I did a test with one of our
plug-ins. I built a universal test app and then copied the dylib out of the
package and used RB Plugin Converter to make a new plug-in. I was able to
use the new plug-in to build and run the same test app. If you want to avoid
this kind of problem you need to add some kind of registration function to
your plug-in like Christian does with MBS.
Chris
on 7/28/07 10:26 AM, Giovanni at rbml at alphaview dot com wrote:
> So a plugin that gets compiled as part of an app under osx can not be
> used by another user who is trying to gain the functionality without
> paying or without proper license?
>
> Are you sure?
>
> Kind regards,
>
> Giovanni
> rbml at alphaview dot com
>
>
>
> On Jul 28, 2007, at 7:19 AM, Daniel Stenning wrote:
>
>> If they are commercial plugins I believe you can only use them
>> within your
>> own compiled apps. ( assuming you purchased the plugins ).
>>
>> Once inside a built app the plugin is in the form of a dynamic library
>> designed specifically to interface with the app you are running.
>> They are
>> not like, for example windows DLLs where sometimes the same DLL
>> instance in
>> memory gets shared by several apps the same time. A good thing too,
>> because
>> this used to ( does ?? ) lead to endless issues around DLL versions
>> and
>> mismaches between apps. One of the great things about RB apps and any
>> plugins they use is that everything gets "locked" into a single app
>> bundle.
>> This removes so many hassles.
>>
>>
>> On 28/7/07 08:16, "Giovanni" <rbml at alphaview dot com> wrote:
>>
>>> Hello there
>>>
>>> On OSX apps packedges, are the plugins accessible and reusable? Or
>>> are
>>> plugins safe to distribute?
>>>
>>> Thanks guys,
>>>
>>> Giovanni
>>> From my iPhone
>>> alphaview.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|