I have made this graph illustrating how qTeach's chat/messaging system will be implemented.

1. The messenger loads as soon as qTeach session begins. It will display (for a few seconds) a "Messenger Loading..." while it connects to the mySQL databases for the chat and userlist.

2. It prompts the end-user to enter their requested username. If it already exists, it will ask for a different one.

3. Upon entering your username, it will add the username to the userlist mySQL database.

4. It loads the messenger user interface (if I decide to make it as it's own utility as well as being a part of qTeach.)

5. In sync, it will pull the chat table from the mySQL chat database and the userlist from the mySQL Username/Userlist database.
6. User interface is formed, with the appropriate information set up, end-user is now able to message.

Issues this would draw at first:
1. How will the chat area be deleted? Will there be the "back-end"/admin format too?
-This can be solved at first by requesting the chat area to be deleted by using a simply drop-down contact page. When a back-end is created, it will allow the administrator to delete the mySQL databases, therefore deleting/clearing the chat.
2. How would the page auto-refresh?
-Page will auto-refresh via jQuery libraries.

So what is completed right now? What can be used? We have heard of many projects you have going on, it's really difficult to keep track of everything without seeing things in action.

I'll be making another video update for AOSDT talking about what is completed right now.

Currently, just the home page is developed. I'm currently working on the chat system, it should be operational by next week (no promises though).

Currently, you can see the home page by going to the qTeach site.

FYI: Clicking on the #qTeachDevelopers classroom just goes to a "In Construction" page, so it's pointless to click on it. I'll also have the Online Videos module up in a bit.

Latest Updates:
I have programmed the login/username input...


I have also programmed the chat area. Currently, I do not have it so it can send data to the chat output area, as I will have to work out how I will be able to send that to the mySQL database and then output it again. Otherwise, voila!

Just thought I'd let you guys know, I've completed chat integration, however there is the following bugs I am currently working on fixing (by the way, finished chat integration at 12:02 this morning and was up until 2:00, completely forgot to post the update)..

1. Username will remain in database until manual deletion - username does not delete when tab is closed.
2. On log-in, system message will appear then an empty text element, drawing from the "user" field of the mySQL database, this is being fixed right now.

Obviously auto-refresh doesn't happen, it will eventually.

Bug #2 has been relatively fixed, it's been replaces with a new bug!

-On refresh, php reuploads information to mySQL database, causing multiples of the same name in the userList. (Is trying to figure out how to make it so when the page refreshes, the mySQL database will be checked for the user, if user already exists, it will ignore the "add user to userList table" code...

If you are experienced in PHP and mySQL, I'll need your help. JavaScript experience is not necessarily needed, but a good thing to have.

Bug #2 is fixed!
Only need to fix bug #1. Should be easy with "window.close" javascript functionality.

qTeach's code can now be found on GitHub. Yes, this means I actually learned how to use a version system !

To view qTeach's project page, click here.

For those coders out there, I'll be posting on the AOSDT's site->forum area more than this area, so please get involved there if you are truly interested in helping AOSDT achieve it's goals!

Sincerely, Joshua Strobl

P.S. I'll be copy and pasting this in the deadlines area too!

interesting source code