Viewer v3.0 impplimantation issues list

GroupDocs.Viewer Product Family
21

Hi,


Few of our other team member are not able to track this post with their Groupdocs account.
it shows access deny to this post.

I am not aware of any post updated as private, I am also not able to post in public as “Keep this post private” option is checked and read-only.
could you please make this post general so other team member could follow this post.

Thanks
Puneet Rajak
22
Hi Parth,

Thank you for your query.

As far as the upcoming release Groupdocs.Viewer 3.3.0 is concerned, the product team has given an estimate to publish it in the last week of this month. However, the front-end related issues would be handled earlier than Groupdocs.Viewer 3.3.0 release. The following tickets are expected to be covered in upcoming release.

VIEWERNET-459: Provide remove old cache utility feature in the next generation API
VIEWERNET-416: Get selected attachment from email documents
VIEWERNET-414: Render attachments from email documents
VIEWERNET-550: MSG file is not rendering properly
VIEWERNET-478: Pre-Render Information required of a remotely located document or document in the form of streams.
VIEWERNET-582: The GroupDocs.Viewer 3.x is slower than 2.19 in performance
VIEWERNET-591: 'System.OutOfMemoryException' thrown while rendering as image
VIEWERNET-475: Opacity setting for Watermark.

Note: You'll be informed via this forum thread, in the case of any further updates regarding to the front end or back-end API.

Many Thanks!



23

Hi


In together with action of above post.

Could it be possible for you to update us on the progress of main issues raised in #11999
we require to update our customer.

Thanks
Puneet Rajak

24

Hi Umar


Thanks for sharing detail list of release package.
As our urgent priority is performance right now, please let us know what improvement we would getting through this release.

Also 2 raised ticket are not included in your release package.
VIEWERNET-480 PreloadPagesCount is not working in V3.0.
VIEWERNET-493 Css classes are overridden in multiple pages documents.

Please let us know more details about the fixes of these issues.

Thanks.
25

Hi Puneet,


Thank you for your inquiry.

Below is the inline response against your points.

I am not aware of any post updated as private, I am also not able to post in public as “Keep this post private” option is checked and read-only.
could you please make this post general so other team member could follow this post.
In-fact, we are unable to make this thread public. This issue is relevant to our forum and has been raised with the concerning department.
The concerned department will look into it and also adjust the user rights so users can mark a thread public themselves.

Could it be possible for you to update us on the progress of main issues raised in #11999
we require to update our customer.
Below is the list of your raised points which has been resolved and would be found fixed in upcoming release V 3.2.0.

VIEWERNET-472 Invalid Parameter Exception on rendering PDF to HTML.
VIEWERNET-451 Empty Value Exception on rendering PDF File.
VIEWERNET-480 PreloadPagesCount is not working in V3.0.
VIEWERNET-493 Css classes are overridden in multiple pages documents.

Many Thanks.

26

Hello Puneet,


Thank you for sharing your point of view.

I am going to write an inline response against your points.

As our urgent priority is performance right now, please let us know what improvement we would getting through this release.
The following ticket is logged, generally as the performance related .
VIEWERNET-582: The GroupDocs.Viewer 3.x is slower than 2.19 in performance.

VIEWERNET-480 PreloadPagesCount is not working in V3.0.
As you already mentioned in the earlier post of this thread.
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
Hence, performance is the issue in this regard. Which is being addressed in the ticket VIEWERNET-582.

VIEWERNET-493 Css classes are overridden in multiple pages documents.
This is relevant to the front-end and we are already resolved this issue in the open sourced MVC Legacy front end. The front-end team is now working to improve this in Web Form Front end.

Please, let us know if you need more clarification.

Thanks in advance.
27

Hi Umar,


Please follow inline response.

VIEWERNET-493 Css classes are overridden in multiple pages documents.
This is relevant to the front-end and we are already resolved this issue in the open sourced MVC Legacy front end. The front-end team is now working to improve this in Web Form Front end.

We understand that MVC legacy front end example is working correct, but we are bound to use Web Form front end. Please follow the post 12607 where you have shared that you would provide fixes in couple of days,
If example solution is ready with fixes please let us know, we want to fix all other issue prior to our main concern performance issue which solution you would provide with next release.

Besides from that, Please also let us know that using usePDF = true definetly improve the quality of document for us, but it produce extra burden on performance because it is creating 1 pdf file for each page which is really time consuming for us.
so how could we improve caching speed with maintain quality of document.

Thanks
Puneet Rajak

28

Hi Puneet,


Thank you for sharing your thoughts with us.

As far as the Web Form is concerned. One of the issue of cutting text has been fixed and apparently it was looking the work of a couple of days. However, team is working to resolve the CSS issues on priority basis. Hopefully, this front end would be published with the release of Groupdocs.Viewer 3.3.0.

As you stated:
Besides from that, Please also let us know that using usePDF = true definetly improve the quality of document for us, but it produce extra burden on performance because it is creating 1 pdf file for each page which is really time consuming for us.
so how could we improve caching speed with maintain quality of document.
Please create another thread and elaborate it more. It will help us to log the issue more clearly, in our issue tracking system.

Many thanks.
29

Hi Umar,


Thanks for acknowledging that css issue would be fix and provided by upcoming release.

As far as the Web Form is concerned. One of the issue of cutting text has been fixed and apparently it was looking the work of a couple of days.
Please share its implementation example in C# so we can fix this issue in our web application.
we are bound to use ASP.Net so please do not share any MVC example.

Please create another thread and elaborate it more
Sure I will.

Thanks
Puneet Rajak

30

Hi Puneet,


Thank you for sharing your concerns.

Actually we have a good news about Webform Front End. The team has resolved the issue of over ridden CSS. We’ll update the project in the start of upcoming week.

Please stay tuned.
31

Hi Umar,


Thanks for the good news.
Please also share the link for your new sample of webform front end for .Net.

Thanks,
Puneet Rajak
32

Hi Puneet,


Yes, sure, I’ll share the link through this forum thread.

Please stay tuned!
33

Hi Puneet,


We have updated the Web-Form Front end in which the CSS overridden issue has been resolved.
Please download the sample project from here.

Thank you.