I love my Das Keyboard Ultimate mechanical keyboard. It feels great to type on, and the plain-black keys always raise an eyebrow :)
Unfortunately, it doesn't come as a wireless version. I've seen a number of people asking for one. And even some very impressive hobby projects. But no easy answer. However, I recently stumbled upon a near-perfect solution!
I purchased a Velocifire VM02WS Wireless Keyboard. These are wireless, almost the exact same size/shape/weight as the Das Keyboard Ultimate, and feel very nearly identical to type on (slightly softer, though still brown switches). They're also incredible value.
Now for the clever bit: the Velocifire comes with a keycap puller. Simply use the keycap puller to pull all the keycaps off your Das Keyboard and swap them with the Velocifire (they fit perfectly). You'll end up with a plain black wireless keyboard:
As a bonus, your old Das Keyboard Ultimate now has a full set of printed keys - so it can be handed down to a non-touch-typing family member :)
Update: the Velocifire is a very similar weight to the Das Keyboard, but I found it doesn't slide as easily on my desk whenever I want to change position. Thankfully, the feet have removable rubber caps. Removing the caps gives back that Das Keyboard slippiness.
I was delighted to receive a NSW Volunteer of the Year Award from the Centre for Volunteering, for my contributions both teaching and coordinating Primary Ethics at my local primary school. Primary Ethics is a volunteer-based organisation that teaches philosophical ethics to primary school children across NSW.
My thanks to the Centre for Volunteering for organising the event, and for their recognition.
One of our developers just lost a couple of days productivity (even going so far as to reinstall Windows) to a very elusive Eclipse bug. After working fine for months, his Eclipse suddenly starting experiencing significant delays (up to a couple of minutes) when trying to publish changes. Eclipse would just sit there, stuck at 0%, saying Publishing to WildFly. It did the same with other applications servers we tried (such as the Deploy Only Basic Connector).
We eventually managed to resolve this as being an issue with m2e-wtp. We found the mappings it uses under .settings/org.eclipse.wst.common.component. We then modified these mappings to copy individual webapp folders one-at-a-time. Specifically, we avoided copying very large, nested folders such as node_modules.
After editing the file and refreshing the Eclipse project, the publishing pause is gone! The developer will have to be careful that future changes (such as doing Maven > Update Project) do not override the .settings/org.eclipse.wst.common.component file, but if they do he'll just need to revert changes (we've checked the file into version control).
I'm posting this blog because we couldn't find any reference to this issue anywhere on the Internet. I can only assume it may happen for others who use Eclipse, Java EE and Node Modules together.
We're continuing to explore ways to apply Virtual Reality to non-gaming applications. Our latest prototype is to expand Wealth Projector's Adviser Interface using a complementary Virtual Reality module for client-facing meetings.
The idea is to replace the 'let me turn my monitor around' or the 'let me sketch this on some paper' moment into a richly graphical, engaging Virtual Reality experience.
Check out video of the prototype below:
