• New logo for a client.
• Planning ways to record behavioral data for teachers and students. Brainstorming on paper and writing down ideas.
• We had a request from a user to be able to copy the part number into the description field. So, we added a small button that helps that to happen if wanted. While we were working in the parts and general items section, we also added the key word “auto” to the main parts field. We could already do auto for barcodes, but not for actual part numbers. Anyway, we cascaded the code throughout that section and pasted new files online. Emailed a client that his request had been granted. This could really help with consignment folks.

• On the phone with Steve going over upcoming projects and current tweaks. We talked about 3rd party vendors, eCommerce, kiosks, custom code, and splitting databases. We also talked about options on part numbers to use the auto generated main part numbers and how that could be used. We also talked about a client and his trucking systems and possibly offering additional services for them such as accounting and payroll. Anyway, he is excited and pushing the ball forward.
• Helping my wife get setup on the next project. We are starting to document the adilas database tables.
• Got some new files from a developer. Made the changes and posted them online and emailed he and Steve with updates.
• Working on the teacher/student interface and the new behavior tracking section. Lots of work on layout options for touch screen.
• Phone calls and tech support. Lots of accounting type questions. Average costing options and special mappings for deposits and refunds.
• My sister came over to work on the database project. We spent a couple of hours writing table descriptions for the different tables. We worked on all the “P” tables like payee, parts, paycheck stubs, payee permission list, etc., etc. Great session.
• I got a call from a contact about a possible technical contact and a guy who knows code stuff and may want to do some adilas code projects. Anyway, I chatted on the phone with him for about half an hour. He has been such a good support. I would love to start using him as a project manager of sorts. He could do a great job. I'm excited to see where that could go. Good stuff.

• Working on the teacher/student behavior tracking section. Tying in code to work with elements of time.
• On a conference call with the folks from Cash 4 Ever and EZ Kiosks. We talked plan, options, and time-line. I will be working on that project all day tomorrow as needed. We are planning a super simple interface with special rounding to whole dollars for the first round. Lots of comments going back and forth. Spent a couple of minutes recording notes on a piece of scratch paper.
• More work on teacher/student interface and tying the behavior tracking system to elements of time.
• My sister came over and we worked on more table descriptions and lining out adilas database tables.
• An intern also came over and said that he could help do some adilas code work. We talked about 10 hours a week and helping me on a number of small projects that I am working on. Casual but good meeting.
• Working on switching main elements of time for the behavior tracking module for the teacher/student interface. Small little page switching buttons and links. Behavior tracking uses sub dates and times tied to main elements of time.

• Started working on a new kiosk interface for Cash 4 Ever. This is going to be the project of the day today. Started out with some planning. Did a small flow chart to show the five pages that are needed. Started working through the pages one at a time. Lots of validation and trying to keep things very simple for the user.
• Working on the java script and backend logic for the Cash 4 Ever kiosk. Got the pages ready and posted them online. Ran a number of tests and prepped for a phone call with the C4Ever systems guys.
• On the phone with some guys from C4Ever Systems. We did a GoToMeeting session with one guy at the kiosk, one guy remoting in from the background, and me on the GoToMeeting session. I showed them what was going on and we walked through a number of small demos.
• Helping my sister with database table stuff. Recording notes and writing down things from the conference call.
• Working on a few pieces of the C4Ever systems wish list.
• Finished up some small changes on the C4Ever Systems wish list. Also updated the add item page for shopping carts. Added buttons and helped with some basic math values on the page. Posted files online and did some testing.

• Custom code to help an adilas rep out with some inventory management functions. See notes below for more details.
• New logo for a client.
• Email tech support on calculating and recording overtime based on state specific rules. The answer was basically, use the tools to record the story, then change the automated numbers to match what you need. The system tries to help but has no idea about every rule out there. Let it do what it does and then edit the information to make it correct.
• Emails to the C4Ever Systems guys with login and passwords to the play sites and kiosk interface.
• Working on the MEI BNR (bank note recycler) API for the C4Ever Systems guys. Reading documentation online and trying to figure out the pieces that we need. Built a small test page to see what values and errors we were getting back from the different method calls and responder functions. On the phone with the guys at the actual kiosk. They were feeding in bills and I was testing, uploading new code, testing, and doing it all over again. Hours of back and forth testing. By the end, we could start the kiosk accepting bills, turn it off when enough, and return change due. Good session.

