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 - 11/1/2014 to 11/30/2014 - (56)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 2907 |
|
Daily Tasks | 11/1/2014 |
• Working on in-line discounts and adding in the manager’s approval option for discounts. Added some new methods to look-up users per permission and then sub password or sub sign-off checks. Started adding the preset discount campaign buttons to the bulk discount calculator page. • Working on preset discount campaigns and applying discounts on the cart as a whole. • More discount work. Changed time zones for day light saving on all servers. Add the new trade show banners to the web site. |
|
|
AU 2915 |
|
Daily Ideas | 11/1/2014 |
-On my cart favorites… what about a new kind of button that could call and/or display custom code. That could allow custom stuff (code) to be run or shown from inside the shopping cart. -Button name – goes here – custom code button – possible option for my cart favorites |
|
|
AU 2908 |
|
Daily Tasks | 11/3/2014 |
• Updated some code to help with restoring quotes to the shopping cart and duplicating invoices. Added small fixes to allow these pages to play with in-line discounts and discount campaigns. Emails and light tech support stuff. • Email update on the discount project. • Recording notes and drawing in my notebook. • Working with my brother on loops and formatting variables. An intern came over and we worked on validation for his web/API documentation project. • Recording loose notes and pages into my notebook. • On a phone call and GoToMeeting session with a developer. We covered more adilas login info and underlying code logic. Lots of review and even got into some new territory. |
|
|
AU 2916 |
|
Daily Ideas | 11/3/2014 |
-We had a request to record a button or general sales campaign per line item. People want to track their promotions. -Maybe use the discounts campaign field to track gift card numbers, discounts, sales, coupons, etc. Basically, that field is a hidden, in-line independent field that may contain data per transaction. -See notes on 10/18/14 about rewards cards, lunch cards, etc. It might be cool to allow for all kinds of special marketing or campaign tracking stuff. |
|
|
Adi 905 |
|
Logos for adilas university | 11/4/2014 | See attached... These are three ideas that were created by Dave Forbis for logos for adilas university. We can add any verbage that we want, these are just the logos or shapes. | |
|
AU 2789 |
|
Logo ideas and proofs for adilas university | 11/4/2014 | See attached... These are three ideas that were created by Dave Forbis for logos for adilas university. We can add any verbage that we want, these are just the logos or shapes. | |
|
AU 2909 |
|
Daily Tasks | 11/4/2014 |
• Brainstorming on presets and allowing a number of predefined functions to be a sub of time. See prior notes. • Brainstorming on simple tools like pencils, paper, grids, spreadsheets, etc. Also some thoughts on "tweeners" or "inbetweeners". We need to set the key frames and then allow others to help fill in the gaps between the key frames. See notes on Disney and Flash (back a page). • Got some new logos from a marketing consultant for adilas university. I put them online and sent an email out to different people trying to get their opinion. Other email stuff. • Working on the standalone discount options for the new discount calculator page. I need code to do both in-line discounts (new) and standalone discounts (older). • On the phone with Steve. We talked options and did a GoToMeeting session. We worked on the adilas world (live help) pieces and showing images and gallery stuff. We also worked on some of Steve’s sales reports and graphs. • On the phone with a consultant going over things for a conference call later today. Also reformatted the new adilas banners back to a Photoshop file type for a print shop. • Tech support. • On the phone with a client. We talked adilas for a while and then we talked about the client's own virtual warboard product. I took a page of notes but it sounds like a fun future project. It will include transforming day-to-day business data into a virtual game or virtual reality model. Kind of like my idea of making a virtual movie of how the data and players interact and play together. See my notes from later 2010 into early 2011. Anyway, I have a page of notes. This client’s stuff has some purpose based projections and cascading data forward pieces that could and will be fun to play with. • Working with my brother on formatting data and variables. • Working on clearing all discounts that are set from the bulk discount calculator. • Working on displaying the data on the bulk discount calculator page. The project is slowly coming together. |
|
|
AU 2917 |
|
Daily Ideas | 11/4/2014 |
-Presets… preset attributes, preset attribute pools, preset attribute grids, preset rules and assignments, preset colors, preset colors, and sizes, preset pricing matrix, preset sizes, preset qualities, preset weights, preset conversions, preset custom options, preset rules, preset assignment pools, preset stages, preset phases, preset sub locations, preset checkpoints, preset goals, preset groups, preset categories, preset measurements, preset allowances, preset layers, preset campaigns, preset coupons, preset discounts or prices based on time (time or hour related sales), preset quantities, preset settings, preset permissions, preset whatevers… Define your space with presets -What if we helped and provided tons of preset options. We could let the people name the pieces, add/edit the preset values, and then assign and use them as needed. It could almost be a preset library of sorts. -All of these presets cold be done in-line to help it feel like it was part of the original. -On presets and how to assign them to time… Think shopping for options or shopping for presets. Option 1: - Need presets o Color only o Black o Blue o Purple o Red - Size only (add) o XS o S o M o L - Color and size o Grid (add) o Colors on the select top & side o Mini grid - Pricing matrix o Etc. Option 2: - Need presets o Buttons - Click to setup or select o Colors only o Sizes only o Colors and sizes (grid) o Pricing matrix (grid) o Marketing campaigns o Attributes o Assignment pools Option 3: - Need presets??? - Setup/Use Existing – o Colors o Sizes o Colors and sizes o Pricing matrix o Market o Assignment pools o Attributes - I ran out of room but basically buttons to add, use existing, and then the preset name -Presets don’t have to be tied to time and elements of time… What if we just set them up as if the system owned them… We could then use them with time or any other piece without forcing the user to go to elements of time to set them up or use them. Make time and space be sort of transparent or background features. -A pencil – It could be that simple. What did they use while they were trying to make a pen that would work in space? A pencil. Dieter F. Uchtdorf “Of Things That Matter Most” – October 2010 Conference address -A classic grid or spreadsheet. Very simple tools that may be used without too much hassle. -Simple text lists. Pick and choose attributes, store all of the pieces in simple text lists. This is a poor man’s one to many relationship container. -Add check boxes to add the attributes. -Tweeners – or the in between pieces. Disney did key frames of his mouse (Mickey) character… then they hired artists to fill in between the key frames. Adobe Flash uses tween or inbetweeners. Interesting concept. -Pretend that this was a picture of a person laying in a bed. The key frames are laying and then sitting. The in between frames or the tween is what goes in the middle. -Key frame: person in a bed (laying) – tweens or in-betweens – Key frame: person sitting in a bed (please see sketch in photo gallery) |
|
|
AU 3727 |
|
Notes - From a Call with a Client | 11/4/2014 |
Notes from a phone call with a new client: - “War board” - “Business as a war game” - Purpose driven - Supply chain - Virtual reality - State & status on everything based on purpose - Disruptive technology - Through put accelerator - Communications - Business turn around - Oxygen & cash flow - 1985 – disk based game - Attari – 94-95 - Operations - Time, money, personnel - Adam Smith – “Wealth of Nations” - Division of Labor – sometimes people use people as tools - Everything is seen – total push model |
|
|
AU 2910 |
|
Daily Tasks | 11/5/2014 |
• Added the new trade show banners and graphics to the tools and features page on the main adils.biz site. Helping an intern with icon menus for elements of time. • On the phone with a developer talking about needs for development access to live (production) database assets and tables. We talked about security and privacy and how to help keep track of what is going on. We talked about setting up a consulting meeting for mid-November to discuss these topics further. • Went in to town to meet with some developers for a lunch meeting. We talked a lot about learning curves, help files, development, and project management, I extended to both of them that I would like to hire them for 5-10 hours a week for adilas projects. 30 miles. • Helping an intern with error handling and page validation. Got a special SQL tool up and online for adilas developers to use. This allows a direct, view only, SQL select query to be run on live production data. The system will monitor requests behind the scenes. • Recording notes from loose pages and post-it notes. |
|
|
AU 2918 |
|
Daily Ideas | 11/5/2014 |
-We need to make communication more a part of the whole system. This is true internally, externally, and everywhere in between as well. I think that elements of time needs to step up and play! -I was listening to a mother help her child with math – What do you know? What is your strategy? Etc. Fun to listen to her help and lead her child. |
|
|
AU 2911 |
|
Daily Tasks | 11/6/2014 | • Recording notes in my notebook. Trying to catch up. | |
|
AU 2912 |
|
Daily Tasks | 11/7/2014 |
• Spent all day in Mantua, UT, at the Box Elder Campground recording hours and notes from loose pages and post-it notes into my real notebook. I’ve been a bit behind. • More of the same… recording notes and drawings from loose pages into my notebook. |
|
|
AU 2919 |
|
Daily Ideas | 11/7/2014 |
-For best results – align yourself with the laws of nature and the laws of God. I was sleeping in my SUV (Chevy Tahoe) on the way home from a river trip in Southern Utah. I was way up in the mountains and just parked off the road. The vehicle was parked on a pretty good slant. I was tired. I folded down the seat, threw out a sleeping pad, and grabbed my sleeping bag. I then laid down and went to sleep. However, because I wasn’t aligned with the laws of nature (meaning gravity, slopes, and angles) I ended up fighting all night to get comfortable. In the morning when I was more awake, I kept thinking… Man, it sure is easier if we align ourselves with the laws of nature and the laws of God. Things just naturally go better and we don’t have to fight a losing battle. -Not to be gross, but we (as a company and as an application) need to be able to excrete and/or dump waste. We’ve got to get it to that level. If not, over time, it will get toxic. We’ve got to be able to excrete or dump waste. -The reason for the comment above deals with trying to pattern our needs after what nature already does. Lots of great lessons are right in front of us. I spent 7-8 hours today at a public campground and picnic area recording notes in my notebook. During that time I had to use the restroom a number of times. Each time, I kept thinking how important that process was and also the where that process takes place is also very important. When I’m at home, the bathroom is just down the hall… when I’m outside, it can be more open (a tree, a bush, etc.) or it could be a small hike each time to be in the right place. In a shared public environment, if waste (any type including trash, rubbish, and body waste) isn’t disposed of properly, it could get out of control and eventually become toxic. Anyway, just drawing some parallels between nature and web applications. -Try to drain the pond a little bit… I keep writing and writing… Maybe I need to keep more on top of things. Maybe, I’ll start uploading my own notes instead of making my sister take care of all of that. That might help if I could do a little at a time. -I did some calculations… I need about $2,000 to $3,000 a week to keep my current people, interns, developers, designers, and helpers going. That is 6-8 hours a piece for about 10 people. There is a current team of 10. That’s a pretty good team! Let’s make it happen. |
|
|
AU 2913 |
|
Daily Tasks | 11/8/2014 |
• A developer came over and we did a simple demo method or function from scratch clear out to the API socket level. It was a good session. • Recording ideas and notes. As of today, I’m actually caught back up… yea! |
|
|
AU 2920 |
|
Daily Ideas | 11/8/2014 | -Check on developersnotebook.com as a new domain name. | |
|
AU 2921 |
|
Daily Ideas | 11/9/2014 |
-Be one in a million – The Friend Magazine. I want to be one of the many who help and play the game. -I re-read and watched a talk by Dieter F. Uchtdorf – “Of Things That Matter Most” – October 2010 General Conference. A great talk on slowing down and focusing on what matters most. He speaks of the simplicity of a pencil. A coach teaching his athletes the basics and fundamentals, even when they had already played the game for years. They would only become great by mastering those core fundamentals. Take the time to create and foster relationships with God, family, other people (fellowman), and one’s self. It takes time but has great side effects and lasting results. -Teach the basics again and again and again. That is where true learning comes from. These are the keys. The fundamental and foundational principles or doctrines give us understanding and capacity. |
|
|
AU 2914 |
|
Daily Tasks | 11/10/2014 |
• Sorting through tons of email. New logos for clients and starting to prep a patient upload. • Working with an intern on his icon menus for elements of time. • Phone calls and emails. Paying bills. • Helping an intern with more icon menus for elements of time. • More prep work for a patient upload. Did the full patient upload. Invoiced and sent an email update. • Emails, tech support, and phone calls. Trying to clean up emails and support tickets. • Small web/API demo code clean-up. Working on adding both test and live modes to the API test mode (pre-built visual interface) page. • On the phone with a developer going over flex grid assignments and data logic. He is building custom code and logic for an advanced pricing matrix of sorts. Pretty intense. • On the phone with a web designer from Salida. She is going to be working on an eCommerce website for a client. • Adding some new page flow to the adilas API pre-built interface. Trying to make the page and section more user friendly. • Working on the help file for the adilas web/API sockets and data ports. Took off the word test mode and changed it to pre-built visual API mode. I want people to know that the page is in live mode all the time. |
|
|
AU 3728 |
|
Tech - API FORM Fields & Elements of Time Form | 11/10/2014 |
API Testing FORM Fields: - FORM: o Call function date o Call function name o Calling server ip o Calling server name o Corp key id o Current payee id o How many rows o Input output type – a “JSON” o Page submitted o Row data 1 o Row title 1 o Step o Test live switch – “test” o URL encoding = “Auto” o Username o User password Template Main Project: (See sketch/layout in photo gallery) Round 1: - Main Details: o Color o Title o Client o Actions status o Finished o Main date o Priority o Targets o Budgets o Note (scope) - Action status logs: o No notes - Sub dates & times: o Name o Start & end dates o Allows small notes o Track time - Sub comments: o Phases o Huge notes o Date or both date & time o Emails - Flex grid o Expenses o Invoice o Quotes o Sub time card - Photos/scans - Media/content |
|
|
AU 2873 |
|
Daily Tasks | 11/11/2014 |
|
|
|
AU 2875 |
|
Daily Ideas | 11/11/2014 |
-Adilas will need to make the first eCommerce API templates. Ideally the web designers will need ColdFusion installed on their machine. All other interactions will be done using real live API calls. The first template will be tied to a demo site. Keep it simple and help them see the whole flow... These templates will be given to other designers and developers. Anyway, adilas will need to make the first eCommerce API templates. -Point people to God! -One of the big holes seems to be on adding new items. People just want to create the item without tying it to the PO first. We used to allow that, but it ended up stranding or leaving random parts all around. Maybe we will need to look back into that or provide some help as people aren't really able to find their way very easy. Communication is so important. Help out wherever possible! -What has been promised? -Who is doing what? -What are the expectations? -Timelines, budgets, scope, etc. -Triangular sketch – 3 points – Client, Adilas, Other parties (developers, designers, reps, consultants, etc.) -3D levels – x=time or timelines, y=money or budgets, z=space or scope -Communication needs to run over and through all levels and dimensions. That is so important. A modern buzz word is: Unified Communications or UC. Ideas from a developer out of Salida, CO: -We need to get the shopping cart to an API level. There is tons of code but it is all in-line or hardcoded per page right now. We need to get it to function or method (API) type level. -The system needs to own the core. Set things up on a one-to-many relationship wherever possible. Standardize as needed. -We haven't even launched in-line discounts yet and we are seeing a need for multi-discounts per line item. For example a veterans discount as well as a weight or quantity discount. I'm assuming, but if we need two right now... we will need three, four, five, etc. (multi or unlimited) by the time we are done. |
|
|
AU 2874 |
|
Daily Tasks | 11/12/2014 |
|
|
|
AU 2876 |
|
Daily Ideas | 11/12/2014 |
3D Concepts of time, money, and space could also be stated as: timelines, budgets, and scope. Anyway, the terms used don't really matter... It still comes back to tracking objects and data over time. -X=Time, timelines, checkpoints, phases, stations, events, stamps, actions, reactions, cause and effects, histories, ages, aging, flow, milestones, periods, seasons, maturity, term, cycles, ranges, scheduling, dates, etc. -Y=Money, budgets, financials, balances, accountability, accounting, funding, cash flow, trending, profits, losses, assets, liabilities, equity, capital, revenue, cost of goods sold, expenses, forecasting, registers, etc. -Z=Space, scope, depth, levels, layers, stacking, adding and subtracting, multiplying and dividing, wrapping, covering, uncovering, organization, packaging, bundling, processing, locations, sub locations, moving or categorizing, types, subs, details, grouping, spreading, joining, chaos, order, etc. -What about establishing multi-point locations or geographic areas? Think of uni (1), bi (2), tri(3), quad(4), and poly(unlimited) points to determine a certain place, location, perimeter, boundary, or area. My dad and I were talking about GPS tracking and RFID tag tracking this morning on our walk. Anyway, a location or sub location may need to be defined further. At the same point, it might be nice to keep things general unless more points or details are needed. Maybe optional pieces if more is required. This might also deal with multiple naming conventions and an unlimited amount of locations and sub locations. -It might just be me... but everything seems to be going in a sub or small detail level. Most people don't want to stay there very long but they need that level of control. I think that it is interesting how we rolled out round one of elements of time... We have a build your own temple structure (point and click interface), we allow for types, kinds, functions, subs, etc. Each template is independent of any others. The report types are also interesting... We have calendar, time-slot, details, groups, build your own, and even exports to Microsoft Excel. Tons of options. I really think that elements of time is our most progressive system yet. And where we are headed is really fun as well. We want more tie-ins, more transparency, more custom interfaces, more ease of use, more options, and more functions. At the same time... we want simple, intuitive, dumbed down, and still lightning fast speed. It has to be all of these things. That's a pretty tall order... Well, I guess we know what the goal is... Now we just need to do it! Yee Haw! On the phone with a developer from Salida... Small ideas and future to do list: -Make a black box inside the shopping cart. It will be created and cleared just like normal. The custom code or settings (weight calcs, discounts, rules, etc.) will then be fully custom based on needs of the client and the developer. Basically, we will acknowledge that it is there but won't touch it other than creating it and clearing it. (Black box inside the cart) -On page level black boxes... Don't include an abort code. Let the developer leave it out to make the custom code transparent or have them add it to their page which will virtually take over or pass full control and display to their code. -We need a recalc cost method or function... Pass in the current cart structure line items and return totals and cart calculations. -Maybe think about using spreadsheet type documents as simple databases. They are quick and easy to update... however they are not as quick to be searched or as standardized as normal databases. We may need to pick and choose when to use what tools. -We need our own little mini spreadsheet or quick grid tool. Basically an app where you can create your own grid on the fly. We could do simple math, simple formatting, and be able to export out to a real spreadsheet like Microsoft Excel or Google spreadsheets. -Another idea is to allow custom mapping from adilas to a spreadsheet. This could be something like – put the item number in G4 or the price in H4 or the description in I4. Use rows, columns, and the laser focus and place data and hardcoded values as needed. -What if each spreadsheet was just stored as a JSON object verses a real database table. Basically, can make, store, and show a simple grid that the system can use and manipulate almost on the fly... (Sketch in photo gallery – quick grid tool, How many rows? How many columns?) -On all parts look-up’s add all parts and pieces. We need all available fields to show up for roll call. This deals with general inventory items and invoice line items. We are starting to use more and more of the other options. |
|
|
AU 2935 |
|
Daily Tasks | 11/13/2014 |
• Scanning pages of my notebook and sending them to my sister. • Working with an intern on icon menus. • Light work on in-line discounts. • Signing off on new icon menus that the intern created. • Lots of work on elements of time pages and media/content pages. • Talking with an intern about the process of bringing on new developers. See other notes for full details. • Recording notes on new adilas interns and on boarding processes for new developers. • Adding in a new custom code – black box option to the shopping cart. This allows for transparent cart code and logic or for full on taking over the cart display, layout, and interface. Working with our developer out of Salida on flow and logic for the new black box options. Pretty cool! • Checking out the first piece of custom code to go into the shopping cart. The developer created some custom logic that checks items, quantities, prices, and weights and figures out a pricing matrix accordingly. Pretty in-depth. Emails back and forth. |
|
|
AU 2950 |
|
Daily Ideas | 11/13/2014 |
-I went to a large multi-stake Priesthood training meeting tonight. Very good training. The whole thing was on the meaning of the Sacrament and how we, personally, can remember Him, meaning Jesus Christ. I loved how they used principles of learn, act, share – over and over. Very effective way of teaching. It encourages participation and interaction. It also has deeper levels of learning because you end up learning from multiple sources, including directly from the Spirit or the Holy Ghost. On boarding new interns & developers: Ideas between an adilas intern and Brandon dealing with bringing on new adilas developers: 1. See notes from 9/12/14 for requirements for new adilas interns. Lots of good stuff there. 2. Looking for skilled independents (contract labor) 3. Start them out at $10 per hour. Keep them at this until they are ready to move up 4. Require 30 hours of training. That would be 15 hours of Cold Fusion, 10 hours of adilas training, and 5 hours working with Brandon or other adilas developer/trainer on projects. 5. We would pay $300 for the training. That works out to $10 per hour for training. 6. On budgeting … We can budget $300 for Cold Fusion (code) training. $200 for adilas training and $300 to pay the new developers. Our goal is to get the new persons trained for $800 or less. The $300 & $200 for training would go to the instructors or trainers. The other $300 would go directly to the new developer. This way we try to cover all parties. 7. Our goal for the new developers would be to get them to the $35-$50 per hour rate. At that point their skills will be enough to help them do whatever they want to do. 8. The whole project is just in time. Just in time projects, just in time funding, just in time skill sets. 9. Dream dreams! Follow those dreams! |
|
|
AU 3729 |
|
Brainstorming - On-Boarding Interns | 11/13/2014 |
Working with an intern on developing a program to help new developers come on board – See 9/12/14 for requirements On Boarding: - Skilled independents - $10 per hour - 30 hours training o 15 CF – back to instructors o 10 adilas o 5 project or with Brandon o $300 pay them o $300 CF teacher o $200 adilas teacher - Once on board as independent, keep at $10 for the first month - Just in time - My goal with skills to $35-50 - How to pay back - Dreams! Planning numbers & budgets |
|
|
AU 2936 |
|
Daily Tasks | 11/14/2014 |
• Working on custom code for a shopping cart include. Going line by line. • More work on a developer’s custom shopping cart code. On the phone with the developer and then emails. Sent him my final copy and revisions. • Working with an intern on new training criteria for new developers. Uploaded some new files with icon menus. Found that some of the new files had overwritten some previous changes. Small version control issue. Reverted back to older files and put files in question into a temporary staging folder. Fixed problem online and talked with the intern about sign-off processes. See other notes for details. • Recording notes and ideas on version control and code sign-off processes. • Meeting with an adilas associate about project management and bringing on new qualified adilas developers. We are going to be adding new adilas university classes for HTML, ColdFusion, Database stuff, and adilas basics. See other notes for details. • Recording notes from loose pages into my notebook. See notes: • Signing off on icon menu pages from an intern. Pages are for media/content and elements of time. Small tweaks and checking code. Added some java script to help with subs of time. I added a counter for the caption for sub dates and times. |
|
|
AU 2951 |
|
Daily Ideas | 11/14/2014 |
Code Sign-Off Process: 10. Sign-off on code and add small version control per page. Talking with an adilas intern. 11. I would like to work with developers on their machines and sign-off on things locally. 12. Once a page has been signed off locally, the developer will upload pages into the top secret/need sign offs folder. This will keep it out of production until it gets a final gate keeper review. 13. The gate keeper (Brandon for now) will pull down the files that need a sign-off. The gate keeper will then test and make sure that things are good to go to production. 14. Once put in production, new code will be put up online in the released or normal top secret folders. All developers will go to the FTP server to get the latest files that have been released. We had a request to help manage max & minimum inventory levels across companies. That sounds like application flex grid or real in-line extensions. These projects are gaining momentum and heat. New Developers: 15. Meeting with an adilas associate and talking about a company that can help or who would manage the process of bringing people on board and bringing them up to speed. Both reps and consultants as well as developers. We are focusing on the developers right now. 16. Film and record all of the training pieces and put them up on adilas university. 17. Have a test and/or certification level to help with skill sign offs. Maybe use flex grid tie-ins or elements of time to accomplish this. 18. Do things once and then use over and over again. 19. Make the first video as a 5 minute overview. Keep it brief. 20. Anybody new needs to go through the process. 21. Use the code segment – can act as an evaluation process of sorts. Basically, do we want to spend the money on their education? In other words, a trial period of sorts. 22. Plan some 2 hour session in December & November – monthly & weekly training sessions. 23. -Generally schedule out time frames for each subject. o Topic: • Bullet points • Requirements • Options • Visual aids • Time frame 24. Double the bang for the buck… show code sample and concepts and how they relate to adilas. Put the concepts into action at the source. 25. Use all of the different teaching methods and learning styles. Audio, visual, actual, hands on, etc. 26. There will be quite a lot of time in both pre & post production stuff. 27. API – Play at the wall! This is where we could support the largest number of code developers. 28. Do a small 1-2 hour seminar for interested developers – Look for people who are interested. Pull from a bigger pool! 29. Start the first seminar with hand-picked folks who want to play. 30. Use the seminars and meetings as a screening process for qualified people. Help them get the skills to pay the bills. Share, share, share! 31. Try storming – Be willing to circle back around. 32. It is ok to break models. We do it all the time. BE sensitive about his but don’t fear. Take more counsel from your faith, hopes, and dreams than from your fears. Let faith win! 33. When teaching a code class, it might be cool to have a way for class participants to submit and run code. Maybe use elements of time and sub comments. Maybe each person has their own main element and then uses the sub comments for assignments. |
|
|
AU 3730 |
|
Brainstorming - On-Boarding Interns & Code Sign-Off Process | 11/14/2014 |
- 30 hrs - $300 o 15 CF Code - $20/hr = $300 o 10 adilas - $20 hr = $200 o 5 actual project – hands on o $800 - New 10-20 new clients - $2,000 per month - New custom jobs - $5,000-$10,000 per month - Company who manages (Facilitator) – on boards process & bring them up to speed - Film and record all of the pieces adilas university - Have a test and cert base to accomplish the sign-offs - Do it once – use many - First video is the overview – 5 mins (brief) - Anybody new needs to go through the process - Code evaluation process o Do we want to speed the money on their education - Plan 2 hour sessions in December - Generally schedule out timeframes for each subject – (Liks – 10 min) o Bullet points that need to be addressed and/or covered o Options o Visual aids - Double the process by showing these concepts in action inside of adilas - Auto, visual, hands on or actual - There will be some pre & post production stuff - API – Play at the Wall! - Small 1 hour seminar for developers – look for people who are interested (pool of people) - Start the end of November - Use the meeting as a screening process for qualified people - Try storming - Okay with breaking models - David.forbis@adilas.biz – Project Management - What if we had a way for class participants to submit code for running and/or checking? Maybe use elements of time & sub comments Talking with an intern about flow & code sign-off process: (Please see sketches on scan in photo gallery) 1. Sign-off locally 2. Upload all to need sign offs 3. Pull down from need sign offs 4. Brandon is the gatekeeper (right now) 5. Once actually released they will go into production & updated on the MDI server 6. Max & min on inventories |
|
|
AU 2937 |
|
Daily Tasks | 11/15/2014 |
• Signing off on icon menus done by an intern. • Posted 19 new files online. I also made a couple of other flow and ease of use changes. • Working on a customer data file and digital upload. Logged in and most of the records had been created manually. Other emails and tech support stuff. • Small code tweaks to the adilas API socket pages. • Working with a developer on the API sockets – wiring up the wall. |
|
|
AU 3731 |
|
Sketches - API Socket Connections | 11/15/2014 |
Brandon & a developer talking about API Socket Connections: (Please see sketches on scans in photo gallery) - Pages – “.cfm” - CF - Components – “.cfc” - Adilas API Demo - Security cfc - Page – adilas api calls cfm - Special include - JSON - Black box o Web api o Adilas demo cfm o “.cfm” external use - Adilas API Calls / External API: o Check permission o Get web inventory o Adilas API demo - Return info in – JSON – CF – general validation – CF include, their request – custom validation 1., 2., 3., 4. Call .cfm |
|
|
AU 2938 |
|
Daily Tasks | 11/17/2014 |
• New logo for a client. • Emails. • Reviewing custom code from a developer for the first page of custom code for the main adilas shopping cart. The code will go live later today. Good stuff. • Tech support, phone calls, and light code changes on the web/API pages. Tech support calls about printers, label makers, credit card swipers, etc. Busy day today. • Helping an intern with icon menus. Phone calls with Steve and other clients. Tech support on merchant processing with a new client. • Putting together some PDF documents to help get the adilas developers and adilas interns headed in a more standardized process and format. Sent an email out to local developers here in Utah. • Looking deeper into code for a credit card merchant processing group. • Working with an intern on custom tags. Working with functions and Cold Fusion components as well. |
|
|
AU 2939 |
|
Daily Tasks | 11/18/2014 |
• On the phone with an adilas consultant going over updates and progress. • Emails, tech support, and talking with my sister about where we are going. Told her about our plans to help train new adilas developers with 10 hours of adilas training. • On the phone with Steve talking about my sister. Talking with Steve about how we could use her skills to help us out with different things. We decided that we don’t want to lose her. We talked about funding, training, tech support, reps, consultants, trainers, developers, etc. We talked about making time for core projects (scheduling time) and how to also make time for customer funded projects. • On the phone with a developer going over rounding errors and multi-level decimal accuracy in the shopping cart. I told him that quantity, cost, and price per item can hold up to 5 levels of accuracy. Once things go out to the extended price and extended cost, they have to go back to two decimals or normal dollars and cents. • Working with interns on their projects. One was converting page code into functions and the other was reviewing HTML & Cold Fusion stuff. We did a small group teaching session on functions and method calls. • Recording notes in my notebook. |
|
|
AU 2940 |
|
Daily Tasks | 11/19/2014 |
• Emails and passing projects out to a developer in Salida. He is going a great job. • Phone call with my sister. She is going to be working for adilas on almost a full time basis. • Crazy times… Working with an intern on icon menus. • On the phone with Steve going over his new sales reports and graphs. • I then had a new potential intern come over for an interview. We chatted for an hour, did some light training, and talked about vision. Good interview. I then talked with an intern about training outlines and needs. After that I called Steve and we talked about projects, funding, and ways to help fund the upcoming projects. Good stuff. • Emails and follow-ups. • Trouble shooting code for the Ezic gateway and Mile High Merchants. For some reason, unable to connect. Back and forth with tech support via phone and email. Small code hacks and changes. • Emails, phone calls, and messages. • New logo for a client. • Checking on a custom file integration and product sync for a client. They want to upload vendor product lists and have the system loop over existing items and update costs, prices, and descriptions. They also want the system to add new items as it finds them. They want this option for multiple vendor/suppliers. • Uploading a logo, emails, and small server tweak for a custom cfx component (cfx_http5) |
|
|
AU 2952 |
|
Daily Ideas | 11/19/2014 |
-This morning my dad and I were walking on a snow covered trail. We could see lots of different footprints on the trial in the snow. My dad made the analogy that many different people (and animals) use the same trail but each has its own footprint. He related it to adilas and helping to build a virtual trail for businesses to use. Each business leaves its own footprint and many use the trail for different reasons. People use trails and roads because it is easier than bush whacking. -Steve had the idea to charge $17 per training session. That would help us fund that project. -We need to setup adilas eCommerce and online bill pay options for ourselves at adilas. We need to charge for new setups, training, custom code work, consulting, adilas world, and other events. -We also need to circle around and finish up the email and email confirmations section. -We need more options to schedule and take reservations for classes, training, and other events. We, as adilas, need round two of elements of time. |
|
|
AU 2941 |
|
Daily Tasks | 11/20/2014 |
• Reworking the non-compete and non-disclosure agreement for a developer. He wanted a couple changes to allow him still to be an independent developer and work with other clients. Added verbage to include more flex and known grey areas. • Playing with the cfx_http5 custom tag and Cold Fusion extension. • Working with an intern on a Power Point presentation for our upcoming intro to Cold Fusion class. We were going off of an outline from 9/12/14 (see earlier in this notebook for details). • Went into town to have lunch with my dad and a GPS guy. We ate lunch and talked GPS (Global Positioning System) and GIS (Geographic Information System) stuff. Good meeting. We are working 3D even tracking and using both GPS and GIS data to support the time, money, and special elements of different events. 30 miles. • Working with an intern on Cold Fusion training. We worked on lists and loops. • Small team meeting with an adilas associate and adilas interns. We went over options for new developers and helping to on board new talent and skilled independents. • The associate and an intern broke off to talk about on boarding new developers and the other intern and I worked on code stuff. • Working on emails and going over direction with the adilas associate about project management and using adilas. We set up a meeting for next week to create a process for project management inside of adilas. • On the phone with a developer working on the adilas API stuff. He also showed me a screen sharing software called Teamviewer.com, good intro to the API general format. |
|
|
Adi 906 |
|
Custom code - NDA | 11/21/2014 | Jimmy | |
|
AU 2942 |
|
Daily Tasks | 11/21/2014 |
• On the phone with Steve going over options for new developers. We also threw around ideas for residual commissions or options to build and maintain apps and code in order to get “mailbox money” or reoccurring revenue. • On the phone with Steve and another developer out of Salida, CO. We talked about API connections, flow, etc. The new developer is really into weather, GIS, water, mapping, surveying, and other geographic or geospatial options. We talked about some new avenues connecting to the geospatial concepts listed above. We also talked about 3rd party solutions and commission structures for code based projects and development. See notes on other page. • Also on the phone with Citrix for GoToMeeting tech support. • Recording notes in my notebook. |
|
|
AU 2953 |
|
Daily Ideas | 11/21/2014 |
-A shopping bag or grocery bag is a great one-to-many analogy. I was trying to bring things into my house and had a huge full arm load. I was using both hands, arms, and chin. Then I thought, man, if I just had a grocery bag or two this would be easy. The more I thought about it… the more I think it could be a good one-to-many relationship example. All you need is a small container to hold the pieces… -See sketches in photo gallery: Person trying to hold all of the pieces – too many to manage. VS Good use of a one-to-many relationship: Person using a container (shopping bag) to hold smaller details or items. -We had another request to show grouped data per day. They wanted the daily, weekly, and monthly totals. Basically, they wanted the financial history homepage report that will show data specific totals based on categories. See notes from 9/12/13 in adilas university for info on the financial history report. Commission Structure for 3rd Party Solutions: • To adilas: a. 20% • To 3rd Party: a. 80% • What: a. External solution. They bill the client. Then they pay us back 20%. • To adilas: a. 30% • To 3rd Party: a. 70% • What: a. External solution. We handle all the billing. We pay the 70% back to them. • To adilas: a. 40% • To 3rd Party: a. 60% • What: a. Internal solution. We host the files, pages, and apps. We handle all the billing. We then pay the 60% back to the vendors. Usually, this is an adilas developer that creates an internal 3rd party solution. • To adilas: a. 50% • To 3rd Party: a. 50% • What: a. Internal solution. We host the files, pages, and apps. We handle all the billing. The developers create, makes and does the maintenance on the project. We handle all the billing and pay back the 50% commission back to the developers. This is an option for adilas developers who basically make the app or feature happen and then maintain it. The original work and effort are on the developer. The maintenance also falls on the developer. They also get a perfect 50/50 split of the revenue. |
|
|
AU 3732 |
|
Brainstorming - Adilas Project Management | 11/21/2014 |
Adilas Project Management: - Names - Phases - Sub title - Start date - Start time - End date - End time - Notes Adilas Project Management: - Multi vendors or people doing hours - Phases - Budgets - Colors - Types - Photos & content - Invoicing - Quoting - Queue - Sign offs - Purpose, scope, details - Time tables - Flags - Communication between players: o Users o Flex o Cust o Inv o Quotes o Parts/items o Time o Balance sheets o Deposits o E/R’s o Vendors - Client Logs o Project - Invoices: o Sub time o User o Vendor time cards - Flex |
|
|
AU 2943 |
|
Daily Tasks | 11/22/2014 |
• Getting organized with what files to upload and what changes have been made. Using pen and paper to create a master list of files to upload from pages as far back as 8/15/14. • Going over the master list of files page by page checking for changes. |
|
|
Adi 908 |
|
Client/Server Model & ColdFusion Structures & Scopes | 11/24/2014 |
This is a simple drawing of two different pieces that we use to help developers understand the servers and what they do. Part 1 - Client/Server Model This section helps show the flow of what happens as an outside client makes a web call or page request. The diagram shows clients (laptops, desktops, tablets, phones) connecting or requesting something from a normal web server through HTML (hyper text markup language). If the web server can handle it, the web server returns the request. This is called static HTML or a basic web site. If the normal web server does not know what to do, for example a ColdFusion page request, the web server hands it (the request) off to the ColdFusion server. Basically it is a please help me, I don't know what to do with this... The ColdFusion server than plays with all of its options and assets and returns the results in normal web language (html). The ColdFusion server is kinda like the brains of the process. It is very flexible and can deal with variables, conditional logic (if statements), loops, multiple sets of data coming from different sources, and even database and API connections. Very powerful. If the ColdFusion server needs database information or records, it uses an internal API (application programming interface) to get the data back to the ColdFusion server. This is the wall outlet looking piece of the diagram. ColdFusion (the brain) then talks to the database through a language called SQL or structured query language (database talk). The database responds and sends the information back to the internal API and then back to ColdFusion. The trip between ColdFusion, the internal API, and the database all happen very fast and possibly multiple times per page request. Think of those three pieces (ColdFusion, internal API, and the database) as the three musketeers. They work very well together. Most of the work in the system is done by bouncing between those three players. By the time everything is done, ColdFusion converts the values into normal web or HTML and sends it back to the normal web server that sends it back to the client. All of these connections are done in super fast, lighting quick phases so that it appears that only a single page was requested, processed, and returned. In reality, there are multiple different servers working in combination, each doing their own job, to make the whole. If you take any part of it out, the process would fail. Another fun part of the model deals with how an external API socket connection might take place. We, at adilas, allow access to backend database pieces based on settings and permissions set inside of the main secured environment. The external API is represented by the surge protector type piece that has sockets, data ports, and plug-ins. This section takes a standard piece or request and sends it to the internal API (wall socket in our diagram). The connection is made in a non native format like JSON (java script object notation) or XML (extensible markup language). This allows various 3rd party players or 3rd party solution providers to play with functions, data, and pieces of the adilas.biz business platform. Basically, they (the 3rd party players) are able to code in their native environments (other programming languages) and then request, pass, or pull data from our servers (logic and databases) using external API socket connections. See this help file for more information about the adilas.biz API. Part 2 - ColdFusion Structure & Scopes This diagram shows a large dresser with multiple predefined drawers. Think about both predefined and user-defined containers for storing values and data. We use this analogy to help new developers understand where things are stored and how to get pieces in and out of the application. The drawing has a number of predefined dresser drawers called structures (super variables with names and objects). Here is a list of the predefined structures and what are called scopes. 1. variables scope - Set on the page level. They only live on the page where they are created. This is the default scope. 2. URL scope - These values get passed in to a page via the web address field or URL. These values may be passed from page to page and allow dynamic access points from the web address or link bar. These values are often used to help speed up dynamics, templates, and quick dynamic page results. 3. FORM scope - These are values that get passed to a page from user interactions. FORM scope values often come from searches, reports, data fields, selections, filters, and other web form based options. The FORM scope is much bigger than the URL scope and should be used if size, quantity, and/or security options are needed. Technically, these values are virtually passed behind the scenes in page headers and page bodies. The normal public can't see these variable/value pairs without looking deeper into the underlying pieces. Think of the FORM scope like a giant hidden folder full of data that gets passed from page to page. The hidden folder is marked as private or don't show the values unless asked. 4. session scope - The session scope is set at the cloud or virtual memory level. This is great for storing things that need to last (timeframe) between page requests. These are things like logins, user settings, date ranges, shopping cart data, and other pieces that may be needed by one or more pages. As long as the user is interacting with the server, the session variables will continue until cleared or a preset time period (2 hours) of inactivity occur. Whichever is first. 5. application scope - These values are set when the server starts up and gets used for the first time. The application variables are at the site or server level. These variables and values can live on and on for days, weeks, months, etc. They are values and settings that are needed in multiple places in your site and/or application. 6. arguments scope - These values are used inside of methods, functions, or internal API socket connections. They must be passed in when calling and/or requesting methods or functions. Often arguments have requirements, defaults, and even data types (strings, numeric, dates, etc.). 7. attributes scope - These values are used inside of ColdFusion when making, using, and creating things called custom tags. The custom tags are usually some sort of action or routine that gets performed over and over again. The custom tags help the developers to code once and then use over and over again. 8. CGI Scope - These values are fairly techy and are created behind the scenes. This scope allows the developers to get at things like server paths, page names, IP addresses, and other http or web settings (hyper text transfer protocol). 9. Other Predefined Scopes - This entry is here to help the developers know that there are a number of other scopes that are specific to the task at hand. These include things like error scopes, cffile scopes, cfhttp scopes, and try/catch options. There are a number of other scopes that may be available. See the actual code and/or documentation for more information. |
|
|
AU 2927 |
|
Client/Server Model & ColdFusion Server Structure | 11/24/2014 |
This is a simple drawing of two different pieces that we use to help developers understand the servers and what they do. Part 1 - Client/Server Model This section helps show the flow of what happens as an outside client makes a web call or page request. The diagram shows clients (laptops, desktops, tablets, phones) connecting or requesting something from a normal web server through HTML (hyper text markup language). If the web server can handle it, the web server returns the request. This is called static HTML or a basic web site. If the normal web server does not know what to do, for example a ColdFusion page request, the web server hands it (the request) off to the ColdFusion server. Basically it is a please help me, I don't know what to do with this... The ColdFusion server than plays with all of its options and assets and returns the results in normal web language (html). The ColdFusion server is kinda like the brains of the process. It is very flexible and can deal with variables, conditional logic (if statements), loops, multiple sets of data coming from different sources, and even database and API connections. Very powerful. If the ColdFusion server needs database information or records, it uses an internal API (application programming interface) to get the data back to the ColdFusion server. This is the wall outlet looking piece of the diagram. ColdFusion (the brain) then talks to the database through a language called SQL or structured query language (database talk). The database responds and sends the information back to the internal API and then back to ColdFusion. The trip between ColdFusion, the internal API, and the database all happen very fast and possibly multiple times per page request. Think of those three pieces (ColdFusion, internal API, and the database) as the three musketeers. They work very well together. Most of the work in the system is done by bouncing between those three players. By the time everything is done, ColdFusion converts the values into normal web or HTML and sends it back to the normal web server that sends it back to the client. All of these connections are done in super fast, lighting quick phases so that it appears that only a single page was requested, processed, and returned. In reality, there are multiple different servers working in combination, each doing their own job, to make the whole. If you take any part of it out, the process would fail. Another fun part of the model deals with how an external API socket connection might take place. We, at adilas, allow access to backend database pieces based on settings and permissions set inside of the main secured environment. The external API is represented by the surge protector type piece that has sockets, data ports, and plug-ins. This section takes a standard piece or request and sends it to the internal API (wall socket in our diagram). The connection is made in a non native format like JSON (java script object notation) or XML (extensible markup language). This allows various 3rd party players or 3rd party solution providers to play with functions, data, and pieces of the adilas.biz business platform. Basically, they (the 3rd party players) are able to code in their native environments (other programming languages) and then request, pass, or pull data from our servers (logic and databases) using external API socket connections. See this help file for more information about the adilas.biz API. Part 2 - ColdFusion Structure & Scopes This diagram shows a large dresser with multiple predefined drawers. Think about both predefined and user-defined containers for storing values and data. We use this analogy to help new developers understand where things are stored and how to get pieces in and out of the application. The drawing has a number of predefined dresser drawers called structures (super variables with names and objects). Here is a list of the predefined structures and what are called scopes. 1. variables scope - Set on the page level. They only live on the page where they are created. This is the default scope. 2. URL scope - These values get passed in to a page via the web address field or URL. These values may be passed from page to page and allow dynamic access points from the web address or link bar. These values are often used to help speed up dynamics, templates, and quick dynamic page results. 3. FORM scope - These are values that get passed to a page from user interactions. FORM scope values often come from searches, reports, data fields, selections, filters, and other web form based options. The FORM scope is much bigger than the URL scope and should be used if size, quantity, and/or security options are needed. Technically, these values are virtually passed behind the scenes in page headers and page bodies. The normal public can't see these variable/value pairs without looking deeper into the underlying pieces. Think of the FORM scope like a giant hidden folder full of data that gets passed from page to page. The hidden folder is marked as private or don't show the values unless asked. 4. session scope - The session scope is set at the cloud or virtual memory level. This is great for storing things that need to last (timeframe) between page requests. These are things like logins, user settings, date ranges, shopping cart data, and other pieces that may be needed by one or more pages. As long as the user is interacting with the server, the session variables will continue until cleared or a preset time period (2 hours) of inactivity occur. Whichever is first. 5. application scope - These values are set when the server starts up and gets used for the first time. The application variables are at the site or server level. These variables and values can live on and on for days, weeks, months, etc. They are values and settings that are needed in multiple places in your site and/or application. 6. arguments scope - These values are used inside of methods, functions, or internal API socket connections. They must be passed in when calling and/or requesting methods or functions. Often arguments have requirements, defaults, and even data types (strings, numeric, dates, etc.). 7. attributes scope - These values are used inside of ColdFusion when making, using, and creating things called custom tags. The custom tags are usually some sort of action or routine that gets performed over and over again. The custom tags help the developers to code once and then use over and over again. 8. CGI Scope - These values are fairly techy and are created behind the scenes. This scope allows the developers to get at things like server paths, page names, IP addresses, and other http or web settings (hyper text transfer protocol). 9. Other Predefined Scopes - This entry is here to help the developers know that there are a number of other scopes that are specific to the task at hand. These include things like error scopes, cffile scopes, cfhttp scopes, and try/catch options. There are a number of other scopes that may be available. See the actual code and/or documentation for more information. |
|
|
AU 2944 |
|
Daily Tasks | 11/24/2014 |
• Working on in-line discounts and calculating the total saving per shopping cart. • In-line discounts. • Recording notes from loose pages and post-it notes. • Emails and drawing a graphic to show the web client/server relationship between clients, web servers, Cold Fusion servers, internal API sockets, external API parts, and database servers. • On a conference call with a financial services going over a kiosk, payment, bill recycler type interface. An adilas associate is the project manager and I was being the technical contact. There were two other gentlemen on the call and we talked ship and shared ideas. I told them that I would send them some brainstorming documents from 9/3/14 to 9/6/14. • Working with an intern on a new developer Power Point presentation to help train adilas developers in adilas. Also talked on the phone with our new adilas project manager about the meeting and call earlier today. He is doing a great job. • Drawing a graphic to help with Cold Fusion training. Adding the new graphic to adilas university. I then started writing some information and explanations on what the graphic contains. Lots of back and forth editing. • More writing about the client/server model and the Cold Fusion structures and scopes graphic. See time entries in both the main adilas.biz site (#908) or on the adilas university site (#2927) for details. • On the phone with the new developer from Salida, CO going over code structure, flow, and how things work. We used the new graphics that we created today to help illustrate the processes and structure. That was kind of fun. • Recording bills for adilas. Uploading scans and checking account balances. |
|
|
AU 3733 |
|
Sketches - Client/Server Model & ColdFusion Structures & Scopes | 11/24/2014 |
Client/Server Model – sketch ColdFusion Structures & Scopes – sketch (Please see sketches on scan in photo gallery) |
|
|
AU 2945 |
|
Daily Tasks | 11/25/2014 |
• Emails, tech support, and follow-ups. Added the new client/server model graphic to a standalone help file. I also added the Cold Fusion structures and scopes graphic to its own help file. • On the phone with Steve talking about the need for a custom label making application and/or app. We did a GoToMeeting session on in-line discounts and both Steve and an intern participated. • Working with two interns on their first customer upload projects. We had an Excel files with 4,000 names, addresses, and other contact info. We combed the file, mapped it out, imported it, and started to go over the page to do the validation and final import. • Went out to my brother’s house to help him get his local machine up and running. He was picking things up very quickly today while working with the other intern. 30 miles. • Our adilas associate came over to talk about using adilas as a project management tool. We talked and then sat at the kitchen table and did some planning and training using paper and flow charts. Great session. I learned a ton. One of the fun things was laying out the tools in blocks so that we could see our options. We used simple blocks and kind of setup basic wire frames with key points, benefits, and options. Another cool idea was allowing the action status logs to be dynamic per corporation or per world. The other great idea was allowing groupings to take place on the subs of time. For example: Say we were using sub dates and times. It might be really cool if we could use the same table for digital time cards, phases, progress reports, deadlines, targets, budget checks, etc. However, we may not want all of that data to be grouped all together. It would be really cool if we could reuse the same tool over and over and then just group or sub group the display or output. Anyway, I loved the idea of being able to group the data as needed. |
|
|
AU 2954 |
|
Daily Ideas | 11/25/2014 |
-On elements of time, I would really like to be able to do mini P&L (profit & loss) type reports. What was made, what was spent, what was gained? -Currently elements of time can do billing but it might be nice to be able to nest or do sub billing on a single bigger project. There are ways to do this already but it has to be done manually. We need to enhance that. |
|
|
AU 2946 |
|
Daily Tasks | 11/26/2014 |
• Tons of email stuff. • On the phone with a developer from Salida going over my cart favorites and how they work. Lots of details. • Writing an internship letter for an intern to USU. • Helping another intern with some icon menus. The intern and I worked together on a customer upload. We talked a ton about working with data and how we have to change between huge sets to laser focused smaller pieces like individual variables. • Working with an intern on more customer migration stuff. My sister came over and started to scan notebooks while I worked with the intern. • Had a meeting with my sister to talk about direction and new changes. I really appreciated her just listening for almost an hour straight. That was good for me and hopefully helped her out. She is working hard on the developer’s notebook. She is also looking into a new adilas tech support phone number and voice account. • A developer came over to work on API socket connections. We had a good session and point him in the right direction to go for wiring up the wall and data ports as part of the external API socket project. |
|
|
AU 2955 |
|
Daily Ideas | 11/26/2014 |
-Small miracle this morning as my dad and I were on our walk/run. The roads were like bullet proof ice this morning. They were snow packed but it was warmer so they were melting. We drove up the canyon and it was so sketchy that we turned around. On the way back, we started to slide off the road towards a steep bank that went down to the river. Anyway, we were about to slid off the road and suddenly we were able to stop. We didn’t know how or why but we were able to stop. That particular corner sloped off the wrong way (downhill) and could have dumped us off the edge. Anyway, once we stopped we said a prayer. My dad then put the Jeep into 4-wheel drive low and we crawled out of the sketchy zone. We ended up drifting sideways down the next hill as well. Super slick. We made it out eventually to plain ground. We then put on some special foot traction devices and went on our run. As part of our run we ended back up the canyon by the hill and corner that almost ate our lunch. With the foot traction stuff we could walk on the icy road. What we found at the scene of our almost crash was pretty cool. We found a small rock that had been dislodged when we went into a skid. The rock had left a small grind path in the ice for over 7 feet. Basically as the wheels locked up the rock was in front or under the back right tire. It’s carve in the ice was the only visual evidence of the skid. As we looked at the scene, we couldn’t help but feel blessed. That little rock being drug under a locked up tire helped stop the vehicle from going over the edge. That same rock, most likely also allowed for the Jeep to get traction when crawling forward to get out of the danger. I am so grateful for a loving God that watches over us and teaches us along the way. I’m grateful for the Rock! (Sketches on scans in photo gallery) -I want to map out each tool as blocks. Break it into tools, sections, subs, and options… Similar to the plates and cup analogy but use blocks and wireframes. Blocks & wireframes: (sketches on scans) • Main items • Line items • Payments • Photos, scans, files, flex grid, etc. • Internal & External API socket options -As a note, a wireframe is a mix of both technical information as well as a visual representation of the data. It is very simple but helps to convey functionality, behavior, and priority of content. See Wikipedia – website wireframe – for more information. -A new personal setting could be what set of my cart favorite buttons to use. That would really help save users a couple of clips. Idea came from the Salida, CO developer. -Showing big picture to smaller sub details. Yesterday, I used simple drawings to talk with different people to show multiple different levels and how we deal with each one. These could be some great teaching analogies. Think big picture… clear down to smallest pieces and sub details! Huge to micro – go as deep as you want! See sketches in photo gallery: • Internet – Worlds • Servers – Locations, States, City • Databases – Highways, Streets, Roads • Tables & Queries – Traffic, buses, cars, motorcycles, etc. • Individual cells, data, and variables – Individual persons, drivers, passengers, pedestrians, etc. |
|
|
AU 2947 |
|
Daily Tasks | 11/27/2014 |
• Recording notes from loose pages and post-it notes. Happy Thanksgiving! • Emails to the new developer out of CO and to Steve about harnessing hours and hours of emails back and forth to clients answering their questions. |
|
|
AU 2956 |
|
Daily Ideas | 11/27/2014 |
-Today is Thanksgiving. Lost to be grateful for… Count your blessings not your problems. Build on what you have. Work as if for years. There will still be time. Keep moving forward. -We may end up needing to get our own GPS server to catch and hold GPS data. We could then use API’s and web services to connect and pull real time reports and data. Another option is to use a GPS server as a service (pay for somebody else to host the data). Either way, we just need access to the data or virtual air time. See Wikipedia – GPS & GPS Server. -Steve thinks that we need a help forum or some sort of way to answer multiple questions at once. Answer once, use many. Share our library of questions and answers. Steve has kept tons of emails for years. He would like to circle back around and use some of that content. Great idea! We’ve spent hours and hours and more hours writing emails and answers on how things work or step-by-step instructions on different subjects. We need to capitalize on all that effort. That would be awesome! Maybe have my sister help make that archive as part of adilas university. That would be really cool! |
|
|
AU 2948 |
|
Daily Tasks | 11/28/2014 |
• Working on in-line discounts. Adding original cart sub totals. Also checking code to stop discounts on top of discounts. Working on the logic to update discounts line by line. Spent four (4) hours of that session on the phone with Steve using GoToMeeting to do training and page logic. We used tons and tons of drawings, training exercise, dumps, etc. It was an awesome 4 hour session. We also covered scopes, structures, arrays, functions, internal API calls, error handling, and how the external API”s play into things. Lots of fun! • Working on in-line discounts. • Got a phone call from a client about a tax setting that was not applied correctly. Fairly hot. We logged in and finally got it fixed after a couple attempts. Recorded notes inside of adilas after the phone call. |
|
|
AU 2957 |
|
Daily Ideas | 11/28/2014 |
-Graphics, eye candy, and turning adilas into the game of business. After Thanksgiving dinner I got to see my brother’s graphics and small game he was creating. He is getting good and I’m excited to advance the ball in the dream to make adilas an interactive environment. He will be doing an internship with us starting in a couple of weeks. Yee haw! -“Even though it is deep – keep it simple!” See notes on 11/26/14 about mapping out tools and features and wireframes. We also need to add… 1. Layout & display options 2. Navigation & links 3. Main item details 4. Line item details or subs 5. Payments 6. Flex grid tie-in and custom fields 7. Photos, scans, and images 8. Custom code, custom documents, paperwork 9. Media, content, and other files 10. System history 11. Special subs & relationships 12. API sockets (internal and/or external) 13. Extensions, Database changes (+ or -), flow, processes 14. 3D wrappers of x=time, y=money, z=space As a note… These are the numbers (in the box – sketch in photo gallery scan) that are set on the cup and photos model graphic. Expand the tool mapping to include more depth, layering, and custom options -Idea from Steve… We need to be able to rename the bin location field in the parts section. More and more people are needing custom fields and custom naming conventions. As a funny history note, the bin location field in the parts section. More and more people are needing custom fields and custom naming conventions. As a funny history note, the bin location field is actually called catalog_page under the surface. Way back, that field was used to help with catalog ordering. Funny how things change. |
|
|
AU 3734 |
|
Tech - Discounts | 11/28/2014 |
Discount per line fields: - FORM default discount type = 1 (in-line) - FORM use discount = 0 - FORM apply discount type = 1 (percent) - FORM campaign = “ “ - FORM cart = “____” Loop values: - FORM: o Qty o Price o Original price o Discount o Discounted price o Campaign o Tax o Cost o Inventory type o Part category o Tax Math for an unknown percentage (12/13/14) |
|
|
AU 2949 |
|
Daily Tasks | 11/29/2014 |
• Emails and graphics to show tax settings and requirements. • Went in to the add/edit store location and tax settings pages and added some additional validation. Uploaded the pages to the servers and sent an email to Steve and a couple others dealing with the update. • On the phone with Steve going over plans, projects, and where we are headed. We spend the first half an hour talking about training, validation, slowing down, finding a base camp, pacing ourselves, and acting on our current plans that have been made. We then switched over and did a GoToMeeting session on in-line discounts. Lots of back and forth training. We talked a lot about custom tags and validation routines. • Steve and I were back on GoToMeeting to finish out our section. We spent some good time looking into the underlying validation and digging in deep to what is going on. • Working on in-line discounts. Testing logic and flow. • Working on normal price changes and bulk cart edits. |
|
|
AU 3735 |
|
Tech - Variable Cart Tracking | 11/29/2014 |
Notes: - Training - Validation - Stop running - Circle back around - My sister & training - Set a pace and keep going – build and work as if for years - Setup a base camp Variable Tracking: - Total savings amount - Original cart sub total - Set back to the array – bulk edit, cart action - Update cart 2 (lines) - Line quantity - Item price - Extended line total - Original list price - Original list price extended - Use in-line discount - In-line discount per line - In-line discount extended - In-line discounts campaign - In-line discount percentage |
|