Facebook Twitter

A successful Git branching model » In this post I present the development model that I’ve introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful.

A successful Git branching model »

I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. I won’t talk about any of the projects’ details, merely about the branching strategy and release management. It focuses around Git as the tool for the versioning of all of our source code. Why git? ¶ For a thorough discussion on the pros and cons of Git compared to centralized source code control systems, see the web.

But with Git, these actions are extremely cheap and simple, and they are considered one of the core parts of your daily workflow, really. As a consequence of its simplicity and repetitive nature, branching and merging are no longer something to be afraid of. Enough about the tools, let’s head onto the development model. Decentralized but centralized ¶ The main branches ¶ develop.

Game dev

Mobile apps. Html5. Understanding Digital Image Interpolation. Image interpolation occurs in all digital photos at some stage — whether this be in bayer demosaicing or in photo enlargement.

Understanding Digital Image Interpolation

It happens anytime you resize or remap (distort) your image from one pixel grid to another. Image resizing is necessary when you need to increase or decrease the total number of pixels, whereas remapping can occur under a wider variety of scenarios: correcting for lens distortion, changing perspective, and rotating an image. Even if the same image resize or remap is performed, the results can vary significantly depending on the interpolation algorithm. Itis only an approximation, therefore an image will always lose some quality each time interpolation is performed. This tutorial aims to provide a better understanding of how the results may vary — helping you to minimize any interpolation-induced losses in image quality.

Doxygen. Generate documentation from source code Doxygen is the de facto standard tool for generating documentation from annotated C++ sources, but it also supports other popular programming languages such as C, Objective-C, C#, PHP, Java, Python, IDL (Corba, Microsoft, and UNO/OpenOffice flavors), Fortran, VHDL, Tcl, and to some extent D.


Doxygen can help you in three ways: It can generate an on-line documentation browser (in HTML) and/or an off-line reference manual (in ) from a set of documented source files. There is also support for generating output in RTF (MS-Word), PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The documentation is extracted directly from the sources, which makes it much easier to keep the documentation consistent with the source code. Praxisbuch Objektorientierung – 8.2 Die Präsentationsschicht: Model, View, Controller (MVC) Ein sehr erheblicher Teil der Funktionalität auch von objektorientierten Systemen spielt sich bei der Interaktion mit dem Anwender von Software ab.

Praxisbuch Objektorientierung – 8.2 Die Präsentationsschicht: Model, View, Controller (MVC)

Für die Modellierung dieser Interaktion in der Präsentationsschicht gibt es verschiedene Ansätze. Am weitesten verbreitet ist dabei der so genannte MVC-Ansatz (Model-View-Controller). Mit Model-View-Controller (MVC) wird ein Interaktionsmuster in der Präsentationsschicht von Software beschrieben. MVC ist wohl einer der schillerndsten Begriffe im Bereich der objektorientierten Programmierung. Viele Varianten haben sich herausgebildet, teilweise einfach aufgrund eines falschen Verständnisses des ursprünglichen MVC-Musters, teilweise als Weiterentwicklung oder Anpassung an neue Anwendungsfälle.

Da es sich bei MVC nach wie vor um das wichtigste und verbreitetste Muster für die Präsentationsschicht von objektorientierten Anwendungen handelt, gehen wir in diesem Kapitel ausführlich darauf ein. 8.2.1 Das Beobachter-Muster als Basis von MVC. Code Conventions for the Java(TM) Programming Language: Contents. Programming.


- WiiYourself! - gl.tter's native C++ Wiimote library. The Wiimote C Library. Microcontroller. 1k demo submission [793] Neural network res. Serving Static Files from Node.js. Posted: 5/6/2011 12:14 PM In the last post I showed you how to get started with Node.js on Windows.

Serving Static Files from Node.js

Easy, wasn’t it? Remarkably so since there was no install requirement. This time we are going to tweak the system a bit then learn how to return static files like plain ol’ Html, Css and Javascript files. Note, for posterity's sake, that all of this is based on node.js as of version 0.4.7. Making Things Easier Last time we got started by unzipping the file that contained all the node files. Computer > Right-click and hit properties > Advanced System Settings (on the left) > Environment Variables > System Variables > Path > add “C:\Program Files\Node” So now the files that we use can be in a directory all their own and you still only have to type “node.exe server.js” to get started.

And another tip, keep Fiddler open while you mess around with node. Serving Up A File First, let’s create a very basic html page. <html><head><title>Rockin' Page</title></head><body><p>This is a page. And voila! Videos. Launch4j - Cross-platform Java executable wrapper.