Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • CamiTK Community Edition CamiTK Community Edition
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • CamiTKCamiTK
  • CamiTK Community EditionCamiTK Community Edition
  • Issues
  • #57
Closed
Open
Issue created Jun 13, 2018 by Emmanuel Promayon@promayoeOwner

Launcher wizard for Action State Machine interface

About you

Submitted on bugzilla by Antoine Tacheau @tacheaua, 2017-09-11

Product

Action state machine

Overview

Currently, we need to open a terminal and type this kind of command to start asm:

camitk-actionstatemachine -f <ProtocolFile> -o <LogFolder>

Since Action State Machine can be used by 'basic user' to run new protocol, it would be easier if a launcher or an interface were available.

For instance: a gui interface in order to select which protocol should be started or - a specific protocol file (only changing extension by .asm, .prot, .protocolASM ...) to be associated to asm executable. Thus, users only have to double click to start application (moved to issue #67)

It is also required to set a default behavior for log file argument

-- Antoine Tacheau

As of 4 July 2018, this issue was split in two. Current issue is about showing a dialog if no command line argument is given. The other issue (issue #67) is about defining a specific "protocol" file that contains the SCXML file as well as the log folder and adding a -protocol option to provide this file.

Hints

I think the best would be to:

  • detect the case when the user launches camitk-actionstatemachine without any command line arguments (not even --help)
  • in this case, offer a mini Qt Wizard with:
    • 1 page with explanation why the user is asked for more
    • 1 page to choose the scxml
    • 1 page to choose the output directory
    • launch the normal process
Edited Jul 04, 2018 by Emmanuel Promayon
Assignee
Assign to
Time tracking