What did you use to make that... Interface Builder? What are you using as the backend, iTunes?
Is the row of buttons on the bottom really necessary?
I'm looking for some input on the construction of my Applescript front end. Given the limitations of Applescript on controlling the exact look, I've opted to go with buttons along the edge of the screen, similar to OEM nav systems or ATM machines. While I think I can eventually figure out the Cocoa calls to set the size of the text and make it all a bit bigger, right now I'm just struggling with learning Applescript, debugging, puzzling, failing, and generally just trying to get really simple ***** to work.
I'm soliciting advice on the general approach to the interface itself. I've chosen to use the tab switchers at the top because I think I'll be able to hit them with my finger pretty easily. The big buttons are squared to make them easy to hit on a touchscreen. I'll set it so if I don't use all of the buttons, I'll be able to hide the unused ones when switching apps. (I'm also planning on using the built in speech recognition to navigate around the interface as well, but that's a ways off.)
Given the limitations of Applescript, which means you basically have to use controls that are designed mostly for use with a mouse, is there any constructive feedback you all might have for the layout of the interface, whether on the music screen or the other tabs?
The other tabs, by the way, are just teasers. No controls implemented on them yet -except video.
Thanks in advance!
Edit: I like the white but that's probably too washed out for the car. I've got a different version that uses the brushed metal window style like Safari and iTunes has and improves the contrast.
Want to:
-Find out about the new iBug iPad install?
-Find out about carPC's in just 5 minutes? View the Car PC 101 video
What did you use to make that... Interface Builder? What are you using as the backend, iTunes?
Is the row of buttons on the bottom really necessary?
Yes, interface builder. No, the row of buttons along the bottom isn't strictly necessary. However, in looking at the number of buttons on some of the other front ends, there's in the range of 18. At runtime, as you select the various tabs, I can hide/disable the buttons and extend the center window, etc.
I guess I was thinking that the buttons on the bottom would be easiest to locate with your hand and if they were big enough, it would be pretty easy to locate them quickly.
Want to:
-Find out about the new iBug iPad install?
-Find out about carPC's in just 5 minutes? View the Car PC 101 video
Call me a minimalist. I'm just saying you don't want it too cluttered. I'd imagine it would be hard to navigate while driving. Back/RR, Play/Pause, Forward/FF, Shuffle, Repeat, Browse, Visualization. That's the most I can think of... or at least that's all I'd ever use. Aesthetically, the bottom row could stay and the sides could go.
Make it as safe as possible while driving
have the audio functions on the bottom buttons like play pause etc.
then maybe use the side buttons to scrollup and down the list?
buttons on the left scroll up and down the playlist and the right scrollup and down the track list?
just a thought![]()
CarPC Status:
GPS: 99%
Hardware: 99%
Software: 92%
Case Install: 99.9%
Dash Install: 100%
Car Install: 72%
The more it looks like Febsperanza's skins the better. Those are (were) skin perfection.
Thanks!
I took a look at them and yes, you're right, Feb's skins are pretty nice. He's got about 18 buttons on them too but they don't look as overwhelming because of the size and the location of them.
While I still want to keep the tabbed format, at least until I've had a chance to try it in the car, I'll take a look at changing the layout a little bit to match a bit closer. That may entail putting some of the buttons inside the Music tab by moving them from the sides onto the music tab itself.
Thanks for the input, guys. I appreciate it.
Want to:
-Find out about the new iBug iPad install?
-Find out about carPC's in just 5 minutes? View the Car PC 101 video
Looks cool. Want some help coding it in applescript? i've hit a brick wall in getting some things to work w/ my software, and it looks like you've figured most things out. Plus i've got a cool few things i'm working on...
Wait for Tiger on April 15th, and Automator to go with it.
Life will be much easier for "mac heads" to write GUI
(0.0%-) starting over
iPad 3G 64GB, RF 600.5 amp, JL10W0V2, 8 Infinity Components
That is what I am waiting for:-) stuck with 10.2 OS X and waiting for Tiger to be released to upgrade.
"If it works this good why F with it?" -KMFDM "Intro"
Strive for ethical wardriving: http://faq.wardrive.net/
My CarCPUs: v1 - 2000 | v2 - 2004
Mp3Car Meets: http://detrimental.org/eyecandy/MP3CarMeets
Bookmarks