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 - 2/1/2010 to 2/28/2010 - (30)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 31 |
|
Daily Tasks | 2/1/2010 |
• Working on encrypting SSN’s, EIN’s, driver licenses and usernames. • Posted files online and ran update pages to encrypt existing values. |
|
|
AU 32 |
|
Daily Tasks | 2/2/2010 |
• Checking files, updating help files and going over things. • Worked on a small fix for recent PO’s and recent expense/receipts. • Added paid dates and ages to the reports. Started working on the Dewy … (decimals). • Created a user defined function for up to 5 decimal places. |
|
|
AU 33 |
|
Daily Tasks | 2/3/2010 |
• Brainstorming on page wide and column wide dewy decimal formatting. • Worked on a new user defined function for the group dewy settings. • Talked with Steve on the phone going over things. • Migrated parts for a company, did redneck and quality parts. • Setting up email addresses and email aliases for adilas users. • Biked in to town. Went on a zip line trip, helped guide the trip. Got a $7 tip. |
|
|
AU 2152 |
|
Brainstorming Dewy Decimal | 2/3/2010 |
Challenge of figuring out dynamically how many decimal points to show: 1. Max of 5. 2. Norm of 2. 3. Need to make everything follow suite per page on per column. 4. Already have a special dewy decimal formatting on a one by one basis. 5. Database stores in 5. 6. Most math is done on the database side or through output loops. 7. Column values need to be known before any output starts. 8. I’m trying to make things (reports & numbers) as slim as possible. 9. It would be easy to force all to 5, 4, 3, or 2 by using a decimal setting on a corp level. 10. It forced to a certain level, a flag may be needed for values that exceed the formatting. Ex: $ 45.015. In order to line up the decimal, the flag would need to be on the left or in a different column. 11. It is possible to split a single number into three pieces and format on an individual basis. a. Main number – format right b. Decimal c. Random cents left 12. It is possible to take all 5 digits and check (loop) to see if more than 2 or needed. Hold the highest number in a master format value. Only replace the value if a higher number is needed. If a 5 is ever reached, break the loop and force everything to 5 decimals. |
|
|
AU 34 |
|
Daily Tasks | 2/4/2010 |
• On the phone with Newtek trying to change over my merchant processing account. • Random different things. Phone calls, emails, support stuff. • Called and talked with some associates from two companies. One wanted a couple of changes on the receivables and I thought that they were good ideas. • Made the changes and posted the files. The ideas were to default the receivables homepage back to the who owes us money report. They also wanted the customer type to be added to the receivables advanced search. • Spent some time trying to get help and info on how to speed up the merchant processing between adilas and USAePay. • Worked on fine-tuning the adilas dew decimal function to handle both dollar signs and non-dollar signs (normal numbers). |
|
|
AU 35 |
|
Daily Tasks | 2/5/2010 |
• Went in to town and helped guide a zip line tour. $23 tip. • Testing wink output at 800x600. Much better than the 480x360. Slightly bigger file. • Working on the dewy decimal system. |
|
|
AU 36 |
|
Daily Tasks | 2/6/2010 |
• Working on the dewy decimal. • Added a multiplier to the recipe/build prep page. • Fixed a small bug on the pdf version of the P&L. Changed the word “yeild” to “yield”. • New logo for a company. • On the phone with Steve for ½ hour. • Started working on the rounding error. • Working on receiving a request PO and turning it into a live PO with math and rounding. • Worked on a dynamic mask creator for the dewy … |
|
|
AU 113 |
|
Daily Tasks | 2/8/2010 |
• Migrated all of the parts for a company. • Added customer logs to help document what was done. • Worked on the dewy … and showing rounding errors on the PO line items. • Worked on both the simple PO and advanced PO line items page. • Added tons of Java Script to help with math calcs and rounding on the add line item page for PO’s (advanced). |
|
|
AU 37 |
|
Daily Tasks | 2/9/2010 |
• On the phone with Steve a couple of different times. Went over the Dewy Decimal system and progress on the add PO line items. Talked about merchant processing and possible problems with swiping cards and retail transactions. Talked about maybe using a single retail injection key for the entire adilas application. • Sent emails back and forth to Newtek to see about options for the retail injection key. • Conference call between USAePay and Newtek about need of injection key. Basically, we don’t need it because of the way we interface with the gateway. The trick is that Newtek needs to flip the account type to “retail” and then our existing code will work. • Worked more on the dewy and working on the bulk PO request to live flip pages. |
|
|
AU 38 |
|
Daily Tasks | 2/10/2010 |
• Changed all of the titles on a company’s website. Sent an email update. • Checking email and saw a newsletter from a snowboarding camp. Thought about LTF and picked up the phone. Talked to them and then wrote a quick email intro. This totally derailed me from working on adilas. • Working on multiple-decimal formatting for PO’s and parts. • Added cftry and cfcatch tags to all web service calls. • More dewy stuff on parts. |
|
|
AU 39 |
|
Daily Tasks | 2/11/2010 |
• Prepping files for an associate to work on. Sent an email with files and instructions. • Got a package ready for the snowboarding camp. Wrote a letter and reviewed LTF products. • Working on the dewy for parts, recipes and reports. • Added new filters to the printable parts list. • Worked on changing how the advanced parts search worked and pulled back quantities. |
|
|
AU 53 |
|
Daily Ideas | 2/11/2010 | -Future marketing for companies – they enter data, widgets, parts, accessories, units, etc. We take the data and show a giant market place. We also pump their data out to Amazon, Craig’s List, eBay stores, etc. Not only do we provide them the tools to buy, trade and sell – we help them distribute and market their products and services. (Idea from Steve on 2/10/10) | |
|
AU 40 |
|
Daily Tasks | 2/12/2010 | • Working on the dewy for parts. | |
|
AU 41 |
|
Daily Tasks | 2/13/2010 |
• Working on the dewy for parts. • Spent hours working at the table on paper. • Worked on tracking inventory in, out, costing and profits. • Called and talked with Steve about using actual costing on adilas inventory tracking. |
|
|
AU 2153 |
|
Brainstorming Inventory & Balance Sheet | 2/13/2010 |
Inventory & balance sheet stuff. Flow from a to z… (See charts on scan in photo gallery – 5 pages dated 2/13/10) Sections: “I received some inventory…”: - Part - Qty - Cost - Cost - Extended - Date “I made some sales…”: - Part - Qty - Cost - Cost extended Profit: - Price - Price extended - Date Scratch paper continuing counts and flow: (See scans in photo gallery for 5 pages dated 2/13/10) Notes from working through these examples: - There was a cost change on part pdq-1 and we still had a couple in stock - Both of these (referring to 2 different methods on sheet) methods cause a problem when you go back in time (the variable that changed was current cost…) - A variable is introduced in to the mix (current or average cost) – this uses average price - Some known issues arise: o At this point I have a problem. Do I use actual, current, or average cost? o How does this effect things going forward? Going backward? - This gets a little cloudy because it gets hard to tell what is real o New question: How do you calculate average cost? In, out, both, extended, only cost changes, how? - If you have 0 items… the value would also be forced to 0 even though there is a difference of $ -1.00 between actual paid and actual attributed cost. Conclusions: 1. I was able to calculate total Quantity without checking on a part by part basis. I did have to exclude any special parts and quantities (see out_5 for a labor item). Basically, sum of the incoming values minus sum of the outgoing values. Individual parts were not eve taken into consideration. 2. In order to get the item count, I had to check on a per part number basis. I included any item that was not a 0 quantity count. 3. Actual value was calculated by taking the sum of the extended cost coming in minus the sum of the extended costs going out. I did have to exclude any special parts and quantities (see out_5 for a labor item). 4. The actual values were just math (in minus out). a. The current cost required a look-up and then an individual quantity times the current cost. Some parts were able to ride. b. The average cost required even more look-ups, averaging calcs, and then individual quantities multiplied by the calculated average. Some parts were able to ride. 5. Price and profit only counted on the income statement and had nothing to do with inventory counts and values. 6. Profit per line was done by taking a quantity times the current cost = extended cost price times a quantity = extended price. Extended price – extended cost = profit per line. |
|
|
AU 42 |
|
Daily Tasks | 2/15/2010 |
• Steve came over, we had a meeting and I showed him the progress on the dewy decimal system. We did 3 new pdf forms. 1 for Texas and 2 for Colorado. Good meeting. • Posted the new pdf files. • Small change on eval defaults for a company. Sent them an email. |
|
|
AU 43 |
|
Daily Tasks | 2/16/2010 |
• Changes to how inventory was calculated. On the phone with Steve going over what we have, what we need and where we are going. We talked about new clients, dewy decimal, balance sheet, marketing on the customer website, eCommerce, etc. • Found a small problem with transfer invoices (no costs passed along). • On the phone with Steve going over part costing and hole on transfer tickets. • More work on the dewy for parts. |
|
|
AU 44 |
|
Daily Tasks | 2/17/2010 |
• Working on the dewy for parts. • On the phone with Steve. • Worked on the dew for carts and invoices. • Worked on a new graphic for a company. Posted new graphic and color online. |
|
|
AU 114 |
|
Daily Tasks | 2/18/2010 |
• On the phone with a customer, helped them with changing part numbers. Sent them an email with step by step instructions. • Added Java Script counters to the stock/unit descriptions. • More dewy stuff. |
|
|
AU 45 |
|
Daily Tasks | 2/19/2010 |
• Working on the dewy … • On the phone with Steve going over plans and options. Talked about the balance sheet, dewy …, eCommerce and customer time clock. • Added number formatting to all SQL insert and update statements. This was part of helping to standardize the dewy stuff. |
|
|
AU 54 |
|
Daily Ideas | 2/19/2010 |
-Need a customer time clock – it might also be nice to have a start/in time and end/out time those would then help to convert to the value and time period fields. (This feeds the controls.) (Silver permission – this controls the time cards – sketch in notebook) -Need a customer time clock that you could either clock – in/out or put a physical number of minutes and hours into. That would then show-up and you could create an invoice from that for the customer. It would need to tie itself to the invoice and become part of it. It would then show that it was already invoiced. |
|
|
AU 46 |
|
Daily Tasks | 2/20/2010 |
• On the phone with an associate going over things. They want a few small links on their website and a mock-up site for another company. • More number formatting on insert and update SQL statements. • Worked on the dewy for cart, unit sales, quotes and invoices. |
|
|
AU 47 |
|
Daily Tasks | 2/22/2010 |
• Finished up the first round of the dewy. • Updated all of the database tables. • Posted files online (hundreds of files). • Testing and did a database back-up. Finished up at 1:00am. |
|
|
AU 48 |
|
Daily Tasks | 2/23/2010 | • Small tweaks on the dewy decimal system. Checked some math and adjusted the max number validation. | |
|
AU 49 |
|
Daily Tasks | 2/24/2010 |
• Working on problem between transfer invoices and part costs. • Working on special mass update page for stock/units. This check invoice prices and back figured invoice costs and base prices by a specific percentage. • Ran code for a company. • Sent update emails and started working on new fields for parts. They are show on web and unit of measurement. |
|
|
AU 50 |
|
Daily Tasks | 2/25/2010 |
• Added a new logo for a customer. • Changes to parts and worked on standard units of measurements. • Biked into the accounting office to work with Steve. Went over the dewy and Steve got to play with it a bit. Talked about balance sheet and upcoming game plan. • Set up a company on new Colorado PDF forms. |
|
|
AU 55 |
|
Daily Ideas | 2/25/2010 | -Just the other day I was thinking about a simplified help system and logic helper. Start out really simple… what would you like to do? Then you show options and let the person choose or lead/guide them through it. | |
|
AU 2154 |
|
Brainstorming Units of Measurement | 2/25/2010 |
Units of Measurement: Long: Initials - Each: ea. - Inches: in. - Feet: ft. - Yards: yd. - Centimeters: cm - Meters: m - Millimeters: mm - Cups: c - Pints: pt. - Quarts: qt. - Gallons: gal. - Fluid Ounces: fl oz. - Ounces: oz. - Pounds: lb. - Grams: g - Kilograms: kg - Milligrams: mg - Liters: l - Hours: hrs. - Minutes: min. - Days: dd - Hundred weight: cwt - Teaspoons: tsp. - Tablespoons: tbsp. - Tons: T - Per 10 (Latin deci): D - Per 100 (Latin centi): C - Per 1,000 (Latin milli): M |
|
|
AU 51 |
|
Daily Tasks | 2/26/2010 |
• LTF lingo changes… A guy from Washington State submitted a number of typos on the LTF logo section. Made changes. • Calling and talking to a contact at the bank. Over an hour on the phone. Calling credit card companies. Getting financials ready and sending 2008 taxes, 2009 income and expenses and writing an explanation email to a contact. • Small fix on the advanced part search. Problem with pagination. Posted files online. • Worked on units of measurement. Added a bunch of system basic measurements. • Did some phone calls and emails. • Light training for some customers. |
|
|
AU 52 |
|
Daily Tasks | 2/27/2010 | • Working on the parts and units of measurement pages. | |