all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
On the GoToMeeting session with Steve and Alan. We started out and setup a number of new developer accounts for each server. We then started talking about the potential of making adilas into a "game based" interface. Alan has taken some game development classes. We have always wanted to turn the adilas functionality into a game type scenario. This would have players, choices, consequences, problems, locations, tools, permissions, etc. Without being super crazy... what if we put a visual spin on what we are doing... If you want to pay for something, you go to a certain spot and start doing things. Lots of drag and drop, lots of pushing and loading things into one-to-many relationships, etc. Going way back, we had the idea of entering the business data sphere. This would be loops, orbs, tracks, with different destinations, tasks, etc. Each person would have their own pod and/or vehicle of sorts. They could then port and transport where ever is needed. As they interact, they are actually doing work, but it feels like a game type interface. Steve would like to know what the next phase is... dashboards, user interfaces, connections, quick links (buttons), short cuts, user-designed navigation and custom interfaces. Got a call from Dave Forbis. He was asking about cascading the customer table settings throughout the system. This is where a client could name, show/hide, set defaults, set light rules, and sort the different fields. They currently only show up on the add/edit custom page. We need them to start cascading beyond that. The problem is, we haven't had time to go over and/or check the code. It was written by Calvin in cfscript which most of my guys don't know. Also, we do have an awesome database to hold the values and it has been prepped, but still needs to be put into action. The name of the database table is "db_field_settings" or database field settings. Going back to the gaming interface and ideas... Could a switch to this type of interface help with training? That would be awesome. Maybe we could make an attempt on some of that stuff. People expect that they have to experiment and try things in the gaming world. A reward based process (keeping track of where you are and showing what the goal is). The way we work with our developers will start turning more into a small game of sorts. For example: Do "A" and come back. Then I'll show you what to do on "B". Think of bite size pieces. We need to plan it out, let them work, check it out and inspect some things, and then go to the next level. We can't just give them the whole project and make them run with it. We may need to prime the mental pump, then do some brainstorming, then make a plan, and then start working the plan. We need to morph our morning meetings into planning sessions. This could be new projects, older needs, to do list stuff, etc. We need help with the lots of the day to day stuff. We will use some of the morning meeting times to go over tasks, post-it notes, and other things that need to be done. |