gpower2 / mangetsu Goto Github PK

We need a general way of marking our code in order to actually fix stuff later on.

Something like capitals for global, small for locals, _for classes etc.

Any ideas?

A class that contains all the functionality for interacting with MySQL database.
It should contain functions that:

• allow execution for INSERT, UPDATE, DELETE operations, returning the number of rows affected
• allow execution for scalar queries returning DataTables
• allow execution for scalar queries returning single data values
• allow execution for scalar queries returning an enumerable object

I think we should upload some workflow diagramms on each component before actually coding stuff. We could have a better idea on what links where and why, and we could aslo suggest better algorithms-ideas on implementing each feature.

We want the new board to be designed MVC style.
So we need an MVC infrastructure.
We will either implement our own basic infrastructure, or copy an existing one from a bigger framework (eg. CodeIgniter, Laravel).

We should decide on a database schema for implementing forums, sub forums, threads and posts.

We should have in mind their connection with the privileges mechanism, and the hierarchy of forums/subforums. (Each sub forum should inherit the privileges of the parent at creation and perhaps we should let a sub forum to have ONLY stricter privileges than its parent.)

Private messages should be implemented in a more flexible way that we have now.
We should allow:

• Multiple recipients
• Read date
• Reply to all/partial reply
• Connection of pms

We should also implement searching.

We need to decide about our authentication system.
Password hash and salt, session etc.

An object that will check the security checks for each request

We must decide upon a database schema for managing users/groups/privileges.

The controller objects must implement methods for managing this data.

A class that will contain the functionality needed for BBcodes:

• parsing
• writing
• fixing???

It should make heavy use of regular expressions in order to be as fast as possible.

We should implement a logging mechanism for error and warning logging.

It should be accessible from everywhere in the code, in order to have a unified way of logging.
It should have logging levels predefined, preferably as an enumeration.
It should be able to write to a database and a file medium (selectable).

We must decide upon a database schema about projects, the tracker and their relation with the users (credits, participation)