Using Android Support V7 Appcompat on Eclipse

Had an interesting request - customer wanted to convert the Android Studio project to Eclipse - I did that and found a couple of weird errors including:


error retrieving parent for item: No resource found that matches the given name 'android:Widget.Material.Button.Colored'.

when importing the Android Support V7 AppCompat library into Eclipse. The solution is fairly simple!

Just change the Android SDK to 23 (the latest/ Right click on appcompat project and click on Android, choose Build) and the errors will be gone.

SocketIO on Windows

I found recently that I was unable to install SocketIO on my Windows development platform.

The installation will throw out some errors.

It turns out that EngineIO on npm is the older version and will not work with SocketIO.


The workaround is to :


npm install Automattic/engine.io-client --save
on your local node project.

SocketIO will work after that.

Babel NodeJS Starter project

This is a starter skeleton NodeJS that I built for my use. I hope you will find it useful as well.

The ES6 files that you write will reside in ES6 folder:

Do note that you will need to append the suffix "-ES6" to your file. For example

hello-ES6.js

gulp watch will pick up the change and transpile it to ES5 in ./dist folder.

the gulp file resides in the ./gulp folder.

Issue 'gulp build' to rebuild all files. 'gulp clean' removes the entire dist/ directory 'gulp watch' will compile files that are newly created or modified - this is the option that you would want to issue when coding as it will run in the background and automatically pick up any changes.

There are some sample ES6 files in ES6 folder and a sample index.js file to test the transpile.

The requirements for this are :

• NodeJS
• Gulp
• Babel

In this cloned repository: issue

'npm init'

Node will download the required modules.

The location of the code is:

https://github.com/rebooting/ES6Sample

Monogame 3.4 SDK templates( Visual Studio 2013) not found after installing

I've installed Monogame SDK under a normal user account. The installer prompted for an administrator account and correctly detected that VS 2013 is present. 

Once done I was unable to find the templates in my normal user account, turns out that the templates were installed in the

  Documents\Visual Studio 2013\Templates\ProjectTemplates\Visual C#

directory. Copy the files into the same directory structure in the normal user account and the project templates will show up.