realbasic-plugins
[Top] [All Lists]

Re: A proposal for plugin authors...

To: realbasic-plugins at lists dot realsoftware dot com
Subject: Re: A proposal for plugin authors...
From: Brendan Murphy <bmurf at comcast dot net>
Date: Tue, 24 May 2005 21:47:56 -0500
Delivered-to: realbasic-plugins at lists dot realsoftware dot com
References: <20050524170055 dot 725C39BA5E6 at lists dot realsoftware dot com>
Alfred wrote:
This is a plugin management issue. I would like to see a common
solution that everyone can pony up to and be happy with.


Brandon, I really try to follow you, and really would like to help out. But
what do you mean with proprietary tools? We are talking about a file
containing XML formatted text. The XML structure was posted to this list, and yeah you could argue about the Xml attributes, the nodes, the encoding, whatever, but it is there for you to discuss. There isn't anything closed here. What is closed is how an OS formatted file structure is transformed to
a vv, but that's not hard to do?

And again, if William suggests to versioning the plugin name within the vv,
then I would rather support that over what ever will be put into the
VersInfo.txt. That file is a convenience, given a plugin tool out there, but
I am not dependent on that.

I apologize if I cannot follow you, perhaps because I am too occupied with
other pressing and urgent needs,

regards,

In this case, proprietary means someone owns the copyrights to the
tool and chooses to not share it (open source it) with others in
order to maintain an advantage. You can choose to support Bjorn's
format, but he is not thinking of you when he changes it. He is
thinking of his own needs and plans point of view. This is what
people in business do. To be frank, Bjorn has threatened in the
past to completely leave the REALbasic market. Who is to say he
will not threaten this again in the future and carry out such a
thing? This past behavior always hangs as a distant looming cloud
on the future availability of the tool.

I am sorry you feel you can't follow what I am saying, but my
words are not difficut follow. There needs to be a more formalized
way to manage plugins. The RBX format itself does not provide
this, thus Bjorn's plugin tool exists. It fills this need. Ask
yourself why Bjorn created what he did and why and you will see my
point.

What William suggested is inadequate as a solution. So what do we
have? Bjorn has one way, you do it another way, and I'll have to
come up with a different way in order to accomplish the need of
managing the plugin sets for the developers that work for me. In
the case of the plugin tool like Bjorn's, it makes little sense
since there is no financial gain for it.

Please don't let me keep you from your "urgent" needs.  :)

_______________________________________________
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>

<Prev in Thread] Current Thread [Next in Thread>