Valentine One to a PC

Quote:

---

Originally Posted by jimbonzzz

Honestly, I wasn't planning on it...
Let me take a some time and get a better feel for the systems you guys are running. If necessary, maybe I could eventually meet you half way, and do an API release or something like that. :)

Jim

---

Front End integration in this case is not necessarily crucial. You don't necesarily have to release the source code. What i would is some sort of full screen overlay that would pop up when you were radared. When i say overlay I mean semi transparent. So you could see the Front End behind the popup window. If it would pop up full screen and not be "windowed" it would look the cleanest.

Also the kind of applications we usually run more often than not skinablility is key. In this case i don't think it is crucial becasue it is basically just a display of the V1.

I sincerely appriciate you for Writing the software, designing and testing the interface cable and joining the forums here to help us out.

:D

Quote:

---

Originally Posted by antimatter

I sincerely appriciate you for Writing the software, designing and testing the interface cable and joining the forums here to help us out.

---

I think you speak for everyone here at mp3car.com when you say that.

i also agree with the semi-transparent overlay. theres no real need to add it into a program, because whatever screen the program is on, i would want notification if the radar goes off. would probably be the easiest way if it was a seperate program...

yeah thanks a ton that software looks sweet and the overlay idea is a good one!

If there was a cable I could buy to get the mute functionality, I would buy it! Don't know ish about making these cable things I read about on here haha.

Quote:

---

Originally Posted by antimatter

Front End integration in this case is not necessarily crucial.

---

True. Since the program can now pop up and hide as necessary, its much better than being integrated because of its independence. As a programmer, I do like the possibility of an API though.

Quote:

---

Originally Posted by antimatter

Also the kind of applications we usually run more often than not skinablility is key. In this case i don't think it is crucial becasue it is basically just a display of the V1.

---

Skinability is definitely key for us but I disagree about the need. Yes it duplicates the display of the V1 but how many of us have a frontend that just simply duplicates the look of a headunit? Ok, so there are some that do such as More Mods Alpine skin and the Audi MMI skin that Btbe is making. I think it would be cool to be able to create different skins for the radar display. Some could be smaller, more compact, others could be completely different. But more importantly, the skin could be made to complement our frontend's skin.

Quote:

---

Originally Posted by antimatter

I sincerely appriciate you for Writing the software, designing and testing the interface cable and joining the forums here to help us out.

---

Totally agree with you. Jim, you're an asset to the community.

Quote:

---

Originally Posted by fantomas

i also agree with the semi-transparent overlay. theres no real need to add it into a program, because whatever screen the program is on, i would want notification if the radar goes off. would probably be the easiest way if it was a seperate program...

---

Here's what I'm thinking are the advantages:
1. Frontend can mute or reduce the volume of music whilst the audio warnings play.
2. Frontend can switch views to a full screen view of the V1 whenever anything is detected. And then switch back after a short pause.

I don't rate skinning very high beyond the option of having some skinned UI in a bar across the bottom or top with a back button on it. I don't like the idea of a transparent overlay since that will degrade the quick legibility of the UI.

A simple API would probably allow for the above.

Quote:

---

Originally Posted by contaygious

If there was a cable I could buy to get the mute functionality, I would buy it! Don't know ish about making these cable things I read about on here haha.

---

Once the interface design is tested as working 100% (or at least 99.9% for all those who try it) I may end up making a few more, just for the experience and 'iron-time'. I may even dive into toner transfers and see if I can make some quality etched boards. And if time/money permits, I'd even like to see if I could make a SMT version that's small enough to fit inside a DB9 hood (much like the double-sided 6-transistor design Jim posted a link to).

That being said, I could part with the extras for nothing more than the cost of materials.

Quote:

---

Originally Posted by drait

Once the interface design is tested as working 100% (or at least 99.9% for all those who try it) I may end up making a few more, just for the experience and 'iron-time'. I may even dive into toner transfers and see if I can make some quality etched boards. And if time/money permits, I'd even like to see if I could make a SMT version that's small enough to fit inside a DB9 hood (much like the double-sided 6-transistor design Jim posted a link to).

That being said, I could part with the extras for nothing more than the cost of materials.

---

Great!!

I would be interested in purchasing one from you once it is all tested. I really don't care if it is surface mount or not. as long as it works

That would be awesome, I'd be interested as well..

I guess I'll add the me too in there.

I would love to buy the TTL one, but for $40+$10+$7 it is really too much for what I do with it.

If someone wants to prefab Jim's circuit in the $20 shipped area, I would be on board. :)

Would it be possible to modify the homebrew cable to be USB without too much difficulty, or is that crazy talk?