-
Notifications
You must be signed in to change notification settings - Fork 137
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
implement in-app-wiki #862
Conversation
Edit: found out! |
@stefan-niedermann How would you like to be attributed for your app? Is this okay? |
I think we could easily put this with all the other outstanding features into a Version 5.0.0. It's a nice round number, and there was quite a bit of work done to justify it 👍 |
Hey @newhinton : Thanks for your work on this! The screenshots are looking very well so far. Since you are still actively working on this PR, I wait with a final review. But it's going in a good direction! But I have one request: could you please set this (and other not yet finished) PRs to "draft"? It would be very helpful to have a direct insight if a PR is ready for review or not. Regarding the version name: I'm using the milestone planing. The plan was to release version 4.4.0 several weeks ago. It should have contained all the stuff that change the public API (attachments, custom file extension) -- but the last thing is still left, since I've not found the time :-( . After that, the plan was to release 4.5.0 with all the UI stuff (three-column layout, help-screen, toolbar etc.). Version 5.0.0 was planned with the switch to the Nextcloud Text editor, but that is currently halted due to the open issues regarding the Text app. |
Yes i will convert everything to drafts soon. However, this is not so drafty-anymore, it is mostly done and we need to discuss content. Regarding 5.0.0: Since we more or less implement everything text does (except concurrent editing), do we need that issue at all? It does not seem that the issues will be fixed anytime soon, if at all, and since we have a very well working setup with the new additions, i think we can do without it until something major changes. |
@newhinton Is there anything to be done here? Could you please rebase the branch when this is ready to review? |
Yes and no :D I think the technical side is done. There was the question wether or not to replace the initial welcome-page with a popup, but this can be done later. However, we should check two things: But besides that, i think its good to go. (When i will rebase this, i'll also check if there are still console errors) |
Any veto @stefan-niedermann @phedlund ?
I'll do a deeper review. |
src/components/AppHelp.vue
Outdated
{ shortcut: t('notes', 'CTRL+Alt+L'), action: t('notes', 'kes the current line a list element with a number') }, | ||
{ shortcut: t('notes', 'SHIFT+CTRL+H'), action: t('notes', 'toggleHeadingBigger') }, | ||
{ shortcut: t('notes', 'F9'), action: t('notes', 'toggleSideBySide') }, | ||
{ shortcut: t('notes', 'F11'), action: t('notes', 'Make the note fullscreen') }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. This is not the same like the fullscreen action in the three-dots menu. Hence, remove this entry?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it is? In the end the tree dot menu calls "requestFullscreen()" on the dom, which acts the exact same way as F11.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least not in my Firefox: pressing F11 goes into fullscreen but all the Nextcloud frame and app navigation is still visible. Using the fullscreen option shows the note only without any distracting frame.
src/components/Welcome.vue
Outdated
createNote('') | ||
.then(note => { | ||
const query = { new: getDefaultSampleNote() } | ||
this.$router.push({ | ||
name: 'note', | ||
params: { noteId: note.id.toString() }, | ||
query, | ||
}) | ||
}) | ||
.catch(() => { | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like this approach, because it generates a very long URI. Instead, you should add a second parameter to createNote
that takes the content and directly sends it to the server in the same request that creates the new note.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the query, this is how the sidebar is doing it. (If i remember correctly, that's where i found the code in the first place. I just extracted the query so that i could add content more cleanly.
Should we change that in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidebar? What do you mean?
But yes, please do not put a whole note in a query parameter. :-)
src/components/Note.vue
Outdated
|
||
const newContent = this.$route.query.new | ||
if (this.isNewNote && (newContent !== '' && newContent != null)) { | ||
this.note.content = newContent | ||
this.onManualSave() | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like this approach, because it generates a very long URI. Instead, you should add a second parameter to createNote
that takes the content and directly sends it to the server in the same request that creates the new note.
That's fine, thanks 👍
Nope 🙂 |
@korelstar I have implemented a lot of the changes you mentioned. However, do we have any tips we want to add? Otherwise i need to remove that section from the help. |
Fixed it. |
cecf6c8
to
6c726c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@korelstar I have implemented a lot of the changes you mentioned.
However, do we have any tips we want to add? Otherwise i need to remove that section from the help.
Thanks so far! I think it can be removed, for now. Would you mind doing a rebase (due to #928)?
src/components/Welcome.vue
Outdated
<button class="button-icon-add icon-add" @click="onNewNote"> | ||
{{ t('notes', 'Create a sample note with markdown') }} | ||
</button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use NcButton
from @nextcloud/vue
instead
src/components/AppHelp.vue
Outdated
<button class="button-icon-add icon-add" @click="onNewNote"> | ||
{{ t('notes', 'Create a sample note with markdown') }} | ||
</button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use NcButton
from @nextcloud/vue
instead
@korelstar So i did rebase, but it did not want to push. For now i have not force pushed my code, but created a second branch. You can check it here: https://github.com/nextcloud/notes/tree/feature/noid/help2 If it works for you, i can force push later.
|
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Update Text Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
fix padding for help Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
Signed-off-by: Felix Nüsse <[email protected]>
e9e47d2
to
e62eecf
Compare
Hey @newhinton ! I did a rebase of |
Signed-off-by: korelstar <[email protected]>
@korelstar It looks good to me! Thanks for helping out |
Signed-off-by: Felix Nüsse [email protected]
closes #287 and closes #793
Todo:
Discussion: