I got the license for the web version and have a page that works like I want in Firefox when launched from xojo debug. As far as I can tell there are two possible options to build the page for use. 1. Use the build or 2. export web page. Neither one of these does what I had thought was going happen. I had imagined an html page that I could then click on and it would open Firefox and I’d see what I saw from debug. The build is creating various folders and files, the export is not html but rather binary or xml. Can someone please shed some light on what the concept is to take what I see in debug and be able to do the same out of debug. Thanks.
You build web apps for deployment:
http://documentation.xojo.com/index.php/Web_Deployment_Overview
Xojo web apps are executable apps, not HTML files.
Thanks Paul. My intention is to provide a browser based method for my clients to update firmware on my product via USB. I have a web app that will communicate and transfer the files to the microprocessor from the local computer via USB, my hope was to use the web browser as a simpler method that having to provide a real application they have to run in addition to me sending them the actual 32k binary with the software update for the micro. It now seems that the web browser version is much more work than the standard app, As I understand it, the application running on the server can talk to the USB/serial port, but no other clients connected remotely would have the same USB access for data transfer. I do not need the the hosted server to have USB access, only the browser.
Xojo web apps cannot communicate with the USB/serial ports of the clients that connect to the web app. A Xojo web app would only be able to use the USB/serial port of the web server running the web app, which doesn’t sound like what you want.
Perhaps a combination approach would work? You could have a desktop (or console service/daemon) app that checks for firmware updates by communicating with a web app. If an update is available, the desktop app could download it and then send it to the device.
As Paul suggests, you can use a Helper app wich does the work. It could be a 1-time install for the user.
You may use a URLHandler (on the system) to activate that app for the update (over USB).
A URLHandler may be FirmwareUpdate://someinfo/somemoreinfo/
Wich can be like a link to open the app. Just as Xojo Feedback does it. (you might have noticed the feedback:// links).
You might have a look here:
http://developer.chrome.com/apps/app_usb.html
Chrome supports USB handling (in browser communication over usb).
If there are more browsers, perhaps you can use that?