Bryan, Steve, and I joined up on a GoToMeeting session. Steve started out and showed us some of his work that he has been doing in the elements of time with sub phases, sub locations, and such. Good demo and he is making tons of progress. Basically, a full on internal wire job using parts, items, PO's, elements of time, sub inventory, and sub phases (special flags and tags). Pretty cool.

After that, Bryan and I chatted about options. I tried to show him where we were headed and he brought up some valid points. One of the points that he brought up was how complex and how many moving pieces. He wanted to do a simple build out to help a single client. We talked about it and he showed me what was planned and we decided that he could do that if he used the new custom JSON table that stored custom JSON objects. The better choice is to go in the direction that Steve is going with subs of time but it does take time to build all of that stuff out. I did warn Bryan that the custom JSON will allow him to store almost anything but it will be harder to pull reports and/or search. Basically, JSON is another word for miscellaneous blob of information vs rows and columns like a traditional database table.

Our final project was going into the secure/choose_corp.cfm page and making it into a black box page. That page has been used and abused (code wise) and wasn't really that straight forward. We got in there and finally I told Bryan to keep working on it and then get back with me. We have different styles and I thought it would be better to let his do his thing and then bring it back to me when he got it work. I felt like a back seat driver... :)