IWDSA Home
Welcome to the official Interactive Web Development Student Association website.
Team Meetings
When: Every Thursday @ 5pm-6pm
Where: 98C 4-023
Our team meets to work on Project Legacy development. Anyone interested in working on project legacy is encouraged to attend.
Information Wiki
- Areas Of Study In Web
- What is Project Legacy?
- Legacy Project Skeleton
- Project Legacy Interface
- Developer Tools
- Project Setup Tutorial
- How to update and submit your code
- DISCUSSION
- What system-wide features should be available?
- 'Message' feature between users
- What is the purpose of Group Classes?
- Parent groups moderating child groups
- Adding new groups
- Handling extra club content (pages, info, bylaws, etc)?
- List of requirements for clubs to become chartered
- Creation of new groups and group hierarchy
- Membership roles vs subscriptions
Todo Lists
- Notes Requiring Discussion
- Tasks: General
- Delete Edit Complete 'How to get install' needs to be updated for both beginners and mac users
- Delete Edit Complete Easy: (Z) 'What is Project Legacy?' needs to be filled in to inform visitors to our website
- Delete Edit Complete Easy: Transfer the latest version of the database into the visual designer (instructions in description)
- Delete Edit Complete Easy: After the dbdesigner has been updated, create Screenshot with notes
- Delete Edit Complete Easy: Add test data for group_categories (instructions in description)
- Delete Edit Complete (Design Team) Create a nicely formatted 'thank you for registering' email template
- Delete Edit Complete Easy: More test data needs to be filled in
- Delete Edit Complete When should group admin controls be visible?
- Delete Edit Complete Easy: Create a user 0 for administering the system
- Delete Edit Complete Medium: Documentation: Validation error messages need to be written
- Delete Edit Complete Easy: All view files should be checked for dead links
- Delete Edit Complete Medium: A workflow map needs to be made. A tree that has all the links found on the pages
- Delete Edit Complete (Z) Easy: Patent Design Or Immatations
- Delete Edit Complete Easy: Group test-data needed with realistic tree structure for example usage
- Delete Edit Complete Medium: Create tutorial on how to submit code and update code in Git
- Tasks: Frontend
- Delete Edit Complete (Design Team) Site Design
- Delete Edit Complete (Design Team) Design Logo
- Delete Edit Complete (Design Team) Sketch a mockup of the 'Group Browser' pages for categories, searching, and browsing
- Delete Edit Complete (Z, Design Team) Create a nice graphical skin theme for the website in Photoshop
- Delete Edit Complete Hard: Turn nice graphical photoshop skin into CSS code
- Delete Edit Complete Medium: all 'index' pages need to be reskinned into nicer pages rather than ugly tables
- Delete Edit Complete (Design Team) All forms need to be checked for security (users shouldn't be able to register and make themself admins)
- Delete Edit Complete Easy: Finalize navigation bar layout and update views accordingly
- Tasks: Backend
- Delete Edit Hard+: (DJ) Calendar helper needs to generate a table with calendar data
- Delete Edit Easy: (DJ) Add database.php and database to online Legacy Project
- Delete Edit Complete Hard+: (DJ) Calendar Behavior needs to be finished to allow formatting of data for the calendar helper
- Delete Edit Complete Hard: Events in calendar should link to their respective event pages
- Delete Edit Complete Hard: Figure out how Calendar Events need to store 'event repition' data (such as how often) like google does
- Delete Edit Complete Hard+: Code the extended form inputs and hooks for events that allows them to repeat on a schedule
- Delete Edit Complete (Design Team) Security permissions must be checked for all data (try to find hidden pages that people shouldn't get to, such as add/edit/delete)
- Delete Edit Complete Easy: (DJ) User views need to be updated for messages instead of Sender/Reciever
- Delete Edit Complete Hard: (DJ) [ACL] Create a function that checks if the logged in user is an admin of the current group
- Delete Edit Complete Easy: Picture uploading needs to have the thumbnail sizes tweaked.
- Delete Edit Medium: Creating a new group should make the current user the admin president
- Delete Edit Hard: Link generators don't work with admin prefix
- Delete Edit Complete Hard: Groups and Categories trees should show the number of groups they have.
- Delete Edit Complete Medium: User messaging system needs to be reinstalled
- Delete Edit Complete Easy: Attach emailer to announcements
- Bugs
- Feature Requests
- Board Members
- Completed Tasks
- Delete Edit Feature Requests: Mini group creation (for project teams)
- Delete Edit General: Install password generation
- Delete Edit Admin: Install password generation on iwdsa.org
- Delete Edit Admin: Transfer google groups to iwdsa.org
- Delete Edit Board Members: Confirm Coldfusion public speaking arrangement
- Delete Edit Admin: Fix presentation of iwdsa.org lists
- Delete Edit Board Members: Add tutorials for Git and Wamp
- Delete Edit Bugs: (Dean) WYSIWYG Text Editor Bug
- Delete Edit Discussion: (z) What system-wide settings should be available when clients install legacy?
- Delete Edit Discussion: Discuss on a wiki page what the purpose of 'Group Classes' is. What are they, how should we use them? Give examples.
- Delete Edit Backend: (Jonathan) Create a recursive function for rendering the Group Categories tree
- Delete Edit Backend: (Jonathan) Create a CakePHP 'Helper' class to house the group categories function
- Delete Edit Discussion: What are membership roles vs subscriptions?
- Delete Edit Backend: (DJ) Install the group parameter prefix into legacy
- Delete Edit General: (Jonathan) Group categories droplist needs to display as a tree heirarchy
- Delete Edit Discussion: Should 'Messages' between users be added/allowed in the project legacy?
- Delete Edit Discussion: Should we have an option that prevents parent groups from moderating child groups? (to hide small teams from asi, etc)
- Delete Edit Discussion: How should we handle creating new groups while preventing people from placing their new group under an existing group, instead of specialty
- Delete Edit Backend: All models need to be checked for hasMany/hasOne relationships
- Delete Edit Discussion: Should add group membership use a hidden form group_id field or should i use the url prefix?
- Delete Edit Discussion: How should extra club content be handled (pages, info, bylaws, etc)
- Delete Edit General: Update online git code
- Delete Edit Backend: (DJ) Club Categories (Max of 2)
- Delete Edit Backend: (DJ) Merge the welcome plugin git into the legacy git
- Delete Edit Backend: (DJ) Fix relationships for multiple group categories
- Delete Edit Backend: Install Meio_Upload behavior for logos
- Delete Edit Backend: When users register their email must be a .edu (validation)
- Delete Edit Discussion: List of requirements for clubs to become chartered
