Pseudo-grad project (maybe with OOP)?

[InsaneObject]

Surprising you don't have a re-use category. I was looking, didn't see anything that fit what I was trying to post. I'll put it here.

I've been thinking about my resume and job skills more recently, and realized I should really take some time out to create a real project that is visible. I've also read a great deal of OOP related material in the last 6 months, although I'm still a rookie in OOP dev, b/c it is never worthwhile to do in my everyday job.

Any ideas, or burning desires you have that could be solved in re-usable fashion in LV? I might just take you up on the request and spend many productive hours on it. Unfortunately, I'm not really qualified to tackle most of the requests I've read, they're over my head for now.

I didn't get this in college, and I'm now trying to mimic some other heavy hitters out there, or what they did to become what they are.

A couple things I've done in the past that might be good ideas are:

1. A CSV file reader/writer that mimics the numeric X/Y cell pointing done in XLS files. Thus, using just a CSV file, you can still read and write to a particular cell using e.g. X=5;Y=21.

It's quite useful for setup files that go beyond the typical INI usage, where the file should be pleasant/meaningful to read more than what INI files usually look like. I've used it in a couple projects now, but I still haven't made it quite OpenG usable. A lot of thought would have to go into the API. Might not be OOP.

Also, it is somewhat useful for adding something to a data file after a test run has completed. Let's you edit headers in big files after the fact.

Just be aware that so far it's N^2 for efficiency, and bogs down badly on large files. Perhaps some intelligence should be added (quite easy now that I think of it) to deny the request and report an error when X times Y array size is over say 100k. Without resorting to complicated algorithms, I don't know of a simple way to avoid this N^2 behavior.

2. A circular buffer module that sits directly before a graph on the BD, and takes options. It kind of bridges the gap between graphs and charts. This is super common, and I've seen a lot, but I'd have to sit down and give a heroic think about how the API should look, and which modules should be public. Some common options would be 'display channel?' 'perform moving average?' etc. I wrote about this in another post.

3. Actually, a third is something I started to work on but didn't finish, and is oddly bugging me, is a picture control Xcontrol that is nothing more than a pic control with the added ability to grab & drag (scroll w mouse), and zoom in/out with mouse wheel. The point of this was to make it as efficient as possible and not interfere with anything, not make it something monolithic. Just make it something people could drop in and use, b/c I know I've looked for that functionality many times.

Appreciation in advance.

[crelf]

Surprising you don't have a re-use category. I was looking, didn't see anything that fit what I was trying to post. I'll put it here.

Our reuse section is essentially the LAVA Code Repository.

I've been thinking about my resume and job skills more recently, and realized I should really take some time out to create a real project that is visible... Any ideas, or burning desires you have that could be solved in re-usable fashion in LV?

I've got an idea - instead of polling the general population on a new toolkit, why don't you get involved in the OpenG movement? Thier whole existance is what you described, and they're often looking for developers to do exactly what you're talking about.