-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regarding the Notes app #6
Comments
I think Stefan would be glad to be able to only focus on the android app. Also, the note app was being rewritten to vue apparently: https://github.com/nextcloud/notes/tree/vue The two apps kinda overlap, but maybe the current note app offers more features than just a markdown editor? 🤔 |
Personally I am using notes app on server with notes (by stefan) on Android and qOwnNotes on desktop. As far as I know/understand notes are only text files (with markdown) stored in /Notes, but they can (somehow) have categories. While text editor and notes have something in common (text editing), both are for me from UI/UX two totally different things:
So all in all, I would see (of course only from my personal view) that notes is still needed, but can benefit maybe from collaborative editing. |
The notes app also provides a rest api for the notes (e.g. with category management) which is used by the android app.
Stefan was in the 17 meeting as well, he is aware of that we work on "something" but yes we should talk with the other notes maintainers as well I think. I would actually just go for having text as a file editor. Since the notes app also works on files, it shouldn't be to hard to integrate out new collaborative editing view into the notes app as well. So we could keep Notes as an interface to the notes folder with the sidebar showing all notes with categories. |
Yeah, good points, also about the rewrite. I think we should just contact both korelstar and stefan-niedermann ahead of time about this. Some more:
|
@tobiasKaminsky regarding your points, that’s the current state, but I’m not sure if people really make that distinction. Apple Notes for example is both things – a simple personal notes app, but you can also share and collaborate. It’s very nicely integrated. |
(I’m just mainly worried about having X apps for the same thing again, kind of like with Circles / Contacts / users and such. :) It takes away focus and dev resources, and in the real world people don’t care about these small differences and won’t find all the different apps that we have. It needs to just work.) Maybe also cc @MorrisJobke @rullzer regarding general direction. |
@jancborchardt What a lot of apps in #2 (Apple Notes, Evernote, Slite) but also other note-taking software like OneNote or Google Notes have in common is that they don't use a file based approach but have a simple interface for navigating though your notes, just like how we do it with the Notes app. I would actually say we should integrate the editor properly into the notes app, so this is our basic note taking system and the ability to edit files from the files view is the "bonus" feature. 😉 |
Ok, sounds good! But let’s properly communicate that with the Notes devs? |
So, what is the status here? :) |
Yes, apart from Stefans concerns that his Notes app for android would not have any usecase anymore (which I don't see that way) they liked the idea. Once I have finished the basic files app integration, I'll create a branch that hooks our new editor into the Notes app, as a replacement for their markdown editor. |
It should be possible to handle this in the notes app, once I find some time to look into, so let's keep this without a milestone for now. |
👍 Absolutely don’t see it that way either. I use the Notes Android app a lot, and a big part of it is that it’s super snappy and works offline. Nothing that we will be able to do soon (ref Future plans for mobile #1) – and actually Stefan’s app is a great "Nextcloud Text" Android app already, and we can improve upon it too. |
Also cc @korelstar @stefan-niedermann @nextcloud/notes here. :) |
Yippie! 🎉 I just created a (pinned) issue in the notes repository in order to provide some information for users and developers of the notes app: nextcloud/notes#331 I'm looking forward for the first integration attempt by @juliushaertl (see #6 (comment)). As soon as I find some time, I will have a look at the code of Text. But I doubt that it will be in the next weeks. |
Perhaps @pbek has some thoughts on this as the maintainer of Qownnotes. Cheers. |
I also think Notes and Text are overlapping but not the same, like QOwnNotes (that is a note taking app) and a Markdown editor. Notes and QOwnNotes should making using a lot of markdown files to take notes easier, I'm not sure Text does that already or should even do that... |
The idea is more to integrate our new editor into notes, so notes is taking care of managing notes and providing a sane interface, which is more suitable for notes than a file list while you get the rich editing possibilities of the text app. |
Sounds like a good idea to me 😃 |
I agree that the concepts of text and notes might appear strongly overlapping, especially given the ongoing convergence of software components. However, it might be valuable to consider that comparing the two terms, as they have evolved recently, might be mixing metaphors. Text a type of asset, in contrast to images, audio, and so on; whereas notes has come to mean a way of managing assets, that favors an informal, ad-hoc organization. A text document might be note, or might be a book that takes years to write. A note might be a photograph, or an audio recording, or a photograph with a text snippet attached, or any combination of such elements. Notes versus files being one distinction, and asset type being another, appear to be orthogonal considerations. A notes application should ideally handle a variety of asset types, but itself should focus on the appropriate organizational metaphors. As such, I agree largely with the consensus, but I would emphasize the organizational approaches provided by a notes application might equally be available for other asset types. Aside from being able to handle a variety of media types, a notes application that excels is one that helps the user store assets quickly and without planning, and also helps the user to find an asset later, despite lack of conscientious organizational practices. For such purposes, a metadata-based view that emphasizes fields like creation date and user-supplied tags is more helpful than a file-based view, regardless of what might be the actual backend storage means. A simple example that gives me an idea of how useful a notes application is for my needs is to ask both of the following questions:
This freedom marks a strong contrast to a file system, in which every asset is identified by at least one unique path. In a notes context, forcing me to choose a unique title at the time I create a note takes time and focus away from my other responsibilities. |
Just to throw this out there, I create OwnNote back in the day which got hugely popular (still a lot of users using it in Nextcloud, but if this integration occurs they will likely tail off. One of the most commonly said things in issues was "make sure to keep both the file view and interface view." Looking forward to the progress here as I was just about to jump in and see if I could integrate the two until I saw this conversation ;) |
Is there a branch this is being developed against? |
Sorry for the flood of comments, but as I've just gone through a little evaluation of using the existing Could notes just be handled with a slightly altered view with tags?
What about mobile? |
A good idea in general, it would seem, but apparently already planned (see nextcloud/viewer#15).
Then would the Viewer have a separate interface for notes? Or would a similar interface be provided by an entirely distinct component? The specific actions and information desired for a file view may be different than for a notes view. |
@brainchild0 I'm guessing what I'm envisioning is allowing existing tags to be categories, and simplifying the layout. For instance, if the "Notes" app altered the view (granted, I think having the left nav "Tags" option be a display/filter like in the "after" shot is a good idea regardless). For instance... Before (Standard files view of Notes folder): After (Notes "app" view of Notes folder): Differences:
|
I think this discussion has mainly shifted to the notes app. The consensus here seems to have been that it would be nice to reuse text as the editor in notes. For now I will close this issue. I'm happy to reconsider once we have a solution to #593 and maybe even a way to switch between wysiwyg and md source editing. Feel free to reopen if you think we should continue this discussion. |
It appears the sense of the idea is that in each context, the user is limited to a subset of total possible features. Would the best solution not rather be simply one in which the same editing environment is shared by both contexts, with the user permitted to select which editing mode, and other preferences? |
@brainchild0 I agree to your point. I hope we will get to a point where you can switch seamlessly between md and wysiwyg editing, show both at the same time and still collaborate. At that point it would be great to use the same editor in notes and files. Right now i think we are targeting different audiences and there was (something like) a decision in notes to not use text as the editor. I hope the approaches will converge in the long run. |
@max-nextcloud, In principle there is nothing to prevent separate teams from maintaining distinct notes apps, if the contributors are available, in advance of a full convergence. For example, the wysiwyg interface could be applied to a new notes app, and then later the same interface could be extended to support mode switching, such as to make the other app obsolete. I know this approach depends on sufficient interest for making the contributions. |
@brainchild0 we also have the collectives app which can be used for taking notes and is based on text for the editing: https://apps.nextcloud.com/apps/collectives . So if people want wysiwyg with a knowledge management interface rather than files that might be an option. |
@max-nextcloud, The intention of my suggestion was separate front ends that would converge with the same files store. |
Editing notes both in the database and on the filesystem would be great in
relation to collectives
…On Tue, Nov 8, 2022, 7:48 AM brainchild0 ***@***.***> wrote:
@max-nextcloud <https://github.com/max-nextcloud>, The intention of my
suggestion was separate front ends that would converge with the same files
store.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANUKZVHC2EZPFP7K5DH6LTWHJY6NANCNFSM4HG3R25A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Now the main thing we are doing with the Text app is replacing files_texteditor and offer a lightweight collaborative document alternative.
But we also overlap a lot with the simple Notes app. Maybe we should talk with the contributors (korelstar and stefan-niedermann) there ahead of time since it seems that when the Text app is fully fleshed out, Notes is a bit redundant. Since the design goal with Notes from the beginning was simplicity, then if the Text app is using the Viewer then it’s even more simple and focused as it doesn’t even show a left sidebar.
Or what we could keep in mind for Text and / or viewer is possibly have a left list on the side which could be expanded to show other documents in the folder for quick switching?
Not entirely sure here, what do you think @juliushaertl @skjnldsv?
The text was updated successfully, but these errors were encountered: