Skip to content
kaku edited this page Sep 13, 2010 · 51 revisions

Con Schedule TODO:

Master Code

High Priority

  • Move conDay[][] to settings.php
    • (Mark says) Drupal integration gets rid of settings.php and puts all that stuff in conschedule_init / conschedule_global in conschedule.module, should probably create a custom drupal admin page.
  • Add a table to the database that allows the “tagging” of date ranges.
    (e.g. index.php?tag=mew2008 will pull up the events for mew 2008.)
    • (Mark says) This corresponds with conday to some degree especially if tags always correspond to cons:
      MewCon II from December 30th 2009 to January 2nd 2010 which get’s broken down into conDay0 conDay1, conDay2, etc.

Medium Priority

  • Putting a quote mark in a title renders it as a question mark instead (e.g. Say “What?” => Say ?What??). Possibly because of verify_string()?
    • (Mark says) no longer an issue with drupal integration, all queries use db_query now which auto-escapes strings (well, semi automatically)
  • Add previous/next event links when viewing an event.
  • addUserEvents will only allow people who have an event add more, this is a bit of a problem
    • I’m failing to reproduce this -Kaku
      • I think I either fixed this or it only applies to the first person to use the system. So let’s leave this up here
        • No longer an issue with drupal integration
  • (Mark says) choose between left-align with padding or center align with no padding for event titles in schedule (I prefer centered no padding, Kaku’s code had left-align with padding originally, that’s what I’ve left it as for the moment).

Low Piority

  • userSchedule has a day separator based on midnight rather than con days.
  • Move menu creation into its own function so it’s not tied specifically to MEWcon.
    • (Mark says) no longer an issue with drupal integration.
  • [new] Add some sort of visual way to know which events a User is signed up for in the Event Schedule, whether by changing the background color or adding a badge or whatever.
  • use theming api to allow drupal themes to theme conschedule (for schedule,“view event”, and user schedule only probably)

Optional / Brainstorm

  • Have the main schedule allow admins to start adding an event from a certain time.
    • (Mark says) Kaku did this, it’s awesome.
  • Allow grouping/filtering by room or name in userSchedule
    (e.g. userSchedule.php?orderBy=‘room’ will group all rooms together, where userSchedule.php?room=0 will only display roomID 0)
  • Move user events table printout to Webpage.
    • (Mark says) drupal integration completely rearranged the code anyway.
  • Ability to filter by panelist. Will require a Panelists table and a slight restructure of the Events table. This will also allow multiple panelists to host a single panel.
    • (Mark says) could tie panelists table optionally to forum/drupal account
  • Add a compact view option to index that groups rooms together (e.g. a header for “Room 1” with a compact list of all its events – ordered by time, followed by a header for “Room 2,” etc).

LazySQLConnection Branch

Description

  • Makes a connection to the mysql database at the last possible minute: when a query is run.

Reasoning

  • By using this, we should cut down on some unnecessary SQL connections made by simply creating a Connection object and using validate_string() to verify data. Add.php, for instance, uses a Connection to validate strings and then checks some of them for errors. Because no query was run if the _POST strings are invalid, we just wasted a mysql connection.
Clone this wiki locally