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 a GoToMeeting session with Wayne Andersen (chiming in from Portugal). Steve and I were on the meeting. - CF Wheels framework - Model view controller strategy - A model is specific business groupings (say our 12 main players). - The view is how the pieces show up and/or be displayed. - The controller part is the logic and/or rules for each section. - Object oriented programming - Inheritance - Beefing up the actual methods and frameworks to have all of the custom validation on the methods themselves. - Using the database to help populate and drive the page layout, display, logic, validation, etc. As you change the database, the page automatically flexes and rolls out the new fields and values. This could even help us run the custom logic and pieces. - Think one-to-many on code, logic, functions, display items, etc. - Getters and setters - playing with smaller pieces. - Using a related folder structure vs. page names. For example: a users folder, customer folder, invoice folder, etc. Currently, the page names hold the underlying things such as add_edit_customer or invoice_home or view_cart. - We are getting more mature and are seeing more of what is going on. We could really plan and lay things out better and better. This is the nature of the beast. - Noodle code, sprawl, and custom add-on's - currently, we have code all over the place and have tons of different developers working on different pieces. We need to reorganize and plan things out more fully. We then, at some time and/or while we are running, will need to do a full re-write and then make that transition into a more robust framework. - The more we go into an object oriented framework, the easier it will be to help train and bring on new developers. That is huge... Right now, we spend months and months trying to bring on new developers and trying to help them find their way around. Imagine if we could bring them in, get them oriented, and then help them get in easier and do their job. - We will still need to allow for custom code, custom display, and custom logic, but we could really benefit from a standard framework. One of our goals is to become a full on platform that others could build off of, duplicate, extend, re-use, re-purpose, and/or consume as needed. - We want to provide our users with their data... that could be web, html, csv, excel, xml, json, pdf, etc. We have tons of critical data that our people need. It would be so cool if we could provide any data or data tables or tabular data in all kinds of ways at the click of the button. As far as the data goes, it is their data, we just need to allow them to get it and provide it in as many ways as possible. - The look and feel is huge... many of the sales start right there. Some people don't even look past the cover to see what we have under the covers. We need to change the appearance of what people are seeing. In some ways, we have been lightly hiding. We may need to come more out in the open. We need to keep the logic and view on separate layers. Right now, we have a number of files that are intertwined together. We need to somewhat break things apart and allow the logic and data to be on a separate level than the display. - If we use a framework, we are using some existing pieces that already exist and then we get to leverage those functions how we want. We could really harness that and it would save us tons of time. - The API layer (application programming interface) is huge. This is the path to the data. If you make it so that you use the API for all of your calls, it makes it really strong. Currently, we use the same methods but internally we use native ColdFusion. Externally, we format things into XML and JSON and run our methods through other pieces. If we used the same thing for both... It would be very stable and a well beaten path because we are using it all the time. Currently, it is lightly coupled but it is separate. It would be really nice if we could tie things together. - We want our more senior developers to work on this project. This is not for our beginner and/or junior developers. We need to make it stable, good, easy, etc. Totally possible. - Steve would love things to go toward the gaming level. Full on interfaces, levels, characters, worlds, etc. Virtual environments, custom interfaces, and showing real-time data tracking. Take real processes and then simulate them in some kind of a system. Similar to the idea of harnessing our users clicks and navigation patterns. What if they could help us do the things we need to... Take real actions and turn it into science and/or data management, internal processes, warehousing, etc. Great meeting and some really fun progress. Good stuff. |