Replacement Interface

[Paradox]

i dont know whether anyone has mentioned this yet, but could you not have different viewing options? list for songs (like Tebb's), and grid icons (like DaveC's) for files and programs, in the same menu, would truly rock. i don't see why as ideas they're mutually exclusive..

​

Isuggestedthatearlier,youllhavetoexcusemylackofspacesibrokemyspacebarbutton.

 

[Goity]

I think the colourful one which DaveC and Hanz created is best, the dark one is too dark, and you just don't want to look at such a boring interface.

 

[subin]

I think the colourful one which DaveC and Hanz created is best, the dark one is too dark, and you just don't want to look at such a boring interface.

​

i wouldn't mind.. looks a bit like the classic winamp skin. and it could be skinned perhaps..

for me if the beauty is partly in the design and ease of interface, then it's as successful a menu, if not more.

 

[ThorC]

To me, it seems that there are two issues that are really taking place here. The design of an interface, and the platform of an interface.

In my opinion, the platform (how the interface works) is what is important, which is what I was trying to look at in my earlier post. What I think would be great is a customizable and flexible interface which can allow any of the designs in this thread to be applied. With a flexible platform, people can design the interface as they want, by putting their images and layouts together.

A platform for an interface which can allow all images and layouts to be changed in the way allowing for people to put together an interface design as they want it, and release it. Once such a platform is created, the designs will come naturally, just as the skins have for the current menu.

I was thinking a simple standard or language for laying out the interface, taking a similar approach to HTML (My attempt). There's also the XML approach, or even fully programmable menu's, although that might be harder. I think the primary point here is the freedom and customizability of the interface.

The interface is incredibly important. I mean, take Windows for example. Windows is just an OS, the applications and games are what are important, yet to be able to customize one's system is very important, and very fun and enjoyable. One only has to take a look at sites like Wincustomize to realise this. Personalizing, customizing can be quite important, but most importantly, enjoyable

Just trying to consider some options, I apologise if this is the wrong approach. I would just love to see a possibility that could allow all these designs to be put into practice, which shouldn't be too hard, rather than trying to find a nice design, which while important, the design is the layer on top - and it would be nice to have a supporting underlayer or foundation to hold it - Imagine seeing the designs offered here all as skins which we could apply, the freedom that would bring

Of course, I could have completely the wrong idea here, in which case I apologise - I tend to be quite good at that

 

[Squidge]

I think we need both styles in the menu system and be user selectable between them. So you have either a screen full of icons, or a list (like the icon view and detail view in windows).

The icon view look very nice, but I think I'd actually use the list view most of the time as long as it was alphabetical, as there's already a lot of programs out there now that will not have icons, and list view also means no time wasted actually loading the icons

Anyone used Z-Launcher on the Zodiac before? http://zztechs.com/en/zlauncher.php

 

[parag0n]

A platform for an interface which can allow all images and layouts to be changed in the way allowing for people to put together an interface design as they want it, and release it. Once such a platform is created, the designs will come naturally, just as the skins have for the current menu.

I agree, we need to put a standard XML based backend in place ASAP, maybe based on the freedesktop one posted above, as once that is designed and working, we can get on with building the frontends!

 

[Hodr]

Come on, its a Linux handheld after all. We need to keep it real.

 

[greenpix]

I like your html like approach.
But i'd like to get closer to a "programmed' interface, with something like this:

//First off, a Window is needed to be declared. A Window is a container for menues,lists and other items
window.MainW(0|0,320|200)show{//This sets the upper-left and bottom right corners of a Window that is by default shown
     setBackground(Color.FFFFFF);
     setMainFont(Verdana);//This just needs to be declared if the font is supposed to vary from the default font Arial
     menue(main).setBounds=(0|0, 320|50){
           button.gamesB(0|0,50|50);//This adds a button to the menue
           gamesB.setLabel("Games");//sets a Text to be shown in the Button. setBackground can also be used.
           gamesB.setAction(show.gamesW)&(hide.main2);//clicking this button will show/hide the Window games
           button.musicB(0|50,50|100);
           musicB.setLabel("Music");
           musicB.setAction(show.musicW)&(hide.music);
           }
     window.gamesW(0|50,320|200)hide{ //this window is by default hidden
           setBackground(Image.games/gamesBG.png);//loads a background image from the default skin directory
           field.field1(0|50,250|200);//here we create a Field that shows the content of a directory.
           field1.setDir(mnt/sd/games);//sets the directory to be shown by the field.
           field1.setItems(Icon+Filename);//Alternatives would be Icon only or Thumb for thumbnails (if possible)
           field1.Scrollbar.view(Visible);//sets up a visible default scrollbar
           field1.Scrollbar.Pos(0|25,0|200);//sets coordinates of the Scrollbar. Also possible:scrollbar.background & scrollbar.arrow
           }
     window.musicW(0|50,320|200)hide{
           setBackground(Image.music/musicBG.png);
           list.list1(0|50,250|200);//creates a List that shows the content of a directory
           list1.setDir(mnt/sd/music);
           list1.setItems(Icon+Song++Artist);//++puts the next item in the line below.
           list1.Scrollbar.view(Visible);
           list1.Scrollbar.Pos(0|25,0|200);
           rightShoulderButton.setAction(show.informationW)&(hide.informationW);//by the use of the right Shoulder Button the window information will be shown.
           window.informationW(200|50,250|200)hidden{ //creates a hidden Windows inside the other one
                  text(200|50,250|100);//creates a Textbox in the information Window.
                  text.set(musicW(list1.selectedItem).Bitrate++Artist++Song++Album);//puts the desired information of the selcted Item in this particular Order into into the Textbox.
                  }
           }
     }
