Archive for January, 2013

Home » January 2013

Developing with Apache Wicket

I've been working with Apache Wicket on a rather complex client project for quite some time now and I'd like to share my experience. Apache Wicket is a component-based web app framework for Java. In contrast to MVC frameworks such as Rails (or Play and Grails in the Java world), which map requests to controller actions and views, Wicket is more similar to stateful GUI frameworks like Swing. Wicket applications are made up of trees of components. Each Wicket page is a root ... Read more

(Deutsch) Piraten auf Abwegen?

Sorry, this entry is only available in German. Read more

Live Tools For Building Website Elements

Ui Parade have released a series of design tools that allow you to have common website elements generated in HTML / CSS: These tools include: Button Builder Form Builder Icon Bulder Ribbon Builder Have a look at Ui Parade's actual website, too. It lists quite a bunch of useful and inspiring design elements. Read more

Regexper: Visualize Regular Expressions

Regexper is a new visualization tool that renders regular expressions as the equivalent finite-state machines. Very cool stuff, give it a try. Read more

WordPress Child Themes

A few days ago I read a very useful tip regarding customizing WordPress themes and why you should use child themes for that. In short, child themes allow you to extend and customize existing WordPress themes without compromising the ability to update the original theme. If instead you directly customized a theme your changes would be lost once you install an update (or have that update installed automatically). Read more

Privacy Preference Center

Strictly necessary

These cookies are necessary for the site to function.

PHPSESSID: Preserves user session state across page requests.



Google Analytics statistics cookies help us to understand how visitors interact with our websites by collecting and reporting information anonymously.

You can opt out of Google Analytics tracking by clicking on the opt-out link in the banner below.

_ga: Registers a unique ID that is used to generate statistical data on how the visitor uses the website.

_gat: Used by Google Analytics to throttle request rate.

_gid: Registers a unique ID that is used to generate statistical data on how the visitor uses the website.

ga-disable-UA-25326096-9: Stores whether you have opted out of Google Analytics tracking.



These cookies are used for storing your privacy settings

gdpr%5Bprivacy_bar%5D: Privacy settings have been reviewed.

gdpr[consent_types]: The uses of your data you agreed to.

gdpr[allowed_cookies]: The cookies you allowed us to set.

gaoop_hide_info: Set if you agreed to our use of Google Analytics.



We use Wordfence to secure our website against hacking attempts:

Cookies set by the Wordfence plugin
To help you understand which cookies the Wordfence plugin sets, when installed on your WordPress site, we have provided the guide below. Wordfence currently sets three cookies and we explain what each cookie does, who will have the cookie set, and why the cookie helps secure your site.

What it does: This cookie is used by the Wordfence firewall to perform a capability check of the current user before WordPress has been loaded.

Who gets this cookie: This is only set for users that are able to log into WordPress.

How this cookie helps: This cookie allows the Wordfence firewall to detect logged in users and allow them increased access. It also allows Wordfence to detect non-logged in users and restrict their access to secure areas. The cookie also lets the firewall know what level of access a visitor has to help the firewall make smart decisions about who to allow and who to block.

What it does: This cookie is used to notify the Wordfence admin when an administrator logs in from a new device or location.

Who gets this cookie: This is only set for administrators.

How this cookie helps: This cookie helps site owners know whether there has been an admin login from a new device or location.

What it does: Wordfence offers a feature for a site visitor to bypass country blocking by accessing a hidden URL. This cookie helps track who should be allowed to bypass country blocking.

Who gets this cookie: When a hidden URL defined by the site admin is visited, this cookie is set to verify the user can access the site from a country restricted through country blocking. This will be set for anyone who knows the URL that allows bypass of standard country blocking. This cookie is not set for anyone who does not know the hidden URL to bypass country blocking.

How this cookie helps: This cookie gives site owners a way to allow certain users from blocked countries, even though their country has been blocked.


Close your account?

Your account will be closed and all data will be permanently deleted and cannot be recovered. Are you sure?