From 5e6f3d96b17a6d87952d5d4a0373d4b3e64a1e77 Mon Sep 17 00:00:00 2001 From: Ethan Dalool Date: Sat, 13 Jan 2018 20:06:53 -0800 Subject: [PATCH] Remove localstorage from the todo list because that's done. --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 294e43f..6b66b3d 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,6 @@ If you are interested in helping, please raise an issue before making any pull r - Improve the appearance of album page. Too many section headers and the "Create album" interface should allow giving a title immediately. - When users have '%' or '#', etc. in their username, it is difficult to access their /user/ URL. I would prefer to fix it without simply blacklisting those characters. - Currently, the Jinja templates are having a tangling influence on the backend objects, because Jinja cannot import my other modules like bytestring, but it can access the methods of the objects I pass into the template. As a result, the objects have excess helper methods. Consider making them into Jinja filters instead. Which is also kind of ugly but will move that pollution out of the backend at least. -- Use browser localstorage to act as a clipboard for holding photos, so that you can select them on one tab and move them into an album on another, etc. - Perhaps instead of actually deleting objects, they should just have a `deleted` flag, to make easy restoration possible. Also consider regrouping the children of restored Groupables if those children haven't already been reassigned somewhere else. - Add a new table to store permanent history of add/remove of tags on photos, so that accidents or trolling can be reversed. - Currently, the photo clipboard only stores IDs and therefore when we construct the clipboard tray elements we cannot provide more rich information like filename, the user is only presented with a list of IDs which they probably don't care about. Should the localstorage cache some other more user-friendly information?