Finally, the project is completed! The final report has been uploaded.
A CD containing the documents, source code, executables, and other useful stuff has been delivered, so this will probably be the last post on this blog.

Good bye and thank you for your attention

According to the requirements for the delivery of the project, the report must be delivered in both printable and web formats (i.e. PDF and HTML). To quote the requirements: “Prosjektrapporten skal leveres både som Web versjon, dvs. som HTML eller XHTML, og på et format egnet for utskrift, f.eks. PDF.”

Therefore, I have used the TtH tool to convert the LaTeX document into a HTML version of the report.

I am starting to see the end of this project - a week before deadline!
Many corrections and inprovements have been made to the main report these last days.
I have also written a simple user manual for the client.
The project is to be delivered on a CD, so a readme-file has been prepared with installation notes and some troubleshooting tips…

I believe the contents of the report is in place now - editing and spell-checking is next on the list! Since the deadline has been pushed, I’ve even got time left for the other subjects

I have completed the prototype evaluation, interviewing three VTS “experts” last monday. So now it’s simply write write write! A new version of the report has been uploaded, with most of the results from the testing. And the references have been fixed! If time allows, I will also write a simple installation/user manual…

I have designed a test for the prototype. Important questions to be answered are:
- What can the product be used for? Who wants it? What problems can it solve
- What are the main problems in using the product?

The test is an interview with a small walk-through of the prototype, targeted at “VTS experts”. Documentation of the test can be found in the report.

I have also converted the report to TeX and written some more, but the references have not been converted yet.

…already I miss the easy scaling of figures, the WYSIWYG editor and the easy reference handling in Word…

Trying to get started after a great easter without much schoolwork… Written some more on the report. I am also thinking about how to evaluate the product. Perhaps it will be something in the line of a questionary to be filled in while playing with the application.

I’ve been working with the Arealis vs Nokia series 40 problem, which seems to be caused by the long URL required by Arealis. Tried to use HTTP POST method instead of GET, but Arealis didn’t seem to like that.. However, another solution was found: the request is forwarded through the VTS gateway server. HTTP POST method is used for this request, with the complete Arealis URL as data. The request to Arealis is then performed by the VTS gateway, and the results are streamed back to the client. This might seem complicated, but didn’t really require that many lines of code…

Have also done some cleaning-up in the code, and removed lots of (now) useless debug output…

I’ve been doing some more programming on the system lately, even though I know I really should spend time with the report now

Made a fix for the “pan vs select” problem by using the “exit” button to switch between pan and select! Application exit is moved to the menu. Added some nice arrows to show if we are in pan mode or not. Added geographic filtering in the track request, which means that not all tracks are sent everytime. And now comments are correctly forwarded into the VTS system. Finally, I have a working “bookmark” system. Hopefully, I won’t have to spend much more time with the programming…

Switched to the Arealis web service (Thanks to Stig-Erland for assistance!), but new problems occured. The map requests doesn’t seem to run correctly on the Nokia series 40 and 6230 emulators, and the problem could be that the URL is too long. Some people say that it can only be 127 characters long…

Completed an evaluation (in Norwegian) of the Cell Info Road Tracker project by John Simensen.

Also done some more work on my server - fixed the HTTP parser to handle requests split across multiple TCP packages (in other words, not all data is received immediately). This was necessary in order to receive HTTP POST packages from my Nokia.. Now it is also possible to enter requests manually through a telnet session…