Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

Search The Adilas.biz Developer's Notebook
Time Period:	Daily (enter the day you want to see) Monthly Custom Date Range to
Template Filter:
Color Code:
General Text Filter:	(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:

Adilas.biz Developer's Notebook Report - 2/1/2017 to 2/28/2017 - (114)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 2235		Adilas Time	2/1/2017	GoToMeeting with Bryan, Steve, and Danny. Worked with Bryan for the first hour on his projects. We were doing some clean-up on marking invoices paid. I then finished up the bulk print labels and pushed up files. Danny got on and I gave him a small run through on what is needed for the new custom stuff. Emails and tech support. Meeting with Steve to go over plans, ideas, and what we want for our business model. See attached. Expand...

	Shop 2241		Lunch	2/1/2017

	Shop 5036		Virtual Post-It Note	2/1/2017	-Add a link to the customer log page for the online bill pay portal - that way people could copy it into an email so the client could go online and pay.

	Shop 2282		Meet with Michael	2/1/2017

	Shop 2278		SHAWN	2/1/2017	On a GoToMeeting session with Shawn. We were both working on our own projects for awhile. We then did some testing and merging for a PDF project that Shawn was working on. It was a federal 1096 annual summary report. We had to do some tweaking and printing to work with the data overlay. Back and forth and finally got it done. Pushed up new files.

	Shop 2284		Calvin Time	2/1/2017	Quick phone call with Calvin. Going over what is needed to setup a local development environment for someone that is working with Calvin on a mobile app project.

	Shop 2236		Adilas Time	2/2/2017	GoToMeeting session. Helping Bryan with his projects. We had some database setup stuff (username/password stuff), and then some custom cart logic stuff. We then jumped on with Eric and Steve and has a session on loyalty points, discounts, and smart cart logic. See attached. Expand...

	Shop 2242		Lunch	2/2/2017

	Shop 5026		Virtual Post-It Note	2/2/2017	-We need a way to limit discounts - maybe a corp-wide setting. -Maybe think about discount rules. -Maybe on the item level adding a flag "allow discounts" --On discounts . . . maybe go to categories level. -All of these are recorded on some brainstorming notes from 2/2/17 -Brandon Moore -Stratos - they want a custom email address, and all older deleted emails. Let Dawn know quoted at $150. -Know problems with icon menus. -Add_edit_receipt_payee cfm. -Search_receipt_payee_results.cfm. -Payabled_home.cfm. -As a side note . . . we may need to set a var for the hard coded grayed out link colors on the icon menus. Set this in the Application Page.

	Shop 2283		Server Setup	2/2/2017	Bryan and I got on a Join.me session with some of the C4Ever (cash management guys). We went over some stuff, got some ideas, and then went to work on fixing them. After the Join.me session, we switched over and jumped on a GoToMeeting session. We looked at code and worked on making some new changes to flow and processes.

	Shop 2285		Calvin Time	2/2/2017

	Shop 2224		Russell Moore	2/2/2017	On a GoToMeeting session with Shawn for a little bit. We were talking about payroll issues, logic issues, and user input and data issues. After that, I got on with Russell and we met over a Zoom session. Russell and I talked the whole time about our model and what we are and are not. There is a small disconnect between where we are headed and what we are vs. where we could go and who we really are. See attached for a bunch of notes.

	Shop 2217		General	2/2/2017	Emails and tech support. Working on the logic for the bulk print cart labels. I had taken out some of the logic and removed some needed pieces. Putting it back in. I guess that I got too aggressive in the clean-up effort the other day... :)

	Shop 2300		SHAWN	2/2/2017	On a brief meeting with Shawn and on to more bulk print cart label stuff. Finishing things up and did some testing. Pushed up code and let key persons know about the updates. The piece that was missing was sub inventory attributes and custom mappings to top, middle, bottom left, and bottom right mappings. As a side note, I can feel that pressures are mounting. I've got a lot of my guys very busy and things just keep coming. It feels like another storm is coming... We are also seeing an increased sense of requirements and huge expectations. All possible but we don't have that stuff done and integrated yet. That adds to the pressure.

	Shop 2247		Brandon out of the office all day	2/3/2017

	Shop 4960		Virtual Post-It Note	2/4/2017	-We need a virtual payee/user list so we could find people from a central spot. Search by name, email, or phone number.

	Shop 2237		Adilas Time	2/6/2017	On a GoToMeeting session with Alan and Steve. We started out and touched base and then worked on our own projects. After we got some email and other stuff done, we met back together and looked at Alan's progress on the Converge payment integration. Alan gave a demo to Steve and I we made a couple of small suggestions. Alan has been doing great and his projects have been doing awesome. After that, Steve and I jumped on and looked at some of his code. We made a couple minor tweaks here and there and got him going. We got a call from Shannon asking about a tax question. We are seeing a need to be able to expand the tax settings and percentages to more decimal levels. That may sound easy, but it would cascade through the system and would require us to visit a number of pages. Both on the setting level and on the calculation level and display level. We ended the meeting by talking about industry specific skins, packages, and settings. Steve has done a great job of skinning things for the MMJ industry. That little project has taken 3+ years and countless hours. If we could do that for one industry, that would be fun to plan and coordinate things to do it for other industries. That may be down the line a bit, but hopefully on the horizon. The secret is "platform" and being able to build off of a steady platform.

	Shop 2243		Lunch	2/6/2017

	Shop 5027		Virtual Post-It Note	2/6/2017	-What about Custom projects? -Mark Myer with Arizona Organix Customer upload, CSU, or FTP info $500 to $750 -Renee Grossman with Quotes High Q -Daily announcement page. -Setting to lock down cart . . . -Taxes need to be expanded. -On taxes and tax settings we need more decimal places (go from 2 to 5) -This goes to the percent ages and the calculations for the percentages. -We are seeing a fined tooth detail mentality v.s. an older batch process mode. Interesting the switch -"We are looking for a platform that does everything" a client that Steve was talking to.

	Shop 2286		Calvin Time	2/6/2017

	Shop 2301		Gernal	2/6/2017	Working on general to do list stuff. Lots of emails and recording notes. Did a couple of tech support calls and what not. Nothing major.

	Shop 2274		Shawn	2/6/2017

	Shop 2302		money updates	2/6/2017	On a GoToMeeting session with Bryan. We jumped on a number of conference calls with clients and with IT tech people at the server farm. We talked about a number of different projects and bounced around from project to project. Basically a multi directional work session. Towards the end of the session, Dave Forbis came over. We talked about some of the existing projects and who is doing what. We then talked about some marketing ideas and how to push things forward on the same page. Currently, we have lots of people pushing on different things, but nobody is really calling the shots and coordinating things. We could get a lot more done if we were a little bit more organized and on the same page.

	Shop 2307		Product data import	2/7/2017	Doing a product/item data import for a client. Setting up new vendors, item categories, and doing the digital migration. Invoiced the client and let the rep know that the items were in the system.

	Shop 2238		Adilas Time	2/7/2017	The main session was a GoToMeeting session with Danny, Steve, Kelly, and Brandon. Prior to that we redid the data import for another company. Apparently, the rep wanted us to import the products into one company but didn't really state that in the instructions. We did the import and then got an email saying that they really wanted it pushed into another company. We had to flip flop some things and get that taken care of. We had to take a couple of tech support calls and helped Steve with some of his code logic. We finally got started on our main meeting about 10 am. Big brainstorming meeting on the custom label app and where we could take it. Tons of good ideas from Kelly, Steve, and Danny. I was taking notes and drawing and they were talking and brainstorming. See attached for the first draft of the notes. Expand... As a side note... On 2/13/17 - Alan Williams mentioned that we could use a JavaScript canvas object and then draw and write over that. That is a great idea and I didn't even think about that. We have used canvas objects to catch digital signatures and such. We have even taken that canvas object and then saved it as a standalone image.

	Shop 2244		Lunch	2/7/2017

	Shop 2287		Calvin Time	2/7/2017

	Shop 2308		General	2/7/2017	Reviewing notes and drawing from some of the past meetings. Emails and other basic stuff.

	Shop 2225		Russell Moore	2/7/2017	On a Zoom session with Russell. We fixed some CSS and then spent most of the rest of the session working on being able to select and control the site colors through CSS. This is new based off of the new snow owl theme from AFB. The new color changes should really help. Russell and I also talked a little bit about client demands and how to manage the requirements that are placed upon us. Sometime it can get pretty intense. Normally, it is Russell helping me out because I'm super stressed. Today, I think I was able to him out a bit. At the same time, some of the new stress was probably coming from me and my requests. Anyways, it worked out ok and we are making progress.

	Shop 2303		SHAWN	2/7/2017	On a call with Shawn. He is kinda stressed due to some PDF forms and getting the printing to line up correctly. We talked on the phone and I authorized him to go get some pre-printed forms for testing purposes. After that, I went in and did some bills and prepped some stuff to Shawn paid on his payroll commission stuff. I have to visit multiple servers to get all of the numbers.

	Shop 2306		Doing some quotes with Shannon	2/7/2017	More emails and monitoring the data 4 server. Shawn came over and we chatted for a bit. We are all learning tons of lessons. Hopefully, we'll figure it all out. I was not able to get with Shannon to do any quotes. Lots of emails, tech support, and text messages back and forth.

	Shop 2239		Adilas Time	2/8/2017	GoToMeeting session with Steve, Eric, Alan, and Brandon. The subject was smart cart logic, promotion codes, QR codes, campaigns, in-store credit, gift cards, etc. See the attached notes for more details. We also spent some time and talked about reoccurring percentage models and how to pay for these new features. Steve lightly extended some options to Eric during the call. Expand...

	Shop 2245		Lunch	2/8/2017

	Shop 2288		Calvin Time	2/8/2017	On a phone call and then a Zoom meeting helping Calvin get some live data for testing. He is working on the admin time clock stuff and pulling time clock records. We went in and did a quick export for departments, payees, payee to departments, and time cards. We then ran some local code to make sure all was well. We didn't finish but at least got him headed in a good direction.

	Shop 2304		Meeting with the AFB team	2/8/2017	On a GoToMeeting session with the AFB team. We had Steve, Chris, Russell, Brandon, and Shari O. on the call. We started off talking about Chris' needs for sub inventory on the ecommerce level. He is clothing and retail and needs colors and sizes. We talked about some options and recorded some small notes. After that, we talked tons of sales stuff, model stuff, and what is our next move. See the attached set of notes for more info. Great session and we recorded some ideas on packages, sales models, and how we could combine forces in order to increase sales for adilas. In talking about different package sizes and different industries, we did go over a concept of corp-based permissions vs. user-based permissions. If we took things clear out to the corp level, we could virtually hide (smoke and mirrors) or take parts away to simplify the options. As a side note, when dealing with custom... not everything is adding. Sometimes removing things really helps to make the pathway clearer.

	Shop 2309		Full circle planning/server cleanup	2/8/2017	On a GoToMeeting session with Bryan. We were looking into the data 7 server and what is needed there. We were checking the Application files, login pages, etc. We then finished up the meeting by talking about other projects. One that we looked into was Bryan's menu board project. We made a couple of formatting changes and added in some dynamics.

	Shop 2312		General	2/8/2017	Emails, notes from the day, and light tech support. Uploading documents, notes, and helping to communicate next steps and such. Clean-up and recording notes.

	Shop 2240		Adilas Time	2/9/2017	Steve was talking about some different ways to run with projects. Whole and full projects vs. smaller planned out pieces. Kinda like just in time planning. - From Steve - Adilas is done. It is finished at the level it is at. We can sell it right now. It is not broken. If we want, we can break a small portion and then fix that. Basically, build on what we have. - Think of additions to a house. We take small steps and keep advancing the ball. - Plan the work and work the plan. - We have some great people that are involved. Let's help to focus and channel the talent that we have. Our job (Steve and I) needs to be helping them focus on a task at hand. - We would love to work towards a 4-day a week schedule. - We would like to add another $1,000 a month for each of us. - Part of the focus is helping our people (our family) get to the numbers or financial level they need to be at. Help to stabilize the playing field. - Steve and I will become more of the project managers. We plan and then help our guys/gals push the plan and/or project. - A philosophy for business - a delayed response can be strategic at times. - At some point we need to get some money for cleaning up the mess some of these clients leave with data and data storage. We may even need to develop a back-up plan. - The emotional state of our mind - that could be good and bad. - Sometimes the pressure is like a mini blowtorch - this is like job security. - Laundry and dishes... we can only do so much per load. Keep pushing forward and load what we can. We can use some of our people and then load them up to the level they can handle. - We have some really good people that we are working with... That is a huge part of the puzzle. - If you help enough people get what they want, you end up getting what you want. - Proactive customer care... reach out vs. waiting for the emergency call. What about other proactive options... care for what we have and do preventative maintenance stuff. - When we do our planning... cut out the white noise... give them just what they want. Break things down into pieces and baby step it. We shift through the mess and help the cream rise to the top. Small return and report type tasks. After the brainstorming meeting between Steve and I, we jumped in and did more work on the custom label app. Danny, Steve, and I worked together and even had Molly join and make some comments. A number of new comments were added to the custom label app notes (see attached). Towards the end of the meeting, Danny and I were going over the adilas pricing matrix document (older MS Excel file). This pricing matrix was built quite awhile back but was never used. It has some good potential and took into consideration number of employees, number of invoices, number of locations, special add-on's, and other services that we provide. It was a good pricing sheet as well as a good sales tool to help remind the people of what they are getting that we aren't charging for. See attached for a copy of the doc in the current form.

	Shop 2246		Lunch	2/9/2017

	Shop 5028		Virtual Post-It Note	2/9/2017	-On the elements of time, turn the gifts (cal, time slot, group, horizontal) into png's -On taxes and cakes . . . we may need a rounding field to show the diffs. currently, we round the state tax . . . -POS -Accounts Payable -Accounts Receivable -Financial stuff Pay roll -E commerce -Not discounting -Up selling -Corp-wide permissions -Start trying things for sales. -We also need to tweak out the elements of time home page and the white calendar - put a var in the application.cfm page or the basic_css.cfm page.

	Shop 2289		Calvin Time	2/9/2017	Quick phone call with Calvin. We touched base on a couple of things and just chatted. Nothing major.

	Shop 2313		Server Setup	2/9/2017	On a GoToMeeting session with Bryan. We were working on the new data 7 server. We were transferring tax tables to other servers. Other small changes.

	Shop 2226		Russell Moore	2/9/2017	On a Zoom session with Russell. One of the first things we talked about was security... The goal there is to push them (our users) towards the wall. Just like we used to say, "Play at the wall". That is huge. That is where outside parties play. We then spent most of the rest of the session working on the new pick a color option for the AFB snow owl theme. Tons of different options. We spent tons of time tweaking out colors, checking things, and testing different pages, etc. Here are some of the other things that we talked about. - Only change what you need to or want, leave all the rest as defaults. On his new color pickers, you can pick and choose any color you want. You don’t have to do all of them, just pick and choose what you want. Instead of chewing the whole thing... just take one small bite at a time. Great concept. - On figuring out your target – use the bell curve model. You have outsides, the 80% (still on the outsides but part of the main meat), and the main 60% (the middle of the curve). Defaults in the middle and custom on the outside.

	Shop 2280		Working with Steve	2/9/2017	On a GoToMeeting session with Steve and Russell looking over new custom look and feel options. We spent most of the time looking at the new Snow Owl theme and playing with the new settings. - One of the questions that Steve had was related to creating a dashboard. Very similar to building custom labels, we need to be able to build out custom dashboards. - We are seeing more needs to be able to customize the whole user interface. From buttons, to CSS, to backgrounds, to colors, to navigation. - The user interface is huge... it is the application. I would still love to build out the icons and/or graphic homepages. I have some samples and small drawings back in the developer's notebook. The graphic homepages are somewhat tied into the GPS core layout graphic. - On with Shannon. We had questions on QuickBooks and playing well there. We had questions on being able to make and control our own child barcode values. We also had some other questions on daily announcements and locking down the cart to not allow invoices out of the cart without full payment. Shannon took some notes on these in a different element of time. - Steve and Shannon were working on some things and talking about tech support vs. customer care. We then talked about some smoke and mirror stuff with barcodes and QR codes. The barcode and/or QR code still holds the old sub id but we then show a different display value. Good stuff. - We need to help update some of the older legacy accounts and get them on to the new tools and features. That is a whole new level of training and customer support and customer care. - We need a master list of features, advantages, and benefits. We have a good start on the older user guide stuff. We need to keep updating it. We also have a web page called tools and features. The problem with both of these is they haven't been updated since 2010 (ish). :) Time for a change in the wind... - We need to use elements of time more for recording the notes. If we use other outside files, we end up having a small disconnect and it is not searchable. Use the tools we have.

	Shop 2248		Brandon out of the office all day	2/10/2017

	Shop 2251		Adilas Time	2/13/2017	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.

	Shop 2261		Lunch	2/13/2017

	Shop 5029		Virtual Post-It Note	2/13/2017	-Get Steve and Danny on Git. - We need to add Sub notes and comments Searchable by the quick search options. Maybe expand to all subs of time.

	Shop 2290		Calvin Time	2/13/2017

	Shop 2315		Custom checkout process	2/13/2017	On a GoToMeeting session with Bryan. We ended up talking about how to add a convenience fee to a checkout process. We went over some ideas and I pointed him to some existing code and such.

	Shop 2275		Shawn	2/13/2017	On a GoToMeeting session with Shawn. Working with PDF's and trying to remove passwords and other security features. We were trying to work on alignment issues for some government based forms.

	Shop 2316		Server Setup: Data 7	2/13/2017	On a GoToMeeting session with Bryan adding in code to help with his custom project to add a convenience fee to the cart during the checkout process if a certain money type was selected. We were actually coding the page and making sure we had all of the pieces. We didn't get it all done, but making progress.

	Shop 2317		Planning and upload tool	2/13/2017	Meeting with Steve and then Will after that. We changed the focus of the planning session. It was going to be the custom label app but we switched to a custom upload project for customer data (csv file). Expand...

	Shop 2252		Adilas Time	2/14/2017	On a GoToMeeting session with Steve and Nick. Shawn popped in for a bit as well. Our original goal was to make a quick fix on the price override switch for the add to cart page. We were then going to do some brainstorming on the changes we need for the email feature. That never happened. We spent the whole time working on the shopping cart price override option and feature. We'll have to hit the email stuff later on.

	Shop 2262		Lunch	2/14/2017

	Shop 2291		Calvin Time	2/14/2017

	Shop 2319		CCComply- Charley Ford	2/14/2017	On a GoToMeeting session with Bryan. We were looking into some of his code logic that added in a fee upon usage of a certain money type. We found an error with the money type id's. He will fix it and get back with me.

	Shop 2227		Russell Moore	2/14/2017	Russell was slightly delayed for our meeting today. I did emails and helped Steve check out some code. Dave Forbis also came over and we chatted for 15 minutes or so. After that, Russell and I did a Zoom session for about 45 minutes. He showed me the progress he is making on the change colors for the CSS stuff for the new snow owl theme. Pretty cool. Anyways, good session.

	Shop 2320		Server Setup: Data 7	2/14/2017	On a GoToMeeting session with Bryan. We worked on flushing his money type tables and getting his stored settings to reflect the correct id numbers. Just cleaning up some differences between the testing environment and the live environment.

	Shop 2336		Scanning and entering expenses	2/15/2017	Scanning credit card bills, entering expenses, and interest payments. Paying bills and writing checks.

	Shop 2253		Adilas Time	2/15/2017	On a GoToMeeting session with Alan. We went over some of the existing code that interfaces between a kiosk and a bank note recycler (BNR). We drew out some diagrams and talked about the old flow vs. where we want things to go. I then did some light research on in-store credit and loyalty points. Lots of good stuff out in the adilas university area. It may take some time to do the research and gather things up. I can see the need for someone, most likely me, to do that research and bring things together. There were also a number of entries here in the adilas shop that dealt with loyalty points. Lots of options to search. Steve popped in and we started talking about new corp stats and getting some of that information tied in. We talked about adding in some new fields to the master corp table. We talked about multiple salespersons, commission percentages, tying to customers, reoccurring invoices, etc. We then started to talk about dynamic interfaces, quadrants, navigation, accordion stuff, frames, drag and drop stuff, etc. We talked about flash interfaces, skins, themes, etc. We would love to build out some of the graphical carts, interfaces, navigation options, etc. Steve was even talking about how his ColdFusion Builder (development environment) allows for docking, moving, sizing, panels, expanding frames, minimizing, maximizing, show/hide options, etc. Basically, a fully functional and controllable interface, data sub sets, and custom page layouts. We started to revisit loyalty points and special accounts with Eric. We got into the smart cart logic and a virtual pricing engine. We also started talking about how to build it out and how to record where things are coming from (QR codes, barcodes, buttons, certain pages, etc.). We talked about using the custom cart black box stuff... "session.myCart_st.myCustomCodeInfo_st" and then making and assigning custom arrays, lists, and other stored values. Light brainstorming with Steve and Eric on the pricing engine and possible other values and variables for the smart cart logic: new fields we could set on the whole cart level (new internal fields and flags)... part_id special_flag allow_price_recalc item_to_cart_source visual_uofm_id visual_uofm_initials visual_description item_size item_color item_weight locked_original_price locked_original_tax_category_id on the item level... what about special flags and options... allow_discounts exclude_from_discounts allow_price_recalc counts_for_loyalty use_pricing_matrix on the child level... what about special flags and options... allow_discounts exclude_from_discounts allow_price_recalc counts_for_loyalty use_pricing_matrix - Using simple lists with line references. setting up lists, dummy lists, real lists, list appends, list finds, etc. simple mini database stuff. - These lists will be added into a virtual cart black box piece of sorts - Speaking of lists... maybe we build a list of rules and exceptions - what about checkboxes and building dynamic lists. Using checkboxes allows us to show multiple things and still get a list of entered values. We love the simple rules and options. - As a side note, they used a pencil up in space until they could figure out how to get a pen to work (temperature, gravity, etc.). It was that simple.

	Shop 2263		Lunch	2/15/2017

	Shop 5030		Virtual Post-It Note	2/15/2017	-Put up digital copies of LTF for both Mac and Windows. Make it pretty obvious - Give it away and let people use it. -It might be fun to put it on a tablet and see how much it does . . .

	Shop 2292		General	2/15/2017	Steve and I were talking... we kinda need some honey to sweeten the deal with reps and developers. We are using the shared percentage of monthly revenue stuff plus a basic hourly. Mixing and blending.

	Shop 2311		Meeting with the AFB team	2/15/2017	On a GoToMeeting session with Chris, Russell, Steve, and Shari O. We met and talked about some more sales and marketing options. See the attached notes for more information. Steve and the others keep going after I dropped off. We had a problem with the data 0 server and I had to jump off and do some fire fighting to help a history table that got locked and was issuing out duplicate primary key id numbers. - Idea from Steve, Russell, and Chris - What if we turn some of the existing places of business into real adilas training centers. For example: Say a retail shop that uses adilas - they could charge for training some of the new people to use the system. They, the new clients, then pay to come and learn on site with people who know how to use the system. - What about pitching a pilot program where an existing company that uses adilas becomes a virtual training center of sorts. This could be a great sales tool for the owners and their employees. - This new program is more of a shadow and mentoring model.

	Shop 2321		Fixing a bug and server problem on data 0	2/15/2017	We got a number of calls that the data 0 server was having problems with invoices. We shut it down and so did Newtek. It was struggling for awhile and we finally found that it was a locked table that was dishing out duplicate primary keys. Basically, it seems like the database was part-way through a transaction and recorded a key auto increment id in one place but not in another. Then when it came back up, it was tripping on it self. This little hiccup was on the customer_history table. That table shutdown all quoting, all invoicing, all assignments for element of time, all add/edits of customer info, all add/edits for customer logs, and all add/edits for additional customer contacts. It effected ecommerce, reoccurring invoicing, etc. Pretty pivotal. We got everything all fixed and back up but it was pretty crazy and intense. As a side note, we may want to go in and wrap that section with its own try/catch stuff so that if an error occurs, it just softly floats over that section without causing an error. That could be good and bad. Anyways, just making a note. We ended up resetting the auto increment id number and then re-pushed up new code. We recorded notes and let our developer team know what was going on.

	Shop 2254		Adilas Time	2/16/2017	On a GoToMeeting session with Steve, Nick, and Eric. We stared out the day and Steve updated me on the rest of the conversation with the AFB guys. It sounds like we would like to do a pilot program that turns existing adilas clients into a virtual adilas on-site training center where clients could pay to be trained by people in their field. That has tons of potential and could be super awesome. It is just an ideas and concept right now, but it could work and be very effective in the future. On the loyalty points and special accounts... maybe treat it like elements of time where you could setup as many templates as needed and then you have these virtual accounts for all kinds of things like: gift cards, loyalty points, affiliate programs, in-store credits, vendor credits, rewards points, etc. Let the people setup and maintain their own mini virtual accounts. Eric and Steve chatted about the loyalty points project and some of the funding plans for getting it done. We also reached out to Nick and touched base on some of the projects that he is working on. He is going to be changing gears from API's back to internal project such as the black box and the adilas user guide stuff. We have tons of projects that are needed and/or available. Towards the end of the session, we all broke out into our own little work sessions. I was scanning credit card statements and entering interest expenses. Steve was doing phone calls and Nick and Eric were doing their stuff. Good little work session.

	Shop 2264		Lunch	2/16/2017

	Shop 2338		Leaf Data error messages	2/16/2017	We're getting error messages on two of the Leaf Data pages that have been built out in the last six weeks. The first one is Leaf Data MMEs. This page worked just fine locally and live until about two weeks ago, when it just randomly stopped. The error message here is 401: Unauthorized. This is odd, given that ten other pages use those same credentials for GETs on the Leaf Data API, but they all work fine. The second one is Leaf Data Inventory Adjustment. The GET works fine, but when submitting a POST request we get a 301: Moved Permanently message. The URL and all elements of the request were taken directly from the API test page. Furthermore, when we take the exact piece of JSON that we are submitting through the Adilas page and try to submit it through the API test page, we get a 500 Server Error message.

	Shop 5032		Virtual Post-It Note	2/16/2017	-On emails from adilas . . . put that the email is sent from a non reply address - help them know to contact the company directly. -On the export to Excel for Customers, we need to check for a slash character. It is making the Export fail.

	Shop 2293		Calvin Time	2/16/2017

	Shop 2322		Alan Time	2/16/2017	On a GoToMeeting session with Alan. We talked about his research on the BNR (cash handling stuff) and what that project will take. We then flipped and started talking about world building stuff and splitting apart the database into corp-specific or world-specific pieces. That is huge and big part of where we are headed. We setup a saved favorite report inside of the adilas university site for world building. That will make it easier to get to. We also setup a saved favorite here in the adilas shop for world building research.

	Shop 2228		Russell Moore	2/16/2017	On a Zoom session with Russell. He was showing me the progress on the snow owl theme and being able to change the CSS and the corp look and feel. He is doing great. We also briefly spoke about some sales ideas and how to push the ecommerce to a bigger and better level. Exciting times.

	Shop 2318		Black Box Project/ Metrc and Leaf Data	2/16/2017	Pushing up credit card statements and scans. Recording expenses for adilas. I then met up with Nick and we did a GoToMeeting session to help merge in some code to help with sub inventory dates and showing the correct format. Small changes but it affected about 40+ files.

	Shop 2249		Brandon out of the office all day	2/17/2017

	Shop 2339		Working with Shawn on PDF forms	2/18/2017	Shawn came over and we were working on new PDF forms. We are having major difficulties with printing PDF's. We can populate the forms, super easy. The problem we are having is printing and alignment on digital overlays. We have so many variables between printer types, brand, margin settings, and even paper sizes and such. We talked about taking the overlays to a Flash level where we could control the _x and _y coordinates like we do on the check write system. We are seeing more and more needs to build out custom printing options. After that, we did a small session on the current email and communication problem we are having from inside of adilas (emailing invoices, quotes, PO's, and statements). We took a picture of the brainstorming session and it is on my phone. See attached for a copy of the whiteboard session.

	Shop 5033		Virtual Post-It Note	2/18/2017	-On email setup, we could add more settings per corp and/or use a mini black box page to handle custom messages and/or addresses.

	Shop 2255		Brandon out of the office all day	2/20/2017

	Shop 2256		Adilas Time	2/21/2017	On a GoToMeeting session with with Steve and Danny. We worked on some issues from yesterday and servers that were running slow. We then helped Steve with some flex grid stuff and then onto some logic to switch between the snow owl theme and the other classic themes. We are seeing more and more needs there (coding for both older classic pages and newer powerful and visual options). - Steve would like us (Alan and I) to check out the MySQL enterprise edition before we do the world building and splitting of databases. Currently we are using the MySQL community edition.

	Shop 2266		Lunch	2/21/2017

	Shop 5034		Virtual Post-It Note	2/21/2017	-Check into both square and stripe for new credit card API's and merchant processing.

	Shop 2295		Calvin Time	2/21/2017

	Shop 2323		Alan Time	2/21/2017

	Shop 2229		Russell Moore	2/21/2017	On a Zoom session with Russell. - It is not as important that you know all of the skills but it is important that you know people who have those skills. Basically, surround yourself with talented and awesome people. - digital dashboards, visual homepages, and using Ajax, jquery, ect. Creating places and pages where admin persons hang out and watch what is going on. The virtual war room and how things are playing out. - This may need to be things like watchers, feeders, and live data feeds. Maybe even stand-alone declarations and other hardcoded or set pieces. - Build on what you have. Focus on the operational side of things. Put that horse before the cart. - Shortcuts and quick paths. Help people get things done, quick, and in bulk. You may need to provide both the standard path and the quick path. The quick paths only catch smaller and required data. The standard paths will show more flow, logic, validation, and information. - Russell's quick 3 - powerful, easy, and looks good - if you get all 3, the product will sell. - Quick setup options and quick paths... point and click, add things in bulk, don't worry about all of the other tie-ins. Add items, assume locations, loosen setting to be able to sell without a PO or an incoming fully set path. - If you want the full data assembly line concept... go for it. You may also need to allow more choices even though if they choose the quick path, it may be missing some things. It comes back to agency. - Maybe let people put things where ever they want, then when they want more details and data, it will already be there. Often we try to feed everybody everything... we need to cater that and only feed them what they need. Try to point them to what would be best, but let them make those choices. - Remember the bell curve analogy. You will have some that will be on the outside (outliers), some that will be mostly there, and some that hit right in the middle. Shoot for the 60-80% ratios. The other pieces still exists, but we have to shoot for where the main spot or meat is. Capture the main bulk of what is needed.

	Shop 2333		Alan Time	2/21/2017	Alan came over to my house and we looked into the database world building project. This is where we will be splitting up databases and changing the underlying structure of what and how we store the data. We talked about a number of key things. Here is a small list as a reminder: - We started with some history and how in 2010, we started to map out the system. As we did that, we found that we were missing a huge date/time type component. - We lightly went over the interactive map graphic and the GPS core graphics and how they play in. Basically, as we get deeper, we are starting to see where things are going. - We talked about the current model and how the serves are setup with one shared database and one set of code. The new model will have a controller database and then smaller solar system (smaller groups of corporations). We still want the one-to-many relationship between one set of code and multiple databases. - We started talking about the ideal (a full and complete rewrite) vs. a smaller database only focus. Lots of good discussion there. We came up with some smaller barriers to the full and/or complete rewrite. They were: - >>> Time - time to finish, how long it will or could take. - >>> Framework (language) and technology to use. - >>> Talent and training for a project of this size. - >>> Multiple unknowns - scale, goals, funding, new and changing features. - >>> Multiple people that are doing the code. - >>> Lack of leadership/organization. - >>> API socket stuff (what we use and what they use). - >>> Everything ties to time. - We also covered some history on how we built and then broke model after model. We talked about how our current model has been built upon for the last 10+ years. We talked about how it is breaking in some places, fracturing in others, and general state of the platform. - We talked about going clear back to the login level to get things dialed in for the new database changes. This will tie into a corp key that starts the login process. We still need to buff this section out and get a better detailed plan. The concept is there, but the details are still kinda fuzzy. - Alan and I talked about database storage, optimization, and even I/O reads and writes and how to get better benefit out of the database models. We got kinda techy and even talked about changes, new indexes, and such. - Part of the discussion was talking about how adilas is somewhat of an add-on type product. We have a core or base and then add and virtually bolt on new features, changes, patches, etc. As we build and break things, we then start with what we have as the new core. It builds and builds as we go. - The last part of the conversation was dealing with existing code, pages, prep work, and where and how to find that. I will include a couple of word docs that we started (back a couple of years ago August/September of 2014). They are dealing with the database and what the different tables are and what the different fields do, hold, and how they interconnect. - One of our next goals is to get organized and look more into the cluster controller databases and what is needed. there. - As a side note, we talked about finishing up the first round using normal web code and then have Calvin translate that logic into his auto process (database to database) software tool. Here are some files that have been started as part of this project. - >>> top_secret/secure/master_corp_home.cfm - starting page for setting up the other cluster and solar system levels. - >>> top_secret/secure/create_new_cluster.cfm - create new cluster (domain or box level database - level 3) - >>> top_secret/secure/create_new_solar_system.cfm - create new solar system (database within a cluster - level 4) - >>> top_secret/secure/create_new_solar_system_part_2.cfm - migrate data from older shared database to new solar system database. - >>> There are also tons of cfc's that have been started to help with this process. They are top_secret/cfc/admin.cfc, admin_2, 3, 4, 5, A2B, C, D2I, J2O, P, Q2R, S, T, U2Z (all of these files have top_secret/cfc/admin_[whatever].cfc.

	Shop 2257		Adilas Time	2/22/2017	We started out the GoToMeeting talking with Alan about MySQL and database stuff. I then helped Steve with some custom reports. Recording notes from yesterday and getting things semi-caught up. I then jumped in and did some research on database project for the world building piece. Lots of good data on element of time id # 2333. Eric joined us around 11 am to talk about loyalty points and special accounts. - Eric would like to keep it simple. - A possible configuration form - stored in JSON. The JSON would then work with a service layer. The service layers could then have a version number. The JSON would hold all of the setup values that are needed. Basically one record per special account type. - Continue calculating points based on sales. - We talked about global start dates vs. start dates per account. - Other fields we may want to track... - >>> corp, name of the account, what item loads it, what item unloads it, factors (multiplier), quantity based, dollar based, what type of account (asset, liability, virtual), account number, description, customer, vendor, user, generic person, running total, exceptions, start dates, end dates, conditions (rules), extra flags, etc. - Eric would like to use some simple lists and SQL in statements. This could be lists of items, categories, customer types, etc. Simple lists that hold multiple pieces. - We want the users to define their own program and setup the rules. This concept would also translate into the smart cart logic. User-facing and configurable options. - Eric uses iTunes and would like to make a similar type function to allow the users to setup their own rules and such. Each data fields has options such as contains, ends with, does not contain, is great than, less than, equal to, like... etc. They you set the criteria. You basically get to add as many new rules as you need. Add as many rules and criteria as needed. You can set limits and control other values. - Eric is thinking about customer types, discounts, exclusions (items and quantities), inclusions (items and quantities), item categories (include or exclude), date ranges, time ranges, ratios, limits, reusable, etc. What about multi-level cascading criteria such as referral programs, direct sales, affiliate programs, etc. - We are maybe seeing 3 tables: main accounts, account criteria settings, and account transactions. A fourth table might be for sales and special promotions. This needs to be thought out a bit more. - What about rounding for points and credits? Round things, don't round things, what are the settings. - What about data qualifications such as only use customers that have a valid email, cell phone, and address. Otherwise, they don't qualify. - What about data over rides. If x field has y value, this either allows or doesn't allow things to happen based on that data value. Basically, a data driven value that either allows and/or denies certain logic to play out. - What about combining points and credits over multiple corps. We might have lists of corps, lists of items, lists of part categories, lists of customer types, etc. We need to allow for cross corp stuff and allow them to write things into the code. They will need to look up Id's and build the correct lists. Also, we need to validate that corp x can and should be able to talk with corp y. They also need to be on the same server (as of right now). We may need to allow for cross corp passwords or special fields that have the same value (kinda like a virtual password or acceptance option). We then need to total up points and credits for multiple corps. That could be a little bit funky. What about recording the details. We need to keep running totals to allow this to work fully. As a side note, we may do this in a later version. Maybe just stick to single corp stuff for right now. We do need to look at cross corp security and allowing cross corp actions. We already have some of this built in for cross corp sales, PO's, invoices, etc. Look into that. - Think of the bell curve model - develop to the peak and basic audience first. Then look at the outside pieces as custom and/or extensions. - Sub criteria drop-down options: inventory items, item categories, customer id's, customer types, special fields (state, license number, customer tax id, cell phone, email, home phone, terms, etc.). As a side note, what about date/time features. - Eric could end up helping clients setup their more complicated rewards and special account stuff. - Do things run out and/or how do you flush things? Say points earned but not used and then the program ending or something like that. What about transfer of points and/or credits? - What about doubling points during certain sales and/or promotions. What about more rules based on date/time stuff. - We are still seeing that promotions and/or special sales need to be a separate table. We would then need to tie into those tables. - Eric started talking about aggregate functions, analytics, and other business intelligence models. We could help them see the traction and/or activity on sales, promotions, campaigns, etc. Data and the analytics are huge... :) - On the analytics, dashboards, and summary reports we need to move away from the transactional data and show more of the summary and aggregate data. We are seeing this need on all fronts.

	Shop 2267		Lunch	2/22/2017

	Shop 2296		Calvin Time	2/22/2017	Quick phone call to touch base on upcoming plans.

	Shop 2334		Alan Time	2/22/2017	On a GoToMeeting session with Alan. We went over some existing flow of what we have and then spent the rest of the time going over the cluster controller database. We looked at a number of database tables and then drew scenarios, relationships, and went through some general use cases. We had some questions on a master user list and decided that it would be best to have a cluster level list vs. a huge master list. Expand.

	Shop 2337		Server Setup: Data 7	2/22/2017	On a GoToMeeting session with Bryan. Working on setting up the new data 7 server. We checked a few things out and I got him started on checking for new files. Doing somewhat of a clean-up of sorts.

	Shop 2342		Quoting for Branding	2/22/2017	Dave Forbis came over and we worked on some custom options for the adilas branding company. They are a 3rd party entity that is trying to get real-time inventory tracking for some of the supplies (not the main items) that are being used to package the products. If they can get real-time inventory tracking for the supplies and such, they can help fulfill the orders and provide better customer service. Lots of drawing and concepting.

	Shop 2352		Final server setup for data 7	2/23/2017	Online meeting with Bryan. We pushed up some new files and made some changes. Trying to get the data 7 server online. We ran into a domain problem. Other than that, it was working good.

	Shop 2258		Adilas Time	2/23/2017	On a GoToMeeting session with Steve. Calvin joined us just after 11 am. Steve and I started out the morning and got his new report pages up and running. We had to add some variables to calculate some totals. After that, we reviewed an older video and took notes from a prior session between Steve, Calvin, and I using QR codes to do mini conversions. We took some notes and tried to prep for a meeting with Calvin. See elements of time # 2157 and 2167 for notes and other ideas. This current element of time has a number of media/content pieces attached. There is a video recording of the session between Steve, Calvin, and I - It has some graphics, drawing, and some notes. We attached all of those pieces, graphics and notes from our session. The whole thing was dealing with QR codes, mini conversions, sub inventory attributes, breaking things into smaller pieces, and other incoming pieces. Good conversations. Here is a link to the media/content for this element of time. It has tons of special notes about the graphics, the actual notes, and the video link. Please read the next page to get a deeper look at what was being discussed. - A couple of things of interest were... horizontal recording of the data (fixed columns) vs. vertical recording of the data (dynamic one-to-many database records). We want to go vertical as much as possible. It keeps the relationships smaller and tighter. - Dynamic flow and/or processes - We what to allow our users/clients to define what their virtual checkpoints are. This relates back to the data assembly line concept. If we can define the checkpoints, it should help with flow and quality control. If we could set those checkpoints up dynamically (customer flow) that would be awesome. - The power of a relational model. Instead of duplicating tons and tons of data, you just create one-to-many relationships and allow the data to flow both up and down the chain. You only store what you need vs. a huge pre-set grid and/or matrix. It stays small but you still capture all that you need. - We are seeing a converging of many projects for the POS (point of sale) system hitting or being worked on at the same time... They are: smart cart logic, sales and promotions, custom labels, sub inventory, mini conversions, discounts, tiered pricing, loyalty points, and other special account tracking options. See media/content for a quick drawing of the converging of projects.

	Shop 2268		Lunch	2/23/2017

	Shop 2297		Calvin Time	2/23/2017	Calvin joined our GoToMeeting from 11:15 am (ish) to about 1 pm. See other notes.

	Shop 2324		Alan Time	2/23/2017	Quick GoToMeeting session with Alan. We went over some auto discounting stuff from inside the ecommerce shopping cart. We talked about standalone discounts vs. in-line discounts. We looked at some code samples and talked about what we wanted to do. Alan may use standalone discounts for the time being.

	Shop 2230		Russell Moore	2/23/2017	Spent some time working on general stuff, cleaning-up elements of time, recording notes, uploading media/content for projects, emails, and what not. Russell and I got on a Zoom session for about 30 minutes and Russell showed me some of the progress with the pick a color stuff for the snow owl theme. He is currently working on being able to tweak the CSS for the buttons, call out rows, and error/success messages. This deals with rounded corners, pointed corners, square corners, etc. Tons of visual options for the buttons and bars.

	Shop 2354		General	2/23/2017	Recording notes, phone calls, emails, and paying bills.

	Shop 2355		Data Migration	2/23/2017	Custom data migration for a company. There were over 600+ items. We had to go in and do some data combing to get things right. We also had to fix all 600+ items to have shorter item number values. Over half of the items had item names that were longer than the character max of 50 characters. I had to run some special code to make the changes. I finished the upload and invoiced the client.

	Shop 2250		Brandon out of the office all day	2/24/2017

	Shop 2259		Adilas Time	2/27/2017	On a GoToMeeting session with Steve and Alan. We were mostly working on our own things. I helped Steve with some CSS questions. We also talked about taking on some new developers that already have some skills in other languages and such. We are going to restructure things a little bit different this time around. I took a sub inventory page and changed up the page flow. It now has two different sections that are side by side vs. top and bottom. It will help the users get to the data and info that they need quicker. I also paid bills and did some phone calls and tech support stuff. Alan was working on the BNR and Java implementation stuff. Steve was working on custom reports and state API things. Good work session.

	Shop 2269		Lunch	2/27/2017

	Shop 2298		Calvin Time	2/27/2017	Quick phone call with Calvin. We talked about some of the clients we have and some of their requests and demands. Sometime we get pulled into some crazy stuff. We are getting better at saying no and also at saying yes when needed. We also briefly talked about some new table and row level locking stuff.

	Shop 2366		API code	2/27/2017	On a GoToMeeting session with Bryan. We went over some of his projects and he asked some questions about this and that. We then looked at this menu board project. We changed how his information was being stored and did some work on his JSON object and the size of the stored object. Basically, we were maxing things out until we changed the structure a bit. Good session.

	Shop 2277		General	2/27/2017	Recording notes and working with Dave Forbis. Dave came over and we did some bills and deposits for the shop. We then scheduled some time and talked about some of his projects. He has a lot of things going and it is exciting to see where things are headed. We talked about an API socket world where one company could do something in their system and then automatically populate another system with some of the same data.

	Shop 2335		Alan Time	2/27/2017	On a GoToMeeting session with Alan. We were brainstorming on the world building database project. We talked about the available option on the solar system table. That might be where we go in and prep a server and setup a number of shell databases (blank databases) and also ColdFusion datasources to go along with the shell databases. We then check to see what ones are available and virtually claim them as needed. That way we could prep and virtually stock the shelves on the servers so that things would be ready to go. Alan is going to look into cross database options. That could be good and it could be bad. We are going to check into it. Maybe even make a pros and cons list of options. During our session, Alan was playing around and doing some cross joins with multiple MySQL tables from different databases. Pros Traditional (new datasource per): - Meant to be done this way. - Just change the datasource and all existing queries would remain the same. - Easier for future developers. - We do all of the switching and lifting behind the scenes. - Faster processing and development time. - Less errors likely - if done in a traditional way. - We could use a developer to set things up and then make tools that a middle ware developer could use at a point and click level. - We could see the size of their data and the total footprint better. - If we need to move and/or load balance something, we could grab the whole database and just move it. We would have to worry about other dependent pieces. Self contained. Cons Traditional (new datasource per): - Lots of duplicate tables and records (look-up tables, or standard tables) - Updates on the existing tables would be harder. - There might be errors and places where things get out of sync. - It does take a developer to set things up (originally). - You could max out the number of registered datasources. We saw a forum entry that a person was having problems when they got up into the 800 (ish) level for number of single databases and datasources per ColdFusion box (CF administrator stuff). ------------------------------------------------------ Pros Single Datasource (shared datasource but separate databases): - Nice for a hosting type environment. - We wouldn't have to setup any new datasources. Cons Single Datasource (shared datasource but separate databases): - Hard to understand and/or explain. - It feels like a small hole and/or backdoor approach. Possible security problem. - This would give access to all databases from one single master datasource. - If someone figures out what master datasource is... they virtually have a key to the entire house. - We would have to define and code each query to flip flop and use clustrer controller tables and database specific tables. Lots of aliases and virtual pointers. - This could slow down the development time. - It would require more database knowledge from our developers. Mixing databases within a single query. - We would need to totally revisit permission on the user levels, the database levels, etc. This may take some research and implementation. - What about bottle necks, threading issues, locking issues, etc. This comes down to performance. One of our next steps will be to look at the database and see what will be cluster level vs. solar system level.

	Shop 2260		Adilas Time	2/28/2017	On a GoToMeeting session with Steve. We widened out the sub inventory attribute values field. This allows the users to put as much data as needed in a custom built drop-down menu. We went from a max of 255 characters to 65,000 max characters. We often call this unlimited (even through it really does have a limit, it hardly ever gets reached). We met with Calvin at 11 am to go over plans for the mini conversions and transactional data for the cart and breaking things apart. - Communication between us (adilas and adilas developers) and our clients. This is huge. Projects are deep and take tons of time. We need to communicate things as they happen and progress. This is a constant battle. - Agendas (theirs and ours), this makes it tough if they are not communicated. Establishing an actual project scope and requirements of the project is a big deal. Otherwise, their ideas and conception of the product may be multiple projects all combined together. - QR codes and special barcoding options - going clear to a mini conversion level. This is more than just the codes themselves, it deals with sub inventory packages, mini conversions, etc. - We are still having struggles with clients not wanting to pay for new features. They just expect us to pick up the bill. They figure, if we are going to make it available for all of our clients, they shouldn't have to pay for it. We need to help educate our clients on how things work and how much they gain from a communal watering hole of sorts. It is like a piggy-back style of development vs. a standalone development cycle. - We talked about some pricing things. Calvin's rate is $100/hour. We talked about some possible things and ways to work out a deal. We can't afford him at the $100/hour rate. We talked about a discounted rate, trading for leads, trading for other products, and even introducing him into the reoccurring revenue sharing idea and concept. - Let's plan this project out and come up with a price tag that is agreeable for both parties. - We also briefly talked about some of Calvin's other tools. Such as Gmext, FTP stuff, MySQL editors, and other projects. - Calvin likes to think in code... Instead of just concepting on paper, he thinks in code... Where is it going to end up? - Linking things... every child has a parent and so on. Every mini conversion has a sub (child) and a parent (main item). - We talked about locking tables and rows. This is dealing with the inventory state in time... such as made, quoted, in the cart, requested, etc. We need to be able to lock and keep those records tight... The problem comes in when multiple parties are trying to access the same record at the same time. We need to form a line and/or a queue of sorts. - We went into MS Excel and did some sample table building. See attached for some additional notes and known issues.

	Shop 2270		Lunch	2/28/2017

	Shop 5035		Virtual Post-It Note	2/28/2017	-Contact Bryan and Shawn about Texas Trailer forms - 130-u and VTR-141 - $100 for the VTR-141 form.

	Shop 2299		Calvin Time	2/28/2017

	Shop 2325		Alan Time	2/28/2017

	Shop 2231		Russell Moore	2/28/2017	On a Zoom session with Russell. We started out talking about developers, dependables, employees, and how to help them take initiative to just jump in and get things going. One good thing Russell said was "You can't stop an emotion... but you can manage what you do with it." That is like incoming projects and requests. You can't stop them but you can mange them and deal with them. The rest of the session was spent testing Russell's new snow owl color options. He is getting really close to launching that project. It is looking really good.

	Shop 2341		Black Box, etc	2/28/2017	Met with Nick online over a GoToMeeting session. We went over some plans and Nick some light questions about his current project. After we got that done, we did a black box merge session and ended up pushing up close to 40 pages. We then went in and tested files and made sure all was well. Good session. During the session, Nick showed me some of the PHP stuff he is learning at school. I have asked Nick to help me learn, via proxy, about some of the things he is learning in his classes. That should be fun as we go along.

	Shop 2434		Meeting with a new developer	2/28/2017	Joe Tripp came over to my house and we met for a bit. Joe lives here in Richmond and he works up at the University. He does some ASP.net stuff for a department up on campus. He is also quite talented in SQL and MS Excel. He showed me some of his work and I got a small taste for what he does. I then showed him a little bit about adilas and what we do. He should be a good fit. He already has a full-time job but is looking to pick up some moonlighting jobs and small projects on the side. His first task is to get in and start learning Adobe ColdFusion. I pointed him to some developer videos and such on the adilas website. We will get him started and then go from there to see what happens. Good meeting.

What's New

Products

Find Us