| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2015-04-01 | Smartypants | Thibaut Horel | |
| 2015-04-01 | PEP8 | Thibaut Horel | |
| 2015-03-28 | unbroke adding news | Guillaume Horel | |
| 2015-03-28 | add an empty articles section | Guillaume Horel | |
| 2015-03-28 | flash error messages | Guillaume Horel | |
| 2014-12-06 | refactor the templates | Guillaume Horel | |
| 2014-04-05 | forgot to load the timezonesshow | Guillaume Horel | |
| 2013-12-01 | trying again | Guillaume Horel | |
| 2013-12-01 | one more try | Guillaume Horel | |
| 2013-12-01 | try to fix the db lock | Guillaume Horel | |
| 2013-09-17 | New pattern to load the db | Guillaume Horel | |
| before it was reloaded every time due to the @app.before_request now it's loaded on demand. | |||
| 2012-11-14 | Add a link to the news page in the email | Thibaut Horel | |
| 2012-11-13 | fix dates in rss feed | Guillaume Horel | |
| 2012-11-13 | Add the preview feature | Guillaume Horel | |
| not that well tested, so might kill your kitties. | |||
| 2012-11-13 | Use le timago.js plugin to display dates | Guillaume Horel | |
| Ca a l'air de marcher, mais pose la question suivante: Pourquoi pas se débarasser du champ timezone dans la base de donnée et faire la conversion directement au niveau du javascript? L'avantage étant que l'utilisateur n'a aucun réglage à faire car le navigateur a accès à la timezone du système qui est sans la doute la première chose que l'utilisateur change. | |||
| 2012-11-13 | Fix a unicode bug (I thought I had added this .encode() to solve another bug) | Thibaut Horel | |
| 2012-11-13 | Send notification emails as html | Thibaut Horel | |
| 2012-11-13 | Order comments in ascending order (oldest comments first). Feels more natural | Thibaut Horel | |
| 2012-11-12 | Make the locale encoding explicit to work even when the system's config is weird | Thibaut Horel | |
| 2012-11-11 | Finish the timezine feature | Thibaut Horel | |
| 2012-11-10 | The time is be displayed in the user timezone | Guillaume Horel | |
| I can't make the user edit template work The dropdown doesn't default to the current timezone. | |||
| 2012-11-10 | Fix locales and minor encoding issue | Thibaut Horel | |
| 2012-11-10 | Add email notifications | Thibaut Horel | |
| 2012-11-10 | Follow up to previous commit. | Thibaut Horel | |
| * Make flask db connnection also use date converters to avoid crashing when displaying dates * Update the import script to import dates from the old databse as timestamps By the way, I strongly disagree with this choice of using timestamps, for the following reasons: * why would timestamps be a better representation of times than ISO 8601? they cannot represent times before the epoch, they are more easily subject to "year 2000"-like bugs. No wonder why the vast majority of web protocols use ISO 8601 instead of timestamps. * Even MySQL internally uses ISO 8601 strings to store datetime fields * This solution requires to write unsupported sqlite code: there is no "timestamp" datatype in sqlite3, so you implicitely rely on sqlite3 casting this to a string. You also rely on the python doing implicit conversions from the database to datetime objects. The funniest part is that the way Python deals with this implicit conversion is by storing the datetime object as a "%Y-%m-%d %H:%M:%S" string in the database (which is by the way, not even standard ISO 8601:2004)! No timestamp anywhere to be seen, even though this is what is stated in schema.sql... This looks insane to me... Having explicit and standard conventions at the expense of two additional lines of code does not seems that insane in comparison to Python's insanity. python. The funniest part is that they way Python does this implicit conversion is by internally storing the | |||
| 2012-11-09 | Stop insanity with timestamps | Guillaume Horel | |
| still need to check the function which imports the old database | |||
| 2012-11-09 | Fix two bugs | Thibaut Horel | |
| * make the shortening function backward compatible to old comments * fix a bug where the show_user function would always display the current user's profile | |||
| 2012-11-09 | add rss flux | Guillaume Horel | |
| 2012-11-08 | fix up Thibaut's brain damaged code | Guillaume Horel | |
| 2012-11-08 | Add info boxes on home page. | Thibaut Horel | |
| The choice of BeautifulSoup to shorten comments is open to discussion. It is a bit overkill. | |||
| 2012-11-08 | Forgot to take Guillaume's remark into account in previous commit | Thibaut Horel | |
| 2012-11-08 | User feature (view and edit profile) | Thibaut Horel | |
| 2012-11-08 | Filter improvements | Thibaut Horel | |
| 2012-11-07 | fixed up the comment system | Guillaume Horel | |
| 2012-11-07 | reworked the templates | Guillaume Horel | |
| 2012-11-08 | Keep both rst and html rendered content in the database. News edit feature | Thibaut Horel | |
| 2012-11-08 | Add date formatting filter | Thibaut Horel | |
| 2012-11-08 | Also use rst for news content | Thibaut Horel | |
| 2012-11-07 | Add rst parsing for comments. Slightly crude for now, but I need to head out ↵ | Thibaut Horel | |
| to the movies | |||
| 2012-11-07 | Add comments feature: show list, add | Thibaut Horel | |
| 2012-11-07 | Remove useless function, time to add mooorre features | Thibaut Horel | |
| 2012-11-07 | Add logout | Thibaut Horel | |
| 2012-11-07 | Add basic news feature: list, show, add | Thibaut Horel | |
| 2012-11-07 | Code cleanup. Login is now functional. | Thibaut Horel | |
| There is a script createdb.py to create the db from the schema.sql file | |||
| 2012-11-05 | starting to hook things up | Guillaume Horel | |
