Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 1
    can you clarify, has the program got a supported api to plug into, or are you suggesting hacking it? Commented Feb 26, 2018 at 17:46
  • 1
    Honestly, it really depends on a number of factors, including whether or not you actually have a library to call for your command line tool. If not, just build the UI around calling the command line and parsing the response. Commented Feb 26, 2018 at 17:48
  • @Ewan Not really, there is some semblance of an API layer under the CLI but I would have to re-write some portions of it to make it consistent. But I'm asking more in terms of industry practice. Is it normal to write an API layer for a GUI to plug into or do GUIs just invoke the CLI? Commented Feb 26, 2018 at 17:49
  • 1
    @SrinivasSuresh, I've seen both approaches in the wild. I know nothing of your tool, but there are pros and cons to a more integrated approach. One of the cons being the risk of breaking things to create an API where there was none to begin with. Commented Feb 26, 2018 at 17:54
  • 2
    @SrinivasSuresh: if you want to be a really professional software developer, stop thinking in cargo-cult terms like "industry practices" or "best practices". There is nothing like "best practice", only confirmation to requirements. For example, this specific case: there are situations where solution 1 fits better to the give requirements, and there are situations where solution 2 fits better. None of them is "better in general". Commented Feb 26, 2018 at 20:25