Weekly Update: Week of August 29

Last week (and partially the week before)'s accomplishments:

• Educated myself as to how WebSQL, SQL, and JavaScript-editing-document technologies work.
• Set up FTP connection and working folders for the LogTables project and Team ILS in general.
• Established the GUI for the LogTables project, and created its HTML interface.
• Structured all the functions that the JavaScript code needs to do.
• Coded about half of said functions, particularly the ones working deeply with database interaction

The project is now at a state where I can load the HTML page and manipulate the GUI elements - and the code exists whereby I should be able to create, rename, and destroy logs. However, the JavaScript for that does not load, and debugging has not happened yet.

Remaining tasks on the LogTables project:

• Debug existing code until functionality actually displays itself and works.
• Implement date/time handling functionality - Iscoe has been working on the JavaScript clock side of this with limited success. But there is also an SQL storage side, and there needs to be JavaScript code to subtract dates and times and calculate durations, none of which have been implemented.
• Implement HTML date/time display functionality - this might be as simple as "write it to the table elements", but it hasn't been explored yet due to a lack of date/time handling in the JavaScript.
• Test and debug the above features.
• Test and debug the above features ON A SMARTPHONE.
• Optimize for offline capabilities (e.g. add local manifests).
• Test said offline capabilities on a smartphone.
• ???
• Profit!

Goals for the week of September 5:

• Test, debug, and fix existing HTML <--> JavaScript <--> WebSQL functionality.
• If all that is done within the only two class days that exist this week, it hasn't been done thoroughly enough.
• If it honest-to-God works, and works again, and there is STILL time remaining in the week, work with Iscoe on date/time handling.

One final note: I'm unsure what Calvin is working on, and he may be being left out of the development curve on the project - which, if the debugging turns out to be a stupid, easily fixable syntax error somewhere or something similar, is probably half-done already. On the other hand, he is a busy SciO captain and tends to work somewhat autonomously, so I haven't prodded him on this.

One final-final note: We still haven't come up with an idea for our second project.