development

Calendar Widget 1.5

David Jørgensen — Mon, 26 Jul 2010 20:33:30 GMT

Been working really hard lately on the Calendar Widget.

Just to give you an idea of what is happening, here's the changelog.

NEW: Added Froyo support
NEW: Added support for multiple calendars (Google Calendars only tho)
NEW: Added support for 12 hour clock
NEW: Entirely new preference screen
NEW: Now support danish localization (you want to help with more languages?)
Changed: Removed HTC specific onClick support (may add onClick support later)
Changed: General clean up in code
Bugfix: Current week was showing wrong week

Have fun!

CalendarWidget bugtracking

David Jørgensen — Tue, 20 Apr 2010 08:50:47 GMT

Hello all..

I know I have been laying low for quite a while, but I am hoping to get back into the project soon.
Because of that I have just set up a bugtracking system, which should help me keep track of the progress.

Of course, I would like you to report any bugs, features and enhancements you'd like to see as well.

The bugtracking system is located right here

Username: widgetuser
Password: 12345

If you are reporting a bug, please provide me with as much information as possible, so it'll be easy for me to recreate the bug, and hence faster to fix.

Also, this bugtracking system may be closed down if I find a better system somewhere else. If you know a better system or just an easier, more efficient system, please let me know.

Calendar Widget Issues

David Jørgensen — Thu, 26 Nov 2009 08:55:11 GMT

First of all I would like to apologize for the lack of updates lately. Specifically I needed some time away from development since I grew tired of it. I am still not completely back on track yet, but a friend of mine have agreed to help me with development. Perhaps together we can push out some updates soon.

A couple of issues have come up on the Calendar Widget, and I will just try to mention a few of them here.

After a certain amount of time the widget will stop updating (mine did it after 12 or so days)
I have yet to find a solution, but until I do, I suggest you remove the widget and add it again

Here is the top list of things that are on the top priority TODO list

Widget stops updating after a certain amount of time (above issue)
Enable multiple calendar support
Enable support for Outlook calendar

Android and Google Calendar Widget

David Jørgensen — Mon, 31 Aug 2009 08:44:09 GMT

After a way too long period of silence on my website, I can now return to tell you that I've begun working on Googles mobile platform: Android. It all started with me getting quite interested in the new HTC Android smartphones. And of course, being a gadget guy I, of course, had to have one. This also seemed like a good alternative to the infamous iphone.

Well, to be honest, the iphone is not really an alternative, since I could never dream about getting myself an iphone. yuck. :-)

Anyways, I quickly got into the Android platform (and hence Java), and decided to create a calendar widget. This decision was taken after hearing lots of people not fully satisfied with the calendar widget that HTC had delivered (which only displays 1 event).

After little over a week in development I am now almost at a point where I feel it's *almost* ready for an "official" release, and below is a screenshot of how the widget looks right now. EDIT: The screenshot below is from the first official release (v1.0) on Android Market.

I am planning to redo the design, however I need a better design before doing that.. ;-)

Google Calendar Widget v1.0

I'll let you know once it's released to the public, but until then I will do a small changelog.

It's released. Go get it.. :)

UPDATE
Version 1.0 (11-10-09)

Released on Android Market. Have fun!

Version 0.993 (30-09-09)

Changed: The way the events are displayed. Font and size.

Version 0.99 (28-09-09)

NEW: Added EULA
NEW: Added ability to view weeknumber instead of weekday

Version 0.98 (19-09-09)

Bugfix: Accidentally set the time to 00:00 on events happening right now

Version 0.97 (13-09-09)

Changed: Agenda list from current day till current week agenda
Changed: Some functionality in the new API making it more efficient and fast
Changed: Allday events will have their time shown as 00:00

Version 0.96 (08-09-09)

Changed: Opening the HTC calendar is now done by "clicking" on the current date (left side of the widget)
NEW: Now able to opens the HTC calendar on todays agenda list by "clicking" on the events (right side of the widget)

Version 0.95 (08-09-09)

NEW: Now opens the HTC calendar (month view) when "clicking" on the widget. This will most likely only work if you have an HTC phone (not testet on other phones)

Version 0.94 (05-09-09)

Added: More update intervals (15/30 minutes). NOTICE: Selecting an update rate below 1 hour *may* cause an increase in battery usage (battery usage not tested)
Changed: Added a zero to dates (in the event list) on dates before the 10th

Version 0.93 (05-09-09)

NEW: Added completely new CalendarAPI. This API gets it's data from the built in Calendar (if one exists) instead of going online and getting them through HTTP. NOTICE: The actual content provider in Android is still "private", so the API may break when the next version of Android arrives (should be fixable though should it happen)
NEW: Automatically determines which API to use. If you have the internal calendar, that calendar will get priority. It will ask you for login credentials if using HTTP API

Version 0.90 (not released to test)

Bugfix: Widget would not update properly after a restart (Thanks Espen)

Version 0.89 (not released to test)

Changed: Functionality regarding the network availability check

Version 0.87 (31-08-09)

Bugfix: Issues with the event comparer caused it to sort wrongly (Thanks to m.klinge for helping me out)

Version 0.85 (31-08-09)

Added: Network availability check. Should prevent the HTTP connection from timing out, causing the widget to override itself with "No events coming up.."
Bugfix: Sorting was wrong when dealing with recurring events
Changed: When adding the widget the first time, the "current date" is updated right away, instead of waiting for the events to finish

Version 0.80

Initial release to test

First post in 2008.. yay

