I totally agree. Let me propose some first steps we need to take to get the ball rolling.
1) Define who the project lead is, and what the project lead's role is. It seems like the lead is either mccann or twylight. IMO, with the project still so young, it is important to have a single lead that has the final say in just about everything. Otherwise, we will each have our own opinion about where to take this, but we won't want to step on anyone else's toes, so nothing will get done. The project lead should be the designated toe stomper.
2) Let's pick a forum. Most of our messages so far have been about this topic, not exactly a sign of progress. If we're sticking with source forge for our forums, say so. If we're not, say so, and tell us where to go.
3) Put the results of our discussions in forums on the project web site. Add links to design documents, resources, etc. Make our decisions known.
4) Let's come up with a broad description of what we want this thing to look like. This is what I would say today:
"We will provide a COM component (DecalScript) that exposes the current state of your character in AC. We will also fire events in response to certain events that occur in AC.
"DecalScript will be implemented as a Decal plugin.
"DecalScript will be able to be accessed by any application capable of instantiating a COM component. It can therefore be used by custom VB applications, CScript and WScript, etc.
"DecalScript will also be able to be used to execute and manage user-defined scripts written in VBScript and JScript. Those scripts managed by DecalScript can be added, removed, paused, and viewed in-game using a Decal UI."
Once we agree on something at that level, we can move on to deeper details like how we'll implement this stuff, what sub-components we'll use, what our threading needs are, etc.
I know that mccann already posted some thoughts about implementation, but the gif he put in the CVS repository is corrupted so I couldn't see it. His comments indicate that he was working on the deeper implementation level. I'd like to see a clearer statement at the higher level before we go into implementation discussions.
4) At some point, we'll need to decide what properties and methods we're going to support.
On another note, I never used ACScript, so I'm not sure exactly how it was used or how it worked. I would find it useful if someone could point me at ACScript documentation somewhere, or maybe just post a brief description of how you fed your script to ACScript and how it was run.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes... need to pull it together. :) We have many people who want us to use a different forum.
I would like for Twylight, Climax, and me to discuss project lead issues/thoughts off-line. We can either have 1 project lead or divide up the project lead tasks and discuss issues before bringing to the group. And when issues come up, we will deligate 1 person to be authority on it.
I elect Twylight to pick a forum and for us to use it. Twylight, you'll need to get someone to bring the important info back to the main web site/forum.
I agree with #3. Important items will be 'added' back to this project site and kept organized. Eventually, we'll need to have someone volunteer to work on the home page.
#4, I'll create a doc in the repository that captures the vision_scope.html of the project... and what we are trying to do in the first version of DecalScript. I'll publish this (READ-ONLY) to the doc manager. Please add comments/suggestions to the doc in CVS and replublish.
#4 (second one), we have the ACScript API published in the Doc Manager. We'll also need to publish the .js libraries that were used by ACScript.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If we dont get some soon we are going to all have seperate plugins.
I totally agree. Let me propose some first steps we need to take to get the ball rolling.
1) Define who the project lead is, and what the project lead's role is. It seems like the lead is either mccann or twylight. IMO, with the project still so young, it is important to have a single lead that has the final say in just about everything. Otherwise, we will each have our own opinion about where to take this, but we won't want to step on anyone else's toes, so nothing will get done. The project lead should be the designated toe stomper.
2) Let's pick a forum. Most of our messages so far have been about this topic, not exactly a sign of progress. If we're sticking with source forge for our forums, say so. If we're not, say so, and tell us where to go.
3) Put the results of our discussions in forums on the project web site. Add links to design documents, resources, etc. Make our decisions known.
4) Let's come up with a broad description of what we want this thing to look like. This is what I would say today:
"We will provide a COM component (DecalScript) that exposes the current state of your character in AC. We will also fire events in response to certain events that occur in AC.
"DecalScript will be implemented as a Decal plugin.
"DecalScript will be able to be accessed by any application capable of instantiating a COM component. It can therefore be used by custom VB applications, CScript and WScript, etc.
"DecalScript will also be able to be used to execute and manage user-defined scripts written in VBScript and JScript. Those scripts managed by DecalScript can be added, removed, paused, and viewed in-game using a Decal UI."
Once we agree on something at that level, we can move on to deeper details like how we'll implement this stuff, what sub-components we'll use, what our threading needs are, etc.
I know that mccann already posted some thoughts about implementation, but the gif he put in the CVS repository is corrupted so I couldn't see it. His comments indicate that he was working on the deeper implementation level. I'd like to see a clearer statement at the higher level before we go into implementation discussions.
4) At some point, we'll need to decide what properties and methods we're going to support.
On another note, I never used ACScript, so I'm not sure exactly how it was used or how it worked. I would find it useful if someone could point me at ACScript documentation somewhere, or maybe just post a brief description of how you fed your script to ACScript and how it was run.
You wanted some info on acscript, i've posted it at
http://www.gamegalaxy.com/forums/showthread.php?threadid=1313
Yes... need to pull it together. :) We have many people who want us to use a different forum.
I would like for Twylight, Climax, and me to discuss project lead issues/thoughts off-line. We can either have 1 project lead or divide up the project lead tasks and discuss issues before bringing to the group. And when issues come up, we will deligate 1 person to be authority on it.
I elect Twylight to pick a forum and for us to use it. Twylight, you'll need to get someone to bring the important info back to the main web site/forum.
I agree with #3. Important items will be 'added' back to this project site and kept organized. Eventually, we'll need to have someone volunteer to work on the home page.
#4, I'll create a doc in the repository that captures the vision_scope.html of the project... and what we are trying to do in the first version of DecalScript. I'll publish this (READ-ONLY) to the doc manager. Please add comments/suggestions to the doc in CVS and replublish.
#4 (second one), we have the ACScript API published in the Doc Manager. We'll also need to publish the .js libraries that were used by ACScript.