Skip to content
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

Include preview in entry editor #4976

Closed
wants to merge 444 commits into from
Closed

Include preview in entry editor #4976

wants to merge 444 commits into from

Conversation

tobiasdiez
Copy link
Member

@tobiasdiez tobiasdiez commented May 17, 2019

First shot at #2115. Current look:
image

@JabRef/developers @mlep @grimes2
Should I continue along this path, or do we need a different solution?

Related: #4813 and #4808


  • Change in CHANGELOG.md described
  • Tests created for changes
  • Manually tested changed features in running JabRef
  • Screenshots added in PR description (for bigger UI changes)
  • Ensured that the git commit message is a good one
  • Check documentation status (Issue created for outdated help page at help.jabref.org?)

@tobiasdiez tobiasdiez changed the title Include preview in entry editor [WIP] Include preview in entry editor May 17, 2019
@tobiasdiez
Copy link
Member Author

@JabRef/developers I would like to have your opinions about this solution before doing the major code changes necessary for a complete integration.

@matthiasgeiger
Copy link
Member

@tobiasdiez I'm a bit indifferent.
First: personally I do not really use the preview function at all. I'm using standard natbib or whatever styles in LaTeX and therefore know how the entries will be looking like (or I'm not really interested in the exact way they are looking).

Therefore, I'm not sure whether I like it that much screenspace is "wasted" in the entry editor for the required fields tabs. However, I think for persons who are interested in the preview this might be even better than the older style.

So, for me it is okay to have in the entry editor - but it should still be possible to disable/hide the preview in case you are not interested in the information shown there.

victorjof and others added 26 commits July 4, 2019 18:06
Abbreviates  isDateTag() and getDatePriority()
…Contextmenu

* upstream/master: (21 commits)
  Bump junit-vintage-engine from 5.4.2 to 5.5.0
  Bump log4j-api from 2.11.2 to 2.12.0
  Bump junit-platform-launcher from 1.4.2 to 1.5.0
  Bump log4j-core from 2.11.2 to 2.12.0
  Bump log4j-slf4j18-impl from 2.11.2 to 2.12.0
  Bump log4j-jul from 2.11.2 to 2.12.0
  Bump junit-jupiter from 5.4.2 to 5.5.0
  Bump com.github.johnrengelman.shadow from 5.0.0 to 5.1.0
  Bump log4j-jcl from 2.11.2 to 2.12.0
  Bump fontbox from 2.0.15 to 2.0.16 (#5080)
  Bump pdfbox from 2.0.15 to 2.0.16 (#5081)
  Bump xmpbox from 2.0.15 to 2.0.16 (#5082)
  Update FUNDING.yml
  Delete autoapproval.yml
  Bump com.install4j.gradle from 7.0.11 to 7.0.12 (#5077)
  Configure autoapproval plugin for dependabot
  Bump xmlunit-matchers from 2.6.2 to 2.6.3 (#5074)
  Bump checkstyle from 8.21 to 8.22 (#5072)
  Bump xmlunit-core from 2.6.2 to 2.6.3 (#5073)
  Refactor for loop to stream in groupTree Close version socket
  ...
Add copy linked files action to contextmneu in general tab
Bumps [mockito-core](https://github.com/mockito/mockito) from 2.28.2 to 3.0.0.
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](mockito/mockito@v2.28.2...v3.0.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
koppor and others added 13 commits August 24, 2019 10:31
Allow negation (`!`, NOT operator) in \\begin{...} conditionals
* Fix lookup entry types in enums

Make master work again!!!

* fix checkstyle

* fix checkstyle and fix type comparison to lower case

* simplify remove generics
Co-Authored-By: Oliver Kopp <kopp.dev@gmail.com>
If we create journal abbrev files via the JabRef, they are saved in UTF-8.
So it makes sense to use this as default encoding. Also see #5133.
Co-authored-by: Linus Dietz <linus@lynyus.de>
Co-authored-by: Stefan Kolb <stefan-kolb@web.de>
@stefan-kolb stefan-kolb changed the title [WIP] Include preview in entry editor Include preview in entry editor Aug 24, 2019
@LinusDietz
Copy link
Member

Superseded by #5218

@AEgit
Copy link

AEgit commented Aug 25, 2019

I know this is a big thing to ask but can you please revert this change and/or make it just optional. I have just had a look at JabRef 5.0-alpha--snapshot--2019-08-25--master--0c342bdc7 to test #4808 (comment) just to realise that the entry preview is no longer automatically shown at all.

I am heavily reliant on using the entry preview. I often tend to quickly go through different entries and the entry preview gives me a quick overview of the entry. Now I always have to open the entry editor just to see the preview. My feeling is, that this change was introduced by people who actually do not even use the entry preview at all (see also comment here: #4976 (comment)). This new behaviour is completely different from the old JabRef behaviour and from similar reference managers (e.g., Mendeley).
So, unless you can suggest a change in the way I should use JabRef now (maybe I just don't understand, how the entry preview is now supposed to be used) while keeping my user scenario - i. e. quickly cycle through entries and always get a quick summary of the respective entry - I would ask to drop this change or make it optional.

@LinusDietz
Copy link
Member

Hi @AEgit. I understand your concern, and we should definitely not leave it as it is. If we would keep the entry editor open all the time (unless the user explicitly closes it), would that solve your problem?

@AEgit
Copy link

AEgit commented Aug 25, 2019

Hmmm, that might be a solution, although it also means, that it will use up more of the available screen space. To be honest, I am not a big fan of that - I think the old behaviour was just fine as it was implemented (indeed, other reference managers did it also old way JabRef was doing it). Is there any reason, why this change was introduced at all? I personally don't see the user case (but maybe that is just me).

@tobiasdiez tobiasdiez deleted the includePreview branch August 25, 2019 12:30
@LinusDietz
Copy link
Member

Well, we had our reasons.

  • You can start editing entries quicker, because the entry editor is already open (this should be fixed as mentioned above)
  • You immediately see the effect of editing something in the entry preview while you are typing. This is especially important for novice users.
  • Screen resolutions have become bigger since 2003 (?) when the entry editor and the entry preview were first introduced. Thus, we have the space to display both side by side.

@AEgit
Copy link

AEgit commented Aug 25, 2019

Hmm, ok. Regarding the points:

  1. So far the issue with the entry editor does not seem to be (fully?) resolved. Furthermore, note the problems with the focus (searching terms and then suddenly making changes in the entry editor) makes this change currently dangerous. But I see, what is intended here.
  2. Ok, that makes sense. But then, it would probably be necessary to have a single entry tab (not split among different tabs) - at least, that is how Mendeley is doing this. Personally, I liked it the way JabRef had implemented things before. I am not so sure, whether people are happy with the current solution, i. e. entry preview + open editor (but with multiple entry tabs).
  3. Not so sure about the space. Currently using a 1920x1080 screen, with JabRef using up half of the screen. There, it is definitely too small. At work I have a 4k screen, where JabRef is using up a quarter of the screen (= +- JabRef in full screen on a 1920x1080 screen). I don't think JabRef is supposed to be used in full screen mode. I don't think many people have larger screens (especially when you include laptop users).

@johann-petrak
Copy link

I would very much like a simple and one-click way to disable showing the citation preview. I spent quite some time looking for it when I got the update since I could not believe that this change was introduced without an option to switch off the preview that takes away space and cpu cycles for keeping it updated.

@JabRef JabRef locked and limited conversation to collaborators Aug 26, 2019
@Siedlerchr
Copy link
Member

As this is a merged PR I moved the conversation feedback to a new issue to keep the overview.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet