Fix for #139

[bastimeyer]

This fixes #139...
handleMacApp and handleWinApp haven't been upgraded after the platform name changes.

[bastimeyer]

Please don't merge this yet, there is an issue regarding the package.json and utils.getFileList which needs to be fixed first...
I'm using a seperate package.json for node-webkit other than the package.json for the main project. This file lies in a subfolder, in addition to the one in the root folder. For some reason, the file inside the subfolder is being read from while building the application. This of course raises some errors because I don't have copyright informations set in this file (e.g. the osx-plist file is failing).

[adam-lynch]

@bastimeyer brilliant that you're helping with this!

One thing, can you not introduce changes to whitespace? See our .editorconfig, indentation should be four spaces. EditorConfig is really handy, if you install the plugin for your editor it'll automatically pick up what the indentation should be :).

[bastimeyer]

Where did I change the indentation style?

[adam-lynch]

Ugh sorry 👍, I thought those four spaces were tabs because of how they look in the diff

[bastimeyer]

Please ignore what I was talking about earlier. I wasn't aware, that this "package.json bug" was working as intended for the whole time.
The issue I had was caused by npm, which didn't resolve the dependencies of the grunt plugin properly, so I was using an old version. My PR from a couple of days ago (1447f08) already should have caused my own builds to fail, because of the way I am using a second package.json as I mentioned above.
The dependency issues are resolved now since the upgrade to 1.0.0 though... The sad thing for me is, that I released a bugged osx version of my application during this time span and didn't even notice 😞

Should I squeeze these commits or is this ok?

[adam-lynch]

Oh, lucky you :/.

So this is ready yeah?

[bastimeyer]

Nevermind... squeezed it...

What I also wanted to ask: should the copyright informations be mandatory? Right now they are and this is what caused my earlier confusion (paired the the npm issue and the package.json stuff ofc)

[bastimeyer]

Oh, didn't see your post.. It should be good now

[lucienimmink]

This does fix the winIco but breaks compiling osx on 1.0.0; paths can't be resolved correctly when using the macIcns option; omitting that option results in an error that the plist file can't be found :s

[bastimeyer]

I can't reproduce any of these said errors. Yes, these methods are not covered by any test cases, but I tested it manually by using different configurations, and even though, all I did was adding the _forEachPlatforms call. So the build logic shouldn't be affected by these changes.
Did you pull the recent commit? As you can see, I have pushed multiple commits - my first one was a mistake and only fixed the windows builds when building one architecture at a time, so please don't use that...

[adam-lynch]

@lucienimmink did you see the reply above?

[adam-lynch]

I assume it's fixed, we'll patch if not ASAP