• On the phone with Steve talking about the current C4Ever Systems project. We talked scope, options, and where to draw the line. We also talked about where they are headed and where we are headed. I basically told Steve that I was going to hand the ball back to him and let him deal directly with owners and such. I'll get it done and he will handle the negotiations and details.
• Brainstorming and planning. Recording notes.
• Documenting and sketching out new flow and options for the C4Ever Systems kiosk interface. Light planning on a test mode and an admin backend dashboard.
• Working on new layout and logic changes for the C4Ever Systems layout. Added both test and admin sections. Started working on the main payment page code (pretty deep).
• Major work on backend payment page and logic for the C4Ever Systems. Added two different page modes to handle live – attached to the kiosk and test or demo mode – standalone system. Lots of java script work and passing values back and forth between functions.
• Adding logic to cancel a transaction and do a virtual rollback on funds applied to the transaction. Other backend settings.
• Finished up the code stuff for round one of the C4Ever Systems kiosk interface. All that is still needed is live testing actually on the C4Ever Systems kiosk with a BNR (bank note recycler). All of the test mode debugging is complete.
• Working on the behavior tracking project for the teacher/student interface.
• Added the sub behavior tracking to the custom page to add additional records. Basically, on one page you can create and populate as many behavior records as needed. The system keeps you in a loop until you jump out of it. This allows you to monitor and record data on a single student until you need to switch to another behavior or another student.

• Emails and light tech support.
• On the phone with Steve and a guy from C4Ever Systems talking about options for round one. Went through a number of things and verbally defined round one. We also talked about what might need to be on the wish list for round two. After the guy from C4Ever was done, Steve and I chatted for awhile about other developers and how to keep and engage them in our projects. We talked about some of the lessons learned already and options for the future. We are still headed in the independent contractor direction. We also talked about our need for adilas world and how that could help share the work load and job or project options.
• Working on the teacher/student behavioral tracking stuff. Added some navigation buttons.
• Working on a sub page for the behavior tracking section. The page shows all sub dates and times per existing task or behavior. Basically, a grouped list of existing tasks with their sub data points.
• An intern came over and we did some Cold Fusion training. We talked about scopes, variables, and code once – use many concepts. Lots of review and letting him drive and practice debugging stuff.
• Working on the teacher/student interface pages.

• Working with an intern on a custom PDF document. We called the client and talked with him on the phone. It ended up that his simple PDF document wasn't quite so simple. It was actually a rent to own contract of sorts. He wanted it to do this and that and whatever... After that phone call, we called Steve and chatted with him. We will get back with the client on options for his documents. We may need to say no to this client for now. Saying “no” is really hard sometimes.
• The intern and I were working on the teacher/student interface and a new page that will allow a teacher to get at all student data points as quickly as possible.
• Emails and phone calls.
• Working on the teacher/student interface reports.
• On the phone with the C4Ever Systems guys talking about minor changes and possible direct printing options. Other small requests were dealing with auto refresh rates and who is going to do what on the development side.
• Working on a page for the teacher/student interface that puts all of the key student data points in one single place. Wiring up all of the buttons.
• My sister came over and we worked on more database table descriptions. I also gave her a small demo on the teacher/student stuff as well as the kiosk stuff we are working on.
• I got a phone call from a C4Ever Systems guy. He was testing the kiosk stuff and wanted me to help and even make some small changes. On the phone, testing, and debugging flow and processes with live code.
• Went over to our teacher client's house to show her a demo of the new teacher/student interface changes. We played with features and reports and I answered questions.

