Difference between revisions of "QOrbiter"

From LinuxMCE
Jump to: navigation, search
(Home Screen)
Line 13: Line 13:
 
currentUser: the current orbiter user
 
currentUser: the current orbiter user
 
userList: listmodel of all users
 
userList: listmodel of all users
 +
  
 
==Location==
 
==Location==
Line 19: Line 20:
  
 
==Home Screen==
 
==Home Screen==
=List Models for Scenarios=
+
===List Models===
 
These are prepared in c++ and provided to the QML. If you are creating a skin, you will use these variables to call certain arrays
 
These are prepared in c++ and provided to the QML. If you are creating a skin, you will use these variables to call certain arrays
 
of objects like  scenarios, or userlists. This makes it easier for the designer, as they information will be populated and they only need to fill in the variable.
 
of objects like  scenarios, or userlists. This makes it easier for the designer, as they information will be populated and they only need to fill in the variable.
Line 36: Line 37:
  
 
==Images==
 
==Images==
 +
 
Images can be loaded in multiple ways and will be discussed here in the future.
 
Images can be loaded in multiple ways and will be discussed here in the future.

Revision as of 23:20, 14 July 2011

qOrbiter is a new LinuxMCE orbiter designed to run on a multitude of devices as well as provide flexible skinning options to make it truly one's own. The purpose of this document now is for documentation of the app moving forward, followed by it being a reference for creating ones own skin

Concept

Variables

Button variables will be automatically set, so no programming will be needed. There will be variables provided so that skin designers can add information to their skin at will

The format is PropertyName: what it gives

User

currentUser: the current orbiter user userList: listmodel of all users


Location

currentroom: the current room / ea roomList: list of ea's rooms

Home Screen

List Models

These are prepared in c++ and provided to the QML. If you are creating a skin, you will use these variables to call certain arrays of objects like scenarios, or userlists. This makes it easier for the designer, as they information will be populated and they only need to fill in the variable.

currentRoomLights: provides by room scenario list for lights. you will need to use your own delegate. a default is provided currentRoomMedia: provides by room scenario list for media. you will need to use your own delegate currentRoomClimate: provides by room scenario list for climate. you will need to use your own delegate currentRoomTelecom: provides by room scenario list for telecom. you will need to use your own delegate currentRoomSecurity: provides by room scenario list for security. you will need to use your own delegate

Data Grids

Media Grids

Colors

Images

Images can be loaded in multiple ways and will be discussed here in the future.