So Bjorn is not going to open source his plugin tool or the tools
necessary to build the version file, then we must look elsewhere
for that part of the solution. This is no big deal, but when we
come up with an open source solution then what purpose does
Bjorn's plugin tool serve? The answer is I think it will become a
distraction since we want our end users to use a single tool. The
question is will you (Bjorn) pull your tool from the market or
remove the cross over functionality? My guess is you will probably
not, so we will end up with a fragmented choice for the end user.
More important than the plugin tool itself is the format of the
version file. Undoubtily there will be additions to the fields
based on the discussions going on in this news group. Again, will
you (Bjorn) support and follow what is decided upon here?
I hate to be single you out here (Bjorn), but you have put us in a
slight quandry. If nobody had done anything along these lines and
we were starting from a blank slate, this would be so easy. To
make this process work seemlessly for end users, we need your
coorporation. I think there needs to some kind of comprimise on
your part for the good of the community (most likely supporting
new fields as we go forward).
-----
After we establish the necessary infrastructure to support the RBX
format, we (as the plugin author community) should stop producing
the old style plugins and go strictly forward with the the RBX
format. In the long run this will better serve our end users and
ourselves having a unified format.
-----
The first order of business is to decide on the what belongs in
the version file. Bjorn's format begins with the following fields.
- Release
- Revision
- Fix
- Status
- InternalStage
- CountryCode
- ShortString
- LongString
I am not sure what is the value of having a ShortString and
LongString other than for lagacy purposes.
What I think is needed are the following fields.
- Vendor (name of the vendor--MBS, Einhugur, TNSC, etc.)
- Comment (free form text)
I also think we should eliminate the first optional line that
Bjorn had for his old reader.
Does anybody else have other proposed additions or comments.
-----
As for creating an open source plugin tool, I am willing to create
and host and open source tool. I am also willing to entertain
creating the necessary build tools that you can incorporate into
your build environment. Though I think we should probably table
this discussion until there is concensous on the file format.
_______________________________________________
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>
|