When developing an application to run on top of the Pulsar Platform, developers have the freedom to use the wealth of web technology available in the mobile app environment. Pulsar has been successfully used with several popular web frameworks, allowing developers to use some of the same code and techniques they have used in more traditional web development. However, there are a few technologies and methodologies that can be used to improve the developer experience while building a Pulsar-based app.
...
You can add extra email addresses to receive logs from users by adding to the pulsar.logs.email.cc Pulsar Setting
On the Windows platform, you can directly view Pulsar logs at the following directory (e.g., from Windows Explorer):
...
| Name | Hide HTML Navigation Buttons (Back, Forward, Refresh) |
|---|
Key | pulsar.docs.hideNavigation
pulsar.docs.<docID>.hideNavigation
|
|---|
Value | TRUE / FALSE |
|---|
Default Value (if any) | FALSE |
|---|
| Compatibility | |
|---|
Description | This setting will hide the back, forward, and refresh buttons if this setting is specified and set to TRUE. |
|---|
| Notes/Comments |
|---|
Generating PDF files offline - Some best practices
...
If you need to generate a PDF offline from your HTML/JS app, we've determined that the best approach is to avoid the use of <table> elements and instead build the page structure with <div> elements. It's been noted (https://stackoverflow.com/questions/9288802/avoid-page-break-inside-row-of-table/27209406) that <tr> elements do not appear to respect the break-inside/page-break-inside CSS attributes. Note: If you are building your app to run within Pulsar FSLapp: Pulsar FSL app is utilizing Bootstrap 4. In the discussions around page breaks and <table> elements, it's been suggested that Bootstrap may impact this.
...
Using images, canvas elements and fonts will work in your custom HTML implementations, but it is possible to run into issues when attempting to generate PDF files, due to CORS rules or similar access restrictions imposed by the webview environment. Our recommendation is to convert each of these resources to a 'data URI' format with Base64 encoding.
Canvas elements can be converted at runtime (prior to calling print/PDF APIs), using the convenient toDataURL() javascript API. For Images, the same thing can be done by drawing the image in a canvas element and using the toDataURL() API. Note: This particular method assumes a canvas element is available in your HTML page. Prior to generating the PDF or printing the HTML, we recommend removing the canvas from the DOM using jQuery or similar libraries, as we cannot guarantee the PDF engine will render canvas elements properly at this time. ...
Font files may require pre-deployment processing to avoid issues loading during PDF generation or printing. Embedding Fonts as base64 data urls works best, as this can be inlined or added directly to precompiled framework CSS for inclusion in your HTML/JS.