Windows Support

[mcolyer]

🚨 The staging area for windows support. 🚨

• Get core dependencies installable
  • bootstrap fails on clone
  • git-utils builds in windows Port to Windows git-utils#7 (enables git-utils, scandal and collaboration)
  • pathwatcher builds in windows Windows support node-pathwatcher#1 (enables pathwatcher)
• Get dev dependencies installable
• Get core packages installable
  • keytar builds in windows Use Credential vault to manage passwords on Windows. node-keytar#2 (enables github-sign-in, gists and release-notes)
  • spellchecker builds in windows Port to Windows node-spellchecker#1 (enables spell-check)
  • ctags builds in windows Fix building on Windows node-ctags#1 (enables symbol-view)
• Get language-* packages installable
• Get atom's bootstrap to complete

Issues

• atom/apm/src/auth.coffee "security" doesn't exist on windows.
• grunt-coffeelint/node_modules/coffeelint/package.json: "install": "[ -e lib/commandline.js ] || npm run compile",
  You can't use bash in your install script.
• Convert backslashes to forward slashes (git icon doesn't appear in tree-view)
• Fuzzy finder doesn't load
• Crashes after several seconds when autocomplete, archive-view and bookmarks are loaded (but not each package independently.

Development Environment Notes

• Install Visual C++ 2010 Express - English from Microsoft
• Install the latest node 0.10.x from http://nodejs.org, 32bit
• Install the latest python 2.7.x from http://python.org, 32 bit
• Install Github for Windows
• Add C:\Python27;C:\Program Files\nodejs;C:\Users\IEUser\Documents\GitHub\atom\node_modules\ to your PATH
• Set ATOM_ACCESS_TOKEN to your oauth2 credentials (run security -q find-generic-password -ws 'GitHub API Token' on OSX to get your credentials).
• Launch Github for Windows, sign in, clone Atom.
• Use the git shell and cd into your atom checkout.
• Run script/bootstrap

[kevinsawicki]

@mcolyer I see the same crash as you on my vm when activating all the packages.

The weird thing though is that the packages activate just fine if I activate one package per second using setTimeout.

[kevinsawicki]

@mcolyer This branch is 📗 now, what do you think about merging what we have here and moving the remaining todos to an issue or new pr?

[mcolyer]

I'm down with that (merging now). I've got a few ideas around what's left so I'll make the appropriate tickets also.