Christos Monogios

Recently I decided to transfer my personal blog which is implemented with Jekyll from GitHub to Bitbucket and access it with the Aerobatic addon.

Here is a compact list of steps you have to follow if you also want to host your Jekyll blog on Bitbucket:

When working with less you most probably have to do some calculations and assign their result in a CSS property, for example into a width of a CSS class or a margin of an CSS id.

Apart from the calculated number you want to generate valid CSS code, so you also have to apply a measuring unit to this number, for example pixels or ems or percentages.

The TypeScript language was created from Microsoft as a super-set of typed-rules for JavaScript. The language contains features that one finds in C#, something that is completely understandable since the inventor of TypeScript also invented C#.

TypeScript provides interfaces that are used for two main reasons:

1. Standardize/ Giving a type to an object, by defining the properties that an object contains.

2. Define a structure of properties and/ or functions that a class has to implement. Doing this way you can define multiple implementations that implement the interface. In this case, the interface works as a contract (known best practice term from C#) that the classes have to respect.

When using Angular.js and something goes wrong with your code, the first place to look for an error message that came from your JavaScript code is in the console of the browser debugger that you use (for example Chrome developer tools or IE F12).

In the following list you see a collection of common error messages that you will most probably come along when you implement web application with Angular.js. Together with each message you see a quick solution to fix your code:

When dealing with User Experience and user interfaces you often have to do with prototyping an idea or a concept, before going to the implementation of it. Doing this way you want to get a first impression of what you are about to implement. Prototyping can be divided in two categories:

1. Low fidelity prototyping: You create sketches, also known as wireframes, of the user interface you want to program. For creating these sketches you use either a pen and a paper or one of the many available software to draw the sketches digitally. This software can either be a professional one (Photoshop) or a more pen & paper like, like Balsamiq.

2. High fidelity prototyping: You implement a small part of the future application with a limited number of features. The application is testable and you can navigate from the one page to the other. Here the business logic plays a secondary role, the user interface the preliminary. A high fidelity prototype could also be considered a collection of Photoshop designs, each representing a page of your application, that are combined together to build a fake navigation from the page to the other.