Suggestion: snapcraft init-gui

I wanted to suggest an additional parameter to ease the development/start process.

snapcraft init-gui <project-name>
snapcraft init-desktop <project-name>

Action

  1. gui/<project-name>.desktop created with generic values
  2. gui/<project-name>.png with generic image set
  3. snap/snapcraft.yaml that includes these resources

Reasons

  1. Get started quicker
  2. Less errors (less work to do)
1 Like

From a UX POV it might be better to actually make --gui or --desktop an option to “init” instead of inventing completely new commands …

i.e.

snapcraft init --gui
snapcraft init --desktop

(in general that sounds like a very good suggestion though)

3 Likes

Awesome, that would be great.

I notice when these templates are created (more specifically, snapcraft.yaml), it would great to have more links to specific parts of documentation.

name: my-snap-name # you probably want to 'snapcraft register <name>
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
summary: Single-line elevator pitch for your amazing snap # 79 char long summary
description: |
  This is my-snap's description. You have a paragraph or two to tell the
  most important story about your snap. Keep it under 100 words though,
  we live in tweetspace and your description wants to look good in the snap
  store.
indent preformatted text by 4 spaces
grade: devel # must be 'stable' to release into candidate/stable channels
confinement: devmode # use 'strict' once you have the right plugs and slots
# Documentation on assets
# https://snapcraft.io/docs/build-snaps/metadata
icon: icon/snapcraft.png

# For more info on parts
# https://snapcraft.io/docs/build-snaps/parts
parts:
  my-part:
    # See 'snapcraft plugins'
    plugin: nil