Skip to main content

CabControl Project

I have just finished a project for the HND I have been studying for in the evenings through De Montfort Uni. The project was a year long module similar to a normal dissertation.

My project was based upon a mock Taxi Firm that required a management application to track Accounts, Taxis and their drivers. All in all the project went well. I started off with a lot of ideas about what I wanted to do for it but as time crept up on me I found that I had to cut out some of the functionality that I would have liked.

One piece of functionality I was able to keep in was the tutorials for the product which can be accessed through a browser form in the application (the app had to be Win Forms). The browser plugin looks to a page I created on Google Sites to accompany the project. To be honest neither the site or the vids are great but I did it more as an example of what can be done. Alternatively I could have embedded Windows Media players into forms to do a similar thing but with a browser it means I can always update the tutorials even when the application is deployed.

The site I created is here should anyone like to take a look. There are better quality SWFs at the bottom of the page and some of the videos talk about some of the benefits of C#, using ORMs and a couple of other things. -> http://sites.google.com/site/cabcontrolinc/Home
Labels:

Comments

Post a Comment

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.
Post a Comment
Read more

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi
Post a Comment
Read more

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second
Post a Comment
Read more