Adds mechanics to add/rm hashtags.
Also implements help message.

FIXME: Counter still seems to be blocking when crawling through all new tweets. How to solve that?

Next :
Connect mechanics  to actual processing
User can now add and remove keywords using command line.

The counter doesn't seem to be blocking any more. Actually the blocking part was the print to the console and has been removed.

Next: Find a way for the leader board to have access to all keywords.
By writing it into the database ?? Or having some kind of global value for streaming?
Both sound quite logical.

FIXME : BTW, counter is also still working on a static list of keywords placed in data.
Creates test folder.

Not to perform unit tests (I really need to put all that stuff in practise some day), but some silly tests about the best way to chieve next objective.

Next:
- Add a hashtag table in database, to keep track of all current trendy hashtags. That way it can easily be used by everyone and we can get some more tracability.
Adds hashtag table in database to track hashtag activity

trendy list in streaming is synchronized on database content.
Database content can now be used by other processes to keep tracked on active hashtags.

Next:
Create perodic leaderboard of all tracked hashtags.
Changes LeaderBoard class pattern.
Leaderboard is now the root class of all other printers.
A Printer will be dedicated to a type of output media (file dump, console, html, ....)
Finishes first implementation of leaderboard.
Implements StdLeaderBoard, that prints a list of leaders for active hashtags periodically in the console

NEXT:
Implement HTMLLeaderBoard that will create a webpage with the latest results
Starts implementing htmlLeaderboard and prepares dropbox folder

More to be done when jinja2 is installed.
Finishes first ugly version of html leaderboard.
The leaderboard is regenerated periodically.

FIXME : Seems to have a problem with threads using command.py. Let s see why
Should solve bug

Running command.py generates a database problem. Apparently due to passing session/connection between threads.
Sessions have been separated in HashtagLogger to avoid session shaing between threads.

TODO:
Invetigate how many concurrent sessions can be created, and/or how to avoid this problem.
Solves bug :

It is possible to create the same hashtag several times in the databse. => Add existence checks

A bug should not be created twice any more in the trendy list.

FIXME:
Fix waas done in the plane with no internet connexion nor ressource.
Code is really bad and not pythonic :s.
Think about doing better.

database has to be cleaned from hashtags to remove duplicates now.
Update bugs
saves error logs to solve session issue