follower46 / ashaw-notes Goto Github PK

In the main.py all the results for a given query are displayed immediately.
We need to limit the resultset to only 100 lines with an option to view more (show newest notes first, with a "view more" button at the top).

We should also have a "total notes" counter in the filter box which will show how many notes were available.

Currently there is a 250-300ms delay on Redis key filtering.
Fix it.

Use some natural language based python package to allow notes to be filtered by a specific date.
Date ranges can be added later.

This addition should be a plugin not hard-coded into the connectors (although the connectors do have to be updated to use the property on the searchrequest class)

Ugh, I shouldn't have had the connectors be modules only.
The globals were the first red flag that it was a wrong-headed approach.

Refactor them so that they are classes (porting over the unit tests).

Currently the (very basic) GUI is built using QT.
Because the dependencies are such a pain we should investigate using TK instead.

The current tests directory is poorly structured, the scripts tests should be in their own subdirectory instead of being in the root

Convert the migration and quicknote scripts to use https://python-packaging.readthedocs.io/en/latest/command-line-scripts.html

This will remove the need for

if __name__ == '__main__':

and allow for 100% unit test coverage.

Make it run on Android

This will most likely be a Redis only feature.
Redis supports pub-sub events.

Add support so that when a new note is added an event is broadcast to the UI clients forcing a refresh on the UI's.

This will also be needed for edits and deletes.

Unlike local notes, Redis-based notes can come from multiple machines.
Because of this, it would be useful to be able to store what client was used to insert a specific note.

This will require that we change how deletes work.

Currently the note is pulled from redis and the keys are generated off of that key. Because this is note meta-data not stored in the note, it will require that we start storing in redis a set of all the keys related to a specific key so we can clean up those keys on delete.

Currently notes assume unique timestamps for notes.
When a new note is added:

1. Check if a note already exists with that timestamp
2. If that timestamp is unique, insert
3. If a note with that timestamp exists, add 1 microsecond to the insert time and start over

Hard to fully know what these require since none have any description set :P

Currently "find_redis_notes" is pretty messy.
This should be cleaned up (refactored) so that it can be extended more easily.
Specifically, adding in date filtering is a pain in the method's current state.