Structure

[odensc]

We should decide on what we want to do: (if something is not listed here that you want to suggest, say in the comments)

• Node & Webkit Implementation
  • atom-shell
  • node-webkit / nw.js
• Build System
  • Gulp
  • npm scripts
• Frameworks / Libraries
  • React
  • jQuery
• Language
  • ES5 (current)
  • ES6/7 (Babel)
• Modules
  • SystemJS
  • browserify / nw.js builtin require
  • Multiple scripts with globals
  • One file (might be messy)

[CyrisXD]

@thesbros @skibz

I would prefer to keep gulp out of it, but I am happy to change if you guys feel strongly about it. I'll just need to learn Gulp, and most things mentioned above. Haha

[skibz]

my personal preference is to use npm scripts, es5, and node's built-in require. while keeping the cognitive load low for everyone, this might even help make this project easier to contribute to by first time contributors.

but i'm also open to using other tools :+1:

[TheDrDocter]

@thesbros Isn't nw.js (Node-webkit 12) still in alpha? I would rather leave that aside. Also, I've never heard of Gulp before this, and from my understanding it helps simplify the code? Looking at this project it seems to be ok, but I have no idea on what this exactly does, like CyrisXD, I have just learned about most of the things on the list

[odensc]

@TheDrDocter I meant node-webkit / nw.js. I'll edit

[1j01]

You should use nw.js and its require, and include all functionality (building, running) in npm's scripts. You probably don't need gulp or anything like that. Just use node-webkit-builder. You should put the app in app/ , and "scripts": {"start": "nwbuild -r app", "build": "nwbuild -p win32,win64,osx32,osx64,linux32,linux64 app"} Once you have that set up, you could add a "bin" script to run it, and publish steam-roller to npm, so people can run npm i -g steam-roller to install and then run steam-roller to launch the app. React and jQuery are both fine, as long as you never use them together.