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 - 9/1/2017 to 9/30/2017 - (91)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 2921		Adilas Time	9/1/2017	On the morning GoToMeeting session with Steve. We were mostly working on catching up and talking about vision and direction for what is happening and what is going to happen. Lots of moving pieces right now. We are going to be ordering a couple new servers and other projects and things that are taking place.

	Shop 2727		Demo with Caisson Labs out of Smithfield	9/1/2017	Went into town to meet with my dad and to do a demo for Caisson Labs out of Smithfield, UT. They are a manufacturing company that deals with cell cultures, bio-chemicals, microbiology, media, plant biology, etc. They buy raw products and raw chemicals and then produce and build bio-chemical type products. We met with their team and they had 8-10 key players at the meeting. We first met in a conference room and briefly talked about some different things and they had a number of questions. I then handed them a world building graphic and then worked from the whiteboard to help educate them about some world building concepts and data assembly line concepts. Lots of good conversation and ideas. See attached for a copy of the world building graphic that I was using. I'm not sure if it has been uploaded or not before. After that, we went back in their production area and had a look around. The main owner and a couple of his people talked about their general processes. I took a page of notes and they gave me a copy of their excel spreadsheets (for one product). I also got a number of business cards and some custom labels that they are printing for their products. See attached for the notes and other documents.

	Shop 2925		Lunch	9/1/2017

	Shop 2956		Adilas Time	9/1/2017	Recording notes, making plans, and light research. Other odds and ends and small to do list stuff.

	Shop 2957		Labor Day	9/4/2017

	Shop 2980		Adilas Time	9/5/2017	On the morning GoToMeeting session with Steve. Lots of emails, tech support, and other odds and ends.

	Shop 2984		Lunch	9/5/2017

	Shop 2966		Russell time	9/5/2017	On a Zoom session with Russell. We spent most of the time looking back over Russell's progress on the blog project for elements of time. It is very big and Russell has already made a ton of progress. Part way through, I had the thought to help him work on it vs. putting up walls and trying to follow my own agenda. There are a few things that I would like to tweak, but I think the general concept is awesome and will really be a benefit to all parties. One of my main concern is how in-depth the project and the settings are... It is going to take a lot of education to get our users ready to play at that level. What we really need, and it may have to come later, is a super easy beginner level, and then climb up the ladder to get to more intermediate and advanced options. Some of the new settings and proposed options are higher intermediate and/or advanced. Tons of power and potential, but it could be a little overwhelming. Good stuff.

	Shop 2978		Kush	9/5/2017	On a GoToMeeting session with Bryan. We bounced between a number of different projects. Some were just some small questions, others were deeper, and we ended with a code sign-off project. We weren't able to quite finish the last project, but we did get files merged in. The rest of the file uploads and tests will need to be done tomorrow at some time.

	Shop 2981		Adilas Time	9/6/2017	Emails, tech support, and some follow-up. Recording notes and doing some clean-up. Changed to some different projects for Moore Digital Ideas and Learn To Freeride about 10:30 am.

	Shop 2985		Lunch	9/6/2017

	Shop 2991		SWC	9/6/2017	On a GoToMeeting session with Bryan. We merged in some new code, pushed it up, and then rolled into a project dealing with checkboxes and how to quickly select/deselect all of the check boxes. We had to use some older techniques due to the new data table stuff (CSS and look and feel stuff). It worked slick and Bryan was on his way.

	Shop 2977		work on bar code for custom label	9/6/2017	Danny joined the GoToMeeting session. We looked over the existing barcode options for Trinity Fasteners and then built a dynamically driver custom label. It was super simple, more of a proof of concept type label. We did some testing and then I passed the new files off and over to Danny to let him play. Good little barcode session. It was good for me to get back into it as well. It has been awhile.

	Shop 2988		Adilas Time	9/6/2017	Emails, recording notes, and checking into some ideas to put black boxes on quick searches. Dave Forbis called and we chatted for a while as well. He showed me around the Campaign Rise site that uses adilas as the backend tool to show a frontend website. This is like a virtual content management site using tons of elements of time, media/content, photos, videos, customers, users, parts/items, and invoices.

	Shop 2982		Adilas Time	9/7/2017	On the morning meeting with Steve, Alan, Wayne, and I. We started out talking about needs on servers and database stuff. We then touched base on some other projects and just chatting here and there. - Wayne has been spending some time thinking about options and such. - What are the goals and what are we trying to accomplish? 1. a better, cleaner, more modern type interface. 2. a more efficient and faster database model. 3. simplifying the code and doing some clean-up to make things easier and more efficient. Think more along the one-to-many type model. 4. present a full featured API socket set - Lego type building blocks and ability to mix and bled to make custom solutions. - Currently we have business logic, database code, and look and feel all mixed together in the same page. Some pages and sections really mix things - almost to an unrecognizable level of what is what. - CSS is a very easy way to change the look and feel. This could be even set more per corporation than it already is. - Model View Control (MVC) standard. This has three different pieces. You have the model, the view, and the backend controller type functions. The model is an object of some kind. Often the model is related to the database structure. The view is what you see (HTML, CSS, JavaScript, graphics, etc.). Keep this as simple as possible. The controller piece takes the action and/or data and does something with it. These are the rules, the logic, and the decision making pieces. Basically, somewhat of the traffic cop helping to control flow, decisions, and traffic. - Helpers that help with the views... visual displays that show the users what things will look like. Virtually, they see what they will get and help with the sorting, show/hiding, verbage, aliases, data types, rules, etc. We would love to create custom tags to help build the forms and report output. Maybe think along the lines of cf_some_custom_tag. - If we build these custom tags (for building HTML and other visual displays) but we still want the final output to be customizable. - We use the black box customization options all the time. We want to maintain that ability. We could have multiple different builders and/or helpers. In the end, we really need to allow for the dynamics and customization. - How do we go from custom one-off number 1 to a base class or standard feature. This will happen over and over. Someone will have a great idea and build it out as custom. We then get other requests and eventually we want to make it a standard feature and/or option. - On the class models... we start out very broad and then start branching out as we get lower and lower in the structure. The deeper we go, the more specialized we need to get. - Usually there is a main controller and then smaller sub controllers. These could be the different actions and/or functions that could take place per model and/or object. The controller level is where you put the input validation. The controller helps validate the basic requirements. Does this data fit what is needed (super basic and/or generic validation). The model needs to control the details of that transaction. - We need to make lists of what is required and what is optional per model (per object - say each of the main 12 players). - We need to document the database, the data types, the field names, what they need, and what they require. We have started this, but it really needs to be pushed. This will help all parties. - In order to start this... you first start with a goal and then you start building the smaller pieces that will be required. Look at individual pieces and then start applying things as soon as possible. It is not recommended that you globally take over everything. Log and pick your battles... Maybe even take an inventory of what we have and then figure out where the hottest pieces are and work there. - Consistent automated testing... We keep running the tests until everything passes. As new changes happen, we rerun all of the consistent automated testing. This will help with consistency and debugging. Wayne was saying write the tests and then code to the tests. Slowly put test coverage that keeps testing other pieces as it goes out and expands. Basically, instead of testing individually, we test as a general coverage or more of a blanket type feel. This increases confidence and stability. - Taking the version control programs and such even further. Taking it clear to the test, build, test, and deploy to production. We are over writing each others code... who has the last cookie. Some of the developers have too much access to the system (FTPing files). - We could also code in teams and do some peer reviews. Currently we are still in the wild west and shooting from the hip. - This is all part of the growing process. - Setup the models based off of the database data per model. Basically, we document the model in data that could be given to all developers. That helps us have a standard piece that becomes the master plan and/or design. There are all kinds of layers within these pieces and objects. We have data layer, service layer, logic layer, etc. - This is kinda funny and silly... but Steve back on 6/22/17 said we should call our company "Fracture". Everything keeps unrolling and going deeper and deeper into subs and sub functions. - Currently we have methods that we use internally, methods that we use through API sockets, and methods that we use for custom code. We then have to maintain multiple sets of code which may or may not get updated. That flows back into the consistent automated testing and making sure that everything still works and runs correctly. It is amazing to see how everything is truly a system and integrated model. - The software maturity level. Eric would like to see things work towards a higher level. We don't want to get this high, but a level 5 maturity level is what NASA runs at. Jumping up those levels takes time and a good team. The higher the level, the more the cost and the slower things go and flow. Eric was saying that maybe we should check things out and then shoot for a level that looks good for our company (say level 2 - just off the hip number as an example). - We may be able to do some performance changes and then all of our servers are doing so much better. Currently, we keep adding more and more servers to get the performance we need. We need to find the balance between database optimization, code, and hardware/server technology. We will need to mix and blend as needed. We may need to get to a clustered server model and/or look into other options.

	Shop 2986		Lunch	9/7/2017

	Shop 2992		GDA: email fix recommendations	9/7/2017	On a GoToMeeting session with Bryan. He had some questions about upping the amount of characters that we allow to be barcoded. We spent some time talking and looking around at different kinds of barcodes, flash movies, ActionScript, bigger barcode labels, PDF lables, playing with both kinds of labels, and then into some questions and options for PDF invoices and custom layout invoices. As a side note... If we did go into the flash barcode generator application, we would want to add a couple new 3 1/2 inch or 4 inch label options. We may also want to do vertical or horizontal stacked. We may also want to shorten the height of the barcode and uncouple the barcode and the barcode text. It would be really cool if we could have a barcode and allow the line under the barcode to be the description or some other value. That way we could use the real estate better. It would be really cool if the native barcode generator could do all of that vs. making everybody go to custom.

	Shop 2967		Russell time	9/7/2017	On a Zoom session with Russell and his friend Justin (a new guy who is shadowing the development process). We started a new branch and started to work on some new master time template settings. We also worked on some basic project management options and admin notes for elements of time. Most of the session was spent doing database updates and making that code work.

	Shop 2989		Adilas Time	9/7/2017	On a phone call with a client explaining some quotes and projects that he was going to have another developer do. I then had to call the developer and relate the message. I don't like doing this, but I was being used as a middle man of sorts. Basic tech support for both clients and developers.

	Shop 2983		Adilas Time	9/8/2017	I got a call from Bryan Dayton this morning. He has a client that really needs to use the existing barcode generator but yet wanted to almost do the mini conversion stuff. We talked about some options and I wanted to record a couple of things. 1. The client wants to keep using the smaller barcode generator that is built into the system. This has a max of 15 characters on a 2" label. Yesterday Bryan and I talked about options to expand the label size to 3.5 inches or 4 inches but that gets really big. The current label size is awesome, except the barcode is limited to 15 characters. 2. The only places where actual barcode fields exist right now are parts/items, my cart favorite buttons, and flex grid tie-ins. There is already prebuilt code to handle all of those barcode search options. You could also add custom barcode stuff through elements of time, parent attributes, custom fields on the flex grid, or sub attributes per package but those options are custom and don't have any pre-built code to help search them. 3. As Bryan and I were talking, I mentioned to him that we could do a black box takeover of the quick search. We could then look up the special flex grid record and virtually submit either a form or a special URL to add an object to the shopping cart. We were talking about maybe looking for a $ (dollar sign) or something like that as the first character. This would be corp specific, but we could then look up the data and settings and push the item and correct values to the cart. 4. Inside the flex grid, we would need things like quantity to use, price per or total price, custom verbage for the description, and what sub package or sub inventory batch to use. If needed, we could use a key word like "current" or "currentPkg" or something like that to have the system look up the current open package and substitute in that package number or sub inventory number. The main piece of flex grid would already be tied to the parent item which helps us look up tons of other needed data for both the parent and the sub. 5. We already do a ton of this kind of catching and intercepting. Currently most of it is done on the parts homepage or the cart quick search page. The new process would just be creating an interceptor black box for the quick search (both items and/or barcodes), then doing a look-up based off the barcode value that was scanned (most likely looking into flex grid). We then take that look-up data and get enough to pass the request to the add to cart page and bingo, the item could be entered into the cart. Anyways, this is a possible work around using the existing barcode generator, a quick search takeover, black box logic to look-up flex grid data, and then a special URL to pass the data to the cart once we have everything. Pretty cool idea. Going back to other work... After recording ideas and paying some bills, I jumped back on the sales tax expansion project. Working through the recalculate taxes method and underlying logic.

	Shop 2987		Lunch	9/8/2017

	Shop 2990		Adilas Time	9/8/2017	Back on the sales tax expansion project. Lots of work on the core calculate taxes function and main method. Pushed up code to bit bucket on branch BWM-28. Also see attached for a copy of the working text file that I am using to record special notes and values for the project.

	Shop 2993		Adilas Time	9/11/2017	Met up with Steve for a bit and then did some prep for a demo that I have later today.

	Shop 3008		Demo with Caisson Labs in Smithfield	9/11/2017	Went into Smithfield to work with the guys and gals at Caisson Labs. I got there about 10:30 am and did some setup and prep work. We then had a demo from 11 am to 1 pm. We had six people plus myself in the demo. Light dog and pony show followed by some whiteboarding, scenarios, and live demos and training. Good conversations and some good breakthroughs on terminology and flow. Most of the demo was dealing with parent/child inventory, internal build PO's, and tracking lots and packages through the system. We did touch lightly on ecommerce, shopping carts, recipe/builds, and convert parent to child actions after a quote is restored to cart. We spent a lot of time going over what was possible right now and what would be possible with the mini conversion pieces and features that should be coming before Christmas 2017. They really need this and I think that the more I'm involved, the better the final output will be. Kind of a hands on learning and consulting type role. Good demo and they want to know what the next steps are. We rescheduled for a consulting meeting this coming Friday.

	Shop 2994		Lunch	9/11/2017

	Shop 2995		General	9/11/2017	Paying bills, phone calls, and doing emails.

	Shop 3009		Data migration and date flip	9/11/2017	Working on a custom data migration project for a client. They had 2 corps with over 7,000+ clients per corporation. We had to flip four dates and sub flags for all records. This was a custom code job and had to be ran after hours. Once completed, I changed some corp-wide settings to help the data go smoothly forward in the correct fields and containers. Invoiced the client.

	Shop 2996		Adilas Time	9/12/2017	On the morning meeting with Steve. We spent the first couple hours just trying to get caught up on the day to day things that needed to be done. As we were talking and working, Steve made a good comment. He said "Keep riding your own horse and don't worry about the other guys". I thought that was well said and helps us just keep going and doing what we need to do. Most of the morning was spent doing lots of prep work, research, and general to do list stuff. Around 11:15 am (ish) we had a meeting with Anthony from All Greens on the GoToMeeting session. Some of the notes are listed below. - These are requests that would help all parties on the system. A few little tweaks that will help and make these smoother. - As a side note... Anthony has provided a number of documents that have screen shots, samples, and some great verbage. - Auto closing packages for subs - some kind of rules for the children and how they play. - Maybe bulk closing packages - even to the API level where it closes both internal and a state site through an API socket. - On conversions... we need to be able to convert both in and out. Say grams to each and then each back to grams or even out to ounces. Basically, once we know the data... allow it to flow sideways between the different conversions. - Some of the states are interested in the tax collection and making sure that all of the data is not being inflated and/or manipulated. Basically, getting reliable data and having a level of comfort or trust back and forth. - The deeper we go, the more we are seeing the API sockets being a huge part of the puzzle. That allows data to mix and bounce between systems through a controlled environment. - Anthony had some great ideas on speeding up the mini conversion piece. - Setting the expectations on who owns what and who will get what. - We could really gain some benefits by making a niche specific product that has all of the bells and whistles for that niche. That really helps limit the training and education as well as helping the industry leaders play in a level or world where they are comfortable. Maybe refocus by focusing on a specific industry. - The conversion process is huge... All of our companies really need this. - Blocking things going into negatives and helping the flow of things. - Anthony is wanting to help. How can they help and push projects and ideas forward? The goal is to help all parties involved to be faster and run on a smoother platform. Steve would love to see a top 10 list of wishes and requests. What are the pain spots? - All parties are looking for information and ideas. We need to help each other going forward. - Our clients are potentially loosing business due to the processes and complexities of the steps that are required. They are wanting more one-pager type interfaces that are intuitive, easy, flexible, and powerful. - The register and/or cart interface is a huge piece that helps or hinders the efficiency levels of a company. Maybe focus there a bit more. Basically, let's try to smooth out the road a bit. That would help everybody. - Anthony feels that he has a lot of leverage and would like to help. Steve and Anthony are looking to have some other meetings and starting to work on projects and tick lists. - Putting up some seed monies to help push projects forward. These are either custom projects or community funded projects. - More interest in full job costing and other cost accounting options. There are other parties that are interested and are even willing to play. Lots of talk about getting a better grip and more details on the true cost of production.

	Shop 2999		Lunch	9/12/2017

	Shop 3006		coordination	9/12/2017	On a GoToMeeting session with Bryan. We went over some questions on different projects and Bryan showed me progress on the new data 8 server. We spent some time going over a new project to cross tie deposits and balance sheet items together similar to what we did for expense/receipts. Light overview and some drawings of what is needed.

	Shop 2968		Russell time	9/12/2017	On a phone call with Russell touching base on the Adilas Shop and project management. We talked about some options, issues, and direction. Russell is looking to still do project management but wants to focus more on non MMJ type projects. Good conversation. After that, I called and talked with Calvin for a bit. Mostly just checking in and touching base. He had a small project to turn over to me via email.

	Shop 3004		Adilas Time	9/12/2017	Back on to do list items. Emails, tech support, recording notes, paying bills, making quotes, etc.

	Shop 2997		Adilas Time	9/13/2017	On the morning GoToMeeting session with Steve. Rolling through general to do list items. - From Eric... we are seeing more needs on the invoice for delivery methods and even invoice categories and sub invoice categories. As a side note, we developed the sub tags and flags section of elements of time to handle this. The end goal was to extend this functionality out to the other 12 main players. - When doing a transfer of children or sub items... flip those packages to disabled. This would be a child inventory rule. Basically, what happens when a child or sub package is transferred? Is it locked or left open or what? - More requests to make a mobile employee time clock app. Just recording the requests. At the end of the session, I was testing media/content uploads from all servers. All servers passed other than the data 6 box. I then spent some time on the phone with tech support trying to resolve the issue. They want full page by page login info so that they can get in there and duplicate the error and/or problem. I'll work on that later today.

	Shop 3000		Lunch	9/13/2017

	Shop 3003		Adilas Time	9/13/2017	Working on the bug with data 6 and pushing up media/content files. Did some prep work, pushed up some test files, and contacted Newtek about the issue. Spent some time working on and fixing the option to open and close a sub inventory package. Modified a number of pages, did some testing, and pushed new files to all servers. Other emails and tech support stuff.

	Shop 2998		Adilas Time	9/14/2017	On the morning GoToMeeting session. Worked on the data 6 server error with the media/content uploads. Contacted the tech support guys and helped them with a better testing page. Emails and recording notes. Cleaning off my desk and checking things off.

	Shop 3019		Adilas Time	9/14/2017	Back on the sales tax expansion project. Also had to do some other tech support and email stuff. Working on a new SSL for the data 8 server.

	Shop 3001		Lunch	9/14/2017

	Shop 3014		Improve the custom reports for elements of time	9/14/2017	As a note and an idea... We should add settings to the time reports where a specific concept date could be set such as current week, next week, current month, last month, next month, ect. These dates wouldn't have any hard fast value but would be looked up and/or calculated on the fly. That way you could set reports for dynamic time periods and such. As part of the concept dates idea... we need to make a function that would calculate those dates so that we could use it over and over again. As a note, the corp-wide settings for the time homepage already have some of those dates written out. Also, the time homepage has some code that can convert the strings (next week, current month, etc.) into real dates. Look there for some ideas. Another idea is to all the main time homepage to save as custom reports. That way we could use calendar views, time slot views, grouped reports, etc. That would really help that page play more of a role in the application.

	Shop 3010		add subs	9/14/2017	On a GoToMeeting session with Bryan. We were talking about options for custom labels with barcodes and QR codes. We talked a little bit about the new server setup. We then went in and substituted out some of the domain specific files to get the new server more ready to use.

	Shop 2969		Russell time	9/14/2017	Quick phone call with Russell. They (he and Justin) are working on the new adilas.biz homepage. They aren't quite ready yet but are getting closer.

	Shop 3005		Adilas Time	9/14/2017	Working on the sales tax expansion project. Working on the calculateTaxes method or function. Tons of commenting and then starting to run some tests on the method. It still needs some help with the tax category of 17 (with tax included). But we are making progress.

	Shop 3002		Brandon out of the office all day	9/15/2017

	Shop 3020		Demo	9/15/2017	Went into Smithfield to work with Mike from Caisson Labs. We met and did a small consulting session. He drew out what he was looking for and I made a number of suggestions. I then showed him some ways that we have customized the system for other clients. It gave him some good ideas. Good meeting.

	Shop 3022		Adilas Time	9/18/2017	On the morning GoToMeeting with Steve. We were reviewing things and grabbing some adilas time on the shop calendar. We are trying to focus in on the sales tax expansion project. It is somewhat becoming a road block of sorts. We also reviewed Alan Williams' local setup guide (Setup Local Adilas Environment.pdf) file. This is a 25 page document that goes over setting up ColdFusion, MySQL, Git, Sublime, and other stuff. Great resource for developers. See attached for the current version. Cycling through emails and doing some light tech support. Back on the sales tax expansion project.

	Shop 3026		Lunch	9/18/2017

	Shop 3021		Server Setup	9/18/2017	On a Zoom session with Bryan. We spent the first little bit talking about a JSON object solution for mini conversions that Bryan is working on. It is just setup to be a temporary fix. Under a bigger load, it will become too heavy and will be inefficient in many ways. After that, we jumped onto the new data 8 server box. We looked into the setup process and determined that there was a problem with the IIS or Internet information services server. Bryan is going to get with tech support to try to resolve the issues.

	Shop 3030		Adilas Time	9/18/2017	Spent the afternoon working on the with tax included settings for the calculateTaxes method.

	Shop 3023		Adilas Time	9/19/2017	On the morning GoToMeeting with Steve. We started out the day going over progress on the calculateTaxes methods and what not. We got into a discussion about with tax included and how that plays into the whole mix of things. We did some drawings, got out paper and pencil, and ran some scenarios through using our tool and a calculator to do some checking. We determined that if we are doing with tax included calculations, we can't really worry about too many variables. Just back into the price and do the calculations from there. After that, we did some emails and tech support and jumped back on the sales tax expansion project. Most of the session was spent working on and testing the calculateTaxes methods. After the session, I spent some time doing bank stuff, paying bills, and doing some deposits from work that was done for custom AFB projects that they paid us back some commissions. Good stuff.

	Shop 3027		Lunch	9/19/2017

	Shop 3056		Additional discount settings	9/19/2017	I got an email from a client today that requested some settings to allow both auto discounts (based off of a customer type) but then be able to limit any other discounts based off of a manager's approval. Basically, they want to mix and blend auto discounts with manual or extra discounts. That gets pretty deep and almost starts touching advanced discount rules and logic. Just wanted to record the idea.

	Shop 2970		Russell time	9/19/2017	On a Zoom session with Russell. He showed me a new login page and some of the fun things they are planning and doing for the main adilas.biz website. Trying to get a new face lift for the main web site and main login process. We then talked about a number of other projects including new time breakdowns for receivables (who owes us money), automated emails, email settings, location based inventory thresholds, quick inventory counts and inventory adjustments, and other projects. We talked a lot about project management and how we present the projects back to the client. Good session. Russell did video tape and record some of our session. Lots of drawing and talking back and forth about projects, scope, and ways to make the new tools more functional and more robust.

	Shop 3031		Adilas Time	9/19/2017	Recording notes and answering emails and light tech support.

	Shop 3024		Adilas Time	9/20/2017	On the morning GoToMeeting session with Steve. We chatted about some new ideas on barcodes for sub inventory as well as new barcodes for mini conversion. Basically, people want to be able to create and generate their own barcodes for those smaller level packages and such. After that, I started back in on the sales tax expansion project and Steve was making calls and what not. Most of the session for me was spent in cleaning up and doing final checks on the calculateTaxes methods. I even did some testing with the new customer types and how they play into the tax settings for either limiting taxes and/or applying globally based off of the customer type. My next steps are going to be diving into in-line discounts and making sure that the dollars off in-line discounts could play through the add to cart process.

	Shop 3028		Lunch	9/20/2017

	Shop 3057		We need to add sub barcode searches and custom fields	9/20/2017	We have had clients ask for custom barcodes per sub packages and per sub inventory child items. This could be really easy if we added a new sub_barcode field to the time_sub_inventory_[53]. We need the same kind of functionality on the mini conversion table as well. Basically, the users are wanting to come up with their own barcodes for the sub packages and smaller subs of subs. We could then make the field searchable and built-in to work with all of our normal barcode searches. We could even allow the barcode to hold more values than the normal 15 characters (the show value maxes at 15 but we allow up to 50 characters to be stored - the problem is how much room it takes to show that many characters in a normal 128-B barcode). The other option would be to push more on the QR code. The QR code could also be the answer to whatever is needed. It might be nice to add an automated QR code generator or tie it into the flash builder. As a side note, we are seeing people storing and/or adding more sub details, sub locations, sub attributes, etc. into the QR codes themselves. Almost a mini database of sorts right on the QR code.

	Shop 3032		Adilas Time	9/20/2017	Custom work on the Bear 100 mile race. The race is just over a week away and we need to get the site ready for the new pieces and new aid stations. It changes every year. I spent most of the afternoon manually entering cities and states for the runners. There was about 350 records. Combed the data and did the runner upload. I still need to go in and condition the new pages for the new aid stations and time frames. Good start.

	Shop 3059		Bear 100	9/20/2017	Went into Logan for a Bear 100 meeting. While the meeting was going, I updated all of the custom files to run with this years data for the Bear 100 mile running race. I also participated in the meeting with the radio guys and talked about the adilas software and what we do for the race. I uploaded new files. We should be ready to go.

	Shop 3025		Adilas Time	9/21/2017	On the morning GoToMeeting session with Steve. We talked about a few projects that were floating around and some light direction. As part of the conversation, we looked into some funding and what is owed and to whom. This is a random side note, but we discovered that a business lender that we were using pulled a little bit of trickery on what was owed. We had a loan and thought we had paid it all off. Actually, there was $600 that was still outstanding. So, They have been chipping away at that $600 over the last 6 months based off of other payments we have been making. In the mean time, they have been charging us $300 a month as a loan fee. That's just shy of $2,000 over 6 months. This went undetected until just today. As of today, there is still $300 still owed as the final fee. Pretty underhanded if you ask me. Busy times and no one really watching. Hopefully a lesson learned.

	Shop 3029		Lunch	9/21/2017

	Shop 3060		Helping out the splits and payables	9/21/2017	On a GoToMeeting session with Steve. He would like the printable report that you can get to when paying for splits to play a bigger role. It shows stuff like external invoice numbers, payments made, amounts owed, and payment status. He would also like for the external invoice numbers to automatically show up on the expense/receipt notes. Currently we have to copy and paste things into the notes section. He had some other good ideas for the payables section as well. He would love to see some aging on that report. Lots of little tweaks that would make it awesome.

	Shop 3058		Expense/Receipt	9/21/2017	On a GoToMeeting session with Bryan. We spent the whole hour talking about his project to link up the deposit line items with a possible balance sheet transaction. We worked on some light JavaScript and then got into some queries and database stuff. I tried to help him see and catch the vision of what was needed for the rest of the project.

	Shop 2971		Russell time	9/21/2017

	Shop 3033		Adilas Time	9/21/2017	Back on the sales tax expansion project. Went to a couple of pages that already do some in-line discounts and did some studying up on how things work. We are trying to incorporate a number of new in-line discounts such as dollars off, percentages off, and mixed (both dollars off and percentages off).

	Shop 3034		Brandon out of the office all day	9/22/2017

	Shop 3062		Working with Will	9/22/2017	On a GoToMeeting session with Will. We talked a lot about the current way that the API credentials are saved. Currently, there is just a one-to-one ratio and it is possible to overwrite values depending on if you are submitting things through the adilas third party page or the main API socket and connections page. Both pages use the same API sockets, but it is possible to overwrite things due to the one-to-one relationship that exists. That whole section needs some work.

	Shop 3064		Recording notes	9/23/2017	Reviewing notes and recording new ones.

	Shop 3063		Thoughts on teams	9/23/2017	Random thoughts on teams. I watched a movie called "Sully" last night. It was about a pilot who landed in the Hudson River in order to save himself and his crew. The movie seems like it was just about the captain and seemed to focus there, but in the end, it was everybody... it took a huge team effort to pull everything off. Anyways, as I was getting ready for bed, I was thinking about teams and what role I play and/or have played. As a side note... I'm sorry, I often think of only myself and what is required at my hand. I feel pretty selfish sometimes. In the morning, I did a quick search for the word "Team" and I found 50+ entries just in the adilas shop things. It was fun to look over a few of the ideas and concepts. Here are some new questions that I wrote on a post-it note and stuck on my printer. - What team(s) are you on or part of? - Does that change what options are available? - Many times... I have tried to be a hero. Play well with others. There is no possible way we can do everything on our own... We need the other team members whether we like it or not. Play well.

	Shop 3065		Working on the sales tax expansion project	9/25/2017	Back in again working on the sales tax expansion project. Spent lots of time this morning working on the different styles and/or types of in-line discounts. We have normal percentage off, dollars off, and mixed discounts (both dollars off and percentage off).

	Shop 3035		Adilas Time	9/25/2017	On the morning GoToMeeting session with Steve. Doing some catch-up from over the weekend. Wayne came on to ask a couple of questions. Then back on the sales tax expansion project. I was working on testing the add to cart page and logic. Lots of new changes afoot. Lots of testing and test cases. Eric jumped on and had some questions for Steve and I.

	Shop 3039		Lunch	9/25/2017

	Shop 3061		Deposit line item	9/25/2017	On a GoToMeeting session with Bryan. We were doing some light code review and merging some files in with the master branch. We had to do some flip flopping between branches, but we got it merged in. Bryan was going to be doing some testing to make sure that everything works.

	Shop 2972		Russell time	9/25/2017	Quick phone call with Russell to touch base and see if they needed (he and his team) needed any help. We talked about a couple of future projects and he did have a question about auto closing sub inventory packages once the quantity goes to zero. They seem to have most things under control.

	Shop 3044		Adilas Time	9/25/2017

	Shop 3067		Sales tax expansion project	9/26/2017	Working on the startNewCart method and some new invoice level buckets to help with new tax totals and rounding error.

	Shop 3036		Adilas Time	9/26/2017	Working on the sales tax expansion project. I spent some time cascading new tax totals and rounding error around the site. I also added a new developer's tool to be able to dump the different scopes based off of a URL string. I added the new code to the footers, so that it would be on every page. Here is a sample: view_cart.cfm?dev=yes&dump=yes. It is a two part string that says yes, I'm a developer and yes, I want to see the dump. That URL string (just the variables) may be added to any page to get the dumps. That could be dangerous and possibly expose too much info, but I think that it will be ok. If anything, there is so much data, you would really have to know what you are looking for. Anyways, just a small note to other developers. Towards the end of the session, I got a text from a client saying that there was an error with the deposits. I ended up contacting Bryan and Alan and we got it fixed. They launched some new code and it was just a little too tight on the validation. Anyways, we fixed it and all is well.

	Shop 3040		Lunch	9/26/2017

	Shop 3068		Tying the main 12 groups to time	9/26/2017	What if we added in an optional tie-in from every main object to elements of time (basically add a time_id field). That would be a new database field per every main group such as deposits, invoices, PO's, expense/receipts, balance sheet items, stock/units, customers, vendor/payees, employee/users, parts/items, elements of time, and quotes. This would allow us to easily extend the sub add-on's or sub functions of time to all main players and main player groups. We could also add time id connections to smaller subs, line items, payments, or other sub tables within the groups as needed. This will help us track sub locations, sub phases, sub categories, sub types, sub progress, etc. Going way back a couple of years, we wanted to allow elements of time to virtually adopt any other player type or player group. This way we would be starting to allow that to happen from the player groups themselves (reverse connections from player groups to time). We also need ways to tie things from elements of time back out (time to other objects and/or groups), but it would really help if the objects themselves had ways to tie to time. As a general note... we could use app type id, main id, table name, and sub id on the main elements of time to create the back tie-ins. See the flex grid and media/content for ideas on using these generic tie-ins to create a multitude of one-to-many relationships. It is fun to see some of these ideas coming around. Good stuff.

	Shop 3045		Adilas Time	9/26/2017	Started to expand and cascade the new tax totals, rounding errors, and in-line dollars off discount stuff to other pages. Worked on this project from 1:15 pm to about 3:00 pm. Switched gears around 3:00 pm to make sure that I was ready to go for a Bear 100 demo and practice run with the Bear 100 radio folks who are on the data team.

	Shop 3066		Bear 100 meeting	9/26/2017	Did an online meeting with the Bear 100 radio guys and data team. We went over the interface, software, in's and out's, etc. Good meeting. There were three other people on the meeting asking questions and getting a refresher of sorts. As long as the weather holds out, we should be good to go with the race this year. Last year, we had to switch things the night before due to course changes and bad weather.

	Shop 3037		Adilas Time	9/27/2017	Did a little bit of prep work and testing on the Bear 100 mile race and dynamically importing data. I ran a couple of test runs and then reported back to the radio guys and the data team. After that, I went back on the sales tax expansion project. Most of the time today was starting into the edit cart line item page. Changing from add mode into edit mode based off of all of the new pieces that we are implementing for this project. That includes new tax settings, new dynamic tax titles, rounding error, and in-line dollars off discounts. Making progress.

	Shop 3041		Lunch	9/27/2017

	Shop 3069		Kush	9/27/2017	On a GoToMeeting session with Bryan. We spent most of the time looking into the cart payment logic and how to implement new payment types into the flow and logic. We talked a lot about different techniques for figuring out what is going on and virtual problem solving. Hopefully we gave Bryan enough to keep going on his project.

	Shop 2973		Russell time	9/27/2017	No meeting took place. I was working on my own. Kinda sick, didn't do much.

	Shop 3046		Adilas Time	9/27/2017	Reviewing code and making a plan for what needs to happen next.

	Shop 3038		Adilas Time	9/28/2017	On the morning GoToMeeting session with Steve. We chatted and did some catch-up for half an hour or 45 minutes. I showed him the progress on the sales tax expansion project. We went over some percentage off discounts, dollars off discounts, and some mixed (both dollars off and percentage off) discounts. We also talked about super technical stuff like what values to round, when, and to how many decimal places. Just changing the rounding changes the math and the final output. Tiny changes make a big difference. After that, we stopped the call and each of us started working on our own projects. I started working more on the edit process for the sales tax expansion project. Part way through, I got off on a tangent and started mapping out number of decimal points for all of the percentages and dollar values. I need to standardize things and make sure the math is consistent. As a random side note, I got an email from Alan Williams asking about tracking a delay (time) in transferring inventory. I sent him back an email stating that being able to track things over time is huge and keeps showing up. I also added an idea of creating another location called "Pending...". We could then transfer inventory from a location into the pending location. Then when it really hits the other location, we could transfer things from pending into the new location. That does take extra steps but would provide a perfect trail and would take care of the time delay question and problem. Anyways, just an idea.

	Shop 3042		Lunch	9/28/2017

	Shop 3077		New icon menu graphics	9/28/2017	As we transition away from the classic look and feel, we will need to update all of the icon menu graphics to match the new look and feel (say a common occurrence of the snow owl theme). That will help the pages look more up to date and standard. This could take some time, but will need to be done at some point.

	Shop 3047		Adilas Time	9/28/2017	Started going backwards and implementing a standard number of decimals for all known values, database fields, and calculations. I also added some code to show total sales tax percentages on a number of pages. Towards the end, Bryan and I did a GoToMeeting session to look at his new code for different closed circuit payment options (special cards that are loaded and unloaded through 3rd party solutions). He changed the logic and it now seems to be running a bit tighter and has better flow.

	Shop 3078		Bear 100 tech support	9/29/2017	On a GoToMeeting session as the Bear 100 tech support person. Helping to get things started. While I was waiting, I did some payroll commission reports for Shawn Curtis and started working more on the sales tax expansion project. I ended up helping a little bit with the Bear 100 stuff and doing some light tech support. I modified one of the bulk entry files for them and did some light clean-up on a custom page for the Bear 100. By the time I ended the meeting, they had all of the starts, did not starts, and were receiving data from the first aid station. Also as a fun note, there have been 15 or so comments and a couple of photos entered by the runner support groups. It is fun to see how the data starts pouring in and bringing the site to life. Good stuff.

	Shop 3043		Brandon out of the office all day	9/29/2017

What's New

Products

Find Us