Posts Tagged ‘web’

These times

Monday, October 26th, 2009

These are crazy times for me! And that’s true in many ways:

In the last months I’ve been working with three very innovative mobile development frameworks – each of which is remarkable in its own way. I’ve to hate and love all of them and I’m so thankful that I got this chance at all! I’m very happy that I did not loose touch to my old colleagues at WebDev/WebSalesDev and still see them every once in a while.

I’m also working on a very interesting project in my spare time with my buddy Lino – I hope we can give you an update about this soon.

And I’ll be back to Mosbach, soon. I’m so curious about what’s up next – crazy times everywhere I look :-)

In the meantime: I’m afraid I often don’t have the time to post new content here – and some things pass by so fast I just don’t feel like they’re necessary or that important at all.

Stay tuned!

Google Wave and IE-Support

Friday, September 25th, 2009

So after all Google has developed its Chrome Frame plugin for Internet Explorer for a good reason: enabling the majority of users – which are unfortunately still using Internet Explorer (6,7 AND 8) to have a better experience with HTML5-based websites.

Lars Rasmussen posted on the Google Wave Developer Blog that Wave will inform Internet Explorer users to install Chrome Frame for a better user experience. Reason being that Internet Explorer is just too slow at interpreting JavaScript and DOM Manipulations – features Wave heavily relies on. IE’s support of modern web standards such as HTML5 is pretty poor, too.

I’ve been experiencing the same issues with IE over and over for myself – yet in a smaller dimension: Every hour (and it have been many hours) a developer spends on the specific quirks on IE (which of course are different per each version) and to fix them for their application is not spent on adding cool new features or bug fixes which affect general issues.

Since this has been a problem for so a long time I hope this finally helps to fix this issue.

Making Wordpress Upgrades easier with Subversion

Wednesday, August 12th, 2009

This morning I just realized how easy it could be to upgrade my Wordpress installation. Since I didn’t want to upgrade via SFTP (would have required me to install an FTP server first, so *lazy*) and manually upgrading is some kind of awful I was happy to find this article at the Wordpress codex: Updating Wordpress with Subversion

This is a really neat opportunity for all users who are familiar to Subversion and really speeds up upgrades for me since I just will need to switch to the latest release-tag (one should not use the trunk since this may not be stable) and should be fine. Until now, upgrading my blog really was a pain in the ass, but now it’s fun again…

creatified.com now with a wide layout, slight changes

Sunday, June 14th, 2009

I updated creatified.com to now use a wider layout (960px), this will give more space for whatever is coming next.
I also included a lightbox effect for images because there were quite many of them.
And there are some fixes here and there…

Grails Instruments in public SVN now

Sunday, June 14th, 2009

This weekend I’ve been very busy on Instruments again.

Instruments now sports a core Java library which takes care of caching the states of system usage for the last time. This is included in an all new “InstrumentsService” which will provide the necessary methods to controllers.

At the moment this is all trimmed for using flot. There are no other “export options” for now.

I decided to make this publicly available in my Subversion repository. You can checkout the source tree of the Grails application here:

http://creatified.com/svn/creatified/Instruments/

The trunk includes the latest development version. Don’t forget the “grails upgrade”-command after checking out the source tree.

When you run the app, all you’ll find there for the moment is the following site which will be located unter http://localhost:8080/instruments/

You will then be able to see something like this:

Instruments - CPU

for the CPU usage and this:

Instruments - Memory

for the Memory usage

This will be all for now, be sure to check out your own version – I’ll also be testing this on the Google AppEngine soon.