Wijmo Flex Grid | FlexGridPdfConverter

Wijmo Flex Grid | FlexGridPdfConverter

Posted by: predhin.sapru on 23 January 2018, 7:01 pm EST

• 

  predhin.sapru

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 23 January 2018, 7:01 pm EST

  Hello,

  We are using Wijmo FlexGridPdfConverter for doing an export to PDF file usecase in our application. During testing we have noticed that when the row item count is more than 1k, the browser becomes unresponsive. So as the page freezes, user will not able to interact with the application any more(very unpleasant user experience) and user will probably decide to kill the tab or the browser instance.
  
  I would like to know whether we can leverage the HTML5 feature: WebWorker for the pdf export process, that will provide multi threaded javascript execution which can improve the overall performance. Also I would like to know wijmo/FlexGridPdfConverter compatibility with WebWorker.
  
  Please advise.

  Thanks in advance.

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 25 January 2018, 1:49 am EST

  Hi Predhin,
  
  We are sorry indeed for the delay. We are investigating on this issue.

  ~Manish

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 25 January 2018, 8:21 pm EST

  Hi Predhin,

  This issue requires further investigation by development team. Hence, this issue has been forwarded to the team with internal id 306088.

  We will let you know as we get any update on this.

  ~Manish

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 2 February 2018, 7:35 pm EST

  Hi Predhin,
  
  As per the Development team:

  FlexGrid pdf export can’t work in WebWorker, because it needs access to FlexGrid and to the DOM as a consequence.

  We plan to investigate possible scenarios of running export without blocking of the UI thread in the nearest future.

  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

  We have some concerned regarding this change and your comment would be very helpful:

  What if user Sorted /Filtered /Edited data once the PDF export process is started, should it be content these changes or not.

  If yes, PDF export would not be exported with correct data.

  Please let us know your feed back on this…

  ~Manish

• 

  matthew.hudson

  • Post Options:
  • Link
    Copy

  Posted 7 February 2018, 6:05 am EST

  Hi Manish,

  Thank you for your comments, I am working on Predhin’s team and our expectation would be to export with all the existing settings and not to change the settings after the export had started.

  It would seem to me that this would indeed be possible to implement with web workers even if you did want the visible flexgrid to still allow the user to interact with it by creating a unique, hidden instance of flexgrid that would have the settings and items present in the grid at the time the export was initiated.

  I do not see how being tied to the DOM is a showstopping restriction for adding webworker support, but I do see how not adding web worker support is a showstopping restriction for large volumes of data.

  Sincerely,
  
  Matthew Hudson

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 7 February 2018, 3:44 pm EST

  Hi Matthew,
  
  Thank you for your feedback.

  Yeah, you are correct, the issue may be resolved using WebWorker. But as the team mentioned before:
  
  FlexGrid pdf export can’t work in WebWorker, because it needs access to FlexGrid and to the DOM as a consequence.

  Hence, the resolution is not possible using WebWorker since it do not allow to access the Document,Window and DOM object. Please refer to the following links:

  [i]https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers
  
  https://www.html5rocks.com/en/tutorials/workers/basics/#toc-enviornment-features[/i]

  Also, the UI gets locked to prevent changes in FlexGrid or other related controls to get consistent result.

  I think what you are looking for as below:
  
  The export process should not be affected on making changes in UI after Export process is started and during Export process the UI should not be locked which seems browser unresponsive.

  We will forwarded your feedback to the development team for investigating a solution to overcome this problem.

  ~Manish