The Document looks very nice and neat. Great Job! ~Kwabena
Nice, I'm likin the document ;) and nice work on figuring out active controls, that'll be a one-up that should give us an edge.
As for the activity log.. can't think of anything other than just standard coding =p Good job guys, I think we knocked it outta the park ;)
~ Dave Fawcett
- Sorry, glossary not appendix.
- I have updated the Document Index for the binder and put some new entries into the Activity Log (2 meetings, setting up VS, setting up doxygen, writing progress report). If anyone has an activity for the Activity log could you please list it here and I will add it. I just need a name, start and end date, and rough estimate of hours.
~bpeake
Nice paragraph. It fits in perfectly under the "Delegation" heading. When you say appendix, which appendix do you mean?
~DS
p.s. I'm running out of steam here. I'm not going to write about the "distance and angle denomination system." If someone wants to write about that, be my guest, but otherwise I think the report is looking ok.
That looks really good David. Here is some input:
1) Should we added the appendix (I'm not sure... what do you think)
2) In Section 1.2 - "we code an active control prototype" -> "we coded an active control prototype" (I think it needs the 'd')
3) I have an additional paragraph for Section 2.1:
One of the inherient concerns of working with Visual Basic is that VB is not suited well for use
with source control programs. The team is working on setting up a repository so that source files
can be stored in a common location, but because VB has automated code generation for GUI components,
the dangers of two individuals working on the same source file out weighs any potential efficiency gains.
As such it was critical to carefully delegate the project coding into independent chunks (or modules)
and to minimize the overlap and dependence of the code files. The coding progress and risk reduction
that resulted has been a big win for the team that will continue to have a postive impact (especially
in bug reduction and product quality).
~bpeake
I fixed the link and uploaded the most recent version. Here it is.
~DS
That looks scary good Dave. I have taken all the vb files in that rar file and updated the doxygen report to include them (and manually added the code to the html pages produced by doxygen http://people.uleth.ca/~brett.peake2/ProjectProgressReport/). How have you found development so far? Any major/minor concerns?
David the link you posted to the working copy of the progress report is broken because of the space. I'm just reading it right now (by going to your root directory and opening it) and will give you any feed back or additions I have in a few moments.
~bpeake
OK so here is a basic workspace (I called it StationOne) with my scripts setup and working on it. Keep in mind my section is made to work with the control center, so DONT hit 'Cancel' and expect the program to exit =p It will just hide my form, hit 'X' if you want to quit lol
The important files are Enums.vb and GlobalVariables.vb, since those should be used by all scripts. Also I have the MovementPlan class made up to a usable point, I scripted in the ability to lock out indexes from being changed below a specified index. So if we want to edit active motion plans we can set the initial index or whatever, but I remember we ended up boning that part so its not necessary. The class works without worrying about any of that part.
Here is a link to a RAR I created with the solution and workspace etc (keep in mind this is Visual Studio 2008):
http://www.fawcettsoftware.com/misc_stuff/StationOne.rar
EDIT: I should also mention, the design isn't final... just nailing the functionality at this point. So feel free to comment/suggest/whatever
~ Dave Fawcett
Ok, I'm going to post what I have SO FAR. A few more sections still need to be written, but I'm going to take an hour break before I get to them. I'm open to suggestions, but keep in mind this is due tomorrow, so I'm pretty much just pounding it out. Additions and edits are welcome.
Progress Report working copy
~DS
That sounds good David. Let me know if there is any areas you would like help with or input.
Also I have manually copied and pasted the code in and it looks okay so I think I will go with that, unless you guys prefer otherwise. If any more code is posted I will do the same for them. I don't plan on doing the mock-up as it has no functional use, however if you think it would be worth while I could easily do it...
~bpeake
Oh, and incidentally I'm working on a write-up for our progress report right now. I'm roughly using the eight points outlined below supplemented with some of the wiki content (coding conventions, Doxygen explanation, etc.).
~DS
Ah, I see. You might want to turn it off; it doesn't really add anything to the content. Were you going to run your GUI prototype code through, or is there no code to speak of? Is Dave F. going to post his code?
~DS
Yeah perhaps I will turn that feature off. We don't get the entire source code because our VB code is filtered into C++ like code. The code that you are seeing is actually all the code that passes through the filter.
~bpeake
It looks very nice, but was it supposed to display the actual source code? It's just displaying an abbreviated list of functions where it claims the "source" code is.
~DS
Sounds good. I'll let you know if I run into any trouble with it/need to make any changes for doxygen.
If anyone else has some code ready for doxygen (or will have some code), feel free to just post a link to the .vb file and I will run doxygen on them all.
Here is the link to the doxygen output http://people.uleth.ca/~brett.peake2/ProjectProgressReport/
~bpeake
Here's my VB code file for the active control prototype. Brett, please feel free to many changes to my commenting before you run it through Doxygen, if you want.
I'm still learning VB, so there might be some odd stuff in there. Also, my variable names aren't to convention because I wrote the code before we decided on it. I'd go back and change all the names, but since this prototype isn't a part of our actual project per se, I'm not planning on using the time.
~DS
This is the SVN part for the progress report.
~Kwabena
Uh, Kwabena, you know, Robert has the address to this wiki.
~DS
The progress report is due on Thursday. What progress have we made in terms of coding?
- Delegated main tasks:
- Vincent and David S. will work on the Communication Module.
- Kwabena, Dave F., and Brett will work on the Editor Module.
- Outlined coding conventions.
- Produced GUI mock-up.
- Produced active control prototype.
- Set-up Doxygen.
- SVN.
- Had two code-related meetings.
- Developed distance and angle denomination system.
~DS
Robert has yet to give us criteria for the progress report, but I'm hoping it will be straight-forward.
Before we can write the progress report, we'll need some progress. I think that compounds the importance of starting early, because yes, we have two weeks to do this, but there are sort of two jobs going on: one, we need to get "coding," and two, we need to report on our progress.
So far, I've read this info Brett posted, and I'm also busy downloading Visual Studio 2008 (which is going to take awhile). I've also started looking for good Visual Basic tutorials: if anyone has recommendations, I'd appreciate it.
~David Sharpe
Comments (0)
You don't have permission to comment on this page.