Looking for a windows software programmer for bikey related project

[WildBoarMouse]

Ok, so if there's no comms, it's an easy project. Graphing, data grids, all those sorts of things are easy peasy in .NET. I'd be keen to see your file format (or just whatever you want to store) and what you want out of the interface. C# is .net, so all native Windows calls, be easy to knock something up.

We don't have any kind of file format yet. I figured that would be something to knock together with the person that would end up having to read from it. We're probably a few weeks away from beginning to log data. I figured it would be a good idea to have a chat to a GUI person first so I/we don't go down a path that makes their life difficult

[imdying]

You'd be hard pressed to make life too difficult. .NET (and I'm pretty sure Delphi) has heaps of string manipulation functions and classes that'll take any data you want to throw at it. Throw up some ideas and we'll put our collective brains together

[WildBoarMouse]

You'd be hard pressed to make life too difficult. .NET (and I'm pretty sure Delphi) has heaps of string manipulation functions and classes that'll take any data you want to throw at it. Throw up some ideas and we'll put our collective brains together

Will do. I'll throw up another post once we have some sample data.

[Wonko]

What sort of look/feel are you after?
mI my minds eye I see the interface being a screen full of different dials and graphs showing all the data as it happens.

could be run in two modes. One "real time", and one at 1/10(or whatever) for more analysis of what's happening. also have the ability to step forward throught time blocks one by one.

I imagin that your data loging would be a csv type file.

I'd use VB.net by choice, but would need to learn about directX.

*sits back and waits for the "My programming language is better than yours" internet fight*

[WildBoarMouse]

What sort of look/feel are you after?
In my minds eye I see the interface being a screen full of different dials and graphs showing all the data as it happens.
Sounds good. Because so many things will be happening, it might be useful to keep all the data the user needs to look at in one place. Possibly something akin to the Windows performance monitor? Sounds like the ideas are heading down the same track though... To begin with, something that displays everything in a simple, easy to use fashion. Something that non-computer people will have no effort in understanding.

Could be run in two modes. One "real time", and one at 1/10(or whatever) for more analysis of what's happening. also have the ability to step forward through time blocks one by one.
Yep, we're on par with that one

I imagine that your data loging would be a csv type file.
i had a think about this one, and we'd actually end up wasting a huge amount of storage space on comma's. Easy to process, but a little wasteful. This should be an easy thing to sort out...

I'd use VB.net by choice, but would need to learn about directX.
The idea of having the graphical feedback is for the "that could be cool for the future" type thing.

*sits back and waits for the "My programming language is better than yours" internet fight*
Bah, no one here seems to use C# anyway.

[imdying]

Something like the windows perf mon would be easy, add and remove traces as necessary.

If not csv, then fixed length fields?

Shouldn't need directx for this, that's pretty overkill, but quite cool.

80% of .net in this country is c#, would be a good oppurtunity to learn (it's dead dead easy if you know Java, and still quite easy if you know any ,net languages. I'm assuming you know at least one curly brace language?). I'd be happy to help you if you get stuck.

[WildBoarMouse]

Yeah, fixed length of some sort... TBD There will be some variation in the data logged but that can be specified in a file format specifier at the beginning of the file. That specifier can be a fixed format. I'll have a good think about it next week. I've written a few data logs for security systems and larger projects so this should be relatively straight forward.

Agreed. For the first part of this directX will definitely not be needed. We've got some ideas of what we'd like to do in the future so not having to re-write everything that's been done would definitely be an advantage

I'm fluent in C, fairly in C++, less so in VC++, barely C# A few of the guys here at work use C# so there's always a helping hand. Just a pity none of them ride bikes!