Last I heard java doesn't have any access to SCO or eSCO connections so what bluetooth do you plan on doing?
So i have been working on NA3 for sometime now and development is going good. Part of the fun of doing a complete re-write of your code is that it gives you a chance to re-evaluate what you want in your application. While I am very happy with what NA3 can do as of right now, I feel that it should be more capable of handling some of the more needed functions that a carputer should easily be able to do. The main thing that keeps jumping at me is bluetooth phone support. I would love to have a reliable bluetooth phone interface built into NAS so that you don't have to juggle multiple apps to answer the stupid phone.
One of the key hurdles that i would have to get over is the fact that NA3 is built on adobe air (essentially flash with some filesytem api's to get access to user files). As most of you know, this does not give access directly to hardware such as usb devices or bluetooth. The good thing here is that there is a project out there named merapi that provides a java-bridge to the hardware and passes the data to/from adobe air. This is awesome, because now i just need to write a java app that can handle all of the bluetooth junk and then just pass the needed info to NA3 so that it can update the UI accordingly.
I am starting to get pretty amped about this possibility. I think that it is totally doable. this brings me to hurdle two.
I am and have been primarily a web developer with lofty dreams of writing super-awesome-genius code for the desktop. Now what this means is that I have not written any code that actually talks to hardware and manipulates it, but i am certain that google can point me in the right direction to learn how to do it. This means, however, that at initially my code is not going to be super-awesome-genius code but bug-riddled-barely-working code. This is where you guys come in. I am going to try and get a project started this weekend that will hopefully get the ball rolling on this and then i will post it up somewhere (google code most likely) and let the community go to town. Hopefully this will not result in vapor-ware but some instead something that we as a community can really put to use.
Please let me know what you guys think
Well this is the type of information that I am trying to gather. What I want is to write an application that handles the connection to the phone, handles the phone call, etc. It would pass only the necessary information (incoming call notification, phone number, etc) to NA3. Ideally, NA3 would be able to pass the command to answer/hang up phone call.
I am still trying to research how to make the connection with java and if it is even possible for java to handle voice data. if it is not then i may have to look at other, more OS specific ways to handle these types of connections. It would be really nice if java could handle this so that everything could remain OS neutral. But it looks like that may very well be out of the cards.
Voice travels over an SCO connection...which no java library i've seen supports. Might want to start googleing from there. I should also add that I truly doubt you'll find any OS independent way to do this. Android implemented bluetooth with java.....by having it call the native linux bluez stack. The windows bluetooth stack requires a third party decoder to handle audio on vista/win7 and a completely separate stack on OS's prior to that.
You picked the wrong platform if you wanted easy hardware access....
Yeah as i mentioned earlier, i am a web developer that was wanting to try to get into desktop development. Adobe Air was the easiest way to do that. I know flash inside and out so it was comfortable for me to just use that with air to have a semi-native desktop app. NAS never was intended to do much more than play music. Now i want it to do more, and i am backed into a corner. I was just hoping that there was some way to try to add some more functionality to NAS, but it just may not be that feasible.
Well there is always the option to do a platform specific binding for bluetooth and use something like a tcp connection for coms but I think that may be a bit heavier then what your looking for.