• Recording notes in my notebook.
• Posting the new behavior tracking and teacher/student interface pieces online. Small help file graphic tweaks and light testing.
• Brainstorming notes and ideas of how adilas could really benefit teachers and educators. See notes on other pages. Lots of notes. My mind has been going nuts.
• On the phone with Steve talking about schools and teachers. Lots of good ideas.
• More brainstorming on ideas for teachers, educators, and students. Lots of fun, cool, ideas. We could really help these guys and gals out. I really think that we could help there!
• More brainstorming on schools, teachers, and educators in general. I scanned the five pages of notes and sent them to my dad and to another contact that has been helping with marketing and other aspects of adilas. I would like him to spearhead that little project.
• Working on help files for the teacher/student interface. Also modified a page to help teachers both add and view (access) data as quick as possible. Helped an intern with installing software on his new laptop.
• Paying bills and recording expenses.

-If we watch people use the system without any other information it may help us find the holes and pitfalls. That takes quite a bit of time, but if you don't have to explain everything, it actually saves you time in the long run.
-Maybe soften some of the error messages. Help to guide and virtually hold the users hand a bit more. Show them the goal and then how to do that.

Notes About Teachers & Educators - & How They Could Use Adilas:

-This morning I have been thinking about teachers and educators. I really think adilas could be beneficial to teachers at all levels.
-I was thinking about a guy who has been helping with adilas and having him spearhead this little project. I really want to get this product out to educators and people who are teaching the next generation. It could really help them out.
-We could sell a single teacher license for $10 a month. What a benefit to the teachers at that price! We could do a whole school from $17 to $187 (whatever) based on number of teachers and students. We could do districts at a different level and even dedicated servers at another level. Tons of options.
-We could do public schools, K-12, preschools, private schools, charter schools, alternative schools, technical colleges & schools, colleges, universities, etc. No limits! Hey, even Sunday Schools... :)
-We could make a number of other interfaces that fit styles and different age groups.
-We could set a flat rate of $50/hour for custom work. That is much easier to swallow than $100/hour or higher.
-We could offer custom interfaces, custom documents, custom reports, and custom training. These are all part of the system and great potential revenue streams and profit centers.

-A CRM (Customer Relationship Management) system for teachers and students.
-Teachers could use – CRM, scheduling, photo management, documentation management per calendar event or per student, custom fields for tracking data, backend login (eCommerce) for parents, personal expense tracking, etc. Tons of options!
-We could approach schools at the state and district levels. We could approach teachers at a private or personal level. It is just a tool! They could use it at school, at home, over the summer, even while on field trips and bus rides. All they need is a hotspot or Internet connection.
-The application can be used on ipads, tablets, PC's, Mac's, phones, laptops, desktops, etc. Piece of cake and super small bandwidth and footprint.
-No contract. Month to month or annual plans. Free updates. Freedom and organization of their data.
-Cloud based, hosted solution.
-Privacy of data in multi-teacher environments.
-The power of a full business software system – catered to help teachers, educators, and students! A teacher's business is their classroom and their students. We can help with that!

Random note: I saw an interesting phrase in an email this morning... It said “disposing of digital debris”. I find that interesting as one of our current thought patterns deals with waste and being able to remove sludge and unneeded digital debris. All of nature has a way of getting rid of waste. We need to build those features in our data projects.

More notes on adilas for teachers & educators:
-School lunch program. They could pay and load cards from backend eCommerce. This is kind of like a gift card type interface or options. We could have an easy my cart favorites menu to bill out lunches and charge the cards accordingly. It could be super simple.
-Schools may need small online stores for yearbooks, t-shirts, game tickets, plays, donations, etc. This could be more eCommerce school funds cards. Pretty cool.
-Schools need email and text messaging between teachers and students and teachers and parents. We could use Full Circle IM as a 3rd party vendor for that. Piece of cake.

