[ Streams ] : future development

[saqimtiaz]

@arunnbabu81

@saqimtiaz I think you should add back the double click editor to exit feature as a configurable option. I think it would be better to have that feature than not have it. One thing which went against double click editor to exit was that it may conflict with text selection using double click, but text selection can be done by Drag selection or keyboard shortcuts also. Also the number of times we may need double click to exit editing will be far more than number of times we may need double click to select text .

I am afraid this will not be introduced. There were several usability concerns with it and having extra configurable options incurs an overhead in terms of code maintenance and performance.

@arunnbabu81

Swipe to indent/unindent could also be brought back to the plug in with visual feedback. I had shared my suggestion in github sometime back. If the swipe is of sufficient distance, indent or unindent is triggered. If the swipe is shorter, just like in WhatsApp for iOS , show options like context menu, indent/unindent etc. and select which ever is needed.

I will consider this if I find the time and motivation to work on new features for Streams, though my focus is unlikely to be on mobile UX.

[arunnbabu81]

Any possibility of monaco editor support for streams in the future

[saqimtiaz]

If support for any more editors is to be added, we would need to drop the features that involve knowing where the caret is in the editor.

For example:

• backspace at the beginning of a node to merge with the previous node
• splitting a node at the caret on enter, etc

None of the editors provide the necessary information for these features to work, and adding these features to them manually and maintaining that isn’t sustainable. Truth be told, I regret adding support for codemirror. It has made the codebase more brittle and harder to maintain.

[saqimtiaz]

I have moved speculative discussion on new ideas that I am exploring to a separate post, as the audience for that might be smaller than those interested in support and news of more concrete development:

Streams: exploring ideas for new features

I had a chance to revisit Streams development recently as it dovetailed nicely with other work. Here are some of the improvements that I am currently exploring: expand all / collapse all affordances for the children nodes of a stream further simplification of the templates and DOM structure improvements in performance and drag and drop behaviour the possibility to select node(s) with the mouse and copy and paste them between streams. the above will entail coming up with a string representa…