-
Notifications
You must be signed in to change notification settings - Fork 302
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
Platform overrides #94
Conversation
} | ||
}); | ||
|
||
return Promise.all(copiedFiles); | ||
}; | ||
|
||
NwBuilder.prototype.getZipFile = function(platformName){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is instead of this._nwFile
because we could now have multiple (ZIP) files. Also, this.getZipFile('osx')
is a lot clearer than this._nwFile
anyway.
Nice work, I'll have a look at it over the weekend |
One downside to this is that it's not supported by node-webkit so if you run But thinking about it now, is node-webkit-builder's run option intended for dev yeah? I've never used it. So does that mean that it's suggested the user doesn't use shama/nodewebkit at all? I didn't actually apply the platform overrides when using the run option. |
Ok, I've decided the run method will not support platform-overrides. It doesn't make sense since run is just meant to take existing files and pass them to node-webkit. It doesn't create a ZIP, temporary files, etc. The note in the README already covers this;
I guess this means that someone will have to create a Grunt plugin though to wrap platform-overrides for dev. @steffenmllr did you have a chance to look over it? |
Once this is merged, I'm also going to see if node-webkit would like this kind of functionality as part of the core. |
LGTM. I also think supporting multiple platforms for run doesn't make sense. You could merge the commits into one feature commit if you like to. |
Yeah ok, I'll squash & rebase them there now. |
0f27683
to
df45f72
Compare
df45f72
to
eed864b
Compare
Ok, after a bit of a battle... they're squashed & rebased. |
Fixes an issue with node-webkit notifications -- nwjs/nw.js#27 (comment)
0.9.2 and below do not include the locales folder.
fc2d876
to
d263166
Compare
I missed a dependency earlier. I commited the fix after I had already pulled in from master, then I tried to squash the fix back with my old commit and now I've mangled everything. It seems some old commits are duplicated :/ |
OK, I ended up having to take a patch from this PR and apply it to a new branch created off master, then squash & rebase again. Merge #99 instead. |
Feature request for support in node-webkit itself: nwjs/nw.js#2542 |
Ok so this resolves #85. See the changes to the README to see how to use this feature.
I'd appreciate it if someone could have a look over this, test and see if I'm missing any use / edge cases or tests.
In particular I'm going to add comments in a couple of places where I think my promise handling doesn't need to be as complex as it is.
So what happens now is:
platformOverrides.osx
exists in the manifest, for example.package.json
during the copying step and just write a new one instead.cc @steffenmllr, @gabepaez, @dylangattey