Shambler,
Good to hear from you. It was me:) However, the liftStart, liftStop, and liftUpdate functions I referred to behave like create, update, and destroy. I could have label these Init, Remove, etc. I agree with you and proposed this structure earlier with the Main.bb.
I've written a Code Wizard that generates common initialization, deletion, load, save (I/O) functions and few others. Its designed specifically for this project. No one is force to use it, however, it could save one some coding time. The only restriction is that its designed to work with types. I would like folks to at least give it a open-minded try and provide some feedback.
The type 'objects' above were written to help fill in the void of object definitions. These objects could be designed in variety of ways, but at least now there is something to start with and can be modified as needed.
Good to hear from you. It was me:) However, the liftStart, liftStop, and liftUpdate functions I referred to behave like create, update, and destroy. I could have label these Init, Remove, etc. I agree with you and proposed this structure earlier with the Main.bb.
I've written a Code Wizard that generates common initialization, deletion, load, save (I/O) functions and few others. Its designed specifically for this project. No one is force to use it, however, it could save one some coding time. The only restriction is that its designed to work with types. I would like folks to at least give it a open-minded try and provide some feedback.
The type 'objects' above were written to help fill in the void of object definitions. These objects could be designed in variety of ways, but at least now there is something to start with and can be modified as needed.