Free Support Forum - groupdocs.com

Viewer v3.0 impplimantation issues list


#1

Hi Groupdocs

This is Gap consulting Team.
As you discussed
we are providing the priority list in descending order.
The first 3 issue raised is urgent for us.

1. PreLoad Page Count Method not working: This is most important feature for fast performance. At earlier with release 2.19 it was working fine for us.
Though starting with v3.x, it is sure that first all the caching files get generated and then after the first page start to render. This is taking 25-30 sec for some files during load which is serious concern for us.
Below is the screenshot of performance testing we done against 2.19 and v3.0

Document

Cached

Viewer 2.19

Viewer v3.0

example with images.docx

No

1.6

17.2

example with images.docx

Yes

1.2

3.7

Business Trip Checklist.docx

No

1.3

5.2

Business Trip Checklist.docx

Yes

1.2

2.8

EU Refferendum PDF

No

1.8

hadnt loaded after 2 minutes

EU Refferendum PDF

Yes

2.2

One Page Letter.docx

No

1.3

1.6

One Page Letter.docx

Yes

1

0.9

scannedletteronepage.pdf

No

hadnt loaded after 2 minutes

scannedletteronepage.pdf

Yes

Threepageletter.doc

No

2.6

4.9

Threepageletter.doc

Yes

1.1

3.7

Threepageletter.pdf

No

2.1

6

Threepageletter.pdf

Yes

1.67

1.5

twopageletter.docx

No

1.2

2

twopageletter.docx

Yes

1.6

1.2

INV - Sent as Email

No

1.1

hadnt loaded after 2 minutes

INV - Sent as Email

Yes

1


Unfortunately we are not able to share all the document.
As you can see that most of the document is rendered slower than its existing version.
For more details regarding setting please take a look on below post
http://groupdocs.com/Community/forums/11912/preloadpagecount-not-working-for-html-based-rendering-in-v3.0-viewer/showthread.aspx#11912

2. Document Format getting disturb: All PDF file initially get render correct, but when we scroll down or use thumbnail to jump on specific page its font get disturb.
for more details please refer shared video: https://www.dropbox.com/s/asiqykj34ofml5j/ScreenRecording_Viewer.zip?dl=0


3. GetDocumentInfo exception(CreationDateValueEmpty, InvalidValueException) : We are very frequently encountering following issue when passing through GetDocumentInfo method
1. "Creation Date is empty" issue
2. Invalid Value format exception.
Groupdocs also confirm that they are able to replicate the issue.
Please refer below post for more details:
http://groupdocs.com/Community/forums/2/11647/document-streaming-js-error-in-viewer-v3.0/showthread.aspx

4. Blurry Images in Image Based Rendering: When we use ImageBased rendering every type of document get blur when rendered. Please see below details for more info
http://groupdocs.com/Community/forums/11935/blurry-document-in-image-based-rendering/showthread.aspx#11935

5. Document Caching removal: In v2.18, there is a method called "RemoveOldEntries" under DocumentCache class. This method used to clean old cache entities.
We are not able to locate this method for v3.0, could you please provide more detail how we can achieve this requimrents in v3.0.
http://groupdocs.com/Community/forums/showthread.aspx?PostID=11870&Subj=remove-cache-entries-documentcache#11870

Please share the dates to relieved these fixes so we can share this with our customer.

Please acknowledge with any query if you have or confirmation once you gone thorough this.

Thanks
[Puneet Rajak]


#2

Hi Puneet,


Thank you for coming back with a priority wise list of issues.

I am pleased to inform you that two of the issues you are facing are already fixed and a release with fix of those issues will be V3.2.0 which can be expected in the month of April '2016. Below are the issues which have been fixed:

VIEWERNET-451: Empty Value Exception on rendering PDF File
VIEWERNET-472: Invalid Parameter Exception on rendering PDF to HTML

For other issues, we need an internal discussion so we can update you once we have conducted an internal discussion + investigation.

Many Thanks

#3

The issues you have found earlier (filed as VIEWERNET-451;VIEWERNET-472;VIEWERNET-479;VIEWERNET-480;VIEWERNET-493) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by groupdocs.notifier.

#4

The issues you have found earlier (filed as VIEWERNET-582;VIEWERNET-459) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by groupdocs.notifier.

#5

Hi Sabir,


Thanks for the great news.
This fixes would going to provide us stability in Viewer tool.

would it be possible for you to share some exact date of April to us so we can share some more details with our customer.

Currently the major concern for us is first 2 points of priority
1. Performance: PreLoadPageCount Method
2. Correct Output: Document Format getting disturb

As you mention that you need some internal discussion + investigation.
If it is possible, Please share some expected date of release after your discussion.

That would really going to help us to keep the ball rolling.

Thanks.
[Puneet Rajak]


#6

Hi Support,

Thanks for the update. We have verified v3.2.0 for the issues which we have raised. Please find detail information on all the issues below.

Performance

