-
Notifications
You must be signed in to change notification settings - Fork 11
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
BibTeX preview window #181
Comments
Looks good. Under the search we have the option to include more fields for matching so I'm thinking a checkbox display might be better with the search being applied to each checked item. The results will need pagination and the selected file will open the BibTex viewer. The viewer will display the citation and its LaTeX form at the top (or 'Citation incomplete') and only the fields relevant to the type. Thus, until the type is filled in, no fields appear. When it is filled in, the relevant type fields are presented. The need for nice interaction is pushing me toward doing some javascript so I've built a demo page using AngularJS for you to review: https://staging.crossculturalconsult.com/documents/bibtex/ As I've updated some of the css and javascript to achieve these effects, you will need to clear your browser caches to be sure of seeing it as it is intended. You can play around with it. It is just using some dummy data to show off the capabilities of Angular for making these sorts of interaction more effective. This style of working is somewhat more labour intensive because I'll need to build an API on the server to supply the data as json to javascript utilities that present parts of the page. Then I need to write the Javascript... I'm getting a bit happier with writing Javascript and I cannot come close to matching the UX with Python and html alone. The angular stuff is fun. Be sure to have a play with the searching and changing the data values. Notice the instant updates and the presentation of the related data as soon as you make changes. AngularJS uses 'double binding' so that changes are reflected across the page while you make them. In practice the searching will not be able to do this because it will require the Javascript to pull down substantial numbers of documents and paginate them but it will still work faster than fetching entire pages every time. What do you think? |
Hi, Paul. Overall this sounds great. Thanks for taking on the JavaScript work. Please let me know if we can support you. I am still open to bringing you onto the CCCS elance account to allow you to try to source some help. I have some minor feedback with regard to presentation. I'm attaching an image to help to clarify.
Let's talk over any questions. Thanks! PLEASE NOTE In the image above, |
this is an idea for an auto-reporting feature, showing the compiled BibTex read-out compiled from the meta-data. It would be cool if the display box showed required vs. optional fields (e.g. with asterisk ) to indicate to users which additional meta-data is needed to complete a standard bibliographic entry
Reference Article : this website lists out required and optional fields per entry type.
The text was updated successfully, but these errors were encountered: