[FEATURE] Restructure config file

[yammesicka]

Some plugins may perform multiple tasks:

• Chrome may open multiple windows
• PyCharm may open multiple projects
• VLC should be able to play a song and increase the volume to 100%
• Git should be able to send a pull request and open a merge request right afterword.

In the best scenario, two plugins should be able to interact (Spotify: Play a random song, Slack: Post that song on the #music channel).

Let's talk about the possible structure of the .comeback file.

GitLab's CI format looks to me like a great example.

[agamm]

Something like this?

job1:
  chrome:
    url: url0
  pycharm:
    cwd: path0
  vlc:
    path: path0
    volume: 100
  git:
    pull: origin master
    #merges automatically?

job2:
  chrome:
    url: url1
  pycharm:
    cwd: path1

This may also work for your example, what do you think?

chrome:
    url: [url0,url1...]
pycharm:
    cwd: [path0, path1]
vlc:
    path: path0
    volume: 100
git:
    pull: origin master
    #merges automatically?

[agamm]

Also, we may need to think about 80/20, what will be the most used use case, maybe we can favor simplicity (helps with a learning curve which is important for a project like this). For example: opening sublime, chrome and a terminal will become:

job0:
  sublime:
    cwd: blabla
  chrome:
    url: blabla
  terminal:
    cwd: blabla

instead of (which is less indented and doesn't have an unnecessary job0 wrapper):

sublime:
  cwd: blabla
chrome:
  url: blabla
terminal:
  cwd: blabla

A solution for the 20 maybe adding a parameter that makes the .comeback behave with jobs like gitlab. Or a shabang stlye patch for the config. Or just using something hybrid like the first comment I did.

Open to your thoughts :)

[agamm]

We will use JSON, as @yammesicka and @yoavgolan helped decide. So it will be a list of dicts.