-Simple pricing structure of $10 per month per teacher. Any of the reps could get 20% of that as the rep and/or consultant. This same commission structure exists for all reps. This deals with accounts, not teachers (unless they are their own mini account).
Level 1 – 0 to 25 clients (accounts) – 20%
Level 2 – 26-50 clients (accounts) – 25%
Level 3 – 51-75 clients (accounts) – 30%
Level 4 – 76-100 clients (accounts) – 35%
Level 5 – Over 100 clients (accounts) – 40%

-Boy, it would be awesome to have a specific website that had teacher specific stuff on it. Ideas, tutorials, consultants, developers, manuals, and other resources. This could be really cool if they could even purchase or setup an account right from there. We could figure out referrals, promotion codes, etc. Just an idea! :)
-On schools and reports, dates are very important. We just barely added some custom date ranges to the school specific settings. This is an admin feature, but the dates could be set by school year, semesters, quarters, trimesters, year-round, etc. You get to set the active date range. All of the older data still exists, but the active date range helps to keep things current and fresh. In a way, it is like getting rid of waste and rubbish without actually towing it away.
-Objects and data wrapped in time... Think of what happens in a school year, a quarter, a semester, a trimester. What if all of that could be wrapped up together. Relationships, characters, players, problems, trouble, decisions, and consequences. Each chapter in the book (school year or timeframe) needs to play out as it happens. Catch the story at the source (teacher/student) and then go from there.
-Mini world building – a teacher, his/her students, their school, their community, their district, their region, their state, their world.

-More ideas and possible needs for an eCommerce and/or point of sale piece of software or solution... Event registration, community events and calendars, book stores, class fees, dances, housing, parking, food, labs, supplies, tuition, clubs, fund raisers, donations, extra curricular activities, field trips, exchanges, trips, etc. Tons of things, at a school, deal with money.
-This might be further down the line, but what about teaching adilas classes to students. Teach them how to run a business, sell things, track things, do accounting, even how to dream! Teach them... You dream it up, we'll help you wire it up!
-What about different accounts per students. Say they put some money on a card or an account, wouldn't it be cool if you could sub divide the money into different areas... For example: food, recreation, fees, book store, clubs, activities, etc.
-What if someone wanted to design a whole new interface that talks with an adilas backend? They could use any programming language and an adilas backend engine or API connection socket. The interface could be 100% specific to teachers and educators.
-I need to get back to my other projects... I'm having a hard time turning off the ideas... :) Good stuff and it could help great people! That's exciting!

Other notes:
-On customer logs (meaning the main customer information page), it might be nice to add all subs of time. Maybe also the invoice number of the main element of time to show what has and has not been invoiced. Then again, maybe just a link instead of showing all of the data. Or maybe wait until we do the roll call page and then link from there.

//////////////////////////

As a side note, we added a Word Document on 10/30/2019. Original date of the entry above is 9/10/2014. The new Word Document came from Chuck Swann, an adilas designer/developer. It was listing out some additional needs for schools. See this link for more info on that doc.
https://www.adilascontent.biz/top_secret/images/corp371_A70F6B3792/pdf/doc_81887_01112B5ABC.docx

• Finishing up help files for new changes and pages. Small layout and verbage changes. Added the default color to the view master time templates page. This has been on our to do list for quite awhile. Added a printer friendly version of the default colors for time templates.
• More help files.
• Reviewing a request for an API connection.
• Writing an email back and forth to Steve about project managers and established processes. I sent him an article that I read back in 2004. It deals with process and documentation. Here is the URL: http://www.sitepoint.com/print/process-and-documentation
• Re-reading the process document listed above. Making some notes on ideas that I had while reading.
• More reading and planning what I want to do and how to do it. I love planning and documenting and then actually creating it. Maybe that's my new job... Less coding and more planning and documenting. Then have other people help me get it done.