The major concern we have is performance issue. There is no performance improvement in v3.2.0 release. Somewhere in this forum you have mentioned you are working on performance improvement and release changes in next version in May. We are already running behind schedule it’s really important for us to release changes for customer ASAP. So if you can fix performance issue and release changes in next few days will really help. Please share release date which include performance improvement fixes.

VIEWERNET-480 PreloadPagesCount is not working in V3.0.

We have verified PreloadPagesCount functionality and we can say it’s working fine. But in earlier version when we have added this functionality (v2.x) to our application we observed good performance improvement. But for v3.2.0 this functionality is not making any major change in the performance improvement. Could you please confirm is this functionality expected to improve performance of document rendering? Considering the earlier version, it should but we are not seeing any performance improvement in v3.2.0


VIEWERNET-493 Css classes are overridden in multiple pages documents.

There is an improvement in the document rendering but it's still having some issues in file rendering. Please see attached screen shots for more information.

VIEWERNET-472 Invalid Parameter Exception on rendering PDF to HTML.

This is resolved now.

VIEWERNET-451 Empty Value Exception on rendering PDF File.

This is resolved now.

So following issues are still open and we request you to release fixes for this in next release ASAP.

· Performance improvement.

· VIEWERNET-480 PreloadPageCount – Please confirm your comments on this as mentioned above.

· VIEWERNET-493 Css classes are overridden in multiple pages documents.

· Document caching removal utility

Please let me know in case you require any further details.

Awaiting your positive response.

Thanks,

[Parth Patel]


#7

Hi Puneet,


Actually your raised points are under the discussion/investigation and we couldn’t finalized yet. However, soon you would hear some good news over it through this forum thread.

Please stay tuned!





#8

Hello Parth,


Thank you for the verification the GroupDocs.Viewer 3.2.0 at your end.

As you stated:

VIEWERNET-480 PreloadPagesCount is not working in V3.0.

We have verified PreloadPagesCount functionality and we can say it’s working fine. But in earlier version when we have added this functionality (v2.x) to our application we observed good performance improvement. But for v3.2.0 this functionality is not making any major change in the performance improvement. Could you please confirm is this functionality expected to improve performance of document rendering? Considering the earlier version, it should but we are not seeing any performance improvement in v3.2.0

Yes here are some issues with performance. The team is working over it.These issues are likely to be fixed in the upcoming release V 3.3.0.

VIEWERNET-493 Css classes are overridden in multiple pages documents.

There is an improvement in the document rendering but it’s still having some issues in file rendering. Please see attached screen shots for more information.

This issue couldn’t be reproduced. Even we have checked out your previously provided files in Html rendering mode and found that those files are working well now. However, can you provide us the recently tested problematic file?

Performance improvements.
It has been logged in our issue tracking system as ticket VIEWERNET-582. Team is working over it. This issue is likely to be fixed in upcoming release V3.3.0.

Document caching removal utility
This issue has been logged in our issue tracking system as ticket VIEWERNET-459 . Team is also working over it. This issue is likely to be fixed in upcoming release V3.3.0 as well.


Thank you




#9

Hi Umar,


Do you get any prediction when would team groupdocs would be able to provide any of the fixes.
we would be glad to hear any date from your side of fixes.

hope your response contain any good news for us.

Thanks
[Puneet Rajak]

#10

Hi Umar


Thanks for your response and enlighten.

As we mentioned in earlier post we are running well behind the schedule. So please provide a sharp date for your next release v3.3.0 and also share list of issues which you would going to provide us with this release.

VIEWERNET-493 Css classes are overridden in multiple pages documents.
We have shared attachment for explaining this. Despite from this if you require further information, please let us know we will share a screen recording with your sample document.

keen to hear from you.

Thanks


#11

Hi Puneet,


As initial prediction, the next version (3.2.0) with most of your concerned fixes would be released around 15th of April. You will be notified through this forum as the version would be published.

Please Stay Tuned!

#12

Hi Umar


Attached is the issuing documents.
Please render its 6 page in native application(pdf reader) and in your Viewer sample solution.
you will realize some incorrect rendering.
for more reference please also see the attached screenshot from above example.

beside from this, we have found issue in one of the fix.
  • VIEWERNET-479 - Blurry document in Image Based rendering
We have test this in most of the document but still the issue of font blurring still persist.
Please look this into as well. though this is not a high priority for us right now.

Please consider that currently our urgent requirement is performance improvement, so awaiting for your response on 12577 as well.


Thanks.

#13

Hi Umar,


Thanks for sharing the good news. It is pleasing to know that Groupdocs is working on our raised issue.

Though we would like to know more about the following:

1. ‘As initial prediction,it would be released around 15th of April’, Please ensure us that 15th April would be a sure date to get fixes for most of our raised issues. So we can plan our build action according to that. Also sure date would help us to satisfy our customer expectation of release.

