Closed DanielBullimore closed 4 years ago
Leave HTML and the DOM in the 90ies where it belongs. Re-manifest in html5 canvas, this is art. Draw. Also values of private properties may be needed for programming. Consider protected values with funGet methods and no funSet:
funGetType() funGetId() funGetName()
Leave HTML and the DOM in the 90ies where it belongs. Re-manifest in html5 canvas, this is art. Draw. Also values of private properties may be needed for programming. Consider protected values with funGet methods and no funSet:
funGetType() funGetId() funGetName()
I'm putting these methods in the designs.
The object index array window.rayOO is decoupled from OO by design, but is this best?
I designed the global array system to simplify implementing the frame work. So long as OO.class.js is linked any child class can just initialize by being declared. Alternatively using the array as a property of OO a developer would first have to declare an instance of OO then an instance of the child class.
The trade off of this easy of implementation is the master index is public. Developers are asked not to directly change its data.
Am I wrong? change my mind.
Sanity checking at the end of Stage One Core Feature list finds this class description is well out of sync with current UML diagram.
Sanity checking at the end of Stage One Core Feature list finds this class description is well out of sync with current UML diagram.
I have synced this today.
I have not implement objPerfectCircle. The game loop is not an object class it is an instance of function object.There is only one master game loop, and that is O. If anything other than a public function object, O could be a function of Oo. Also the function funStartLoop calls itself from a setTimeOut ... set time out doesn't like this.function as a parameter ;-) I'm going leave objPerfectCircle as an interface... you know, so implementing developers can give it One...
Currently the delivered version of OO supports a parameterised declaration. The method was intended for a decendant class to overwrite OO's type property. And it works well. But only for a direct decendant, when a sub class tries to inherit another class's form (which isnt OO) the type can not be overwritten. Fortunatly every class that inherits OO has the .Initialise function. If this function was changed to allow parameterised invokation any decendant of the master class could initialise with its unique type string. Using Initialise method is more effeicent than making every class accept a type parameter and passing that parameter along a chain of declarations though the inheritance tree. Thumbs up to make this change.
Using Initialise method is more effeicent
You mean Efficient? The most efficient way is to make strType a public variable. Doing so would relinquish a portion of control over the framework that OO posseses as the master class ... and we can't have that. Just imagine implemtation developers changing class type variable willy nilly, it could affect functionality and make people think the framework is poorly designed. Make the changes, run the tests for all delivered to date features. When all features pass their test push the changes to Master branch. This is exactly why the production of the testing documents is part of DBTDD.
When all features pass their test push the changes to Master branch.
Complete. 100% pass
Priority:
Depends:
(O)-[O.class.js]
UML
Description:
Master is the master class that all other OOmutiny classes will inherit. It will provide functions to control all Mutiny object instances. This class has default initialize and destroy functions. It will provide an index of all object instances declared which inherit it's form. Functions of the Mutiny class will provide its descendants programmatic access to the index of object instances. This will allow programs and programmers to access the properties and functions of all mutiny objects so long as they have the 'focus' of one mutiny object. For example if a user clicks a mutiny object that target object has focus (programmatic access to an instance). Our example target object can then call functions and use properties of any other declared mutiny object to complete its user experience. However a mutiny class tree can still be accessed by its instance name.
Methods:
Derived Values:
Properties
Testing Plan: #9