• Brainstorming on what new adilas developers need to know. Lots of notes on how to help them get the skills and knowledge that they need. See associated notes.
• A new contact came over and we chatted about code and concepts. This was our first meeting. Really nice guy. Great potential!
• Small changes for a contract. Posted files online.
• Working with potential new developer on getting to know the adilas system and adilas culture. Lots of talking and chatting back and forth. I had him go in and play inside of adilas and do a couple invoices, apply a discount, make a couple expenses, print a check, do a deposit, scan and upload a photo and other small tasks. He showed me some of his work and other projects. I gave him a small test on SQL and HTML. He also did a small Java Script example on paper. He did very well. I'm excited to see where this business relationship will go.
• Random clean-up work. Looking at database files. Helping an intern get adilas loaded on his computer. His system was having a small database connection problem.

• Back working on the database copy and deep database surgery. This is also known as the solar system level. This project was started in mid August of this year. Spent the morning checking different computers for files and progress on the database copy. Reread all of my notes in this notebook from 8/12/14 to 9/12/14. Lots of crazy things happening. The notebook review really helped me remember what is going on and where we are headed.
• Touching pages that are part of the big database copy project. Light work on the in-line discount code. Trying to make sure existing code will work going forward.
• Emails and tech support stuff.
• On the phone with a consultant talking about tax settings and mini invoice options and settings. See notes below. Small code changes for him and his client.
• Small tweak to the mini invoice and corp-wide settings to only show the mini invoice with the items and not the descriptions.
• The guy helping with marketing and project management came over to meet with me about marketing ideas and how to get more developers online and in the trenches. Great meeting! Lots of vision and concepts. I showed him some pieces of the new teacher/student interface and we talked some potential.
• An intern came over and we worked on a customer upload from a digital file. Light database work and combing an Excel file.
• Working on database design and layout at the upper cluster (box or domain) level. Making some decisions about cluster corporations and cluster payee/users. Those two are kind of the crux tables.

• Emails and posting new default invoice views as corp-wide settings. There are six different views to choose from as the default when a shopping cart is converted to an invoice. The new ones are: 3” format – no line descriptions, 3” format – summary, and 8 ½ x 11 summary.
• Prepping files for an intern for more icon menus. Working on parts and general inventory pages.
• Creating icons for parts and general inventory pages and new buttons and icon menus.
• Emails and tech support stuff.
• New logos for clients.
• Research and tracing the existing login procedure. Tying to get insight as to how the new cluster and solar system login procedure will happen and take place. We need to make some changes due to the new and upcoming database structure.

• At the table planning out new login procedures, new database tables, flow, and requirements. Good session. Got a few new pages of notes. We are going to use cluster payee id's, home planets for users.
• Emails and tech support stuff. Light brainstorming on using the parts reference field to help with sub grouping and classifications. See further notes for details.
• On the phone with Steve going over new and upcoming projects. We also talked about using project managers to help with bigger projects. The other main subject was developers and how to help them develop from API's or internal, using templates and skins. We are getting more and more people who want to ride on our platform and charge for custom code that fits on top of or inside the normal adilas system.
• Helping an intern with his icon menus and some light code stuff. Sitting at the table doing some planning. Spent quite a bit of time documenting the inter-workings of the system. I know that all of that documentation could be used against us (showing the whole map) but we gain tons from it. I think it is exciting to see all of the pieces come together. Yee haw! Here we go!
• Writing code for new cluster tables. Trying to prep things for clusters and multiple solar systems (new database levels).
• An intern came over and we worked on his customer migration project. Lots of training on the fly and trying to help him understand what is going on. He is doing a good job.
• Documenting adilas database tables and field names. Working in Microsoft word going table by table.

