aletson/quickmarks

quickmarks's Issues

user auth

• Decide on auth pkg (or roll our own)
• Link to lodestone / web scraping for verification
• Lock down reporting to logged in users

tod reporting

• choose a css framework
• implement the css framework
• modal + jQ datepicker -> POST timestamp

client should ask server for new reports and disable buttons / update tod periodically

• long polling (this might murder the server)?
• sse (looks reasonable but still keeps a bunch of threads open)?
• just check every 15 seconds using setTimeout and get all events since last checkin (by far the easiest and probably least taxing on the server and also this doesnt need real time updates like sse)?

re-think database and make it extensible

• Write reports table model
• Migrate data to reports table and restructure marks table
• Rewrite view to work off of min_cooldown and max_cooldown rather than 4-6 hours for everything
• Rewrite controller to report to the correct table & pull data from the correct table -- something like SELECT * FROM marks m JOIN reports r ON m.id = r.mark_id WHERE r.report_time = (SELECT MAX(report_time) FROM reports AS r2 WHERE r2.mark_id = m.id) for building the index page again

record coords if window is open

and generate a link to retah