Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different icons for application/file extension with same name on macOS and Windows #1268

Closed
iffy opened this issue Feb 15, 2017 · 4 comments · May be fixed by qcif/data-curator#563
Closed
Labels

Comments

@iffy
Copy link
Contributor

iffy commented Feb 15, 2017

  • Version: ^13.6.0
  • Target: Mac/Win/Linux

My application is named LHTML and the file extensions it knows about are lhtml (same but lowercase).

Here's the pertinent parts of my package.json:

{
  "name": "lhtml",
  "productName": "LHTML",
  ...
  "build": {
    ...
    "fileAssociations": [
      {
        "ext": "lhtml",
        "role": "Editor",
        "icon": "build/lhtmldoc.icns"
      }
    ],
    ...
  },
}

So I have these icons:

  • build/icon.icns (macOS application icon)
  • build/icon.ico (Windows application icon)
  • build/lhtmldoc.icns (macOS .lhtml document icon)
  • build/lhtmldoc.ico (Windows .lhtml document icon)

I don't have a way of specifying the .lhtml document icon for both Windows and macOS.

I propose supporting something like:

    "fileAssociations": [
      {
        "ext": "lhtml",
        "role": "Editor",
        "icon": "build/lhtmldoc.${iconExt}"
      }
    ],
@develar
Copy link
Member

develar commented Feb 15, 2017

Why you cannot name file as lhtml.icns?

because the app's icon is Contents/Resources/LHTML.icns and if the file icon is lhtml.icns it can put it at Contents/Resources/lhtml.icns because my filesystem won't allow it

@matiastucci
Copy link

I'm trying to do the same. My app has an icon and I want a different icon for my fileAssociations (same icon for Windows and OS X). Is this already possible?

@iffy
Copy link
Contributor Author

iffy commented Feb 8, 2018

@matiastucci
Copy link

@iffy awesome. Thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants