|
Size: 1811
Comment:
|
← Revision 16 as of 2011-10-17 21:08:49 ⇥
Size: 1542
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| == Eminent Future Things == 1. Add ownership properties to the database and write the synch framework so that we only push owned changes and prevent changes to un-owned data. 1. Add Master / local connections (see Dr. A's Visio chart) |
|
| Line 11: | Line 16: |
'''Possible future change of the use of DBindingList''' DBindingList was something I created to deal with being able to delete an item properly when a GUI object like a DataGridView deleted a row and hence a object from a list. The functionality to delete the item is called by DBindingList using an Interface called IDeleteable (also created). It is possible that this could be taken care of in a destructor and still use a straight BindingList<myClass> where myClass has destructors that do what is called using the IDeleteable interface. HOWEVER: I like my DBindingList because I can control when something gets deleted. So, I think I'll keep it. |
|
| Line 20: | Line 21: |
| '''ListFactory''' | ---- |
| Line 22: | Line 23: |
| Make this a static class and instantiate references to the dataset and the table adapter manager. This should be a Singleton - see notes on google/wikipedia. ---- |
The location part is a problem because of scale The MPP manual has 6 for a 5x5+2 bulks, and that didn't scale to our 4x4 with 2 bulks. Location key is not used, so take out the location key. But we'll keep location and use it as just a general description of the location in cardinal points i.e. NW, N, NE, .... So take |
Program Changes Requested/Identified
These are not bugs. Report bugs on the Bugs Page page.
Changes to do
- The designation in the identification section should be a drop down that equates to what the locus actually "is" See MPP list of types under "Stratigraphy". Dropdown menus in the levels should be taken from "Designation".
- The "Location" field in many parts of the Identification section should be a reference to a point taken with the total station. Fix the "text" and check the type. For this summer, we are not including this except that individuals can enter a comma separated list of point numbers.
Eminent Future Things
- Add ownership properties to the database and write the synch framework so that we only push owned changes and prevent changes to un-owned data.
- Add Master / local connections (see Dr. A's Visio chart)
Far future things to address
Object Addition
There is currently no field in the object to identify what the object actually is except the remarks column. It would probably be better if this was changed to include a parent table of types and a type identifier.
The location part is a problem because of scale The MPP manual has 6 for a 5x5+2 bulks, and that didn't scale to our 4x4 with 2 bulks. Location key is not used, so take out the location key. But we'll keep location and use it as just a general description of the location in cardinal points i.e. NW, N, NE, .... So take