On the morning meeting. Pretty quiet. Russell popped in for a bit but most of the session was a work session. I was working on building a sales tax calculator page for users to test out sales tax and location settings.

Small note on global simple getters and setters... As I was hiking this morning, I was thinking about simple getters and setters. As I was doing that, I would really like to make one super generic setter. Imagine a corporation id, a table name, an id number, a column name, and a value. It could be that simple. Then we could use it over and over again. We might beef it up a bit by allowing lists and arrays of name/value pairs but it could be pretty simple. On a simple getter, what if you could pass in a corporation id number, a table name, a list of fields to pull, and any special criteria. You may also need an order by clause, a group by clause, a limit clause, etc. All extras would be optional and well documented. If you wanted everything, you could just use key words such as all, auto, etc.

Here are a couple advanced SQL methods that we may end up pulling ideas and info from: "tableRecordCounter", "getCustomersSimple", "adminGeneralSQL", and "getSpecificCorpWideSettings". See also these pages for dynamic SQL stuff: developer_update_tables.cfm, test_page.cfm. These are listed to help with getters and setters. Just concepts of what we are trying to do.

Another small thought... While working today on a new calculator page... I was thinking that it might be good if I were to help go through the application and do some maintenance stuff. Don't do huge big projects, but do some code, get it done, merge it in, and push it up. Tons of mini projects. This could be checking pages, writing help files, doing web/API documentation, testing things, adding black box code, checking icon menus, etc. All kinds of stuff that needs somebody to look at it little by little. Just a thought.