David Jørgensen — Thu, 24 Jan 2008 20:46:42 GMT

Having been here at work for 12 hours straight I thought i should take a break, and suddenly realised that my blog has been quiet for too long. This must change, so this is my first post in 2008, and hopefully many more will come.

We have to launch a new version of Elsparefonden's MinBolig, which is a super cool project, and the new version is soooo über cool, you'll wet your pants.

Hope everybody will enjoy this super cool new Welcome application which has taken far too long to implement, but as Adobe says: "Motion Matters".

Cheers.

Javascript error when postback (.net 1.1)

David Jørgensen — Mon, 23 Apr 2007 09:32:38 GMT

Developing in windows XP and working on projects in both .NET 1.1 and .NET 2.0 requires you to change your IIS server settings a lot. Since there's only one website on windows XP, you have to change the .NET version on the IIS.

People who have read my old post probably already know of the kick-ass tool that i'm currently using to do this the fast way.

Back to the problem at hand. So there it was. The e-mail telling me something has broken on the site. It's the search on the site. We used to do the site search on the Index Server, but I always find the Index Server unrealiable and very very slow (at indexing.. the search is fast). The Index Server was always crashing, not indexing or else the service was just stopped.
We decided to do the search by SQL instead. The SQL server 2000 being used some of you might know what this might mean.
Had it been a SQL server 2005 we would have done the search the sexy way, but this is only 2000, so it will not turn out just as sexy. :) But hey, at least it will work, and thats the most important thing.

So there I was, changing the Index Server search to the SQL search. Changing the DataAccessLayer first, then the BusinessLayer, and last but not least, the search module. Now it's time to do some testing. As a company who makes a living on the web, we take a lot of pride in testing our work. A little.

So I start up my website and then firebug gives me this:

What the hell??! It cannot convert my form id into a decent form id??! it actually tries to call it "_ctl0:form1". No wonder it fucks up?! Of course this means that every postback I try to do results in a javascript error.

So before I commit my work, I try my colleages computer, and his is working just fine. I then commit my work, and it STILL works, which must conclude that something is wrong with my IIS or my installation of .NET 1.1 framework.

First thing I did was to compare versions on mine and his machine. The same. WTF?! He's using windows 2003 server, but come on, I KNOW it's been working before.

Searching the msdn knowledgebase I find this site here

It seems that there's a hotfix out for .NET 1.1 fixing this issue, and installing this hotfix, fixed my problem. So if you have this error hurry up and install this fix.

Looking at the source after the update my form id is converted into "__aspnetForm" and the whole javascript is changed into this instead: document.forms["__aspnetForm"];

And now it's working like a charm. Unfortunately. Now I cannot forward all the mail I get to another colleage claiming "my .NET 1.1 applications isn't working" :-)

/David

Windows XP and development

David Jørgensen — Mon, 30 Oct 2006 16:26:34 GMT

As a web developer, i've always been using a server version of windows. I used 2000 server (and previously 2003 server) because it's possible to have multiple websites on the same machine.

Multiple websites.
When developing on a windows server platform, you just create a new website on your IIS. Set the path to the web files and set the asp.net version. This makes it's somewhat easy to switch projects as it often happens when customers call and complain about new functionality not working properly or not working at all?! ;-)

In my opinion a windows server is totally overkill to use on a development machine. There's a reason that it's called SERVER!

Windows XP as a development server
Before my last vacation, I asked our systems administrator, if he could install a new version of windows, because the windows 2003 server was getting VERY slow, and he might as well do it while I was away, not cutting into my precious development time.

He asked me, which software I wanted installed, so my machine could be ready when I got back from my vacation.
Thinking back I had many issues using windows XP as a development server, but nonetheless I told him XP pro with VS.net, SQL server and what not.

Then I got back from my vacation. I went to Toronto, Canada btw. GREAT place. Oakville to be precise.
Anyways, I got back and found my newly installed computer just sitting there waiting for me. YAY!

One of my project leaders came to me and said: "Hi, welcome home. Hope you had a great vacation. You have two/three weeks of overtime working.".
Anybody tried this?

When you are working in Visual Studio.NET 2005 you have access to the internal vs.net 2005 webserver, and this may be enough for most people. But I like to "Attach to process" and debug through my own IIS.

This results in me changing the path, the asp.net version and the host header on my default website to reflect the project I am currently working on.

This, hopefully happens only once every day, but every once in a while customers call and force me to change projects many times during the day. THIS makes changing my default website VERY VERY annoying (and time consuming).

This above, and the fact that many of our old projects are built using Visual Studio.NET 2003 which do NOT have the built-in webserver, I needed something that could remove the nousance it is to change the default website.

The solution: The IIS Quick Tool
I am not going to take credit for this tool, although I did have a small part to play in it.
This tool is created by our systems administrator (ya, he can code too), and by one single click with the mouse (well.. two clicks actually) the tool can change the default path to the website, as well as change asp.net version.
It's so cool, it can even create a new website (or virtual directory) if you are using windows server. BEHOLD THE GLORY!

The IIS Quick Tool

Goodbye annoying manual website changing, and hello to the uber cool IIS Quick Tool.
Another great feature is, that you can make it "refresh", meaning that whenever a new asp.net version is released you just run a reconfig commando, and wham, options for the new version will be available in the context menu shown above.

This tool has made my life a lot easier and if the demand is high enough I might even release it. :-) I'm sure Kenneth won't mind. :)

Btw, if anybody knows how to do menu's in the context menu shown above please tell me.
/David