olmps / memo_editor Goto Github PK

Currently, the app only stores collections in-memory.

Add the option to manage multiple collections simultaneously, instead of just a single one.

Allow the editor to remove, export and import multiple collections in a single operation.

Not necessarily a workflow for this v1, but it must support releasing for macOS and web.

Currently, the editor doesn't allow specific-code highlight, do not allow uploading images and has an overall poor text-editing experience, due to some implementation decisions in flutter-quill.

We should look into these issues and, if they prove to be big enough changes, probably fork the flutter-quill and start from there. Creating a brand new project for this is also a valid possibility, given that the code in flutter-quill do not contain any unit test and has almost no documentation, making it hard to update things there.

As it stands today, the tool is functional but lack a lot on the user experience, as it was made to simply fill an internal problem to deal with collection-generation within the memo project.

We need to make sure that memo_editor also fits the same quality that memo brings to their users, as we eventually plan to release an alpha version that anyone can use to customize its collections and memos, suggest additions to the core memo repository, etcetera.

This also involves adding a bunch of other functionalities that are missing today, like validating the collection properties text fields, responsive layout (with experience-adjusted features for each "major" device size), connecting the existing collections in the memo repository and "bridge" the changes-suggestion in the core repository (using this editor tool), and a lot of other things.

This also brings us one important question (that we are currently evaluating): should we actually merge this editor into the main tool (/memo repository) and diminish the difficulty for new entrants to join the memo ecosystem and start contributing?