FrontRow Remote - Page 3

iamgnat · 03-09-2006, 08:57 PM

Quote: Originally Posted by CArringt

and the number 1 reason is i'm a big geek =-)l

Not big enough, or you would have done like the guy that is linked off MacRumors that bought a Single and ordered the Duo processor from NewEgg

It rocks that it works, but too expensive right now (and almost $500 for a 2GHz duo, ouch!!!!, but talk about geek appeal)

-dave

(i'll go with the Duo too, for the same reason even

)

CArringt · 03-10-2006, 01:34 PM

lol no kidding. i would love to do it. and i might do that when i order another one. i plan on having three all together. one in the car, one as a media server/front end for my tv, and the last for small work loads at home and church.

CArringt · 03-10-2006, 01:42 PM

ok i threw together a little source page for us at Sourceforge.net http://sourceforge.net/projects/macfro. any one that would like to contribute please come by and do so.

This is a wonderful way for everyone to be able to help and still stay organized. if you want to be a developer for this project please email me chanse.arrington@cingular.com; chanse.arrington@gmail.com and i'll set you up to have access. you do have to be a registered source forge user. which i s free and takes about two seconds.

Please please please come by and help (Mahalis, Mac Mobile, Sti robot, and anyone else =-) )

Mahalis · 03-10-2006, 04:38 PM

Okay, I've got something that works pretty well, but I'm running up against an interface-design issue.
As-is, after two seconds of nothing on the control being touched, everything but the Menu button fades out, becoming completely invisible.
But then what? How does the interface know that someone wants the controls again? I'm thinking about just letting a brush across the Menu button make the rest fade in, but that seems kinda clunky. Any ideas?

CArringt · 03-10-2006, 04:52 PM

Quote: Originally Posted by Mahalis

So yeah... does anyone know how to handle non-rectangular click regions? I'm thinking of just using a mouseDown event and checking the coordinates manually but there must be a better way.

What language are you using for the programming?

iamgnat · 03-10-2006, 04:54 PM

Quote: Originally Posted by Mahalis

Okay, I've got something that works pretty well, but I'm running up against an interface-design issue.
As-is, after two seconds of nothing on the control being touched, everything but the Menu button fades out, becoming completely invisible.
But then what? How does the interface know that someone wants the controls again? I'm thinking about just letting a brush across the Menu button make the rest fade in, but that seems kinda clunky. Any ideas?

Why not just have any touch on the screen bring it back? If all you are doing is controlling FR and the window is just fading in and out (vs being destroyed and recreated), that should be the "easy" answer. (i.e. the window is still there and taking input even if it isn't visible).

-dave

CArringt · 03-10-2006, 05:22 PM

Quote: Originally Posted by Mahalis

Okay, I've got something that works pretty well, but I'm running up against an interface-design issue.
As-is, after two seconds of nothing on the control being touched, everything but the Menu button fades out, becoming completely invisible.
But then what? How does the interface know that someone wants the controls again? I'm thinking about just letting a brush across the Menu button make the rest fade in, but that seems kinda clunky. Any ideas?

Have it comback with a "mouse click" tht would be the same as it coming up when you touch the screen.

Did you solve the click regions problem. if not tell me what language you're writing in so i can help

Edit whoops. sorry iamgnat some how i didn't notice your post. anyway i agree with iamgnat

Mahalis · 03-10-2006, 07:55 PM

Yeah, I've pretty much solved the click regions (properly-sized standard rectangular IB buttons

), and after re-reading the original idea for the app I'm planning to just have the window fade to about 50% opacity and then back to 100% when a button's touched, then stay that way for two seconds before fading out. I'm using Objective-C, by the way - it's fast and it has better documentation than Java or Applescript.

Mahalis · 03-10-2006, 08:45 PM

http://www.mm-3.net/frremote/frremote.dmg
Not final, just a beta... and it doesn't show the cursor (cursors + full screen apps = ugly) so those of you without touch screens can have some fun guessing where your mouse is.

CArringt · 03-10-2006, 08:45 PM

that's great! Ojective-C is a wonderful way to go.

ckny · 03-11-2006, 12:22 AM

Mahalis, I just checked this out on my desktop and while it's fun playing guess the cursor, this definately looks to be shaping up to be what I will be going with in the short term. I'm putting together my system soon and think front row will work best for my multimedia stuff.

One question, I was controlling front row using your remote (up, down, play/pause as enter key). Is that how you intended? If so, anyway to incorporate faster scrolling? Scrolling through artists is a bear one at a time. The keyboard simulates this by holding down the arrow key.

execute · 03-11-2006, 12:56 AM

Awesome!!! Just what I was thinking of doing, I was planning on using a widget (with the keep the widget on the screen even when not in dashboard hack) but this is much better!

Props to you Mahalis and everyone in the process! I agree with ckny too, you guys should implement fast scrolling

Mahalis · 03-11-2006, 10:17 AM

Quote: Originally Posted by ckny

Mahalis, I just checked this out on my desktop and while it's fun playing guess the cursor, this definately looks to be shaping up to be what I will be going with in the short term. I'm putting together my system soon and think front row will work best for my multimedia stuff.

Great! Glad you like it.

Quote:

One question, I was controlling front row using your remote (up, down, play/pause as enter key).

Well, the way what I've got is set up - it basically gives Front Row the focus and simulates those same keys (actually, left-right-up-down-space-escape).

Quote:

If so, anyway to incorporate faster scrolling? Scrolling through artists is a bear one at a time. The keyboard simulates this by holding down the arrow key.

I'm working on it... I've found a way to simulate keydown/keyup events using, of all thing, Core Graphics, but I'm a complete novice at event handling and have no idea how to capture the relevant mousedown/mouseup on the interface's buttons.

ckny · 03-11-2006, 10:34 AM

Well, sounds very promising. Unfortunately my programming days ended before they got off the ground so to speak (at vb7), but I definately appreciate your effort. Maybe throwing it out on the forum someone else will be able to point you in the right direction.

Quote: Originally Posted by Mahalis

Great! Glad you like it.

Well, the way what I've got is set up - it basically gives Front Row the focus and simulates those same keys (actually, left-right-up-down-space-escape).

I'm working on it... I've found a way to simulate keydown/keyup events using, of all thing, Core Graphics, but I'm a complete novice at event handling and have no idea how to capture the relevant mousedown/mouseup on the interface's buttons.

CArringt · 03-11-2006, 11:20 AM

Mahalis: great job. thanks for implementing my idea so quickly and putting out exactly what i had in my mind. i love the way the controls look over the interface.

Two things:

1. We need to put an option in the preference pane that will allow you to change the location of the controls. ie. have six positions all the corners and top/bottom in the middle.

2. i also agree about the press and hold commands in the functions. i completely forgot about them when i first listed the commands. getting to the "T's" in a 16,000 song library can be a real chore hitting it one at a time ;-)