window.extraW(0|200,320|240)show{
     setBackground(Image.extra/extraBG.png);
     batteryText(0|200);//creates a text battery indicator(as opposed to batterPicture)
     tvOutText.tvOutT(100|200);
     tvOutT.setLabel.on("");//replaces default text for activated TV-Out.
     tvOutT.setLabel.off("TV - It's Off!!");
     tvOutT.setBackground(Color.Blue);//
     tvOut.setColor.off(green);//just to show that you can do the same things with all objects
     }

 

[Hanz™]

I like your html like approach.
But i'd like to get closer to a "programmed' interface, with something like this:

//First off, a Window is needed to be declared. A Window is a container for menues,lists and other items
window.MainW(0|0,320|200)show{//This sets the upper-left and bottom right corners of a Window that is by default shown
     setBackground(Color.FFFFFF);
     setMainFont(Verdana);//This just needs to be declared if the font is supposed to vary from the default font Arial
     menue(main).setBounds=(0|0, 320|50){
           button.gamesB(0|0,50|50);//This adds a button to the menue
           gamesB.setLabel("Games");//sets a Text to be shown in the Button. setBackground can also be used.
           gamesB.setAction(show.gamesW)&(hide.main2);//clicking this button will show/hide the Window games
           button.musicB(0|50,50|100);
           musicB.setLabel("Music");
           musicB.setAction(show.musicW)&(hide.music);
           }
     window.gamesW(0|50,320|200)hide{ //this window is by default hidden
           setBackground(Image.games/gamesBG.png);//loads a background image from the default skin directory
           field.field1(0|50,250|200);//here we create a Field that shows the content of a directory.
           field1.setDir(mnt/sd/games);//sets the directory to be shown by the field.
           field1.setItems(Icon+Filename);//Alternatives would be Icon only or Thumb for thumbnails (if possible)
           field1.Scrollbar.view(Visible);//sets up a visible default scrollbar
           field1.Scrollbar.Pos(0|25,0|200);//sets coordinates of the Scrollbar. Also possible:scrollbar.background & scrollbar.arrow
           }
     window.musicW(0|50,320|200)hide{
           setBackground(Image.music/musicBG.png);
           list.list1(0|50,250|200);//creates a List that shows the content of a directory
           list1.setDir(mnt/sd/music);
           list1.setItems(Icon+Song++Artist);//++puts the next item in the line below.
           list1.Scrollbar.view(Visible);
           list1.Scrollbar.Pos(0|25,0|200);
           rightShoulderButton.setAction(show.informationW)&(hide.informationW);//by the use of the right Shoulder Button the window information will be shown.
           window.informationW(200|50,250|200)hidden{ //creates a hidden Windows inside the other one
                  text(200|50,250|100);//creates a Textbox in the information Window.
                  text.set(musicW(list1.selectedItem).Bitrate++Artist++Song++Album);//puts the desired information of the selcted Item in this particular Order into into the Textbox.
                  }
           }
     }
window.extraW(0|200,320|240)show{
     setBackground(Image.extra/extraBG.png);
     batteryText(0|200);//creates a text battery indicator(as opposed to batterPicture)
     tvOutText.tvOutT(100|200);
     tvOutT.setLabel.on("");//replaces default text for activated TV-Out.
     tvOutT.setLabel.off("TV - It's Off!!");
     tvOutT.setBackground(Color.Blue);//
     tvOut.setColor.off(green);//just to show that you can do the same things with all objects
     }

​

Don't you think that would just confuse the average user? Or are you suggesting that the interface is hardcoded?
I just think thats a bad idea. Much nicer to use XML as that is really easy.

 

[Paradox]

I think the colourful one which DaveC and Hanz created is best, the dark one is too dark, and you just don't want to look at such a boring interface.

​

i wouldn't mind.. looks a bit like the classic winamp skin. and it could be skinned perhaps..

for me if the beauty is partly in the design and ease of interface, then it's as successful a menu, if not more.

​

thats.a.skin,itcanbechanged,weretalkingabouttheinterface

 

