ParaPlan
There are 8 entries for the tag
ParaPlan
The last month or so, I've been wallowing in Windows Presentation Foundation (WPF), trying to determine if it is the correct direction for our next version of our flagship software, ParaPlan. WPF is flashy and fun and bubbly, but there are not many examples of real world enterprise applications that are built around WPF. After much research, and significantly pushing back our deployment timeline, we decided to rebuild ParaPlan 4.0 using WPF for our UI. We were able to use our existing 2.0 UI framework...
Kyle Archer talks about how Supernova makes it possible for one of our potential clients with a visually impaired dispatcher to use ParaPlan. Creating software that adds business value to a company, eliminates process inefficiencies and has a quick ROI makes for a great whitepaper. When a company writes software that adds quality of life to an individual, that is very cool. Technorati tags: Kyle Archer, EnGraph, ParaPlan, SuperNova...
I just wrote the 300th unit test for our version 4 of ParaPlan (GoldStar). We are about 6 months into the project, 85K lines of code and 60% code coverage on the non-UI stuff. Our first release to alpha testers is July 1. Hopefully, I'll have closer to 85% coverage by then. Technorati tags: EnGraph, ParaPlan, GoldStar, code coverage...
I've thought about posting this for a while now and responses to my architecture post by Dave and Dru have got me thinking about it again. I avoid open source frameworks or libraries in our production desktop applications. I don't have a problem with third party when it comes to web applications or internal apps. I use AjaxPro and skmRSS on Where's Tim and my home site. I use Indy.Sockets all the time in our internal apps. Where's Tim is just for fun though and if it goes down, it's not that big...
When we decided that ParaPlan 4.0 would be rebuilt in .NET (from Access), we decided not to redesign the SQL database. Even though we have some inefficiencies in our db we want to decrease development time and allow our beta testers to be able to switch back and forth between our Access front end and our .NET front end. As development began, we decided that we needed an object for each table and that we could eliminate some of the database inefficiencies in our objects. So we have an Appointment...
I'm not being narcissistic, I just discovered tonight that I'll be able to save over 5000 lines of code on my current project using System.Reflection to internally populate an object from an external object of the same type. I'll post some code later so the true gurus can pick it apart. Technorati tags: Reflection, Justice Gray, ParaPlan, GoldStar...
Jeff Atwood wrote an interesting post yesterday arguing for using GUIDs instead of auto-incrementing integers. We recently had one of our clients merge with another one of our other clients and it was a pain merging their ParaPlan databases. If we were using GUIDs as Primary Keys, the headache would have been much less. Technorati tags: Database design, Jeff Atwood, GUID, EnGraph, ParaPlan...
The Messenger blog talked today about using their protocol handler to initiate IM conversations from an a href or command prompt. The idea is to use their handler (msnim:) as you would a typical handler like mailto. I wonder how hard that is to implement. That would help our clients transition smoother between our .NET and non-.NET applications. For example, if they had a vehicle loaded in our ParaPlan software and wanted to see where the vehicle had been that day, we could put an a href link that...