We're growing into something new. Read More

Martin N.

<!doctype html>
<html lang="en">
        <meta charset="utf-8">
        <!-- Those link targets do not really make sense, they just demonstrate this feature -->
        <link rel="prev" href="http://www.google.com" />
        <link rel="next" href="https://www.github.com" />
        <script src="flipAhead.js" type="text/javascript"></script>
        <script type="text/javascript">
            document.body.addEventListener("touchstart", FlipAhead.handle, false);
            document.body.addEventListener("touchend",   FlipAhead.handle, false);

Flip Ahead Browsing for everyone!

Internet Explorer allows to swipe to logically next or previous content. Say, for example, you come to a blog and read a blog post. You may want to check out the previous or next post, but have never been to those pages (so they're not in your browser history and not reachable thru next/back buttons or gestures) - now IE introduced a small piece of markup: to use swipe left/right to navigate to those pages. What pages that are is entirely up to the page's author. Sadly, this is only supported in IE but I like the feature and find it extremely nice, so I thought about implementing a tiny JS library to bring this to all browsers. I wondered if it's a good idea to mess with one finger swipe gestures, so I decided to resort to two finger swipe gestures, in hope that there may form a convention eventually (I know that for now, I sacrifice a bit of usability and intuitivity here) Read a bit more at [my corresponding blog post](http://ox86.tumblr.com/post/74714078902/flip-ahead-browsing-and-a-js-polyfill) if you like or look at the sample code below... I would love to get some feedback on this!

<div id="terminal">
  <p>Type 'help' to get started.</p>
  <p class="hidden">
    <span class="prompt">guest@terminal.js > </span>
    <span contenteditable="true" class="input"> </span>

Geeks love terminals, so I added one to my website.

For my personal website, [Geekonaut.de](http://www.geekonaut.de) I wondered how to make it accessible for normal people visiting it as well as spicing up the experience to match with what I am: A geek who spends a lot of time in terminals. So I asked a few people, what they would think about accessing a website from the terminal - and most would love that, however most of the websites today are horrible to use in text-based browsers such as w3m and it is not available everywhere. So I decided to give my website 3 ways of interacting 1.) The normal website 2.) A javascript-based terminal that works in any browser and resembles a UNIX terminal. 3.) A telnet version of the terminal. You find the [web terminal here](http://www.geekonaut.de/console.html) and the Telnet interface at geekonaut.de Port 2342. If you'd like to use the web terminal, check out the [Github repository for it](http://github.com/avgp/terminal.js). Have fun :)

Codegrade - Automated code quality reports

How good is your code? No, I mean: Really? Yes, there's a whole bunch of tools to answer that question. But they require maintenance, configuration and you need to run them somehow and keep an eye on the results. But you wanna code, right? Build an ├╝berawesome product! Focus on it. Codegrade got your back - just sign up with Github, select the repositories to watch and get reports when the quality decreases or problems appear. Codegrade aims to be for all languages, but for now it'll support Javascript and Ruby. More is scheduled.

Cloud9Hub - multi-workspace, self-hosted Cloud9 IDE

Cloud9 (http://c9.io) is a really awesome, open-source IDE that runs in your browser. Besides the usual things an IDE gives you, it also features a full-blown terminal, git and mercurial integration and deployment assistance. It is even open source, so that you can host it yourself - however: That came at a price: No multiple workspaces, only one. Having many projects I couldn't cope with having to restart the Cloud9 instance in order to change workspaces. The need to go on the server and restart it whenever I want to switch projects breaks with the idea of Cloud9 being a web-based IDE, so I wrote a little express.js-based tool to fix that: Cloud9Hub. With Cloud9Hub you basically get a simple dashboard (like c9.io offers it, but much simpler and less powerful). You can: * Login via Github * Restrict sign in to predefined users * Run multiple workspaces in parallel * Have multiple users * Create new workspaces * Delete workspaces * Fully work with Cloud9 on each workspace, it integrates seamlessly. Check it out at https://github.com/avgp/cloud9hub

<h1>This is on your primary device</h1>
<div data-screen="remote">
  <h1>This is somewhere else!</h1>

Proposed web standard: RemoteDOM

Similarly to how the Shadow DOM paved the way for custom elements using web technologies, a "Remote DOM" could allow display of portions of the web app to be displayed on "remote" (i.e. "external") devices, such as screens, Smart TVs, etc. This brings interesting capabilities to web apps, such as leveraging external screens for presentation, supplemental content or second screen experiences.


Write hybrid apps using JS, HTML and CSS with Angular.js, Lungo.js and PhoneGap

We just open-sourced some of our libraries for mobile application development.

Neee.ws - making your twitter timeline more interesting

I just started the open beta for my latest project - Neee.ws. It allows you to sign in via twitter and get a stream of tweets from your timeline, ranked with a score, so that you can enjoy only the tweets matching your interests. The score is based upon your own twitter behaviour, primarily your own tweets, retweets and favorites. I tried to make the UI as simple and clean as possible and it's fluid, so it works on mobile devices and small screen devices (such as mobile phones) as well. It is build with Express.js and the Foundation framework and hosted on Heroku.


CSS 3D transforms for image slideshows

I created a tiny javascript library that allows you to have CSS animations (including 3D transforms) to create interesting image slideshows. It is not necessarily limited to images, though. The animation configuration can be done using CSS or SCSS (both files are provided in the repository). Currently, Opera lacks support for 3D transforms. If needed, Opera and IE support can be added (go for a pull request, if you like). As I don't have had much time, this is a relatively hacky solution and may have its glitches..