Chat entries displayed in a hangouts-like format #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Display chat entries only from a selected date - Ability to use a hangouts-like format instead of a raw text format - Removal of extraneous components on screen to prpare for printing
Quick description of changes from forked repo
|
This is, like, a, 5-year-old PR but it would be cool to see this updated & merged/implemented. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure whether that would be useful for many, but I needed to print chat entries in the same way it would be displayed on hangouts, from a given date in the past up to today. I've implemented this so as to retain the initial feature set, but it would certainly need some cleanup.
It's also fairly slow to display/scroll for large conversations. Printing in the correct format also requires that you enable CSS emulation to "Screen" on the "Rendering" developer options of Chrome - no way around this which I'm aware of.
I can clean this up a bit and document the above if there's interest in this pull request. Missing bits:
Added several options: