NetTuts.com has posted the next part in their series (the looking at the SOLID development principles discussing the Dependency Inversion Principle , the final letter in the “SOLID” acronym. It would be unjust to tell you that any one of the SOLID principles is more important than another. However, probably none of the others have such an immediate and profound effect on your code than the Dependency Inversion Principle, or DIP in short. If you find the other principles hard to grasp or apply, start with this one and apply the rest on code that already respects DIP. They start off with a basic definition of the dependency inversion principle and an example of it in a more real world situation. They use it to separate out the handling of reading and rendering PDFs and eBooks. It’s just some basic code, no real functionality, but it gives you an idea of how to architect the application. Link: http://code.tutsplus.com/tutorials/solid-part-4-the-dependency-inversion-principle–net-36872

The rest is here:
NetTuts.com: SOLID: Part 4 – The Dependency Inversion Principle

While the awesome Apache Camel team is busy fixing the handling of the multiple parameters in the query, here’s a workaround. Hopefully, this post will become obsolete with the next versions of…

Read the original post:
Camel CXF Service With Multiple Query Parameters

Matthias Noback has shared a few things he doesn’t like about Symfony bundles , the drop-in components that easy extend Symfony-based applications. This article could have been titled “Ten things I hate about bundles”, but that would be too harsh. The things I am going to describe, are not things I hate, but things I don’t like. Besides, when I count them, I don’t come to ten things… Instead of ten, there’s five things on his list of “hates” about bundles and their handling: Bundle extension discovery Naming conventions Registering service container extensions yourself Naming conventions, part two Duplicate knowledge: the extension alias For each section there’s an explanation and sample code where needed to illustrate the point. Link: http://php-and-symfony.matthiasnoback.nl/2013/10/symfony2-some-things-i-dont-like-about-bundles/

View original post here:
Matthias Noback: Symfony2: Some things I don’t like about Bundles

Gonzalo Ayuso has a recent post to his site showing you how to use Stack to create bundles for your Silex-based applications. Stack is a structure that allows for the reuse of HttpKernelInterface middleware to create a custom “stack” of functionality. Nowadays almost every modern framework/applications implements HttpKernelInterface (Symfony, Laravel, Drupal, Silex, Yolo and even the framework that I’m working in ;) ) and we can build complex applications mixing different components and decorate our applications with an elegant syntax. The first thing than come to my mind after studying Stack is to join different Silex applications in a similar way than Symfony (the full stack framework) uses bundles. In his example, he shows an example of a simple GET endpoint for a blog and API. In the first version, he calls the “run” method to execute the handling of the request. The second example, however, includes the attachment of a simple “MyKernel”

Excerpt from:
Gonzalo Ayuso: Bundles in Silex using Stack

The latest version of darktable shines a light on support for the Canon EOS D700 and Nikon Coolpix P330. Colour handling and bug fixes also serve to improve the photo workflow management application…

Read more from the original source:
Darktable 1.2.2 Adds New Cameras

Red Hat and Rackspace Hosting have announced that they have won the dismissal of a patent suit by Uniloc USA. Uniloc was asserting patent #5,892,697, which relates to the handling of floating-point numbers. “In dismissing the case, Chief Judge Leonard Davis found that Uniloc’s claim was unpatentable under Supreme Court…

Go here to see the original:
Red Hat and Rackspace Face Down a Patent Troll