Package com._1c.g5.v8.dt.platform.services.mobile

Interface IMobileApplicationLauncher<T extends IMobileDevice>

  • Type Parameters:
    T - the mobile device implementation, that is specific for the mobile OS
    All Superinterfaces:
    IRuntimeComponentExecutor
    public interface IMobileApplicationLauncher<T extends IMobileDevice>
extends IRuntimeComponentExecutor
    1C:Enterprise runtime component executor for mobile application launching. Allows:
    • Deploy mobile 1C:Enterprise runtime to the mobile device
    • Deploy mobile application from the local path and run it on the mobile device (optionally in debug mode)

    Clients are intended to deploy 1C:Enterprise mobile runtime before application run. Clients may implement and register this type of the runtime executor component for each type of supported mobile OS.

    • Method Summary

      All Methods Instance Methods Abstract Methods 
      Modifier and Type Method Description
      void debugApplication​(T device, String name, Path application, String debugServerUrl, boolean attach, org.eclipse.core.runtime.IProgressMonitor monitor)
      Deploys an application from the local path to the mobile device and launches it in debug mode.
      void deployRuntime​(T device, IArchivedRuntimeComponent mobileRuntime, boolean reinstall, org.eclipse.core.runtime.IProgressMonitor monitor)
      Deploys the 1C:Enterprise mobile runtime to the mobile device.
      void runApplication​(T device, String name, Path application, org.eclipse.core.runtime.IProgressMonitor monitor)
      Deploys an application from the local path to the mobile device and launches it.

    • Method Detail

      • deployRuntime

        void deployRuntime​(T device,
                   IArchivedRuntimeComponent mobileRuntime,
                   boolean reinstall,
                   org.eclipse.core.runtime.IProgressMonitor monitor)
            throws MobileDeviceException
        Deploys the 1C:Enterprise mobile runtime to the mobile device. Typical implementation flow is:
        • Dearchive 1C:Enterprise mobile runtime component somewhere on the local drive to a temporary folder
        • Deploy and install this 1C:Enterprise mobile runtime component on the mobile device
        • Delete temporary folder
        Parameters:
        device - the mobile device to deploy mobile runtime component to, is intended to be already launched, cannot be null
        mobileruntime - mobile 1C:Enterprise runtime component, cannot be null
        reinstall - whether need to reinstall 1C:Enterprise mobile runtime, if already installed
        monitor - the progress monitor to report progress to and check cancellation status, cannot be null
        Throws:
        MobileDeviceException - if an error occurred; possible reasons may include:
        • Mobile device access error
        • Mobile device is not launched

      • runApplication

        void runApplication​(T device,
                    String name,
                    Path application,
                    org.eclipse.core.runtime.IProgressMonitor monitor)
             throws MobileDeviceException
        Deploys an application from the local path to the mobile device and launches it. Typical implementation flow is:
        • Push application file to the mobile device somewhere (on SD card, for example)
        • Start mobile 1C:Enterprise runtime with templatepath infobase restoring key

        Mobile 1C:Enterprise runtime must be deployed before application run.

        Parameters:
        device - the mobile device to run mobile application on, is intended to be already launched, cannot be null
        name - the application name that is based on the source infobase or project, can be used to create temp folder with application content, cannot be null
        application - the path to mobile application folder, cannot be null
        monitor - the progress monitor to report progress to and check cancellation status, cannot be null
        Throws:
        MobileDeviceException - if an error occurred; possible reasons may include:
        • Mobile device access error
        • Mobile device is not launched

      • debugApplication

        void debugApplication​(T device,
                      String name,
                      Path application,
                      String debugServerUrl,
                      boolean attach,
                      org.eclipse.core.runtime.IProgressMonitor monitor)
               throws MobileDeviceException
        Deploys an application from the local path to the mobile device and launches it in debug mode. Typical implementation flow is:
        • Push application file to the mobile device somewhere (on SD card, for example)
        • Start mobile 1C:Enterprise runtime with templatepath infobase restoring key and debugUrl key

        Started mobile application can be auto attached to the target debug server and will be available as debuggable client in the debug server debugger (in DT IDE, for example).

        Mobile 1C:Enterprise runtime must be deployed before application run.

        Parameters:
        device - the mobile device to run mobile application on, is intended to be already launched, cannot be null
        name - the application name that is based on the source infobase or project, can be used to create temp folder with application content, cannot be null
        application - the path to mobile application folder, cannot be null
        debugServerUrl - the 1C:Enterprise runtime debug server URL to connect started application with, cannot be null
        attach - whether need to auto attach started mobile application as 1C:Enterprise runtime debug target to the target debug server
        monitor - the progress monitor to report progress to and check cancellation status, cannot be null
        Throws:
        MobileDeviceException - if an error occurred; possible reasons may include:
        • Mobile device access error
        • Mobile device is not launched