jchampemont / notedown Goto Github PK

When a user starts editting a note, it should be locked.

When editting a note, the user's browser should send a heartbeat every 10 seconds.

If a note is locked and last heartbeat for this note was received more than 20 seconds ago, the note is unlocked.

When a note is locked, user should not be able to edit it.

UI should display who locked the note.

Compress NoteEvent history:
Using a configurable threshold (property ?), when there is more than X NoteEvent for a Note, oldest NoteEvent up to X should be compressed into a single NoteEvent, in order to gain space in DB.

Allow user to share folders between each other with either read access, read/write access or full control. Full control allows to delete/rename a folder.

Shared folders should be received in a special folder named "shared with me". Users can put them anywhere in their folders.

Individual notes permission is prioritary compared to folder permission.

Add the ability to add one or more images to a note by uploading them.

Allow user to share notes between each other with either read access, read/write access or full control. Full control allows to delete/rename a note.

Shared notes should be received in a special folder named "shared with me". Users can put them anywhere in their folders.

Using the heartbeat mecanism implemented in #16, user should be warned with a smal modal when is session is about to expire. (35s before). A 30s countdown is shown.

There is a button on this small modal to allow session renewal.

When not clicked in time, the button become disabled, and a message states that the session is effectively expired.

The first user created should be admin and have the possibility to add any number of users to the application.

• Ability to add one or more tag to a note from the edition form
  (this plugin seems great : http://aehlke.github.io/tag-it/examples.html)
• Ability to find notes by tag from the notes' list page

Users should be able to upload a small image as their avatar.

This avatar is shown in the UI wherever display name is shown. (Eg. when a note is locked).

Affected version: v0.1.0-RC

Steps to reproduce:

• run application (dev mode);
• create account;
• go to user settings and change language;
• save.

java.lang.NullPointerException: null
        at com.jeanchampemont.notedown.web.SettingsController.updateLang(SettingsController.java:112)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

In my case, default language is French so I tried to switch to English.

Instead of locking (#16), manage conflicts in concurrent saving. Exemple:

• Note is at version 36
• I open 2 tabs to edit the note
• I'm saving version 37, 38, 39 from the first tab. First tab is at version 39.
• Second tab is still at version 36.
• I'm saving from the second tab. There is a conflict as the note has been changed in the mean time.
  • Merge changes if possible, reload the note, second tab is at version 40
  • When changes can't be merged, mark conflicted changes into the file. (See below)

    <<<<<<<<<<<<<<<<<<< Theirs
    ....
    =====================
    ....
    >>>>>>>>>>>>>>>>>>> Mine

Add the ability to create folders, and move notes between folders, arbitrary depth.

Linked to #3.

When trying to save from a version which is not anymore available in history, the user should be warned and asked to reload the page.

Implement a search engine (using elastic search ?)