Find a clean way to reuse code from text app

[mejo-]

In GitLab by @azul on May 18, 2020, 15:59

• find a cleaner solution than importing the CSS from text app with relative links (@import './../../apps/text/css/prosemirror';)
• avoid copying all the css
• allow for defining our own Component that uses EditorWrapper.
• maybe use https://github.com/juliushaertl/nextcloud-text

Missing from !17

[mejo-]

According to Julius, the nextcloud-text library is already usable to some degree. It's not released yet, but could already be used with npm link to local directory.

https://nextcloud-text.netlify.app/markdown.html

[mejo-]

marked this issue as related to #39

[mejo-]

marked this issue as related to #83

[mejo-]

marked this issue as related to #93

[mejo-]

In GitLab by @azul on May 10, 2021, 08:23

removed the relation with #93

[mejo-]

We've made a huge step forward here: starting with release 1.1.0, we use the new @nextcloud/text NPM package for the view mode. 🚀

[mejo-]

Our plan is to expose an editor component as a global object in Text (similar to OC) and use that object in Collectives. Switching between view and edit mode will happen completely in Text.

Short-term, we'll copy the logic that's currently implemented in Collectives into the new exposed Text component: loading RichTextReader with the page content from webdav in the front (for fast loading experience) and loading the full-fledged Editor with page content from syncService in the back.

Mid-term, we might improve the performance in Text and get rid of having two seperate components (RichTextReader and Editor) there.

[juliusknorr]

nextcloud/text#3615 would be the upstream pull request for exposing text through an API