-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Screenshots. #24
Screenshots. #24
Conversation
Codecov Report
@@ Coverage Diff @@
## master #24 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 3 4 +1
Lines 108 157 +49
Branches 12 17 +5
=====================================
+ Hits 108 157 +49
Continue to review full report at Codecov.
|
Not sure what is causing those test errors. I'll have a look at it later. @westy92 have you had a chance to take a look at this? |
Thank you @rhyek, very nice! |
They should work the same, yes. Only thing missing should be tests. |
Hm, well I was sort of expecting some tests to fail due to timeouts where OCR scanning is involved. The other tests I noticed are basically inconsistencies in OCR scanning vs my environment, which I wasn't expecting. Things like HELLO! being interpreted as HELLO'. Those are easy to fix. Thoughts on these tests? |
To be honest, the OCR thing was mostly me having a little fun with writing these tests. I'm honestly more inclined to just remove them altogether instead of figuring these inconsistencies out. IMO, with the PDF tests, screenshots could be assumed to work fine for the most part and a couple of tests should suffice. |
Thank you, @rhyek. Perhaps an idea might be to split this PR into two – one for adding the screenshot interface, other for additional OCR option. That way the screenshot feature could be merged and new package released, and the OCR added separately later on. What do you think? |
Yeah, not a bad idea. I just wish @westy92 would share his opinion. Atm I have no idea when or if this might be merged and published. |
@rhyek Thank you for the contribution! I plan to take a first look tonight. Sorry for the delay! |
It has been nearly a month since I made this PR. Are there any issues that I can help resolve so this can get merged? |
…ausing tests to fail
I cleaned up the tests mostly by removing the OCR ones which I feel were unneeded. The failed tests are are an issue of slow processing on the test server. If there isn't any interest in this PR please close. |
@westy92 why is this not being merged please? This would be a welcome addition to the library as far as I am concerned. |
@rhyek why did you close this? |
@graingert, sorry. I interpreted the lack of attention to this PR as the repo owner having either no interest or different plans for this feature, which is fine. |
@westy92 do you know what's happening with this PR? |
I still have not had the time to review this in depth. Since this is a new (large) feature, I plan to investigate methods of generating images, verify this is the best one, and then think about how I want this new functionality integrated into the project. It will take a lot of time that I have not had yet. I just reopened this, as I will get to it eventually. |
If anyone else wishes to review this changeset, please do. The more eyes, the better. |
Do you think it might be worth splitting the image generation from the
chrome process reuse via tabs?
…On 19 Sep 2017 19:26, "Seth Westphal" ***@***.***> wrote:
Reopened #24 <#24>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAZQTAis8TZmvLFW5unFolrFmXQvKKZfks5skAdmgaJpZM4OqaqJ>
.
|
@graingert I don't see any code here working with tabs, but that implementation should remain separate. |
I am already using my fork in production and since multiple PDFs and/or screenshots are being generated concurrently, I have found my application crashes frequently without the tab functionality. For example, I have a page that displays several (20 or so) screenshots at the same time all generated in real-time with a single chrome instance. Without tabs it does not work. It is very basic since it is just utilizing There is already a test that utilizes tabs. Currently it only generates 5 concurrent PDFs since the global 15s timeout and slow processing of the test server doesn't allow for more, for some reason. That test itself could use a review as well. |
|
||
# tesseract.js eng language files | ||
test/langs/* | ||
!test/langs/.gitkeep |
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.
missing trailing new line
@rhyek do you have a fork on npm? and can you separate out the use of tabs for concurrency? |
I'm using my fork from Github, directly. Changing this branch would not
affect me at all. Nevertheless, are your plans for tabs much different than
what I have implemented?
Like I said, this is already working for me in production and is
transparent to the user. The implementation can be changed at any point
since it is not part of the public API.
…On Fri, Sep 22, 2017 at 8:38 AM, Thomas Grainger ***@***.***> wrote:
@rhyek <https://github.com/rhyek> do you have a fork on npm? and can you
separate out the use of tabs for concurrency?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAq5yrYsJ6JelYS84i1DejYjIxAv_wBAks5sk8ZkgaJpZM4OqaqJ>
.
|
@rhyek can you separate out the fix to use tabs for concurrency into a different PR? |
Sure. I think I'll have some time over the weekend. |
@rhyek I think the project is at a decent position to get this merged in! Could you please sync this with master? Thanks! |
Sorry, I have 0 interest in this PR. If someone else wants to help you out with a new one with my code that's fine. |
Thank you for your contributions so far! I'll take it from here and use this as a starting point. |
@westy92 What's the status on this PR? |
@westy92 Was this ever completed? I have the need to render a screenshot prior to agreement because displaying a final pdf in the browser would be equivalent to free. This would be very convenient and streamline the document process. Is this project active? I hope Puppeteer has not eaten everybody's lunch? |
any update on this? |
Screenshot functionality has been published in version 0.8.0! 🎉 |
Related: #13.
This is a work in progress. I need to know if this is the approach you were thinking of.
Basically:
CreateOptions
now has: