January 26th, 2012 |
by akoelewijn |
published in
open standards, web
I’ve been using When can I use… quite a bit recently. It enables you to quickly determine if a html5, css3 or svg feature is enabled in all the different browsers. Very useful.
January 17th, 2012 |
by akoelewijn |
published in
open standards, oss, web
I’m working on a small javascript library to use svg drawings for presentations. This would allow you to display a single svg drawing similar to normal presentations on slideshare or speakerdeck. You can see the current state here: SVG Presenter test. I wanted to see if you can use webfonts in an svg drawing in [...]
January 3rd, 2012 |
by akoelewijn |
published in
open standards, web
I create most of my presentations using Inkscape (here’s an example: Presentation: Introduction to Scrum). This is quite a bit of work, as i need to export all the separate images, and import them into LibreOffice Impress. I’ve created a small javascript script that can be used to directly use the svg image as a [...]
September 8th, 2011 |
by akoelewijn |
published in
software development, web
Derick Bailey has some good advice regarding the backbone router: Stop Using Backbone As If It Were A Stateless Web Server. A javascript application using backbone is stateful, and implementing MVC doesn’t mean that all actions have to be handled by the router. Only use the router when you want to expose a url in [...]
September 2nd, 2011 |
by akoelewijn |
published in
software development, web
Single page web applications have been around for a while. Applications that run all user interface code in the browser using Javascript to update the user interface. The application server only exists to provide access to data and business logic. However, most Java Enterprise web applications i encounter still use serverside web technology like jsf, [...]
August 22nd, 2011 |
by akoelewijn |
published in
architecture, java, open standards, oss, software development, web
One of the main goals that Software architects try to achieve is to design solutions that will last a long time. You’ll often hear an architect say that the product will have a life span of about ten years, and that all technical choices should support this goal. This means that any framework you select [...]
December 16th, 2010 |
by akoelewijn |
published in
architecture, soa, web
A few weeks ago there was a question about REST on the SOA-BPM Enterprise Methodology Group about The End Of The Road For Web Services. I posted the following reply to the list. It’s my view on the whole SOAP versus REST discussion. (short summary: somebody decided to fix http for rpc usage, without understanding [...]
June 13th, 2010 |
by akoelewijn |
published in
java, oss, soa, web
The following example illustrates how you can implement a composite service using Apache Camel. The service is exposed as a REST resource, and it uses two other resources to collect the data required. The composite service will enable a client to get info on a customer and it’s orders. To get this data the composite [...]
January 5th, 2010 |
by akoelewijn |
published in
cloud, mobile, oss, web
Google used to be a search company making profit on adds. Today’s release of the Nexus One ‘superphone’ illustrates that Google is turning into the next Microsoft: a supplier of software platforms and applications. The Nexus One isn’t a phone, it’s a device to access the web. It’s just another Operating System to use applictions, [...]
November 6th, 2009 |
by akoelewijn |
published in
cloud, soa, web
Recently David Pogue suggested smartphones like the iPhone should be called app-phone instead. I think focussing on the apps is wrong. For me, the thing that the iPhone does better than most other phones is internet access. The iphone is a net-phone. It is your mobile internet terminal. But it’s more than that, it’s also [...]