AMP Wishlist Thread - Page 15

Bugbyte · 09-25-2006, 08:43 AM

How about using a solution developed by our windows carpc buddies? Here's a thread where Justintime has developed a local web page that pulls all the data and displays it in a browser window.

That means you can customize it to your own specs, no additional coding of AMP involved unless you want to give it some kind of gui to alter the underlying file so you don't have to hand edit it.

Here's what it looks like:

LightningMac · 09-25-2006, 11:01 AM

interesting, but I would rather it be a graphically thing, like the Yahoo Traffic Widget, very simpe and easy to see

jkusnetz · 09-25-2006, 05:32 PM

I'm interested in trying to use Amp in my Mac Prius instead of Front Row.

In order for me to be able to make it work every button on every screen would need an equivient keyboard press. For example "p" for play, "f" for fast forward, etc. I would also need to be able to ask Amp with some sort of apple script query what page it is on.

Basically the way the touch screen stuff works is I get back a very low resolution coordinate of where I touched (16x16) I think the buttons are big enough in Amp to where each button could fall in it's own 16x16 coordinate.

So bascially when I touch my screen I would have to make my software say "Hey Amp, what screen are you on?" Amp would say I'm on the play screen, and my software would have to say well in that case coordinate 5x10 is where they play button is, send the keystroke "p" to Amp.

Think this could be done?

qkslvr · 09-26-2006, 02:02 PM