2. You mentioned that release 3.2.0 does contain most of our fixes. Please point down all the fixes which you are going to provide us with this release.
you can refer to response #11999 for list of open issues.

Keen to hear from you.
Thanks
[Puneet Rajak]

#14

Hi Parth,


Thank you for detailed explanation and providing us the problematic files,

We have investigated your provided documents. Here I am going to write against your points

Please render its 6 page in native application(pdf reader) and in your Viewer sample solution.
you will realize some incorrect rendering.
We couldn’t reproduced the issue at our end. Both of your documents are being rendered correctly. At your end, this issue might be related to the system specifications e.g processor cache,RAM capacity. Can you share your system specifications with us.

beside from this, we have found issue in one of the fix.
VIEWERNET-479 - Blurry document in Image Based rendering
This issue has been resolved. But you can make changes in code like following example.

string guid = “document.doc”;

//Set UsePdf option to have better quality
ViewerConfig viewerConfig= new ViewerConfig
{
StoragePath = “c:\storage”,
UsePdf = true
};
ViewerImageHandler imageHandler = new ViewerImageHandler(viewerConfig);


//Use Jpeg as output format with JpegQuality option
ImageOptions imageOptions = new ImageOptions
{
ConvertImageFileType = ConvertImageFileType.JPG,
JpegQuality = 100 // default value is 90
};

List pageImages = _imageHandler.GetPages(guid, imageOptions);

The code written in bold is actually a key thing to set the image quality.

Please write to us if you need more explanation.

Thank you.


#15

Hi Puneet,


Thank you for asking more details.

1) Please note that the release date of GroupDocs.Viewer for .NET 3.2.0 as shared by Muhammad Umar is not an exact date and is just an estimated date. Unfortunately, we can’t be sure of an exact release publishing date because there are many processes involved with the release publishing. Therefore, we are unable to commit an exact date but it should be somewhere before the end of April '2016.

2) The release 3.2.0 will contain fixes of the issues you found in rendering of PDF files - more precisely, the issues I mentioned in 12026. The issues which are related to open sourced front end (but not found in v2.19 where front end was part of API) are still under investigation. We have conducted a gap analysis of open sourced front end with v2.19 and have forwarded the results to the developers who originally developed front end library. Our developers are trying to figure out a best possible solution to minimize the gap which you also have shared in 11999. Most likely, we can have an update on this matter in the coming week.

We apologize for any inconvenience.

#16

Hi Umar


here’s the response of your comment on following:

"Please render its 6 page in native application(pdf reader) and in your Viewer sample solution.
you will realize some incorrect rendering."

We are surely able to replicate this issue even in your example solution provided on your portal.
I am attaching few screenshot with one in browser rendering and other in Viewer rendering with highlighted defect. Please take another look on screen shot.
We are also sharing your example solution, please add licence key and DLL and run the application, you would surely be able to replicate the issue than.
Example Solution
https://onedrive.live.com/redir?resid=8ADE91EF770E49D!425&authkey=!AKGMgEtZhzLOqEE&ithint=file%2Czip

we have notice that the pdf page content get blank after once viewer encounter keyword “sub”.
like in subscription.
thought maybe this could help you in your investigation.

VIEWERNET-479 - Blurry document in Image Based rendering
Thanks for your valuable code suggestion for this. this is looking much better than earlier, though it is still under testing and we would let you know once we are good to progress with this fixes.

Thanks






#17

Hi Sabir,


Thanks for sharing your prospected plans for releasing version 3.2.0

we are pleased to hear that you would going to provide fixes for 12026.
according to priority wise we request to provide fixes for the first 2 issues of 11999. i.e
1. PreLoad Page Count Method not working
2. Document Format getting disturb

This is critically important concern for us as first provide performance and second provide stable output.

Please discuss this and let us know whether these fixes would be include in the package 3.2.0

Thanks.
[Puneet Rajak]

#18

Hi Parth,


Thank you to providing us the problematic source code.

Your provided project is actually WebForm Front End sample project. This project has some issues with Viewer 3.2.0. The relevant teams are working on it. It might be updated within a couple of days. Meanwhile, you can use our Legacy front end sample project. Which is a Asp.NET MVC project and fully compatible with Viewer 3.2.0 API.

Many Thanks!

#19

Hi Puneet,


Thank you for the inquiry.

We have completed our internal discussions / investigations just today and I am pleased to inform you that almost all of your issues are expected to be fixed in GroupDocs.Viewer for .NET 3.2.0 except the below two issues:
  • Performance improvement in the document rendering
  • Document caching removal utility
The above two remaining issues are planned for the release GroupDocs.Viewer for .NET 3.3.0 which is expected to be published in the month of May '2016 so I hope you will be happy with our plan.

Best Regards

#20

Hi Umar,


As you mentioned that most of our fixes would be provided in couple of days or with next release.
Please share your expected date of release for version v3.3.0

Please also let us know a list fixes that you would be able to provide with upcoming version.
This would help us to update our customer expectation.

Thanks.