• Emails and answering tech support questions.
• Created a new table to help with database connections and got it ready to use on the cluster (level 3) database. Ran the code to create the first cluster database.
• Working on the code populate the cluster level database.
• Signing off on icon menus for parts and general inventory pages with an intern. Lots of testing. He is getting better and better at coding. Had a couple of tech support calls during the sign-off session.
• On the phone with a client. Tech support on receipt printing, label printing, and corp-wide settings.
• On the phone with another client going over options for a custom label printing project. He is doing batching, boxing, and needs multiple different label sizes.
• Working with an intern on a customer data upload. We tested things on his local machine and did some light debugging. Tomorrow it will be ready to go live.
• Emails, tech support, and did a small quote for an invoice view with RFID tags (batch #'s).
• Adding dummy records to the cluster database. A dummy record is the first record in the table. Basically, a place holder of sorts.

• Working on the special load options for the cluster level (level 3) database structure. Going table by table and adding custom code and instructions.
• Being a project manager and lead developer for both the interns. I helped one intern put his clients (20,000+) online for a digital migration. We finished up and billed the client. I also helped an intern start working on a custom invoice project. We were carving up existing files and making some custom changes. We also started doing some grouping by item price and description. Fun little project. Got an intern started into his own adilas account to track time and custom projects.
• Working on the steps to create the cluster level tables and populate them with data. Creating steps to help with the process. Testing along the way. A new developer came over. We got his laptop up to speed and installed ColdFusion and MySQL database stuff. My wife was also helping me with some copying and pasting code prep.
• Working on a special counter function to help show record counts for various tables and record sets. This will be used to show progress while copying and transferring data.

• Planning and prepping files and projects for the new developer. Started to implement a light version or version-ing system. Added light documentation for versions 1-9. See element of time # 873 in adilas and #2777 in the adilas university site.
• Burning copies of files for the new developer. Talking with him to let him know where we are headed and what his current project will be.
• Helping the new developer get set up with a new and updated copy of adilas files. We ran updates, installed databases, and got him lined out on his new project. He will be working on building the new solar systems.
• Working on pagination (next n) stuff for migrating data between servers. Helping the new developer out with code questions and light ColdFusion training.
• Working on new code to transfer zip codes. This was the first, bigger table that needed a multi-step process to make the migration go smoothly. Working with pagination to keep the user in a loop or process until they were done with the migration task at hand. This was a lot of prep work for other tables like invoice, parts, customers, expense/receipts, etc. Fairly simple process to migrate thousands of records at a time.
• Working on the create new solar system page. Breaking up the process into bite sized chunks of data. Working on the tables with letters A to B.
• Finished up the create tables and dummy record inserts for the solar system tables letters A to B.
• Starting on solar system tables for letter C.

• Logged in to all of the remote servers and made a physical database copy on each box. On the data 2 server, I created a storage database and copied some selected records over to the storage database. This is a temporary step for the full database copy and world building pieces that are coming.
• Recording notes about the media/content server and needs for the future.
• Logged into the content server to do some prep work. Checked usage and uploads. Found that quite a few companies have hundreds and hundreds of files that have been uploaded. The main type was pdf, pgn, gif, speg, and power point. Interesting. I also saw that one company has already exceeded their free space allocation. We will be making our first over allotment invoice for additional storage. We knew this would be coming at some time, we just didn't know when. That's exciting. We have 5 other companies that will be going over their free allotment within the next month. Yee haw! That's a new revenue stream for adilas.
• Working on adding a temporary storage site to adilas. This was basically created to help temporarily solve the full database copy for a client. We added a new folder or directory, copied the database, added a new datasource, changed code, posted about 1,000 pages of duplicate code online and did some testing. In a nutshell, we virtually copied the bus (normal shared environment) and let it run down the road.
• Helping an intern with his new laptop and getting things installed and setup.
  
  
• On the phone with Steve. We talked about a number of different topics. We talked a lot about copying the database, world building concepts, priorities, new projects, hot spots, custom labels, sub inventory and cost controls (packaging), promises made, known holes, and what developers are on what projects. We also talked about who can take on more work, developer wise. That is starting to be a small bottle neck. Here is a list of our current priorities:
  1. In-line discounts & tax stuff
  2. Sub inventory & cost controls (packaging)
  -Custom label app – fits perfectly in with packaging
  3. Adilas world – list of adilas professionals – who can help and what can they do?
  4. Adilas University – all help files, user guides, videos, developer's notebook, API documentation, etc.
  5. World building and being able to duplicate databases. This deals with copies, migration, independent mini versions, etc.
  
  
• Talking with an intern about direction. More work on his computer. Did some light planning.
• Recording notes and ideas. Checking off the to do list and doing more planning. Crazy times!
• Random to do list stuff and paying a payment on a credit card bill.
• Phone calls on and about API socket projects. One dealing with inventories and another one dealing with virtual banking and monies (kind of like prepaid debit cards).
• Brainstorming on a dynamic label maker or dynamic label app. Basically a build your own label interface.
• Another intern came over to work on stuff. We called a few clients, helped with a tech support call, and then discussed future projects and direction.

• Working with an intern on his projects. Worked on a few things to help his development environment be better on his laptop. We spent about 1.5 hours brainstorming on sub inventory and cost controls (packaging). We did some database flow charts and pen and paper mock-ups. We also worked on his custom invoice project for a client. This is an invoice that takes multiple invoice line items and groups the results based on price and item description. Great little project.
• Our associate came over to talk about a project management project for a company. We talked, watched PowerPoint slides, and took about six pages of notes. We detailed things out and came up with a budget.
• Emails and small to do list stuff.

• Working with an intern on his custom invoice projects. Called clients and did some invoicing for new features.
• Emails and phone tech support.
• Helping another intern get started on his new project. I started working on a half page layout for a magazine and tradeshow flyer.
• Finished up the trade show and magazine layout (½ page ad). Sent the mock-ups to both Steve and David.
• Emails and phone calls.
• Working with an intern on the web/API documentation project.
• New logo and colors for clients. Posted files online for clients.
• Emails and answering tax setting questions.

• Getting a new developer lined out on his newest project. He will be working in the background on the adilas world building concepts and database scripting project. Gave him new files and some papers (loose) that he was using for plans.
• Working with both a developer and intern on their projects. The intern and I started working on adding RFID tag numbers to printable invoices. We also did some prep for adding line item photos to the invoices. Good session. As a note, with both the interns, I've been starting to do mini scratch files on the concepts and then taking them in to the deeper adilas production arena. That really seems to help things stick better.
• Reviewing a proposal that was made by an associate for an adilas API socket integration with a 3rd party vendor called Virchex. Called and chatted with him on the phone.
• Posting the printable invoice file online with links and options to view the RFID tags. Called and talked with a client.
• Working with an intern on his mini API documentation project. Also spent some time recording notes in my notebook from loose pages. It feels good to get caught up.
• Finishing up recording notes from loose pages into my notebook.
• Reworking a flyer and magazine ad for an upcoming trade show. On a funny note, I got an email back from Steve saying he liked my first draft, but it looked “old” - meaning style. Kind of funny. The new draft has more graphic elements, drop shadowing, rounded corners, and light transparencies. Good stuff.

• An intern came over and we worked on cascading RFID tag settings to invoices and different invoice views, such as PDF and printer friendly versions. We also worked on adding invoice line item photos to printable invoices.
• On the phone with Steve going over a code questions and touching base on other projects that are out and in progress. Crazy times.
• Paying bills and finalizing a trade show flyer for Steve.
• Recording notes and trying to get organized.
• Emails, phone calls, and tech support stuff.
• New logo for a company.
• Emails, phone calls, and more tech support. Added a grouped button to the parts and general inventory homepage. I also did some work on showing the original date/time stamp on mini invoices and mini quotes.
• Small fix on web and eCommerce settings. Forced all internal links to the eCommerce sites vs. the older web services links and site. Trying to help transition things over to the new servers.

• On the phone with a consultant talking about exports to MS Excel for P&L (profit & loss) or Income Statement and the Balance Sheet. Great flexibility. Invoiced her for the development time. Sales quotes and email replying.
• Setup a new client out of the Orem, UT area. Invoiced, setup the new corporation, added users, set up reoccurring billing, and emailed back and forth. I imagine that in the not so distant future, we will be automating a number of those pieces. That will be fun.
• Working with an intern on his documentation project. We were setting up the add and edit pages. While the intern was doing certain tasks, I was working on emails and logos. Added a new logo and colors for a client.
• Tech support on my cart favorite buttons. Talking on the phone with a lady from Denver.