Dev Stuff

Well, "DevStuff" makes these pages sound "grand" (no sarcasm). But they are "grand" (with sarcasm). :-)

Reminders for git

I forget okay?!?!?

1. Tell Git your name so your commits will be properly labeled. Type everything after the $ here:

git config --global "YOUR NAME"

2. Tell Git the email address that will be associated with your Git commits. The email you specify should be the same one found in your email settings. To keep your email address hidden, see "Keeping your email address private".

git config --global "YOUR EMAIL ADDRESS"

3. Tell Git to ignore all files modified locally & reset to last fully committed version. This could be useful for getting a local branch to state where one can pull everything from a remote repository. If there are files that are needed to be re-added, they are identified when doing the pull that failed.

git reset --hard

4. Setup & pull from upstream. First commands adds repository for upstream source code. Second command grabs all the changes.

git remote add upstream [url to upstream repository]
git fetch upstream

Node.js / NPM / Exploring Universal Apps

Just notes & thoughts in trying to write an app that runs on most major OSs. Right now, to keep it simple, I'm only thinking Linux (well, Kubuntu) and ChromeOS (well, CloudReady).

Post-thoughts in a pre-way: Restructure to share common files & create build file to put appropriate files in location for packaging.

Starting with Electron

Electron is a way to build a desktop app out of HTML5/CSS/Javascript. It gives you the tools to talk to the OS and wrap it up into a single app. The Atom editor is an example. Some things to get an app started:

  1. Start an empty repository however you want. For ease I start an empty project on Github, clone locally and then start adding stuff to it.
  2. I created a folder called "electron_app" and copied to it the index.html, main.js, package.json and renderer.js files from their Quick Start sample. Be careful about licensing.
  3. From their Quick Start tutorial, go to that directory and npm install to get all the required modules.
  4. Again from their Quick Start tutorial, in that directory, npm start to launch the app.
  5. I added a bunch of CSS and stuff from websites I've worked on to make a fake app. Only big note is "./" sorta "clears" the page; i.e. no index.html is displayed.
  6. To build manually, I created a build directory and started to go through their Application Distribution page.

More to come...