[greenpix]

Don't you think that would just confuse the average user?

You sure have a point here, but what I was trying to do, is creating an alternative Thors approach that didn't seem to offer the same amount of interactivity to me. You may also consider that there would be a default layout file that could be changed and as long as it is well documented I dont think it wont be to hard to work with.
In the end I quess a real wysisyg-editor would be needed anyway. This way more people could play arround, without having to think of coordinates all the time. If anyone would support a new GUI-System I would be glad to create an editor lfor it.

 

[Hanz™]

Don't you think that would just confuse the average user?

You sure have a point here, but what I was trying to do, is creating an alternative Thors approach that didn't seem to offer the same amount of interactivity to me. You may also consider that there would be a default layout file that could be changed and as long as it is well documented I dont think it wont be to hard to work with.
In the end I quess a real wysisyg-editor would be needed anyway. This way more people could play arround, without having to think of coordinates all the time. If anyone would support a new GUI-System I would be glad to create an editor lfor it.

​

There is no reason that XML could not provide complexity and interactivity.

 

[DaveC]

First of all, thanks to everyone who liked my interface, much apreciated

Second, I agree with DaveC about matrix system being faster and showing more icons, but you forget that you can't show the entire file name under the icon, and in my opinion you will finish finding something faster if you actually can see what you're looking for.

I could put it so 10 items could be shown, and the programmer could make it so you would press L and R to jump 5 items up or down in the list...

​

Yeah but lists are BORING as hell, show less on screen, and slower to navigate. They have many minuses and few plusses. The only plus is you can have long drawn out file names. BFD you can always rename the .GPE you know. It doesn't HAVE to be 30 characters long

Besides the fact that icons show more on screen and are better for navigation etc. I also like how the community can design their own icons and backgrounds to show off their awesome Photo shop skillz. I have seen some great looking stuff come from members here. WTF can you do with a boring list? Change the colors? BAH! Whatever the final decision it *must* at least contain the option for an icon view, or at least hooks in the code so someone could add one. Look at all media devices PDAs etc these days they have icons for the reasons mentioned. The GP2X would look boring as hell with only that list view, ick.

 

[Hanz™]

First of all, thanks to everyone who liked my interface, much apreciated

Second, I agree with DaveC about matrix system being faster and showing more icons, but you forget that you can't show the entire file name under the icon, and in my opinion you will finish finding something faster if you actually can see what you're looking for.

I could put it so 10 items could be shown, and the programmer could make it so you would press L and R to jump 5 items up or down in the list...

​

Yeah but lists are BORING as hell, show less on screen, and slower to navigate. They have many minuses and few plusses. The only plus is you can have long drawn out file names. BFD you can always rename the .GPE you know. It doesn't HAVE to be 30 characters long

​

Lists work very well when screen space is needed for other things. Or when you want to have collumns showing Artist, Album and so on.

 

[DaveC]

Lists work very well when screen space is needed for other things. Or when you want to have collumns showing Artist, Album and so on.

​

That is fine for those that use the GP2X only as a power hungry MP3 player. For everyone else it would suck. Besides the music player itself can have it listed like you say. It is not needed for the main interface, it is way too boring.

Also lists don't work any better than icons when you need screen space for other things whatever that may be. Icons can be placed anywhere.

Having only a list would make the GP2X look boring, it would totally ruin the look of it. Imagine when someone turns one on for the first time and is confronted not by a nice looking slick interface with great artwork but instead a drab list of text.

No way.

 

[SolidSnake]

am I the unique that like the actual menu with the KDE skin o.0 ?

the unique thing I miss is some place to check the atual clock speed and some powerful console

 

[DijiTao]

I don't think a fully programmable interface is a good idea – It needs to be easy to make new interfaces, and skins for those interfaces. What I suggested in my post awhile back I think still stands as the best approach. We need a standard set of “widgets” such as icon areas, select item description etc... and then you use XML to determine which “widgets” are placed where.

--this post--
http://www.gp32x.de/board/index.php?showt...ndpost&p=361086

 

[DaveC]

A platform for an interface which can allow all images and layouts to be changed in the way allowing for people to put together an interface design as they want it, and release it. Once such a platform is created, the designs will come naturally, just as the skins have for the current menu.

I agree, we need to put a standard XML based backend in place ASAP, maybe based on the freedesktop one posted above, as once that is designed and working, we can get on with building the frontends!

​

As long as this approach doesn't produce massively huge interface data that has to be loaded on startup. Remember, boot times are important. You don't want to pay the price in boot times everytime you turn on the unit for the benefit of designing an interface once. Clean small code is important here being a gaming/media device and not a PDA or PC.

 

[iignotus]

I'm beginning to get the impression that Dave doesn't like lists.

 

[nickspoon]

I'm beginning to get the impression that Dave doesn't like lists.

A while ago, I got the impression that Dave doesn't like anything.