Luminosity 2.0 - Help me out, be hypercritical!
Hey all. This is my first post here, so I thought it'd be wise to introduce myself before I dive straight into my post. I'm a laserist and programmer, though most of my free time gets spent on the latter. I'm the programmer responsible for the laser warning label generator (that you may or may not actually find useful, but it was fun to write), other calculation-type tools, and (most importantly) Luminosity. It's the LPM logging software I custom-wrote to ship with the Kenometer. At time time of its writing, I was just beginning to learn object-oriented programming (and C#) and didn't really take advantage of the OO paradigm. Now, it's time for a 2.0 version - which I've started from scratch to address the expandability issues of the first release.
Here's a screenshot I took last night (please forgive me for having a pointer, it's the first thing I could put my hands on and is rather convenient for testing):
http://www.safelasers.org/Luminosity...0.10.07.02.png
As you can see, it looks way better than it used to - it now supports multiple datasets on a graph, everything is resizable (except while rendering a graph), will export secure datasets, and generally acts more professional.
Here's where I need your help. For those of you who used Luminosity, what sucked (you won't offend me, believe me - I think 1.0 is terrible now that I've worked with 2.0 O_o )? What did you hate? What did you like and want to return for the second release? For those of you who haven't used it, what do you want to see in LPM interface software? Throw me your far-fetched pipe-dream ideas; I'm at the point in development where I can work basically anything in, and can begin to roll in those huge, far-fetched ideas.
Hit me. Impossible is nothing. :)
-Trevor
