V2 task list

V2 will be a non-trivial release building upon the icon service introduced in Atom 1.2. Because this introduces breaking changes to customisation, it’s pitched for a major release… which presents an opportunity to introduce other features of considerable importance. This tasklist was opened to provide a central platform for feedback and discussion.

Tasklist and progress tracking is now managed using a GitHub project.

To begin testing v2, run the following:
Still being developed. Please hold off until it’s stable again.
Stable again. Go nuts:

cd ~/.atom/dev/packages/
git clone https://github.com/DanBrooker/file-icons.git
cd file-icons && git checkout v2-staged
apm install .
atom -d .

Related pull-request: atom/tree-view#966

Key features

• Case-insensitive matching:
  Capitalisation no longer matters for (most) extensions: .HTML, .html or .hTMl all test the same.

• Easier customisation:
  CSS classes are now used to set colour and icons, sparing users from having to include Less files or squabble with package/theme-specific styling. Icons can be easily changed with a single rule in a user’s stylesheet:

  // Not a fan of elephants? No problem.
  .php-icon:before { content: "\f147"; }
     
  // Something that suits your theme a little better...
  .medium-orange { color: #b8743d; }
  

• Language overrides:
  Icons will change in response to user-set languages for certain files.

• More maintainable:
  File-matching is now handled with a configuration file instead of burying hacky patterns in Less source. A priority property also allows easier sorting of which patterns are matched first.

• Modeline/hashbang recognition:
  Files with #!/bin/sh or the like will now display accurate icons

[Alhadis]

@ccorcos, you’ll be happy to know shebang recognition is really starting to shape up:

[Alhadis]

Okay, this is the point where I need feedback on something. Is having icons for JS/CSS framework files a good idea? And should we have a package option to disable them if a user chooses?

Normally I avoid adding settings that do whatever a user can already do with CSS… but if a user wants all JS and CSS files to show their proper icons, they’re faced with a lot of stylesheet hackery. Makes sense to me, but part of me feels it’s overdoing it.

Paging other maintainers for opinions: @ckross01, @DanBrooker , @astephenb