You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notebook has potential to be used for operator logs if it has a fully functional html or otherwise text editor. Most of the features needed are already there, but it needs to accept at least the following features:
Basic text editing features (font/headers/lists/bullets)
Basic image features (not just from snapshots)
Basic tabling features.
There are some other intricacies that would be nice such as the user that filed the note, but I believe that's outside of the MCT scope.
The text was updated successfully, but these errors were encountered:
Definitely agree on the requested features as above. @mudinthewater Ideas, thoughts on the following?
Is there currently an issue with newlines? In that, if you paste something with newline chars, the entry ignores them? If so, we should fix.
Markdown with an embedded simple GUI (like the one here in GitHub perhaps?) seems like a good starting point, and there are 3rd party plugins we might leverage to support this. If this sounds like a good plan, any in particular that you like?
Imagery becomes a slightly more complex issue, mainly around storage. This is a general issue as well; using images in Display Layouts is problematic as we have no ability for users to upload and store images; they must use images already on a server that doesn't have issues with cross-domain requests.
We're planning to change the way the Enter key currently works because the current approach confused 100% of our testers in a recent user test. Rather than adding a newline/return, it will exit entry mode and save the entry, same as tabbing out. Users will be able to add line returns with Crtl + Enter.
I'll retest but I was attempting to put a list of commands exected to try to get a fake pass log in there but after saving it, the newlines appeared to have been disappeared.
I'm not picky about implementation - my vote is whichever is easiest!
CORs is such a pain - I'm assuming I can work around this by mucking around the JSON in couch like I usually do.
Notebook has potential to be used for operator logs if it has a fully functional html or otherwise text editor. Most of the features needed are already there, but it needs to accept at least the following features:
There are some other intricacies that would be nice such as the user that filed the note, but I believe that's outside of the MCT scope.
The text was updated successfully, but these errors were encountered: