imp1 / iapt1

Interactive web design project for IAPT module in 3rd year Computer Science degree at Univeristy of York.

IAPT Individual Assessment

Interactive Applications web design project for IAPT module in 3^rd year Computer Science degree at the University of York.

iapt1's Issues

Colours of Links in Navbar

• Links are not apparent when they're focussed for monochromatic colour vision deficiencies. Change the saturation and contrast.
• Check the colour of focussed links against unfocussed links for colour vision deficiencies that confused blues and reds.
• Possibly just re-add outlines or a background to focussed links.

Bootables View Page & Confirmation Page

Make it pretty. Should be easy.
Have available pledges down the right.
Each one can have a button that takes the user to a confirmation page (with a var for the pledge selected).
Confirmation Page should have drop down of all the available pledges (with the one they chose selected) and a confirm button.
(Make a new page for this - in bootable controller)

Move css from hug to theme or default

Get rid of unused css in hug.css.
Move the used stuff to either theme.css if it's specific to BootUp, or to default.css if it's general HTML reset stuff.

New Bootable Page

Create a page for a user making a new bootable.

Put the bootable into the Not Available status. Let the user pick a category.

• Title
• Category
• Summary
• Description
• Funding Goal (in £GBP, but make it easy to internationalise)
• Image
• About (about the bootable manager, rather than the project)
• Author (set by controller automatically - maybe a hidden input with the value pre-set as the logged in user?)
• Creation Date (set to 'now' in the controller)
• Status (set to Not Available - see Author)

Bootables Edit Page is removing bootables

Deleted?

Registration Errors

Credit cards aren't being made, and errors at the second stage aren't going back to the second stage prompting users for better inputs.

Make sure tables are in 3NF

Documentation is sub-par to non-existent.

Add it in. Comment the shit outta stuff.

User Profiles

• See information.
• Edit information sigh.
• See pledges
  • Amount pledged
  • Expected reward
  • Total pledged to the project
  • The goal of the project
  • The status of the project

Pledges and Bootables can't be deleted in the edit page if the values are invalid.

The values shouldn't effect the ability to delete things.
Placeholders should work. But they seem to not be.

User password

Read through brief. Check whether they are mentioned. If not, email Chris asking whether they're wanted.

If they're to be added, change the table in the model and add a password input to registration1.html.

RemoveFont Awesome Icons

Possibley replace with Bootstrap GlyphIcons?

Populate Tables

These numbers are minima:

• 15 Bootables
• 5 Users
• 9 Categories (Art, Comics, Crafts, Fashion, Film, Games, Music, Photography, Technology)
• 4 Bootable Statuses (Not Available, Open for Pledges, Funded, Not Funded)

Debugging.

Possibly see about an easier weay to go about debugging the python code (specifically in controllers).

Use the python file IO to write debug stuff to a file?

Don't spend too long on this.

Ordering by funding progress

Not sure how to do this. Find out and do it.

The alternative is what, storing the funding progress in a bootable? Kinda silly.

Can this be done with select statements with select statements? I think so, but my SQL-fu is lacking.

Search within category

When, for example, user is on Books page, search bar has label signifying only books will be searched (and obviously this functionality would need to be the case). This label can maybe be closed to default back to searching all items?
Or maybe the books results will be first and highlighted somehow.

User Registration Page

Working creation of the three tables, with the credit card referring to an id of an address, and the user referring to both the id of an address and the id of a credit card.

• User Address
• Credit Card (with reference to a billing address, possibly one created possibly just the above address.)
• User (with reference to address and credit card)

Splitting of certain table values across two (or more) html input tags.

• Expiry date of credit card being a YY field, a MM field (and a hidden DD field set to 01)
• Post code of address(es) being a 4-length text field and a 3-length field.
• Real name of a user being a first name and a last name
• Birthdate of a user being a YYYY field, a MM field and a DD field.

Registering then proceeds to log the user in (however this is done in web2py).

Bootables Edit Page

User can edit their bootables provided the bootable has the right status_id (1).
All on one page for ease.

Go button in navbar is one or two pixels too tall in Chrome

It comes down slightly too far. The top edge is aligned with the search field fine, but at certain zoom levels (and this is the confusing thing - because it's not all zoom levels) the button's lower edge will be slightly lower than that of the search field.

Documentation

• Replace existing documentation.
• Add documentation to things.

Bootstrap

Why does it not like me?

• Get the icons working with the web2py version.
• Get tooltips working (for .alerts).

Database streamlining

• Give a title field to the bootable_pledges table.
• Remove the bootable_id field from the bootable_pledges_made table, as the pledge, (accessibly through the pledge_id) will have the bootable_id.

Choose Colour Pallette

Bear in mind colour-blindness. Also complimentary colours. Use common colours (blue = information, blue also = links (convention), red = warning)

• Text
• Links
• Visited Links
• Hover/Focussed Links
• Less Important Text
• Progress Bars
• Disable/Inactive items
• Selected/Highlighted Text

Cross-OS support.

Check other OSs.
Not sure how to check on OSX, which will probably be what Chris will be using.
But might as well check on lab computers.

Make entire featured Bootable a link.

In the Search results and Home page, have the featured bootable 'blocks' a link in their entirity. That is, have the a tag either just inside the li, or just outside it.

Add logout functionality

The button is there. How will it be done? Setting session.logged_in_user to None somehow. New page just for that, which redirects to page they were on?

Also, add redirects (to homepage?) on profile and dashboard (and other user-only pages) if no user is signed in.

Edit home page to collect actual bootables

Check out orderby in web2py stuff.

Also limiting results to 5. If there's not a nice way to do this, a counter variable is an easy hack.

Search Categories

• Add css for the select options.
  • Blue border on select/focus
  • Change down-arrow
• Add the bootable categories to the database.
• Add actual search functionality.

Duplication of identical address

Check equality with existing address and reuse their ID.