4D v18 is 750 MB. just over half of that size is taken by the embedded CEF web area. So it would be a shame not to use it at all other than for the welcome dialog.
my understanding is that the Chrome Embedded Framework is using the same PDF renderer as Chrome, that is, PDFium, a Google edition of the Foxit render. https://opensource.google/projects/pdfium https://www.foxitsoftware.com/blog/foxit-pdf-technology-chosen-for-google-open-source/ note that you can pass a posix path or a system path or an URL to the Web area. the difference between posix or system can be determined by the delimiter. but the difference between a path or an URL is less obvious, especially if you pass a file name. the reason you need to append the "file://" protocol, and to use an absolute path that begins with a forward slash (which results in a triple slash), is that as silly as it sounds, "test.pdf" by itself could be interpreted as an internet domain name and therefore ambiguous. > On Apr 22, 2020, at 1:51, Chris Belanger via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I have never used web areas in 4D so I will need to explore the benefits of > it. I notice it can also be used to display .png files and others dragged > into that ‘dropZone’ variable object on my form. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
