ALEXIS touch interface

**deadweasel** · 11-28-2003, 04:05 AM

Still in very early development. Comments and suggestions most certainly welcome! If there's enough interest in it, I will begin coding to provide more flexibility, such as selectable modules (not everyone has GPS or engine sensors), and the ability to be skinned.

It's designed to be simplistic and quick, yet visually attractive. One thing that got to me about MediaEngine was the load times associated with switching modes. This interface doesn't have that issue, but then again, it's not nearly as complex in dealing with mp3 management as ME is. Were I just dealing with multimedia in the car, MediaEngine would be my choice. It's full of eyecandy and features that make it perfect for music and videos and even GPS. BUT I wanted something a little better suited for doing some actual driving while using it. Hats off to Coyote. Here's my entry to the field:

The Alexis Project

Flame if you will, but in the end, this is MY baby, and I wanted to give y'all a chance to peek at a fellow geek's endeavor.

**Confused** · 11-28-2003, 04:48 AM

Looks pretty good!

Keep up the great work!

Looks like another program to make a skin for

Garry

**slarty** · 11-28-2003, 05:45 AM

It looks great I'd like to see more

**Seraph** · 11-28-2003, 11:57 AM

Nice. Send me the specs so that I can put them up on the features list. It is going to be freeware right?

**00CericaRuss** · 11-28-2003, 03:43 PM

looks nice and clean

**deadweasel** · 11-28-2003, 10:15 PM

Originally Posted by Seraph

Nice. Send me the specs so that I can put them up on the features list. It is going to be freeware right?

How about this: mp3car.com has been instrumental in helping me get to the level I'm at today. I've been cruising this site and yapping here and there since about three years ago. In return for all of the generous tips and help over the years, whether I decide to charge for it or not, mp3car.com users get it free.

That way, when I turn this thing into a cash cow to start my own multinational conglomerate mega-corp, you can all own a piece of history!

*stares into space and dreams on*

Seriously, yes, for all the good peeps here, it's free. This is, of course, when I can get this thing locked down and useable by everyone. Right now, it's pretty universal alright, but mainly because it's so naked.

**chut** · 11-28-2003, 11:54 PM

Man, I like that voice!

**Animepix** · 11-28-2003, 11:55 PM

Looks pretty good to me. I like the way your thinking about flexibility. Maby even haveing blank buttons that you can enter your own text into to launch apps that some people might use more than others.

**Seraph** · 11-29-2003, 12:46 AM

Originally Posted by Animepix

Looks pretty good to me. I like the way your thinking about flexibility. Maby even haveing blank buttons that you can enter your own text into to launch apps that some people might use more than others.

That's what I have been preaching forever. I like the new stuff that people are making now. Now we are talking frontend and we have choices.

**deadweasel** · 11-29-2003, 01:06 AM

Originally Posted by Animepix

Looks pretty good to me. I like the way your thinking about flexibility. Maby even haveing blank buttons that you can enter your own text into to launch apps that some people might use more than others.

YES!!! Great idea!! I shall see about making that happen! Maybe an "applications" screen where all the shortcuts are kept? Oooh I sooo like that concept!

At the same time, I have to offer up a sarcastic "thanks alot buddy". You just gave me enough ideas to lock into development for the remainder of the night and most of tomorrow.... in one stretch.

Edit: When I think about it, there arises a potential problem with the button creation thing. What about the people without touch screens? I could probably code something up for people to be able to draw their own simple buttons on the screen and title them appropriately, but what about those with a simple display? As a compromise, how about a configuration setting that allows you to display a certain number of buttons on the screen, and the user could simply use onscreen keyboard shortcuts to choose a number and edit it with name and link appropriately? For that matter, how far should I be thinking about this? How many users surf the web from their cars or would like the ability to launch a game or something of that nature from the interface?

The problems really start coming to bear when I attempt to maintain flexibility, but at the same time attempt to keep it based on the concept that this is to be used for things that you would do while driving. In retrospect, it might be a better idea to provide quicklinks in a separate Applications screen that closes the interface and launches the appropriate program. You see, I want this to be a driving interface, not just all-around carputer Play My Games and Watch My Movies program. While I can't exactly look down my nose at those who want to do those things in a car (I've been stuck in the car while the girlfriend goes into the department store to "just pick up something"), I would like to keep the interface itself a little limited in what it can do, simply to ensure that it remains fast and light, and uncluttered with a lot of options that may not get used all that often.

What do y'all think? I'm all fired up to code like a motherf--ker, but I don't want to come to my senses in the morning and realize that this thing just became a bloated sow of a program....