QOrbiter - Revision history

Marie.o: /* Where To Find It */

2016-06-30T04:38:39Z

Where To Find It

←Older revision		Revision as of 04:38, 30 June 2016
Line 8:		Line 8:
	The latest version of qOrbiter can always be found on the developers [http://langstonball.com/downloads/category/1-qorbiter-downloads site].		The latest version of qOrbiter can always be found on the developers [http://langstonball.com/downloads/category/1-qorbiter-downloads site].
	== Installation Instructions ==		== Installation Instructions ==
	~~More details on~~ Android ~~installation for the qOrbiter (some applies universally), ca~~ be ~~found at~~ [~~[Android Orbiter]~~],		qOrbiter for Android should be installed from [http://192.168.80.1/lmce-admin/index.php?section=orbitersWin the local core].

	=Concept=		=Concept=

Marie.o: /* Example */

2016-04-11T13:24:12Z

Example

←Older revision		Revision as of 13:24, 11 April 2016
Line 157:		Line 157:

	followed by a start of qOrbiter with the -x command line switch as specified above, ie.		followed by a start of qOrbiter with the -x command line switch as specified above, ie.
	~~qOrbter~~ -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins		qOrbiter -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins

	Once you have verified that your changes indeed end up in your qOrbiter, you no longer need to exit and restart qOrbiter, but press <F5> to refresh the QML inside of qOrbiter.		Once you have verified that your changes indeed end up in your qOrbiter, you no longer need to exit and restart qOrbiter, but press <F5> to refresh the QML inside of qOrbiter.

Marie.o: /* Example */

2016-04-11T13:22:32Z

Example

←Older revision		Revision as of 13:22, 11 April 2016
Line 149:		Line 149:

	Next, you try to start qOrbiter with the commandline switch to point to your downloaded stuff		Next, you try to start qOrbiter with the commandline switch to point to your downloaded stuff
	~~qOrbter~~ -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins		qOrbiter -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins

	This should show the same qOrbiter layout as before. Quit qOrbiter, and we make a small change to verify that we are indeed using the QML code in /usr/src directory structure. For example, change line 82 in MainLayout.qml from		This should show the same qOrbiter layout as before. Quit qOrbiter, and we make a small change to verify that we are indeed using the QML code in /usr/src directory structure. For example, change line 82 in MainLayout.qml from

Marie.o: /* Example */

2016-04-05T18:08:03Z

Example

←Older revision		Revision as of 18:08, 5 April 2016
Line 158:		Line 158:
	followed by a start of qOrbiter with the -x command line switch as specified above, ie.		followed by a start of qOrbiter with the -x command line switch as specified above, ie.
	qOrbter -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins		qOrbter -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins

			Once you have verified that your changes indeed end up in your qOrbiter, you no longer need to exit and restart qOrbiter, but press <F5> to refresh the QML inside of qOrbiter.

Marie.o: Example on how to get started with QML modification.

2016-04-05T18:05:41Z

Example on how to get started with QML modification.

←Older revision		Revision as of 18:05, 5 April 2016
Line 141:		Line 141:
	: your skin, both for users and the actual application. its where screen sizes are defined, scaling functions can be		: your skin, both for users and the actual application. its where screen sizes are defined, scaling functions can be
	:located, and anything else relating to the visual style of the application as relating to your skin		:located, and anything else relating to the visual style of the application as relating to your skin

			==Example==
			This is a small example on how to get started, using the existing skins.

			First, you need to checkout the skin from out git repository
			git clone https://git.linuxmce.org/linuxmce/linuxmce.git /usr/src/linuxmce-src

			Next, you try to start qOrbiter with the commandline switch to point to your downloaded stuff
			qOrbter -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins

			This should show the same qOrbiter layout as before. Quit qOrbiter, and we make a small change to verify that we are indeed using the QML code in /usr/src directory structure. For example, change line 82 in MainLayout.qml from
			buttonText: qsTr("Sleeping Menu")
			to
			buttonText: qsTr("Alarm Menu")

			followed by a start of qOrbiter with the -x command line switch as specified above, ie.
			qOrbter -x /usr/src/linuxmce-src/src/qOrbiter/qOrbiter_src/qml/skins

GolgoJ4: /* File Structure */

2016-04-05T17:53:52Z

File Structure

←Older revision		Revision as of 17:53, 5 April 2016
Line 64:		Line 64:
	** The default qOrbiter installation does not ship with the skins folder, so you should obtain it from http://git.linuxmce.org		** The default qOrbiter installation does not ship with the skins folder, so you should obtain it from http://git.linuxmce.org

	Providing a path to your own skins.		==== Providing a path to your own skins. ====
	The default qOrbiter does not ship with skins. With non mobile devices, you can provide a custom path to skins. This allows you to develop the UI without needing to re-compile the application (or needing a full development setup)		The default qOrbiter does not ship with skins. With non mobile devices, you can provide a custom path to skins. This allows you to develop the UI without needing to re-compile the application (or needing a full development setup)
	* To set your own path, you need to pass a special command line option: -x <path/to/your/skins>		* To set your own path, you need to pass a special command line option: -x <path/to/your/skins>

GolgoJ4 at 17:53, 5 April 2016

2016-04-05T17:53:04Z

←Older revision		Revision as of 17:53, 5 April 2016
Line 63:		Line 63:
	* If you provide your own path to the skins folder, please ensure that you have at least the 'default' folder.		* If you provide your own path to the skins folder, please ensure that you have at least the 'default' folder.
	** The default qOrbiter installation does not ship with the skins folder, so you should obtain it from http://git.linuxmce.org		** The default qOrbiter installation does not ship with the skins folder, so you should obtain it from http://git.linuxmce.org

			Providing a path to your own skins.
			The default qOrbiter does not ship with skins. With non mobile devices, you can provide a custom path to skins. This allows you to develop the UI without needing to re-compile the application (or needing a full development setup)
			* To set your own path, you need to pass a special command line option: -x <path/to/your/skins>


	Files should be arranged in the following manner. Please note that you are not required to design your skin according to the default skin. This will be a description of how the default skin works and is organized.		Files should be arranged in the following manner. Please note that you are not required to design your skin according to the default skin. This will be a description of how the default skin works and is organized.

GolgoJ4 at 18:31, 4 April 2016

2016-04-04T18:31:41Z

@@ Line 30: / Line 30: @@
 One should always check the official doc's to see what methods are supported for setting properties.
@@ Line 93: / Line 87: @@
 # OS
 # Distribution (ubuntu, opensuse, etc)
 ==Adding to the filestructure==

GolgoJ4: /* File Structure */

2016-04-04T18:29:13Z

File Structure

@@ Line 79: / Line 79: @@
 :::<folder>components
 :::<folder>js (if used)
 ==Adding to the filestructure==

GolgoJ4 at 18:12, 4 April 2016

2016-04-04T18:12:49Z

←Older revision		Revision as of 18:12, 4 April 2016
Line 119:		Line 119:
	: your skin, both for users and the actual application. its where screen sizes are defined, scaling functions can be		: your skin, both for users and the actual application. its where screen sizes are defined, scaling functions can be
	:located, and anything else relating to the visual style of the application as relating to your skin		:located, and anything else relating to the visual style of the application as relating to your skin

	~~==Variables==~~
	~~'''DEPRECIATE, USE ABOVE SECTIONS'''~~
	*'''ref dcerouter''' - used as a reference object to call functions
	*'''QString dcemessage''' - orbiter messaging output for display in string format
	*'''srouterip''' - string of the routerip
	*'''ref manager''' - reference object for qorbitermanager
	*'''QObject filedetailsclass''' - QObject used for holding file information from the router for use in the UI
	*'''bool connectedState''' - represents the current connected state of the device
	*'''int iPK_Device''' - the orbiter device number
	*'''QTime screen1time''' - clock. will display in
	*'''QTime currentDateTime''' - current date and time
	*---need to outline 'role' data for member data-----
	*'''DataModel currentRoomLights''' - list model of the current room lighting scenarios.
	*'''DataModel currentRoomMedia''' - list model of the current room media scenarios
	*'''DataModel currentRoomClimate''' - list model of current room climate scenarios
	*'''DataModel currentRoomTelecom''' - list model of the current room telecom scenarios
	*'''DataModel currentRoomSecurity''' - list model of the current room security scenarios
	*'''DataModel userList''' - list of the users in the linuxmce system
	*'''DataModel roomList''' - list of the rooms in this home.
	*'''DataModel mediaplaylist''' - the current playlist in list model form
	*'''DataModel simpleepg''' - simple epg model, can sometimes cause router crash.
	*'''DataModel playlistModel''' - list model of the playlist??
	*'''DataModel skinsList''' - list model containing the list of availible and ready skins
	*'''ListModel screenshotAttributes''' - listmodel of attributes correlating to thumbnail/screenshot selection
	*--------------------------------------------------------------------------------
	*'''QObject dcenowplaying''' - QObject containing the properties of the now playing object for this ea
	*'''QColor nowPlayingColor''' - color of now playing button
	*'''int currentcommandgrp''' - int of the current command group being executed
	*'''int gmediaType''' - int correlating to the mediatype the grid is navigating.
	*'''int currentroom''' - int representing the current EA of the orbiter
	*'''QString currentuser''' - string of the current user

	~~==Functions==~~
	~~This will be broken down by section with certain parts relating directly to the screens where they are used~~

	~~==HomeScreen==~~
	~~Special Screen that doesnt have to be implemented, but since it can be considered the start page, certain~~
	~~data is provided to make life easier for everyone.~~