Forums : iPhone Panel 2.0, next generation
This page last changed on Aug 07, 2009 by mredeker.
After playing around with the current iPhone panel and looking at the requirements I defined for my home, I created some mockups for a possible next generation iPhone panel UI.
As you can see I added a tab bar at the bottom of the application. This control gives the UI a really nice look and lets you navigate to the most often used screens. We would need an extra tag in the iphone.xml to say that we want a tab bar and then we have to have a tag for each activity to define if this activity should appear as a tab in the tab bar.
The first mockup "TV" is just a one screen activity because I want to use gestures on it. If we have a multi screen activity the left and right swipe would be taken. This is my general TV remote which is probably used 80% of the time. To be able to control the TV without having to look at the device I want gestures for the most common functions. I was thinking of swipe up/down for channel up/down, swipe left/right for volume up/down and drawing a circle for mute. At least those are the keys on my TV remote which are pretty outworn. We could think of a few gestures which we support and then use the designer to map a button to a gesture. This would mean that we need a new tag for a button to say that this is button can also be triggered from a gesture.
I have an activity "Lights" which shows up in the tab bar but this does not directly display a screen. It will group all "light" related activities together to be able to "drill-down" to whatever 'real' light activity I want to control. This is an extra layer to group activities together for the tab bar.
On the "Livingroom" and "Bedroom" light screens you can see that I used the iPhone table control to organize my switches. I thought it looks pretty neat and we would be able to support the scrolling up and down which Marc already mentioned in the composer discussion. For the light switches itself I used the on/off switch control to be able to see the status. This would involve some kind of feedback configuration. So if that screen is made visible all "status switches" will do a REST request to ask for their current status. Since I also have dimming devices I used the slider control for the dimming. This device would also need a feedback to be able to adjust itself to the current dimming position.
Having stayed at the citizenM hotel, I liked the RGB lights they had and I immediately got some cool RGB led's from IKEA. I control them with a KNX/DALI gateway and this looks really cool. So I created a colorwheel to select the color I want the led's to show. With my KNX/DALI gateway I can also program some nice sequences to have automatic color changes which can be started through scenes. So the colorwheel is probably some kind of special control which can be configured. You also need three KNX group addresses for it to dimm each color.
For some grouping or as labels I want to have elements that don't represent a button or action. This could just be plain text or an image. Right now we only have buttons which trigger a REST command. Each activity should also be able to have a background image. If we a have a multi screen activity the image would stick and the buttons will flow on top off the image. This is a really cool effect and it looks great.
As Marc mentioned in the other post a floorplan could be used to navigate to buttons which are available in one room or maybe to display the status of lights in one room. We could use the zoom in/zoom out with two fingers gesture to go from the whole floorplan to a specific room. Once a certain room size is reached we could overlay the controls to be able to see the status eg. light bulb which is on or off. This is done in a lot of other KNX visualization tools.
|Document generated by Confluence on Jun 05, 2016 09:30|