This encapsulates two separate ideas:

      1. Debugging just a locally-run Node.ACS project.
      2. Debugging a client server Node.ACS project, stepping from the Titanium Mobile client code through to the server call and back again.

      First, do a test to make sure manually installing the plugin allows debugging to work as we expect.

      For option #1, this suggests we need to do the following:

      1. Include, or optionally install on demand, the Eclipse plugin:
      2. Automatically create a debug configuration as specified in the wiki
      3. Hook up debug actions that launch the debug configuration and step through the breakpoints.

      For option #2, this suggests we need to do everything in #1, except we automatically launch two debug processes, one for the client app, and one for the server.

      1. If there are multiple local servers the app connects to, we would need to allow the user to pick one
      2. We would need an additional menu option to allow the user to pick if they wish to debug just the client, or client and server. Or perhaps we don't need that choice? It could be an option in the launch configuration.


          Issue Links



              • Assignee:
                mxia Michael Xia
                ingo Ingo Muschenetz
              • Watchers:
                2 Start watching this issue


                • Created: