However, the printer model mentioned is what my client is using - and this solution seems less than ideal, because we'd need to load certificates on to each of my client's printers, and also renew them. There's a solution mentioned in that post, which involves loading an SSL certificate on to the Zebra printers. While researching the issue, I stumbled upon this post. This request has been blocked the content must be served over HTTPS. Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ''. The error that I could see via the Tulip console was: The issue that I ran into had to do with ' mixed content.' The Tulip app is essentially a Web app that is served up over HTTPS, while the Zebra printers are only designed to accept HTTP requests. Additionally, this will give them the option to print specific labels on printers that are setup with the necessary label types. If a printer becomes unavailable for some reason, the operator will be able to route requests to an alternate printer. My client is using the HTTP method, which allows then to easily route print requests to specific printers in their warehouse. These printers can be connected to workstations using USB cables, where print requests are sent directly, or connected wirelessly, where requests are sent as HTTP POST requests. While working on the project, I ran into an interesting and challenging issue involving printing to their Zebra printers. The app tightly integrates with NetSuite, and makes heavy use of Tulip custom widgets. I'm using Tulip to build an app that will help streamline my client's manufacturing process, including the picking of parts, the build process, quality control and inspection, packing, and more. The Xojo Examples include sample Inno Setup scripts and some sample XojoScript you can use to kick it all off.One of the projects that I've been working on recently is a 'reboot' of a client's Tulip implementation. I think that Xojo packages up your application so nicely that you are not likely to need all the capabilities that the more sophisticated tools provide.įor more information about deploying to Microsoft Windows, refer to these documentation topics: There are plenty of other installers for Windows, including the popular and expensive InstallShield tools. From what I understand, an MSI makes it easier to do remote and bulk deployments In addition to the nice UI, Advanced Installer can create MSI (Microsoft Installer) files, which are often preferred by IT departments. The free version can use the “Simple” template which will likely suffice for most Xojo developers, but they also have a more powerful paid versions ($400 to $3000). Just replace the app names in the example with your app name, generate a new AppID (using Tool->Generate GUID in the menu) and you can build your installer.Īdvanced Installer has a user interface that is quite easy to use, allowing you to create an installer just by selecting files and specifying settings. There are examples for 32-bit and 64-bit Windows apps. Or you can grab one of the example scripts from the Xojo docs to get you started.

The “QuickStart Pack” includes a Script editor that can help with that. Inno Setup creates setup.exe installers and is pretty easy to use once you get your script set up. Both will create an installer that can place your app in Program Files, optionally create desktop and Start menu shortcuts, display a license agreement and much more. What are your options?ĭepending on the project, I’ve used two installers on Windows: Inno Setup and Advanced Installer. Now that you’ve finished creating your Windows app, how do you distribute it to Windows users? Microsoft Windows users expect an installer, so you can’t really get away with just using a ZIP file to distribute your apps.

Xojo printersetup