-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Suggestions for improving the entry preview #5244
Comments
Originally posted by @johann-petrak in #4976 (comment) |
To add to this issue, I copy over also the other message I had written there.
Originally posted by @AEgit in #4976 (comment) |
JabRef 5.0-alpha--snapshot--2019-08-25--master--0c342bdc7 Ok, so I have played around a little bit with the new entry preview, and I can now definitely say, that I would like to see the old behaviour re-instated or alternatively to make the new behaviour optional. First of all, it is no longer possible to quickly cycle through different entries and get a quick idea what they are about. They always have to be opened to see the entry preview (I have already mentioned this in previous posts). Second, there was the suggestion to keep the entry editor always open so that it would be possible again to cycle through all the entries while seeing the entry preview (see #4976 (comment)). I am now confident that this is not a good solution for the problem, since there is not enough space for both the entry editor AND the entry preview, when the group panel is opened as well. I provide a picture to give you an idea of the problem. Note, that JabRef here is using half (!) of the screen on a 24'' monitor with a resolution of 1920x1080. This definitely does not do a good job at the moment. I suggest to revert the changes of #4976 (comment) or to come up with a better solution. EDIT: My impression is that many of the current UI changes, especially those focused on the entry preview have been made without having the group panel open. If I close the group panel (which I would never do for my actual work, since the groups are essential), there seem to be fewer issues with the UI, i. e. often I now have enough space. But when the groups panel is open, most of the time, the UI looks wierd and horizontal space is missing (also because new elements use up more space, than they would need to). For further changes to the UI I would therefore recommend to always have the groups panel open as well. |
I don't know whether this has been mentioned already, but the two screenshots posted in this thread emphasise another issue with the current entry editor. It DOES NOT do an automatic return, which leads to entry content disappearing in the UI, if the content is too long for the entry row (see for example the author field in the post above: #5244 (comment)). This is especially a problem with the newly introduced entry preview that is now part of the entry editor. |
Ah you mean wrapping text. |
Hmm, yes - I am just comparing what the current development version does VS. JabRef 3.8.2 (which I am still using for actual work). |
Adds the entry preview as a tab. Fixes #5244. Plus a bit of refactoring
* Add option to display entry preview as tab in entry editor Adds the entry preview as a tab. Fixes #5244. Plus a bit of refactoring * Fix checkstyle * Fix checkstyle part 2
In the latest development version, you have now the option to show the preview as a tab in the entry editor (Preferences > Entry preview). Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version. |
JabRef 5.0.0-dev--2019-10-17----e81d58c51 Very nice, this is a big step forward. I can confirm that the entry preview as a separate tab works as expected. There are some smaller issues with the current approach, which have been reported here but for which it probably better to open separate issues (I shall do that now). |
show the preview as a tab: You have to restart JabRef after enabling this option so it becomes effective. Is that a bug? |
@sebastian-boecker : See here #5464 |
To prevent further commenting on the pull request I have opened a new issue:
Originally posted by @AEgit in #4976 (comment)
The text was updated successfully, but these errors were encountered: