Skip to main content

Pimp my Ubuntu, Cinnamon style

Some relationships are just not meant to last - c'est la vie. Be it the timing, emotional state, or the fact compiz takes up shit load of CPU in still water.
Unity, I think it's time we see other user interfaces.

A rather short Googling session had led me to this post, which really spoke to my heart. The installation was fast and painless, and once I re-logged in things began to look up and beautiful.
Perhaps going with Mint in the first place would have been the smart thing to do, but given that  I was in too deep and already had Ubuntu 12.04 installed with no desire whatsoever to go through the process of installing a fresh OS, this seemed like the perfect solution.

So Cinnamon it is, and while we're at it, a few addons that have made it to the finals in my book:

  • debimint's Light & Dark Void theme pack, I hit if off with the light version.
  • Window List With App Grouping applet so you could have multiple instances of the same application grouped Windows 7 style. Don't forget to add this applet to your Applets list once you've installed it according to the instructions on its home page.
  • Consider the Zukitwo theme, and make sure to "sudo apt-get install ubuntu-gnome-default-settings" in case it causes some windows to have a background making text unreadable (not a pleasant sight).
  • If you use the Ambiance theme, or some other theme that makes it hard to tell the active terminal tab apart from the inactive ones, you may want to change the color of the active tab in (gnome) terminal, all credit goes to this post. Open "/usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css", and change the background-image to use orange (#fb9267) instead of the @fg_color. The final block looks like so:
.notebook tab:active {
    background-image: -gtk-gradient (linear, left top, left bottom,
                                     from (shade (#fb9267, 1.1)),
                                     to (shade (#fb9267, 1.02)));
    -unico-border-gradient: -gtk-gradient (linear, left top, left bottom,
                                           from (shade (@bg_color, 0.84)),
                                           to (shade (@bg_color, 0.8)));



Popular posts from this blog

Sending out Storm metrics

There are a few posts talking about Storm's metrics mechanism, among which you can find Michael Noll's postJason Trost's post and the storm-metrics-statsd github project, and last but not least (or is it?)  Storm's documentation.

While all of the above provide a decent amount of information, and one is definitely encouraged to read them all before proceeding, it feels like in order to get the full picture one needs to combine them all, and even then a few bits and pieces are left missing. It is these missing bits I'll be rambling about in this post.

Dependency Injection - The good, the bad and the ugly

The Good
Dependency injection (DI, a.k.a IoC - inversion of control) is a well known technique to increase software modularity by reducing coupling between modules. To provide the benefits of DI, numerous DI frameworks have arisen (Spring, Guice, Castle Windsor, etc.) all of which essentially give you "DI capabilities" right out of the box (these frameworks tend to provide a whole lot more than just "DI capabilities", but that's not really relevant to the point I'm about to make). Now, to remove the quotes around "DI capabilities", let's define it as a DI container - a sack of objects you can manipulate using a provided API in order to wire these objects together into an object graph that makes up your application.

I've worked on quite a few projects employing Spring, so it will be my framework of reference throughout the rest of the post, but the principles and morals apply just the same.