Sunday, May 25, 2008 8:37:06 PM (GMT Standard Time, UTC+00:00)

In the interest of self organisation at work, I'm going to write a blog entry each week over at Redgloo with a list of the things I wish to acchieve at work. My boss can then comment and add things and I can cross them off as I get them done.

This is quite a cool idea, and I'm going to start doing it for Scrobbles as well, although maybe not as regularly. I'm dangerously close to finishing this project (at least to the point where people can start using it), and this week and weekend has seen a forced increase in productivity - the likes of which not seen for quite a while from me. I'm not entirely sure how I managed it, as at the beginning of the week I really didn't want to work on it. I just forced myself to by setting some tasks and got carried away from there. Let's try to continue this eh?

I tend to keep a text file on my desktop containing the current 'to-do' list, and as I have this, I can safely post the list as it stood at the beginning of the week, and cross out the things I got done this week also. I have backdated this entry to a week ago, to reflect this.

The way I'll do this, is each time I post, I'll post a revised version of the list, containing only the things I still need to do, and as I get things completed, I'll cross them out of the most recently written blog entry :) If I think of new things that need adding, I'll either edit the blog entry, or if enough has been achieved to warrant it, I'll make a new entry.

I'll highlight the 'next' planned work actions with italic lettering, and these will be things I aim to get done within a week's time.

• Write the public services for third party websites to retrieve/submit data
• Authentication
• FB Application like system, where users choose who is allowed to pull their data from the site
• Totalling queries
• List Queries
• Interval Queries
• User Info queries
• Generic Server Work
• Update database on server to catch up with development version
• Update server site to take on all this new code I've been writing
• Get the automated backup scripts working again
• Work out how to finance the purchase of a new server
• Snippet format work
• Add capability for user inputs to be given to snippets
• Add capabiity for third party websites to insert data into snippets (using public services)
• Editing of pages (Ajax stylee, I already had a syncronous version done)
• Hide/Show editing controls - based on user authentication
• Adding pages
• Removing pages
• Renaming of Pages
• Adding snippets to pages
• Moving snippets around pages
• Editing the inputs to those snippets
• Javascript Based Snippet Editing/Creation
• World of Warcraft Automated Blogging
• Buy domain (wowscrolls.com)
• Choose a technology to build on
• Develop automatic user creation based on Scrobbles data
• Choose a decent template for advertising revenue
• Architect a data-driven pipeline for generation of blog posts based on
• Location
• Activity
• Player Character
• Party
• ???
• Develop background process to generate blog posts
• Use the World of Warcraft Armory to populate character profiles
• Add capability for characters to automatically post comments on each other's blogs for purposes of hilarity
• Online Community
• Populate Wiki with 'general' information
• Populate Wiki with stat family documentation
• Populate Wiki for API documentation
• Create forums for snippet requests/application requests
• World of Warcraft Data Submittal
• Create an online page (using the third party data API) to allow online data submission for World of Warcraft (IE: without using the client)
• Make client application for automatic data submission stable (One is already written, it just needs a lot of work!)
• Automatic World of Warcraft upload (Make this more atomic)
• Create an intallation manager (DOH, re-invent wheel!?)
• Elevated installer process
• XML based 'module' installation/uninstallation
• Filterable install list
• Rollback on fail
• Create click-once installer for the installation manager
• Logistics
• Add a 'status' to each account for payment info
• Provide the means with which to easily pay (Paypal/Google Checkout/Direct CC/Phone??)
• Limit the number of queries each user is allowed and make this dependent on account status
• Third party limitations (payment system too?), to prevent DoS attacks.