all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 1/1/2015 to 1/31/2015 - (51)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 2999 |
|
Daily Tasks | 1/1/2015 |
• On the phone with Steve going over our plan for releasing in-line discounts. Steve wants to participate in the upload and push process. That will be fun. • Posted a new update on the main login page about our plans to launch and release in-line discounts and campaign tracking. • Working on the advanced edit cart line page. I finally decided to limit the number of back calcs that may be done at a time. That should help the page. • More work on the advanced edit cart line page. Most of the work was on the java script for the page. Lots of moving parts and pieces. |
|
|
AU 3655 |
|
Tech - Database Planning | 1/1/2015 |
Database planning – (Please see sketches on scan in photo gallery) |
|
|
Adi 916 |
|
Custom code - Label | 1/2/2015 | Need to add a custom pdf label for Jim at Emerald Fields | |
|
AU 3000 |
|
Daily Tasks | 1/2/2015 |
• Prep work on files to help with in-line discounts. Checking shopping cart stuff, eCommerce code, and adding stock/units. • Huge late night push between Brandon & Steve to get new code launched for in-line discounts, campaign tracking, new payroll withholding tables, new label mapping options, new settings, etc. We had to update and shutdown multiple servers and then bring them back up and online with new code. Major process. Steve and I did the whole session using GoToMeeting. Thank goodness for candy and chips (snacks)… Late night. As a small note, we have a couple of known issues that will be fixed in the next couple of days. They are all noted on a separate page. |
|
|
AU 3001 |
|
Daily Tasks | 1/3/2015 |
• On the phone with our Colorado developer going over his code and custom cart stuff (black box for code) and how in-line discounts play into it. We did a GoToMeeting session and went through his code line by line. We uploaded and tested files. • Reviewing notes from my notebook. • New logos for a client. |
|
|
AU 3009 |
|
Daily Ideas | 1/3/2015 | -The Colorado developer and I were talking about a thing called regression errors and how new updates break or alter existing functionality. As we get more and more custom developers, the possibility of software regression may become a part of the puzzle. | |
|
AU 3656 |
|
Brainstorming - Using adilas for Family History | 1/4/2015 |
Talking with my daughter about family history using adilas: (See sketches & scan in photo gallery) - Flex grid - Customers – family member o Group o Individuals - Elements of time |
|
|
AU 3002 |
|
Daily Tasks | 1/5/2015 |
• Uploading files tot eh adilas code bank. Sending an email to an adilas developer out of Nebraska dealing with FTP access to the adilas code bank. Other emails and recording notes on expanding the 3D World Building model to include other resources in the y axis or money scope. See notes on other page for more details. • Sent an email out the adilas interns with a light schedule of training times for January. • Emails and small code changes. • Fixing some links on the Learn to Freeride site. • Small code changes and updating files with verbage changes and minor code tweaks. • Went in to Bridgerland for the first of a multi-day, multi-week developer training session. No formal training but helped setup computers and laptops. We had a number of people there. My brother and I talked graphic and my sister and I talked training schedules. 30 miles. |
|
|
AU 3010 |
|
Daily Ideas | 1/5/2015 |
-Yesterday I worked with my daughter on photos for family history. I started her on some photo editing stuff. I have made it my goal to do at least two hours a week of family history. I’m planning to use adilas as the backend engine. I will create a skin for it and build whatever custom pages are needed. Here are some of my other plans: -For family history… We will use customer as people and individuals, we will use customer types as family groups or families. We will use a lot of flex grid pieces for custom fields and relationship builders. Elements of time will be big portion of the project. We may end up using media content to store video, audio, and other pictures, and/or documents. Lots of photo galleries for customers and elements of time. I also want to setup the pre-defined groups or pools for assignments to elements of time. We will use some custom interfaces and will make it as easy as possible. Ideas are just starting to formulate… This will be fun! -On 3D World Building… I had a thought yesterday about the y axis. Currently, it is labeled money. What if we left it as money but also included other resources. Using resources or expanding it to include resources is huge. X = time, Y = money, Z = space. 3D World Building Model: X = time, Y = money, Z = space (please see sketch on photo gallery scan). Trying to expand the definition of money. - A resource could be any number of things that you use or have available. A resource could be money (the x axis), but it could also be other things such as… materials, potential, skills, talents, and even time or space could be resources. The goal is to think outside of the box and think beyond normal money. - What about resources like: knowledge, experience, family, land, health, senses, (sight, hearing, touch, taste, smell), etc. - What about love, friendship, humanity, storage or built up levels of something. How about fuel, food, nature, air, water, soil, rocks, trees, beauty, etc. - What about talents and skills like: speaking, writing, acting, entertaining, leading, singing, playing, working, designing, developing, etc. Tons of possible resources may exist and/or be used. Think outside of the box and let the y axis be more than just money. Think about resources… on hand, available, acquirable, promised, used, and/or supply (not demand) levels. Good stuff! - What about people, personnel, science, technology, processes, intellectual property, customer base, data, databases, code, programs, etc. Resources don’t have to be money. - Resources usually need to be harvested and cared for. |
|
|
AU 3003 |
|
Daily Tasks | 1/6/2015 |
• Emails, tech support, phone calls, recording expenses, and talking to Steve on the phone. • Went in to Bridgerland for another setup and developer training day. Met with a new adilas intern, we did an interview and I pitched for him to start tomorrow with training. • Worked with my brothers. An intern was a good helper and worked with a bunch of the new guys. 30 miles. |
|
|
AU 3011 |
|
Daily Ideas | 1/6/2015 |
-We had another request to not allow checkout unless the invoice was fully paid. Basically, don’t allow any short paid invoices based on a new setting. -A client needs a new payment type called “Lottery/Lotto”. As a note, it would be nice if we could allow each corporation to add and/or subtract from the list of payment types that they allow and/or need. -We had another request to be able to add and edit log note types. That is another great future option. There are a lot of preset drop-downs that people may want to be able to control on a corp-wide basis. -Invoices and PO’s need to get to the point of being able to point and click to show/hide fields. Show this… hide this... put this here… move this here… etc. -From Steve… “Some people think that the future is software as a service (SaaS model). I believe is it custom software as a service (CSaaS). |
|
|
AU 3004 |
|
Daily Tasks | 1/7/2015 |
• On the phone with Steve and a contact going over Washington State API stuff. Steve also wanted some direction on some label stuff. • More phone calls and tech support. On the phone with our Colorado developer going over new and existing needs and what not. • Emails. • Went in to Bridgerland for the first day of actual training. We are going to be doing four days a week with night classes three days a week. Our classes today were dealing with an HTML review and basic intro to ColdFusion. We recorded the classes and sessions using GoToMeeting. After class, we (my dad and an intern) did some rearranging of the classroom. My sister did the night class and did an adilas intro class. 30 miles. • Went by and met with my brother and a developer at their houses. I pitched a commission model for the adilas payroll section to the developer. Nothing was decided, but we are starting to talk about it. That would really help me out tremendously. • Went over to another friend’s house to help him get his laptops setup with ColdFusion. His computers were going slow so we talked and did some light training while we were waiting for the programs to load. We finally got it all working. |
|
|
AU 3012 |
|
Daily Ideas | 1/7/2015 |
-When we edit a flex grid title (say a drop-down menu item or sub) we need to offer an option to update all existing matches. This will make the flex grid titles behave more like a true one-to-many relationship. This idea came from our Colorado developer. -Learning to code, program computers, and work with web pages is like learning to weld. If you have the know-how and the materials, you could build anything. -What are my personal resources? How can I tap into additional and/or other resources? Give and receive freely! That’s what I really want to do! |
|
|
AU 3005 |
|
Daily Tasks | 1/8/2015 |
• Converted the videos from yesterday into a useable format. Uploaded videos to the content server so that people can get at them. • Called and talked with a graphics lady about helping out with a graphics course for the interns. She will be teaching the Thursday night class next week. • Emails about eCommerce options and doing custom websites in rounds and stages. • Went in to Bridgerland for a full day of training. I met with my brother and we went over some objectives for his practicum and internship. We set up for the class and did three different two hour sessions. • The first session was an HTML review and we posted a new file online to allow guys to get to the GoToMeeting recordings. We then covered variables, output, includes, and comments. • The next session was scopes and ColdFusion structures. • The night class covered elements of time and new system setups. We got kind of deep into elements of time and I’m not sure if the guys were ready for that. It got better as we let them just play around and then talked about things. • An intern did some training and another developer was making jokes and such. Both of these guys helped another class participant with some one on one code stuff. I took the developer home and we talked more about making the payroll section a commission based piece of the system. |
|
|
AU 3006 |
|
Daily Tasks | 1/9/2015 |
• Added the GoToMeeting recordings to the adilas training page. Added the rest of the schedules to the page. • Recording hours from post-it notes. • Reviewing notes from 9/15 to 9/30 of 2014. Lots of crazy stuff happening back then as well. Thus is life! • Cleaning up my email inbox and recording some notes. |
|
|
AU 3013 |
|
Daily Ideas | 1/9/2015 |
-We need to harness all resources. This may include the adilas content server and charging for companies that are over their limits. -Contact Dave (working with project management) to see if any projects are cooking and/or getting hot. We could use a good shot in the arm to help with funding some of these new interns. -We could gain a bunch by building out the database copy and duplicate process – World Building. -GPS tracking and round two of elements of time could help with future revenue and options. That project needs to get done at some point in the near future. -Sub inventory and cost controls (packaging) as well as a custom label maker app are also very needed. -What about other community funded projects. Open up the options. What about eCommerce templates or other templates. -The whole adilas API backend application. That has huge potential for future growth. -Steve is another huge asset. Many of the adilas custom projects go through him. All we need to do is ask. - We have had a number of requests to do a pricing tier based on a quantity of a group and/or category. We already do a single item tier based on quantities… but we don’t base the sum of each category on pricing matrix. Basically, people are wanting to group things together and then play as if that is the quantity based on the group not the item by item details. Maybe look into a switch or feature on the smart button that allows for things to be grouped by association to a smart button. This may require some math flipping but could be done. Ask a consultant out of Colorado if more info is needed. -As a note about the grouped quantity tiered prices… This may be something that could be run as custom code as the shopping cart gets built… Say the store is using barcodes… as it adds items to the cart… one at a time... it may not know what to do until it gets done or hits certain thresholds along the way. Say for example: Buy 10 of any kind of party pizza for $10 or $1.57 per if under 10. We may not know what we have until just as it happens. I would recommend that we add some kind of price and quantity and category watchers – in the cart – to handle this type of scenarios. It might need to check the cart contents every time a new item is added. -This may already be listed somewhere… but we have had request for discounts per category or per item category. For example: All backpacks 25% off, all climbing gear 20% off, selected camping items 25% off (limited or a sub set of the main inventory). We need to be able to cover both options. Also, I seem to remember a date range and/or a time range for these discounts. Say, a new sale from 1/15 to 1/21 or a reoccurring sale (happy hour) from 4pm to 6pm daily. Anyway, just some ideas. -Sometimes deposits take forever… we need to circle back around and check the tables, joins, and logic. The report that takes the longest seems to be the “payments not yet deposited” report under the running bank balance(s) page. |
|
|
AU 3007 |
|
Daily Tasks | 1/10/2015 |
• Emails, brainstorming on projects and tapping into different resources. See notes on other pages. A developer came over and we sat at the kitchen table doing a white board session on how to harness assets and what is needed to get projects in to play. I then helped him get his system up to speed with new code and new files. He is going to be working on payroll and state withholdings. • Recording notes about project management. • Trying to get caught up on emails. Tons and tons of emails lately. Lots of them are for custom quotes for new features. |
|
|
AU 3014 |
|
Daily Ideas | 1/10/2015 |
-Another huge piece of the puzzle is the dynamic graphical user interface (GUI interface) with the adilas GPS core and adilas interactive map. I would like this to be done in Adobe Flash. -Another huge project is being able to save and create your own reports. This will be done with a page that collects the report settings and then saves the settings as a JSON object. Settings may be applied per page, per corporation (world), per user(s), etc. Basically, a custom option to save favorites, save reports, build reports, assign reports, etc. The data that gets saved needs to be able to be modified (edited) as well as copied to make other reports and/or assignments. Create your own favorite buttons. -I went to a planning meeting today for the youth of the church. I was impressed as I saw different groups of young men and young women meeting with their leaders to help plan the next six months. As I was talking with some of the other leaders at my table, we were talking about how members of the church are trained and able to work and do different callings and jobs. They each user their own resources and even pray for guidance and direction. We were having fun talking about how things work and how so many talented people come together to create great outcomes. I know that God is involved but we were really enjoying talking about the individual efforts of the members and people who are involved. Good stuff! -We are going to allow different parties to help and participate in different projects inside of adilas. We, adilas, will put a person over a specific project and then start building towards that as the goal. We gully know that some of these projects are way bigger than the people we will be putting on them. That is okay and we will use that as a learning and growing options or opportunity. Kind of like what God does for us. He trusts us with all kinds of things and allows us to grow along the way. I am grateful for the chance and opportunity to learn and grow. -A developer came over today. As part of our discussion we talked about opening up additional bays like a repair shop or garage. We also talked about a pool and how there is both a deep end and shallow end. These two analogies were part of our discussion talking about project management and trying to tap into resources. Repair Shop (see sketch in photo gallery – multiple bays and an office) - Garage with multiple bays or work areas. - Different developers may only be able to work on certain projects. Pool or swimming pool (see sketch in photo gallery) - Deep end - Shallow end - Cross cut of a pool - Different levels for different projects – match the level to the developer and the needs -Think of a team scenario… break projects down into the main components. Number the pieces, determine the levels, make assignments and plan accordingly. Almost like an assembly line for projects. Plan, prep, build, sign-off. |
|
|
AU 3008 |
|
Daily Tasks | 1/12/2015 |
• Emails and a phone call with Steve and my wife. My wife was listening to us talk and wanted to participate in the call. We put Steve on speaker phone and all three of us talked for over an hour. The main subject was interns, help, and current and future projects. • Breaking computers down and paying bills. • Went into Bridgerland to work with the interns. We worked on HTML tables, forms, and form controls. We then went into light database stuff and wiring up the form to a back-end database. Lots of good learning going on. 30 miles. • On the phone with a client back east. He needs help with the mini invoice (customer receipt) and a project called ICC’s or internal cost corrections. They would also like to fund a project to add average costing to the inventory model. I have mixed feelings about that…. |
|
|
AU 3657 |
|
Tech: XLS - DB - Loop | 1/12/2015 |
XLS – DB – Loop - Main customer - Flex grid o DMV# - Other 1 - From qry to var - Update – if a flex match, do a baby on just date - Insert – if no match – add full record (See examples: numbers & details on scan in photo gallery) |
|
|
AU 3567 |
|
Daily Tasks | 1/13/2015 |
• Email back to our GPS auto tracking client. • Emails to a client about an eBay data feed. • On the phone with my sister going over projects and direction. We talked about harnessing resources and organizing those resources. • Uploading new vide and code links for the adilas training page. • Prepping a small mini project for one of the new adilas interns. He will be building a PHP connection to the adilas web/API sockets. This will be his first little mini project. • Emails. • On the phone with our Colorado developer going over new code for in-line discounts. We did a quick GoToMeeting session and got him some new files. He is doing tons of custom code for a client out of California. • Went into Bridgerland to help do some intern training. The first hour was spent setting up systems with MySQL and ColdFusion. We then did a small form review and then got more into ColdFusion scopes, validation, and even data drill-downs. It may have been a bit deep for some of the guys. Anyway, we got some feedback and they want to see a project from start to finish. We’ll see what we can do to help them out. • One of our adilas interns did his first solo class tonight. He was teaching on lists, arrays, and structures. 30 miles. |
|
|
AU 3568 |
|
Daily Tasks | 1/14/2015 |
• On the phone with a client. She found an error on the sale stock/unit section for warranties. No taxes were being calculated. The code was hardcoded as a $0 tax. • Went in to Bridgerland to work with the interns. Setting up for class. • Talked with my brother and did some emails. • Posted some new video files online. 30 miles. • Meeting with an intern to go over the adilas API socket project. We did a light code review of the different pages. We drew some pictures and even listed out some flow stuff up on the board. • Working with the interns. Spent the whole day working on variables, lists, arrays, and structures. We spent quite a bit of time on each section and what each piece does and can do. Great class and it seemed to flow much better today. • Fixing a tax calculation issue with warranties on stock/units. Lots of testing and debugging. Posted new files online. |
|
|
|
Adi 917 |
|
Custom code - Deeper Client Search | 1/15/2015 |
Jan 8 (7 days ago) to dgrier, David, Brandon Hey Don! How about if I add a search field to your gun club homepage? I'd say $100 would pay a developer to knock that out for you. Thanks, Stephen Berkenkotter 719.439.1761 steve@adilas.biz :: www.adilas.biz "all data is live and searchable" The information in this e-mail and any attachment is client privileged and confidential. If you have received this e-mail in error, please notify the sender immediately. From: "Donald S. Grier" Sent: Thursday, January 08, 2015 12:06 PM To: davidb@adilas.biz Subject: RE: new adilas updates Hi David. Thanks for the update. One question. When we search our members, we can only pull up the individual member listed on the main portion of the account. We have family memberships where there are additional people that are part of a family membership (sometimes with the same last name, sometimes not). Is there any way that Brandon can add that when we search any name, Adilias will search all the members and the additional people on a membership? We could really use this feature. An example for me is below: If you searched “Grier” you would find me, but none of my family members on my account: Additional Contact/Address Info [add an additional contact/address] Contact Type 1: Wife First Name 1: Elizabeth Last Name 1: Grier Address 1: City 1: Prescott State 1: AZ Zip 1: 86305 Cell Phone 1: 928-420-3457 Show On Every Invoice 1: No Contact Type 2: Son First Name 2: Ethan Last Name 2: Frank Show On Every Invoice 2: No Contact Type 3: Son First Name 3: Aidan Last Name 3: Frank Show On Every Invoice 3: No Contact Type 4: Son First Name 4: Shane Last Name 4: Grier Show On Every Invoice 4: No So if I searched Aidan Frank, Adilias would not show him at all and would require that we add a new customer or our staff will tell the person they are not a member. Finally, we cannot delete an inactive customer or double entry. Sometimes, an employee does not find a customer and then re-inputs the information. We would like to delete the inactive account entirely, but cannot do that. Is that possible as well? Thanks, Don Donald S. Grier Prescott Gun Club 1200 Iron Springs Road Prescott, Arizona 86305 Telephone: 928-717-2218 Website: www.prescottgunclub.com |
|
|
AU 3569 |
|
Daily Tasks | 1/15/2015 |
• New logo for clients. • On the phone with Steve going over projects and how to break things up into smaller pieces. We also talked about sub inventory and cost controls (packaging). As well as ICC’s (internal cost corrections). On the ICC’s the two sides that are really important are the COGS (cost of goods sold) and then inventory value (assets on the balance sheet). • On the phone with a developer from Nebraska talking about a 3rd party API for Washington State. WE are going to be playing with API assignments and storing custom connections settings in JSON objects. Each corporation will be able to store their settings in a special object (JSON) that we will then be able to look-up and use as needed. • Went into Bridgerland to work with the interns. Working with an intern on his mini PHP and adilas API socket connection project. Lots of drawing and illustrating flow. 30 miles. • Teaching a class on if statements and conditional logic. Great session and lots of learning going on. |
|
|
AU 3658 |
|
Notes: Client's Needs | 1/15/2015 |
Client Needs: - ICC’s - New page - Invoice side o $0 price o $0 change COGS – this is the key o + & - o Physical quantities need to be up to date o Invoice to the company – customer invoice - Left side (I.S.) – COGS - Assets (B.S.) – Inventory Value - In db land o Play with formatting a date/time o Stamp into a number like 231716 = 23:17:16 |
|
|
AU 3570 |
|
Daily Tasks | 1/16/2015 | • Converting videos, uploading files, and doing emails. | |
|
AU 3571 |
|
Daily Tasks | 1/17/2015 |
• An intern came over to work with me. We got on a phone call with a client. He was telling us about a possible security breach dealing with permissions that got reassigned to a former owner. After hanging up, we called and left a message with Steve about the findings. I then turned off the user permissions and started to unwind what may have happened. I added a couple pieces of flex grid to help note and document the process. • Working with an intern on figuring out what changes were made on a client account. Ordered a copy of the database from 1/12/15. • The intern and I also worked on code to sign off on new 1099’s and W-2’s for the 2014 tax year. • More 1099 and W-2 tax form signoff stuff. Setup a new system for the intern and got him his first paycheck from adilas. • Working on the mini invoice and customer receipt page. Added code for in-line discounts and reformatted some of the line item output. • Working on an email to our client about our findings on his question about who was doing what inside of the system. Finished up the email to the client and sent copies to all players. • More work on the mini 3” invoice to include code for in-line discounts. |
|
|
AU 3572 |
|
Daily Tasks | 1/19/2015 |
• Going through emails and doing tech support stuff. • New logo for a client. • Adding a new news and updates section to the main login page about 1099’s and W-2’s. Added links to video clips and code samples for the intern training classes. Posted new files online. • Recording notes from loose pages and doing emails. • New logo for a client. • Research on using the adilas customer queue for project management on custom code projects. Also entered expenses and did emails. • Went into Bridgerland to work with the interns. We spent the first couple of hours getting local adilas systems up and running. We had a great discussion on file management and version control. Two interns were the main contributors. We then started to work on a live project but it kind of buried the guys. They aren’t really ready for that level yet. 30 miles. • Looking over and signing off on a new CPA homepage interface that Steve created. His code is getting better and tighter. Good stuff. |
|
|
|
Adi 920 |
|
Custom code - Email Invoice | 1/19/2015 |
From: "Jason Robillard" Sent: Thursday, January 08, 2015 11:36 AM To: davidb@adilas.biz Cc: "mark@greenfrogg.com" Subject: Re: fw: new adilas updates Great features buit dont really apply to our company. What has been promised to us for over a year now is an invoicing email feature without having to save each invoice as a pdf. I understand that that we are the small dog on the block but why make the promise then? Hope you are having a great year. Finally launched new code and email invoices and quotes feature on 9/5/15. This update note was added by Brandon Moore. |
|
|
AU 2933 |
|
Brainstorming on Round 2 of Elements of Time | 1/20/2015 |
Meeting with the adilas interns and going over objectives and scope for round 2 of elements of time. This will be the adilas project for the internship. We used two white boards and had an hour long session on what was included. See photos for more info. Image one has a list of database tables and which pieces are currently done and in place. There are a number of subs that still need some work. The first sub we will be tackeling is the sub GPS and RFID tag tracking piece. Our plans are to make a small sub project for training and then make it go live once everybody knows what is going on in a smaller scale. The other parts of photo one are a small flow chart of pages, the words functions (subs) and types of time applied to the templates, and a rough budget and timeframe for the project. The other image has a number of ways that people use time in their business. We listed and talked about a number of the different options such as: to do lists, basic calendar, reminders, tracking things, date/time spans, rentals, reservations, project management, events, schedules, appointments, meetings, seasonal things, marketing/sales/analytics, family history, inventory tracking, and dispatch. The other pieces of this photo are some small graphics talking about static vs. dynamic and some object lessons on one-to-many relationships. There is also a 3D world building model and how time, space, and money (resources) play into things. The last part is a small breakdown of time into smaller building blocks such as years, months, days, hours, minutes, etc. Great session and we should be starting on the process come next Monday as part of our class. |
|
|
AU 3573 |
|
Daily Tasks | 1/20/2015 |
• On the phone with Steve working on the adilas world files. We did a GoToMeeting session and I was doing some code. We followed a couple of paths and decided that we would just hard code the headers and footers instead of including the prebuild ones. • Went in to Bridgerland to meet with my brother. He had some graphic sketches that he wanted to show me. We also talked about a branching interactive graphic to show cause and effects for sales, purchase orders, and inventory tracking. 30 miles. • Working with the interns on loops and more logic. Great little session. We covered index loops, list loops, array loops, and structure or collection loops. After that we did a whiteboard session on round 2 of elements of time. We used two whole white boards and spent over an hour going over scope and depth of the project. I think it went over well. See elements of time #2933 in adilas university for photos of the whiteboards. • Emails and tech support stuff. |
|
|
AU 3583 |
|
Daily Ideas | 1/20/2015 |
I was reviewing my notebook (church one) from back on 10/10/14 and found some cool stuff on making the foundation a wrapper of sorts vs. a plain bottom level foundation. There are some good notes in that notebook. Here is an illustration that I liked… (Please see scan in photo gallery) - House on top of a foundation: foundation of a house. We place it at the bottom and then build up. - What if… the foundation is or was a giant wrapper. House built inside or wrapped inside of a bigger foundation. If God is our foundation… wouldn’t it be cool to have Him and His love surrounding or all around us – wrapped in His love. I think that would be cool. -Allow the media/content entries and/or pieces to be shown outside the secured environment. This means add a switch to make a piece public or customer facing (normal web). These pieces don’t have to be tied to anything and may be independent items. On the other hand… these media/content entries and/or pieces may be tied internally to an object or item inside. They can play either way –with or without a buddy. -The deeper we go… the more I see that harnessing resources and harvesting resources (both verbs) are so important. In our 3D World Building Model… they y axis is called “money” for something short and quick. However… it truly should be labeled resources. Lots of compound concepts… |
|
|
AU 3574 |
|
Daily Tasks | 1/21/2015 |
• Phone calls with a client about internal invoicing on stock/units. • On the phone with our Colorado developer going over in-line discounts. • Tech support, emails, and helping an intern on a customer data import. • On the phone with two other developers. Started with the one out of Nebraska going over a Washington state API socket connection. I was then on the phone with a developer from California talking about a kiosk and payment project. Crazy times. Bouncing from thing to thing… • Went into Bridgerland to work with the interns. We covered database basics as our topic. We went over lots of theory, concepts, and basic usage. We also wrote a number of queries and played with functions and different where clauses (filters and criteria). We even dipped into things called aggregate functions such as count, max, min, average, sum, etc. After playing inside the database, we started playing with ColdFusion and making ColdFusion talk to the database using form and URL variables. Good stuff. 30 miles. • Answering questions and helping an intern and my sister with different projects. An intern showed me his first round API socket connection using PHP. He had worked all night trying to get it done. I was impressed. It looked great. We will keep tweaking on it but a great start. Most likely we will add some features and documentation to help other developers out. That is exciting. • I also helped my sister with some tech support questions. She is doing a great job helping with the tech support stuff. • Went in to a different room and worked on cleaning up files to make a master copy of adilas code files. We are planning on putting up code on a site called bit bucket. The end goal is a form of version control for teams. • Working with an intern on getting our first full set of code up and online in a repository or code bank. The intern did most of the work. I also helped my sister out with a couple of tech support questions and admin removal options. • Recording notes and reviewing notebooks. Lots of stuff going on. |
|
|
AU 3575 |
|
Daily Tasks | 1/22/2015 |
• Tech support, emails, uploading videos, and paying bills. • Uploaded some new custom barcode labels for a client that an intern was working on. • Large email to a client going over custom code requirements and a progress report. He was the person who needed in-line discounts. We started that project over three months ago. It has dragged on and on but hopefully is nearing completion. Other tech support stuff. • Went into Bridgerland to work with the interns. I uploaded new video links for training. We then spent the first couple hours going more into database stuff. We kept expanding on queries, tables, joins, primary keys, foreign keys, indexes, wildcards, and dynamics. We added conditional logic (if statements) inside of queries, etc. Good session. • An intern taught the whole middle section and did a class on bit bucket, code repositories, team communication, and version control. He did a good job and was bouncing around and helping people. It was fun to see. For the night session, we did a two hour session on database joins and how relational models work. We had a good turn out and had a developer online with us from Salt Lake. We covered basic table joins, unions, self joins, filters, aliases, and other SQL stuff. We got a little bit deep but hopefully still good practice and information. We also jumped into live code and followed some page flow with real data. Good stuff. I think everybody was tired by the end of the day. 30 miles. |
|
|
|
Adi 921 |
|
Custom code - RFID | 1/22/2015 | ||
|
AU 3576 |
|
Daily Tasks | 1/23/2015 |
• Recording notes and planning. Posting new database video clips online for developers. • Working on restoring PO’s that were voided out in a client’s site. Wrote an email to others with an update. |
|
|
AU 3584 |
|
Daily Ideas | 1/23/2015 | -Add a time template setting for show on homepage or some sort of news an update piece. Think news, updates, notes, special sales, notices, cautions, and other communications. | |
|
AU 3577 |
|
Daily Tasks | 1/24/2015 |
• Brainstorming on our plan and new and upcoming options and ideas. The ideas just kept coming. See notes on other pages. This was an answer to prayers. Good stuff. • On the phone with Steve planning out a couple custom code projects. We did a GoToMeeting session and talked about requirements for adding the driver’s license field to the customers table. We made an outline and created a step by step checklist. We also talked about custom black box options for pages. We also talked about project management and delegation. Steve wanted to get more involved in the code side of things. • An intern came over to talk about goals for his internship. We decided that he would work on a gift card and customer loyalty card project. • We got a call from our developer in Salida and went over tax calculations and how the number of decimals play into rounding errors. • More work on the intern’s goals and objectives for his internship. • On the phone with a client going over needs and wants. • Working with a developer on procedures and protocols for developers. Lots of ideas on flow, delegating, inspecting, and approving. We brainstormed on the Adilas model for developing. As a side note, we are going to need to write out a testing and sign-off process and procedure. We need to start standardizing things. • Emails, tech support, and planning. • Emails and on the phone with a client going over things. Prepping files to help with some clean-up of her storage server database. |
|
|
AU 3585 |
|
Daily Ideas | 1/24/2015 |
-I have a plan! Review it, slow down, and focus. Work on specifics of that plan. Take the time to practice. Think about how you practice with a purpose for snowboarding. -The developers who can generate funds will help these who can’t. Once the stranger developers are ready, they can start doing independent jobs and projects. They could even start their own teams. -Take the developers on a round trip to meet with the rest of the adilas team. Have a team meeting and focus on our plan and where we are at on things. -Keep building out the customer facing pieces. This includes customer bill pay portal, eCommerce templates, front facing calendar, scheduling, media/content, web/API sockets, and eCommerce templates and black boxes. -On training and demos… Show real live people, where they are at, where they are headed, and a glimpse of the goal. Make it as real as possible. People can relate to that. A good example of that process is what we tried to do with Learn To Freeride. We used real people doing real tricks and moves at their level. We then did small video clips to help show progressions. -We want to build a house of bricks. A straw house is too easily blow down. That may take some time. -Use elements of time, photos, scans, media/content, and even the customer queue to help with adilas project management. -The customer queue is kind of like a big to do list… What if we added some code to make a system-wide template for a to-do list or project queue of sorts. We could allow some settings to be tweaked but maybe that would help people get their tasks and projects more organized. -The customer queue already has access from every page in the site… The mini calendar icon is another global access point. Elements of time and/or the customer queue would make a great combo. Make it easier to flow back and forth and between the queue and elements of time. -We had another request to mirror and/or make a back-up site available if the main servers go down. Mostly for parts, sales, and other mission critical pieces. As a side note… This could be a great 3rd part application that someone could charge for and develop. -Similar to the eCommerce and main view cart page, we need to add black boxes all around the site. -These black boxes could almost go to the level of open source with custom black box options. -The black boxes are virtually hooks or options to insert or add custom code. We are thinking about at least 4 custom access points per page. They would be – top or full takeover, css (cascading style sheets) box, top mini – under the header, and bottom mini – just above the bottom footer. Custom black box options: (please see scan in photo gallery) 1. Top or full take over 2. CSS 3. Top mini 4. Bottom mini A black box is where we put and/or access custom code per page. See notes on 2/5/15. Added two more for custom headers and footers. Our black box naming convention will be: (pretend that corp #77 is wanting custom code) 1. Top of full takeover – name_of_page_777.cfm 2. CSS – corp_css_777.css 3. Top mini – name_of_page_top_777.cfm 4. Bottom mini – name_of_page_bottom_777.cfm -Steve had the idea of being able to virtually “pin” the to-do list to the calendar and then let it float day to day. Just an idea. -Use the system to teach and show full cause and effects. Steve had the idea of showing a graphic of what is done and what is happening. Education and training as it happens. This may end up being a virtual watcher and/or feeder or sorts. -Get back to mapping and planning things out. That is a huge part of the game and/or puzzle. -Steve and I were talking and he said that he was taught a simple acronym of DIA. This acronym stood for: D = Delegate I = Inspect A = Approve -As we kept talking… We thought about ways of taking the DIA acronym and evolving it into the acronym of ADILAS. The word adilas is already an acronym of “all data is live and searchable”. We thought it might be fun to create a development cycle that used the letters that go with adilas. Here is what we came up with… still kind of rough… A – Acquire, Accept, Approve Requests D – Delegate to our team, Determine the scope, goals, budgets, and project management I – Inspect - microscope, details, inspect what you expect L – Love (you, them, us), logging & communication, learning A – Approve - clean up, upload, feedback S – Submit - close out project, push code up, bill, etc. |
|
|
AU 3659 |
|
Tech: Adding a Driver's License Field & ADILAS Acronym Brainstorming | 1/24/2015 |
Project: Adding the driver’s license field to the customers table 1. We need to add the field to the database a. Name = driver’s license b. Datatype = varchar c. Size = 100 d. Default = Null 2. We need to script that change… this allows us to update all of the other systems a. Show Steve how to do this… 3. We start at the add process a. Add a new field to add edit customer cfm 4. We need to cascade that field all the out to the action file – add edit customer action cfm a. Add validation b. Add to the add method c. Add to the update or edit method d. Unknown – search those methods to see if we cascade i. We also need to search for all instances of “INSERT INTO Customers (“ 5. We need to check eCommerce land… adds, edits, validation, actions… 6. We need to the driver license to the customer log cfm 7. We need the same field (showing it or outputting it) on the customer gallery, customer history 8. We need to add it to the quick search a. Tying it underneath the normal customer search field for quick searches i. New or clause 9. We need to add the field to the advanced customer search cfm 10. We need to add the same field to the output or search results page – advanced customer search results cfm a. We also need to make sure that we pass the correct values to all other including refine search, pagination (next page of n), as well as exports to excel 11. We need to check other places where customer gets exported to excel 12. Get a sign-off on new code changes 13. Clean-up – we need to modify help files and push all new code to all servers 14. Billing for the project - $400 Sketch – Testing protocol flow & testing from different sources: (see sketches on scan in photo gallery) D – Delegate I – Inspect A – Approve ADILAS: A – Acquire, Accepts, Approve Requests D – Delegate to our team, Determine the scope, goals, budgets (internal project management), planning, timelines, assignments, expectations, testing, validations, multi-source or access, non-linear & special cases, future proofing I – Inspect – details, microscope, inspect what we expect, iterations (going through the testing and processes), develop, local, test local, simulate live, get sign-offs (project managers & supervisors lead) L – Love (use, them, you), logging and communication, love (feedback, customer, developer, encouragement), logistics, learning. A – Approve – clean-up, upload, feedback S – Submit – close out project, push code, bill, etc. Water – snow – ice Project: WA State API 1. Jeremy has a java class (functions) written and mostly done 2. He was going to be converting those classes into a CFC 3. I have an assignment to create a holding container for the username, password, license number, and use WA API (yes/no). This is a 3rd party piece and will end up storing a JSON object. 2 hours 4. Test and run it…. 5. Cascade code around the adilas site for usage… Project: Swipe a driver’s license to see if person exists: 1. What is the scope of the project… a. We have to have a swiper b. Customer page to accept this date – new interface page tied to the chooser c. Trying to key off of the license field – tearing apart the scan i. From FORM scope to the variables scope (drawers 3 to 1) 1. We need first and last name, driver’s license, all of the raw data d. From variables scope (drawer 1) to session scope for temp storage (drawer 4) e. If we find a match, go to that page or customer log f. If no, we need to have other options… i. Flip to a first name and last name search 1. Truncate to the first 3 of the first and first 3 of the last name a. Check for a match on both first and mini last (3 chars each) b. Check for a match just on mini last name c. Check for a match just on mini first name |
|
|
AU 2934 |
|
Brainstorming & Planning A GPS Mini Project | 1/26/2015 |
We had a planning session with the adilas interns to help with a mini project connecting elements of time to the sub GPS and RFID tag tracking pieces. This will be a joint mini project to get them into the groove of what is going on. These photos are dealing with page flow and database tables and specs for the mini project. Once the mini project is done, we will help them convert code into production level code and activate this functionality as a sub of time. |
|
|
AU 3578 |
|
Daily Tasks | 1/26/2015 |
• Working on bulk voids for a client and doing some clean-up for another client. Sent emails with info and updates. • Working on ICC’s (internal cost corrections). Gathering ideas and doing research inside of adilas and adilas university. Looking over past notebooks and scans. • Emails. Helping an intern out with some custom logic on a data import. Reviewing some of Steve’s code and helping my sister with some tech support stuff. • Went into Bridgerland to work with the interns. We did a couple hours of review. Each of the guys took turns being in front of the class reviewing code and going over things. After the review, we started planning out our joint min project for elements of time and sub GPS and RFID tag tracking. We made a flow chart and started to define database tables and such. See elements of time #2934 inside of adilas university for photos of the white board planning sessions. 30 miles. |
|
|
AU 3586 |
|
Daily Ideas | 1/26/2015 | -Move and transfer some of the coding ideas and things to do over from the main adilas site over to adilas university site. Help create a single source library to help with research. These additions may go good in the adilas university site under the section called categories inside of elements of time. Basically, grouped research in a single location or library. | |
|
AU 3579 |
|
Daily Tasks | 1/27/2015 |
• Emails and lining out an intern on some new server projects and such. • Working with Steve on a 3rd party solution for the Washington State Liquor Board and the API socket settings. We used a GoToMeeting session and worked together for a couple of hours. • Went in to Bridgerland to work with the interns. We worked on methods and functions. We also ended up working with session scope variables and a bunch of other things. Kind of random but I hope it was good for the guys to see the development process. 30 miles. |
|
|
|
Adi 925 |
|
Custom code - Pricing Sort Order | 1/27/2015 |
When could you build a sort option on the web interface of Adilas, that would allow the user to sort by price (low to high) and high to low? Chris Conger |
|
|
|
AU 3344 |
|
Brainstorming on the mini GPS project | 1/28/2015 | See the Word Doc to get all of the files for the our mini GPS project. | |
|
AU 3580 |
|
Daily Tasks | 1/28/2015 |
• New logos for clients. Also uploaded other files and other small code tweaks. • Recording notes from loose pages and post-it notes. • Working with Steve on his customer driver’s license field and associated pages of code. • Went in to Bridgerland to work with the interns. We spent the day working on our little mini project. We created a new database from our brainstorming pages. We then added some new pages and linked them together. We then started to add code to the files. Fun little exercise. For the night class we switched over to an intro to the adilas API (application programming interface) socket connections. We went over flow, ideas, how things work, and what goes on between the API calls. Lots of server talk. Good stuff. 30 miles. |
|
|
AU 3581 |
|
Daily Tasks | 1/29/2015 |
• Reviewing video footage from yesterday’s classes. Lots of good resources for our current crew as well as for future developers. There is over 30+ new hours of specific code and application programming training. That will help out as we move forward. I don’t know what the end goal is yet but we are building up some great resources. • Working on a custom cart include for a client. They have a special tax fee that needs to be applied and included on every new shopping cart. We will be using one of the new cart black boxes to help with some custom code for them. • Uploading new links and videos from training. Also uploaded some code samples. • Working with an intern on some ColdFusion updates and working on configuring a new server for adilas data 3. On the phone with Steve working on a magnetic card reader for California driver’s license. Did some planning and pointing him in a good direction. • Emails and clean-up. • New logo for a client out of San Francisco. • Went in to Bridgerland to work with the interns. We spent the whole day working on the mini GPS project. The first part of the day was dealing with inserting data. The middle part was working on doing data drill-downs and passing URL and FORM scoped variables around. The night class was a review and doing some debugging. Great session. We had some pizza between the afternoon and evening session. This was our last structured teaching session for this round of interns. Next month will be on to individual projects. 30 miles. |
|
|
AU 3660 |
|
Settings: Shopping Cart | 1/29/2015 |
Settings: (Shopping Cart) - Gram limit - Categories list Other notes: - Use cart original list price extended - Use cart line price Incoming temps: - Current Form Qty - Current Form Price - Current Form Description - Current Form Show - Current Form Tax - Current Form Tax ID - Current Form Tax Name - Current Form RFID Actual line array: - Line quantity - Item price - Extended line total |
|
|
AU 3582 |
|
Daily Tasks | 1/30/2015 |
• Up early working with an intern to help update ColdFusion servers. We did updates on data 0, data 1, and data 2. We used GoToMeeting and I basically watched as the intern bounced around and did a knockout job. Lots of random craziness. He did a great job. I updated the training videos and uploaded code samples. Emails and other crazy things. Lots of things are going on right now. Busy, busy! • An intern came over and we worked on some custom updates from prior data migrations. We also built some update pages to run some new clean-up and migration routines. These updates were for some clients out of California. |
|
|
|
Shop 3811 |
|
Virtual Post-It Note | 1/30/2015 |
|
|