"Finishing touches (additional functionality, based on available time) + Final Code"
Design Fixes:
Chat-box properly displayed (proper width)
New favicon
Bug Fixes
Multiple instances of same user notified of messages, #68
Multiple instances of same user, only disconnects once the last one disconnects
Autoscrolling done properly
Attempts at ping fixes
New Features:
Removing the session on failed login attempt
New font (GeometrySoftPro)
Helpful messages on login (for someone who hasn't really used IRC before)
Documentation
Fixed some markdown errors
I'd like to thank @ChrisDufour for all the help throughout this assignment. A lot of time and effort was put into brainstorming the logic and flow of certain functions and dialogs. A lot of edge caes were considered and error handling was attempted to be done wherever possible.
A big advantage of something like this was that it was a long assignment, working 8:30AM to 1PM every Monday, Wednesday and Friday, but it was not time struggling, it was fun doing the research and actually producing something useful. This has been the first time in my University career (I can't speak for @ChrisDufour that I had fun coding something BIG and COMPLEX), other classes that shall remain nameless would bring us to the point of suicidal thoughts, haha.
The project is still nowhere near our satisfaction, as mentioned in our finalized "Extensions.md", however we are happy with the product we produced, the features we created, and the project we delivered.
And we kinda stole the emoticons and are using a commercial font....lol. But beyond that it is all open source licenses!!! We'll be sure to change that if we go public with this code (which we will do, once we have a more stable release).
We've been reading online and read that a possible technique for making this public would be to give every user who does a pull request COMMIT rights, sure they could break a bunch of things but in the articles I read it could be very amazing the productions that get made....
Would also like to take this moment to thank @falaca for allowing us to bounce ideas off him during the tutorial hours. It lead to some very helpful conversations and provided a basis to breakdown our program and develop new features. We discussed in the past about getting this to be lightweight and potentially putting it on a Raspberry Pi, slap Node on one and it should have no problem running (we never actually benchmarked how process intensive this application is, considering node-irc is the core of the application and we did not develop that portion).
"Finishing touches (additional functionality, based on available time) + Final Code"
Design Fixes:
Bug Fixes
New Features:
Documentation
I'd like to thank @ChrisDufour for all the help throughout this assignment. A lot of time and effort was put into brainstorming the logic and flow of certain functions and dialogs. A lot of edge caes were considered and error handling was attempted to be done wherever possible.
A big advantage of something like this was that it was a long assignment, working 8:30AM to 1PM every Monday, Wednesday and Friday, but it was not time struggling, it was fun doing the research and actually producing something useful. This has been the first time in my University career (I can't speak for @ChrisDufour that I had fun coding something BIG and COMPLEX), other classes that shall remain nameless would bring us to the point of suicidal thoughts, haha.
The project is still nowhere near our satisfaction, as mentioned in our finalized "Extensions.md", however we are happy with the product we produced, the features we created, and the project we delivered.
And we kinda stole the emoticons and are using a commercial font....lol. But beyond that it is all open source licenses!!! We'll be sure to change that if we go public with this code (which we will do, once we have a more stable release).
We've been reading online and read that a possible technique for making this public would be to give every user who does a pull request COMMIT rights, sure they could break a bunch of things but in the articles I read it could be very amazing the productions that get made....
Would also like to take this moment to thank @falaca for allowing us to bounce ideas off him during the tutorial hours. It lead to some very helpful conversations and provided a basis to breakdown our program and develop new features. We discussed in the past about getting this to be lightweight and potentially putting it on a Raspberry Pi, slap Node on one and it should have no problem running (we never actually benchmarked how process intensive this application is, considering node-irc is the core of the application and we did not develop that portion).
To the exams, to third year, and onward.