Printable View
I changed some of the icons and little bit and just updated the post above. The top one would be your home screen and it would have all you icons that are not on the bottom bar. The second is the Music Player screen. Left is controls and whats playing now and right is where you select you song.
Good stuff! I like it. Not sure how the Now Playing / Control on the menu screen would work. Maybe smaller. Just enough to see the track name and if you touch it you will get back to the media screen. Just thinking about how the display of plugin/applet icons will be affected. And in keeping with the Android thing, some little dots near the top or bottom of the menu screen to show which page of items you are on.
I like the layout of the media screen also. I would probably make the right/left sides only 1/2 the screen and show album art on the right. Use top bar to scroll track title, artist, album. Use the left for controls and media library navigation. A couple buttons "Track", "Artist", "Album", "Shuffle" in the control window will product the desired list on the right, if idle it would revert back to Now Playing with the album art.
While a list of media is in the right window, there could also be some alphabet tabs to jump to the appropriate part of the list.
These are just my ideas. You are, of course, not obligated to implement these :)
John
andrew, are those just draw-ups of screens, or are you programming it as well at this point?
Looks really slick, I like it!!!
Well from what I hear you have to know C# to do Open Mobile themes. So right now just draw ups. If someone is willing to do the programming I will do what ever art is needed. If no one can do the programming I will just do the theme for another Frontend and then share the art back here aswell. Are there plans for a theme maker simular to other front ends?
You're right, for now you need to program it in C#. I'm not sure how to 'start' a skin, but it looks like I should be able make the corresponding skin folder, and just fill it with the art and needed compiled dll's. I might not have a lot of time but I can put in a couple hours a week to code it if you would like?
EDIT: Well, my assumption about it finding a new skin folder is wrong. First, we gotta modify the skin switcher plugin in the default skin. Easy enough, we'll just switch to the new skin instead of highway. Later we can add a list of the skins to choose from, but let's get the new skin working at least. Then we'll make a ui.dll and main menu dll (main menu houses the buttons to get to the other screens/plugins). The ui contains information/images/etc...
So, let's say the first thing we should do is switch the skin and get a couple of your new images loaded up, after that it should be relatively easy to place stuff.
Pssst: You can also use VB. As far as I know, any .NET will work.Quote:
Originally Posted by detlion1643
A skin designer is planned, but is on the back burner for now.Quote:
Originally Posted by andrewfblack
Cheers,
John
And to think... OM converted my programming style from vb.net to c#, lol.
Only programming I know is mostly web programmign and a little C++ but just a little I learned in school. I've been working on the theme some more last night. I think we should start replacing each screen one at a time until we get the theme finished. I think the main menu is best place to start. Here are the updated images please tell me what other buttons or information we need for the Main menu when we finish that we will move on.
http://andrewblck.com/images/public/AndroidSkinHome.png
http://andrewblck.com/images/public/...ediaPlayer.png
I'm gonna need seperated images for each item/image/button/etc... Like the background image, then arrow images, etc... I have no experience in photoshop or paint.net so I don't know if you can get those from these 2 images anyways.
Also, to note, I have never worked with android. Never used it nor seen it. I just know what it is. So, at some point I'm going to need to know what you would like each thing to do. Let's start with images though. If you can separate out the background image (or I can use this as a whole to test), we'll get that displaying first and foremost, then add all those little images/buttons that make up the main screen!
EDIT: Just tested a modified version of the skinswitcher (just points to a different filename), errors at no ui.dll found but it does switch (I knew it would error, but a starting point is always a starting point)... Looks like it's on to building out the images to make that. The ui part should house images/buttons that you want accessible all the time, anything as part of the main menu will dissapear when switching views/plugins.
Edit to the edit: Just ran the default mainmenu.dll with a stripped out ui.dll (displaying just the image you provided here) and it's good to go. Stripping the mainmenu stuff at the moment.
OK i wasn't sure if you need complete image(like ride runner) or seporate images I will break them up.