Skip to content
Commits on Aug 19, 2010
  1. Login dropdown display improvements.

    committed Aug 19, 2010
    - Fixes github issue 14.
    - No longer shifts the toolbar links.
    - Drops down, instead of appears from top-right corner.
    - Background is opaque so that underneath content doesn't show through.
    - Has a border around the box now.
Commits on Aug 16, 2010
  1. Restyle the question layout.

    committed Aug 16, 2010
  2. Layout work in progress.

    committed Aug 16, 2010
    - Add YUI grids to layout.
    - Move questions in from the edge (not ideal, but will do for now).
  3. Added cross-browser style uniformisation.

    committed Aug 16, 2010
    This uses YUI's reset, fonts and base styles. Still need to adjust some
    of our internal styles to gel with this but it's a good start.
Commits on Aug 15, 2010
  1. Simplify the standlone login form.

    committed Aug 15, 2010
    It now reuses the {% login_form %} template tag.
  2. Changed the UI for the status of the previous question.

    committed Aug 15, 2010
    It's now above the next question and highlighted slightly. Still not the
    ideal UI, but it's a little less confusing than it was.
  3. Local copy of JQuery and JQueryUI.

    committed Aug 15, 2010
    The JQueryUI dump isn't customised at all at the moment. Can trim it
    down once we know which bits we are and aren't using.
    
    Using a local version, rather than the Google CDN version for local
    development purposes (Google requires an API key which is tied to a
    particular external URL).
  4. Added non-JS versions of login and logout.

    committed Aug 15, 2010
    This includes the hidden form for the JS-enabled login, but it's not
    hooked up yet.
  5. Added placeholder links for stats and login/logout.

    committed Aug 15, 2010
    Committing now to hand over to Matt.
Commits on Aug 14, 2010
  1. Very basic (and ugly) static example of question display.

    committed Aug 14, 2010
    Gives us a concrete target for making dynamic template later.
  2. @ystevens
Something went wrong with that request. Please try again.