In theory, we should be able to modularize the debugger so that any 'transport' mechanism can work to connect the debugger to it's console. The remote console using Flash LocalConnection is just an example.
Henry and I have talked about (but obviously not gotten anywhere on) using XHTTP back to the server and the server acting as a proxy to a remote console in your browser. That would probably be the easiest/most general solution. Your app should always be able to talk to the server it is loaded from, and we would create a remote debugger console app in LZX that connects to the same server. On 2010-06-23, at 07:47, Raju Bitter wrote: > Thanks for the detailed information. It would definitely be a huge > advantage if we could remote debug OL applications on mobile devices. > But to make it clear, I'm thinking of not only debugging an > application running on the same machine, but on a mobile device > connected to the PC through USB. In the case of Android, we'd have > full access to the file system. I haven't tested how that would work > for iPhone or other devices, yet. > > I'd be willing to investigate the debug integration some in mid-July, > once we have Adobe AIR deployment through Ant scripts up and running. > That would be a HUGE advantage for mobile app development, though! > > On Tue, Jun 22, 2010 at 2:05 PM, P T Withington <[email protected]> wrote: >> [cc-ing laszlo-dev, for archiving] >> >> On 2010-06-22, at 03:02, Raju Bitter wrote: >> >>> I'm wondering what the best way to debug mobile OpenLaszlo >>> applications would be. Could the remote debug feature be tweaked in a >>> way to integrate between the mobile device and a browser instance >>> running on the development PC? That would actually be pretty cool, but >>> I don't know the debug mechanism well enough to judge if it's possible. >> >> This should be very doable. The following bugs are related: >> >> http://jira.openlaszlo.org/jira/browse/LPP-7362 >> http://jira.openlaszlo.org/jira/browse/LPP-7406 >> >> but perhaps the easiest approach is to look at: >> >> WEB-INF/lps/lfc/compiler/LzBootstrapDebugService:LzDebugConsole >> >> this defines the protocol from the debugger to the 'console window' (i.e., >> the window that displays the output). This is fairly modular and you will >> find a number of subclasses already implemented for the different runtimes >> and for various bootstrapping scenarios, such as no debugger, a debugger >> that uses an HTML frame, and the 'console remote debugger' that uses a >> window in the developer console. (The protocol for calling back to the >> debugger from the console window, for the eval pane, is not so well defined. >> It would be nice to codify that.) >> >> If you look at: >> >> WEB-INF/lps/lfc/debugger/platform/swf/LzDebug:makeDebugWindow >> >> You will see this is where the debugger makes its decision as to what >> console it is going to attach to. >> >> If you look at: >> >> >> WEB-INF/lps/lfc/debugger/platform/swf/LzFlashRemote:LzFlashRemoteDebugConsole >> >> You will see the implementation of the remote console that runs in the >> developer console using the Flash LocalConnection API. It should be fairly >> straightforward to extend this to do what you want. It's on our wishlist. >> Just haven't had time. >> >> >> >> >> >>