I would like to see Phidgets (http://www.phidgets.com) support, like was planned in the CarMinx front end. There are so many applications that these can be used for. Especially the LCD output... Just imagine, stick that LCD in your gauge cluster or on top of your dash, output GPS turn warnings... Head's up navigation! Audi-style...

EDIT for forgotten AMAZING application: Phidgets also support RFID... Hands-free keyless entry and ignition, anyone?

aychamo · 09-26-2006, 02:10 PM

Quote: Originally Posted by jkusnetz

I'm interested in trying to use Amp in my Mac Prius instead of Front Row.

In order for me to be able to make it work every button on every screen would need an equivient keyboard press. For example "p" for play, "f" for fast forward, etc. I would also need to be able to ask Amp with some sort of apple script query what page it is on.

Basically the way the touch screen stuff works is I get back a very low resolution coordinate of where I touched (16x16) I think the buttons are big enough in Amp to where each button could fall in it's own 16x16 coordinate.

So bascially when I touch my screen I would have to make my software say "Hey Amp, what screen are you on?" Amp would say I'm on the play screen, and my software would have to say well in that case coordinate 5x10 is where they play button is, send the keystroke "p" to Amp.

Think this could be done?

Sorry.. I think you'd be better off getting a real touchscreen.

aychamo · 09-26-2006, 02:12 PM

Quote: Originally Posted by qkslvr

I would like to see Phidgets (http://www.phidgets.com) support, like was planned in the CarMinx front end. There are so many applications that these can be used for. Especially the LCD output... Just imagine, stick that LCD in your gauge cluster or on top of your dash, output GPS turn warnings... Head's up navigation! Audi-style...

EDIT for forgotten AMAZING application: Phidgets also support RFID... Hands-free keyless entry and ignition, anyone?

Some other people have asked about Phidgets too. You oughta get some example Cocoa implementations for them and figure out what's going on, and then build a plugin to support them! And then you can use that in AMP.

catronro · 09-26-2006, 02:25 PM

It would be great if the apple remote (the one that comes with the new mini's) worked with the application. (If it already does please tell me what i am missing).

aychamo · 09-26-2006, 02:28 PM

Quote: Originally Posted by catronro

It would be great if the apple remote (the one that comes with the new mini's) worked with the application. (If it already does please tell me what i am missing).

That's a great idea. Someone ought to figure out how to use it w/ Cocoa apps, and then write a patch for the code to do it

catronro · 09-26-2006, 02:31 PM

Quote: Originally Posted by aychamo

Some other people have asked about Phidgets too. You oughta get some example Cocoa implementations for them and figure out what's going on, and then build a plugin to support them! And then you can use that in AMP.

Quote: Originally Posted by aychamo

That's a great idea. Someone ought to figure out how to use it w/ Cocoa apps, and then write a patch for the code to do it

LOL...Am I sensing a bit of hostility/sarcasm j/k. I know your hurting for other developers to help out with functionality. I am currently finishing up a .NET side project and then I plan on learning Cocoa and diving in. Help is on the way....but it may be slow coming.

catronro · 09-26-2006, 02:34 PM

If anyone is interesting in picking up the apple remote integration. Here is some Cocoa code and example program to get you started.

http://www.martinkahr.com/source-code/

Its like the 2nd or 3rd section down on his blog titled "Apple Remote Controller Wrapper Class"

aychamo · 09-26-2006, 10:35 PM

Quote: Originally Posted by catronro

LOL...Am I sensing a bit of hostility/sarcasm j/k. I know your hurting for other developers to help out with functionality. I am currently finishing up a .NET side project and then I plan on learning Cocoa and diving in. Help is on the way....but it may be slow coming.

Haha

It's not really that. When I first made AMP, my original intention was to build a front-end that I wanted to use, exactly the way I wanted it. All the paths to files were hard-coded, etc. But then I decided to give it out and see if anyone liked it. I started making a few things as options, then it kinda got out of control.

AMP's growing beyond what I had originally planned. I guess it's good that it filled a niche. But.. I'm extraordinarily busy with school, and to be completely honest, it's not likely that I'm going to spend a few days implementing some random hardware or some odd feature request that I will never use. And a lot of people have really weird hardware setups (like the request for a weird touchscreen a few posts up), and I can't possibly make AMP compatible with every odd setup out there. I've made the code available if they want to change things to their liking.

I know a lot of people would like to help, but they don't know how to program. AMP is my first actual program I wrote for OS X (I wrote a few things I never released, just to learn how to use Cocoa.) It's really not that bad. There is an abundance of online resources ( http://www.cocoabuilder.com , http://www.cocoadevcentral.com , http://www.cocoadev.com , and best of all http://www.google.com ) that can be used to look at example code, talk to other people, and get a grip on what's going on.

So, no, its not hostility. I know I'm partially responsible for the problem because sometimes I'll respond immediately to a random feature request (ie, WarDriving) and implement it. I've been guilty of the same thing in other projects too. Sometimes it seems that good software just comes out of thin air, but.. Don't forget there's someone busting their *** behind the scenes :-) I just hope some people can pick up programming and start doing some plugins or tackling some of these feature requests. Like the traffic thing. It's a nice idea, it's easy to do, just open the URL, read the XML it gives you, parse it and then present it to the user. .. But I would never use that, and I doubt I'll spend the time doing it.

I'm only going to get busier and busier with life (studying for the boards, clinicals, etc), and I'll have less and less time to dedicate to this stuff.. I just need some help in sharing the load, is all. I hope I didn't sound like an *** or anything!

Goodnight!

catronro · 09-26-2006, 10:48 PM

You didnt sound like an ***. You've done a great job with the software. I just thought your comments were funny. I will definitely be stepping up soon enough to help out where i can.

JakobMetzger · 09-27-2006, 06:58 PM

ya, just wanna say thanks again for this program.

edit::
I dunno who reads digg but one of the latest stories are
"How to contribute to Open Source software"

1.Contribute quality:
help to make a better project, better looking and with new features
Submit bug reports
Suggest new features and options
Suggest ways to improve the framework (maybe comparing it to similar OS or comercial projects)
Submit some artwork (icons, backgrounds, logos) to use in the program
Correct spelling and grammar mistakes in documentation
Help maintain a web site for an Open Source project

2.Contribute documentation: Some Open Source projects have a poor or insufficient documentation
Help write good documentation
Translate the documentation (and program text) into another language
Read existing documentation, follow the examples, and make corrections
Create diagrams, screen-shots, and graphics for documentation
Develop spelling and grammar style conventions for documentors
Build a glossary of technical terms (so non geek people can understand)
Convert documentation into more useful formats (i.e. DocBook)

3.Contribute support: everybody need it at least once.
Let programmer do their work while you help other people
Answer questions on forums, mailing lists or IRC channels
Contribute to (or start) an online support group
Help other people learn how to use the program (or programming library)
Write HOWTOS and post them in related forums or your own blog

4.Contribute money: many Open Source projects have a donate button or a shop where to buy related products, but there are other ways to contribute money
Send a developer, project or company some money
Buy a Free Software product, or associated products
Hire Free Software developers
Contribute hardware
Contribute bandwidth
Advertise in their web site if they show ads
Buy products from companies that support Free Software

5.Contribute publicity: If the project gets popular there will be more people wanting to contribute
Package the application for a particular Linux distro (or other OS)
Convince people to chose Open Source products when possible
Write reviews
Write about new ways of using an Open Source program

6.Contribute appreciation: it's an extra way to contribute but may be the most important
Express your appreciation to developers (through email or forum post)
Send the programmers post cards
Give a project or developer a gift (some have wish lists for this)
Be polite when reporting bugs or asking for new features; developers has no obligation to do it after all

LightningMac · 09-27-2006, 07:04 PM

ditto

(thanks for the great program)

bcohen5055 · 09-29-2006, 07:12 PM

I know verry basic cocoa and have watched many projects on this site develop only to get out of controll by many crazy options. I have wondered about the plugins for amp for a while now, if I could see a basic readme about them or maby a tutorial or template plugin that would be a big help. then I can start, but I'm not really sure where.

In regards to the phidgets post, I have been looking at them for a longtime and once took a class on hardware/software intigration, however I don't own any and don't want to make that investment seeing that I don't even have a maccar right now.

As far as keyless entry is concerned, I think a hybrid of phydgits and bluephone elete may be necisary. Bluephone can run an apllescript to tell phydgets to unlock doors or whatever when you are in a specific range.

But remember this is a Mac Car COMUNITY it isn't Alchamo's job to be the only programer. How do you expect him to program for phidgets if he doesn't even own any? The idea of a forum like this is that someone in the comunity has them, makes them work for them and submits it to a larger project and I think that is what we are lacking right now.

User Name		Remember Me?
Password