At the moment this is the area I am considering - what issues arise? And this section should change quite a lot in the near future.
Upon first considering this project, my orientation exercise identified serveral facilities this project would be required to provide. To this I would now add a library management facility.
At the time, figuring that in any event Radiographers are going to have to label dcm slides, I quickly made up an HTML interface - a rough sketch of what was being thought about. ( Use the back-button to get back here. ) However, as I was writing it I was considering using either Flash/Actionscript or PHP/Mysql, and a Web2.0 approach, considering it would be a far more robust, cross-platform, and ubiquitous technology to use for all the various interfaces. However, Web 2.0 was seen as low priority, and that direction has been abandoned for now.
Subsequent to that cross-platform development in C++ seemed to be the way forward. However, I am having a look at C# myself. (I am told, thanks Omar) C++ is C++ without pointers, yet remains compatible with C++ which sounds good! I tried out Microsoft Visual Express C# by making a mock-up of a proposed interface modelled on PowerPoint.
Any software should be cross-platform. The OSG/Present3D programmer, Robert Osfield, works on MacOs, and compiles to Leopard and Unix with XCode. Intel PCs tend to follow later. I have written my bit in C# - the walkthrough explaining it (above). I will look at this in more detail in the next few days, because I doubt if it is feasible for me to write anything mission critical unless I have to and it would be a major learning curve for me. However, much depends on what Phil Lavery & Robert Osfieldplan for the Present3D rewrite. Are they going to model it on PowerPoint? ....Because that's a customer driven requirement.
Currently on the back-burner, as not directly related to the project requirements.