psybuzz / goalkeeper Goto Github PK

might be a better idea to just have index.html be a login/registration page, then the goal page be after login

Since the create button is below the goal list, every time we create a new goal, the create button moves down. We should move it above the goal list, so it doesn't do that.

We're switching our back-end frame from PHP-MySQL to Node.js-MongoDB!
Be sure to learn about:
Node.js
Express.js
MongoDB

When creating a new goal, a larger window could pop open that allows the user to input details. This container could include multiple fields of input, while the goal in the leftpane only holds abbreviated data.

Header doesn't appear; create button doesn't do anything.

Priorities are cool. Sorting is cool. Let's sort by priorities.

DEPRECATED

It has been decided that sorting by priority is not a critically useful feature, and we are instead planning on drag and drop for reordering goals.

Drag and Drop.

A page to manage accounts

I think we should have the logged-in page be index.html, and have the index.html page redirect to a login page if the user isn't logged in.

Could be better?

Right now, the 'carpe diem motto' title is like a banner that covers all the goals in the list. The text overflows to the right, so it might be better to just have a bar at the top for the title itself.

Engagement in daily activities can be intensified through social commitments:

• In student clubs, we form families to support and encourage each other to go to events.
• In GTA V, online players band together as a crew to act with stability.
• In League of Legends, teams of 3, 5 achieve more together

Should Goalkeeper go down the path of group goals, and associated group achievements?

Or should it simply offer the option to share goals?

the header function isn't working in Login.php. might be because there's html output coming out of login.php before it reaches the header function

Featurrrre

When a goal is clicked, the goal list should move off the screen, while the checkpoint list moves onto the screen. We'll use this idea until we can come up with a better one.

FRONT END

Makes sense for clicks to open stuff.

Our method of registration is currently not secure enough, as it only uses SHA1 encryption. We'll have to add salt hashing, and maybe a MD5 encryption on top of it.
Make sure to clear all of your MySQL tables when this is updated.

Next step in the back-end. Implement account storage.

We need to plan out how our db tables will be related before we can implement it. http://net.tutsplus.com/tutorials/tools-and-tips/relational-databases-for-dummies/
is a good article teaching the basics of relational database tables.

Should we just store each individual goal as the whole html element? Or should we separate the information into columns, like title, color, index? Should the primary key for the goal table just be the user id(it gets auto-incremented with each insert)?

I will try to draw out a diagram for the relationship of all the tables, but we might need to meet up to figure this out.

Bad for users with OCD.