(quote)Originally posted by Cafall:
Perhaps you have heard of the EVN Expansion Project, a (supposedly) "huge" project in which many people contribute in one little way to making a huge, constantly updated EVN plug-in.Of course, this never really got off the ground, despite what the members may think; the majority of the members are enthusiastic EVN players and a handful of tutorial writers. (/quote)
2 differences exist between the EVN:EP(and yes, I am aware of the project, and wanted no part of it) and the Trinity development project:
Size : There are many, many enthusiastic EV:N'ers who want to be a part of a development project. For trinity there are far fewer. With less people to manage there is less of a logistical problem, less personality conflicts to sort out, etc.
Skill : As you stated, the EVN:EP had a lot of people interested, but they were all "chiefs" and very few "indians." For the Trinity project that I am proposing, I am not interested in people converting Trinity or bending it to their purposes. Pretty much you can throw out all of the "enthusiastic players" and "tutorial writers." My envisioning, which I perhaps did not spell out very well, is for plug-in designers to work on this project so that their own independant plug-ins will be compatible with Trinity. Also I envision plug-in writers that want to fix the bugs in Trinity to help out in fixing those bugs.
(quote) **There are many problems with such an idea, the main problem being that there would have to be a tyrant dictator controlling every aspect of the project, at all hours. He'd not only have to control development and updating, but he'd also have to deal with the unauthorized versions of his plug-in sprouting up everywhere (of course, if you could befriend AAC he could do that for you Your criticisms are welcomed and encouraged, and if they can help make the project work, then great.
(quote) I think Beenox should just release the source and sit back to watch the fun.** (/quote)
This is their intention. The trinity development project is an idea of my own and has no relation with Beenox at all. It is a selfish idea, actually, because I intend to design a plug-in that is currently incompatible with Trinity. It is my intention to modify Trinity in a way that is becomes compatible with my plug-in(although to the end-user who would download my version of Trinity they would see no difference in how it worked... this would all be code-level changes). And I would like to make a way so that if others want to make alterations to Trinity, the changes I made would still be there. So I am being selfish.
(quote) Of course, the addons page admin could conceivably filter the flow of modified Trinities by only releasing the best ones. I believe we could prevent a Trinity "plague" from spreading without attempting to control it completely. (/quote)
This is true. However we would still have "Trinity_Stark's_Version" and "Trinity_Cafall's_Version" and "Trinity_Original_Release" et all. And if someone wanted to use my plug-in along with the additions of Trinity, then they would have to download my release of trinity. And if someone wanted to play a plug-in made by Cafall that requires his version of trinity, then they would need to download that as well, and then make sure they had only the correct version of trinity installed when they load POG. A real hassle and headache.
It is my opinion that if we can find a way to make changes to the Trinity source so that all of our changes remain even after someone else modifies the source, then we should do so. This way when we create plug-ins that are compatible with Trinity only due to modifications of Trinity, then we can put a line in the readme that states, "Must use Trinity version 1.4 or higher." Then our only problem would be to make the user read the readme, which I believe is a much more difficult task
Does this make sense? Is my vision clear, cloudy, or just a pipe dream?
------------------
This may not be your favorite song, but it's got a lot of the same notes.
- KGGO Des Moines in the front?
).
). I think Beenox should just release the source and sit back to watch the fun. Of course,the addons page admin could conceivably filter the flow of modified Trinities by only releasing the best ones. I believe we could prevent a Trinity "plague" from spreading without attempting to control it completely.