LinuxMCE - User contributions [en]

Workstation Agent Development Task List

2012-02-07T17:46:33Z

David: /* Linux Specific Tasks */

Here are the tasks for the Workstation agent. Pick one, and put your signature next to it. Strike it off the list when done.

== LinuxMCE Specific Tasks ==

* Create the Device Templates for the Linux, Windows, and Mac workstations. --[[User:Tschak909|Tschak909]] 01:55, 9 April 2011 (CEST) '''(DONE) for Linux'''
* Finish the Workstation Media Player --[[User:Tschak909|Tschak909]] 01:55, 9 April 2011 (CEST)

== Windows Specific Tasks ==

* Write a script or application that calls MessageSend with MH Play Media, and a path to the media. This path would look like the path from a Linux machine, as the Media Player will translate this path internally.
* Make a file association that calls this script for media files that VLC can play (this needs to be done for ALL the file types that VLC can play)

== Linux Specific Tasks ==

* Write a script or application that calls MessageSend with MH Play Media, and a path to the media.
* Make a file association that calls this script for media files that VLC can play, for GNOME and KDE (xdg? freedesktop? is there a standard way to do this? find out.)

There is a standard way, see http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html

== Installation Package Tasks ==

It is '''IMPERATIVE''' that there is only a single installation package, with everything needed for the workstation agent to work. No Buts.

These tasks need to be done for (mark responsibility for the platforms below):

* Windows (somebody take responsibility)
* Linux (somebody take responsibility)

* Write code in the installer that talks to 192.168.80.1:7238, sends the appropriate string so that the system will create the appropriate devices. (look at src/NewMD_Interactor)
* Package VideoLan Client from source and fold into the Installation package.
* Package The Orbiter executable from TSCHAK and fold in.
* Package the App server executable
* Package the Workstation Agent Executable
* Package the MessageSend executable
* Make a script that creates shares to the public shares at installation.

Things to still deal with

* Making code to spawn the web browser in response to a URL from LinuxMCE to Workstation.
* Making code to spawn the web browser in response to a URL from Workstation to LinuxMCE.
* Handling file shares to user shares dynamically in response to a PIN # being entered.

Qml Ui

2011-11-28T23:16:50Z

David:

This page is intended to serve as an ongoing development guide in relation to using QML as the engine for LinuxMCE's user interface. We shall outline relevant documents relating to QML as well as specifics for designing a skin. Please note, if you are reading this, then this is in fact an '''ongoing''' guide and as such information is apt to change. Personal notes are to be kept in the discussion area of this page, please post only code, links, or other relevant data to UI development. This message will self-destruct in 10 seconds.

=QML KnowledgeBase=
An Overview of what QML is http://labs.qt.nokia.com/2009/05/13/qt-declarative-ui/
A document on styling and whats important, skinning - http://developer.qt.nokia.com/wiki/QmlStyling

*http://developer.qt.nokia.com/wiki/JavaScript_programmer
*http://doc.qt.nokia.com/4.7-snapshot/qdeclarativeintroduction.html
*http://doc.qt.nokia.com/4.7-snapshot/qdeclarativeelements.html

Stay tuned to this development space
==Downloads & Initial setup==
*http://qt.nokia.com/downloads The SDK you will need. Previous releases will NOT work

=Setting it up=
I installed qt creator into home, although the default location is opt. Installing it into home will allow you get up and running right away but if installed into opt you will need to export some paths as described below.

*SVN Checkout of the current /src tree from the svn
*you need to install subversion
sudo apt-get install subversion
*you then check out the source tree by entering this:
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-1004/src
and the web part like this
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-1004/web

Next, we install the QTSDK you downloaded.
*Install QT SDK as outlined

You need a qtorbiter- do this by selecting "Orbiters" from within the webadmin pages and select "qOrbiter" from the drop down menu at the bottom. A router reload is probably required. Afterwards, run the qOrbiterGenerator script from a browser:

http://dcerouter/lmce-admin/qOrbiterGenerator.php?d=+iPK_Device

where +iPK_Device is the device id of the orbiter you just generated.

After you've started QT SDK, some configuration is required to load the orbiter. First, you need to load the project itself. Navigate through your source tree to QOrbiter/Qorbiter_src. In this directory, you will find a .pro file named QOrbiter_src.pro. Open this and it will load the project into qt Creator. It should go without saying, but read the README!

Next, open the qOrbiter project and setup the Build Settings. Do this by clicking the "Projects" button from the left side menu. You need to add to the "Additional arguments:" line for qmake under Build Steps. Do this by clicking the "Details" button to the right of qmake: and additional arguments. These are the current options:

"CONFIG+=for_desktop" :: windows*, mac,linux desktop
"CONFIG+=for_freemantle" :: maemeo5 devices
"CONFIG+=for_harmattan" :: harmattan based meego
"CONFIG+=ANDROID" :: android

Please ensure you include the quotes for the "CONFIG+= whatever"

For example, after adding the above arguments, my "Effective qmake call:" box looks like this, where [username] is my ubuntu login name:

qmake /home/[username]/src/qOrbiter/qObiter_src/qObiter_src.pro -r -spec linux-g++ "CONFIG+=for_desktop"

Next, ensure 'shadow build' is checked in this same menu. Then you need to set the path to '../build-output'

Next, add the PK_Device of your qOrbiter to the "Run Settings". After clicking on "Projects", near the top will be options for the particular simulators you are using. You will see a "Build" and a "Run" button. Clicking on the "Run" button will display the "Run Settings" page. In the "Arguments:" box, enter:

-d iPK_Device

Where iPK_Device is the device id of your qOrbiter.

== Setting up for android development ==

Download Necessitas from http://sourceforge.net/p/necessitas/home/necessitas/

Open the project and set it up as above, using

"CONFIG+=ANDROID" :: android

There is a bug in necessitas at present. Starting the app as is will give an error - "can't find read elf information".

To fix, click '''Projects''' -> '''Android''' -> '''Run'''

Open the '''Package configurations''' section and choose the '''Application''' tab. View/ slightly alter the '''Application Name'''. This will fix the error.

Lastly, choose 'Use devices qt libs' and use a real device for preference.
If you must use the SDK simulator, click 'Install Ministro System Wide...' and download the APK from http://sourceforge.net/projects/ministro.necessitas.p/files/

==Special Notes==

via irc and TSCHAKeee Note, this was for bootstrapping an Archos 9 tablet. Desktops should not need to do this.

i literally just copy -ax /opt/QtSDK/Desktop/* to the core
either tarballing it up or otherwise
then export '''PATH=/opt/QtSDK/Desktop/Qt/473/gcc/bin:$PATH'''
then export '''LD_LIBRARY_PATH=/opt/QtSDK/Desktop/Qt/473/gcc/lib:$PATH'''
this can be placed in your .bash_profile
and you can then run qOrbiter

'''NOTE''' --[[User:Langstonius|Langstonius]] 08:13, 8 July 2011 (CEST)
You shouldnt have to manually tweak the connection parameters at all

You will also need to do a few things to make it interact with your LinuxMCE installation.
*If your installation is up to date, you can add it via the Orbiters page in the webadmin. Otherwise, go to the device tree and add it as a child of the core.
*Quick reload the router. Orbiter Generation is not done the normal way as explained in the next step
*Orbiter Generation is done by qOrbiterGen.php. You need to:
# copy qOrbiterGenerator.php from the web/lmce-admin/ directory in your svn checkout to the core (in /var/www/lmce-admin) you will be working with.
# visit this page http://dcerouter/lmce-admin/qOrbiterGenerator.php?d=deviceno (where deviceno should be replaced with the devicenumber of the orbiter in webadmin you want to use)
# if your device number is found and you entered everything properly, you will see a confirmation.
# you can regenerate the orbiter in the future from inside the orbiter, no need to visit the page after configuration.

*it should now run

You should then be able to compile / run / hack on qOrbiter

=Initial Findings=
All research is being done against the current branch of code in the svn. The Big Idea(tm) is do the following:
Create a new orbiter using qml as our ui both for its portability and skinning ease of use.

Initial experiments
http://wiki.linuxmce.org/index.php/Qml
http://forum.linuxmce.org/index.php?topic=11722.0

If you are interested in playing with skinning only you can find the skinning document [http://wiki.linuxmce.org/index.php/QOrbiter QOrbiter Development Page].

==UI==
*Determine to what level we want QML to control the UI vs the c++ code.
*Provide a set of constant objects for UI designers to connect to for data
*Provide basic qml elements for some design objects. Think buttons specifically. These would be referred to as custom qml 'components'
*Develop a base template for styles to follow. This would allow changes to be made globally that would affect all qml objects loaded.
*determine animations sets for our custom qml objects

Following this idea further, its been decided to attempt to define the orbiter varables and data as a complex Data model. While the disadvantage is the complexity of the model, it will expose essentially a simple api to skin designers to access linuxMCE data in their skin, further removing programmatic responsibilities from the ui.

The initial work in this area includes
*creating the needed subclassed models from QAbstractListModel
*creating a purpose specific orbiter generator as the current orbiter gen does more than is needed and is too tightly coupled to the concept of deign_obj's something we wish to get away from.

==C++==
There will need be be considerable time invested into understanding and picking apart certain functions of the existing orbiter to determine relevance in any new orbiter. These include not just the orbiter itself, but datagrids and how it interacts with other plugins. We will need to translate the functionality to new methods because of the inherent difference in the two ui toolkits. Things such as screen handlers and the callback system will be replaced with the signal and slots mechanisms of Qt and so must be understood to be replaced.
*Datagrids - Custom DataModel has been implemented.
*Screen Handlers - Handled by native qt functions
*Mouse Handlers - Not needed as of yet

=

[[Category:Programmer's Guide]][[Category:QML]][[category:QOrbiter]]

Installing LinuxMCE on Virtual Machine via VirtualBox

2011-11-13T22:40:51Z

David:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{stub}}

 
'''THIS IS STILL WORK IN PROGRESS. WHAT YOU SEE HERE WILL GET YOU STARTED BUT WILL NOT COMPLETE IT JUST YET, PLEASE HELP FIX THIS PAGE WITH YOUR OWN INPUT'''
 
----

= Advantages of running LMCE in a Virtual Machine =
Virtualization is a good way to take LinuxMCE for a test drive before spending any money on new hardware, or running a virtual core to serve multiple media directors without dedicating a new machine. USB and serial devices are accessible to a virtual machine so USB-UIRT and other popular devices should be usable (note pci cards cannot be use in a virtual machine as of yet). Another advantage is the ability to save working LinuxMCE setups (snapshots) which you can revert to in case you break your LMCE install.

Virtualisation is also useful from the point of view of running the [[MD]]s themselves; for instance, you may have a "normal" desktop in a given room that you don't want to dedicate to LMCE (and you don't want to buy extra hardware). A [[VirtualBox_MD|VirtualBox MD]] allows you to run an [[MD]] in a window on the desktop machine.

= Instructions for Core Installation =

== Different types of install ==

=== DVD Install ===
LinuxMCE 0810 DVD (2010/03/16) installs relatively hassle free in a virtualbox. Some erratic behavior with the wizard and media director in the virtual machine but all features seem to working to spec. Confirmed boot of virtual diskless MDs and real diskless MDs.

=== CD Install ===
LinuxMCE 0810 cd install seems to have some problems with AV Wizard.

== Download and Install VirtualBox ==
(updated for Virtual Box 4.0.2)
# First grab the latest VirtualBox from here [http://www.virtualbox.org/wiki/Downloads VirtualBox download page] '''Right click and save as'''
# Install VirtualBox on your machine
# If you are a Linux user make sure that
## your username is added to vboxusers (installed should do that automatically)
## Log off and back in.
==Create your new VBox==
#Start VirtualBox.
#Click New
#Click Next
#Name it whatever you want and choose Linux 2.6
#Click Next
#Give your machine at least 1024
#Click Next
#Make sure Boot Hard Disk is checked, and choose Create new hard disk and Click Next
#Click Next
#Check Fixed-size and Click Next
#Allocate at least 50GB of space and Click Next
#Click Finish to Create your HD. This may take a while. Go grab a Beer! (20GB took 6 min)
#Click Next to use your new virtual drive
#Click Finish
==Setup your Virtual Machine==
#Select your VM and Click on General on the right or settings up above.
#Click System
##Check CD/DVD-ROM in the boot order.
#Click Display
##Give as much memory as you can for video. I did all 128MB.
###Note: Do NOT check Enable 3D Acceleration before you have installed the OS as it can cause the OS to not boot.
#Click Audio
##Check Enable Audio and choose ALSA Driver
#Click Network (still testing how these settings work on the network)
##Changed Adapter type to the Intel NIC
##Change NAT to Internal Network
##Under Network Name type, vboxnet0
#Click Ok

===Development Network Settings===
These allow the core to communicate with the outside world via one network card and have an internal 80.X network that it can manage that is cut of from the outside world, but is accessible from the host.

##Adapter 1
###Attached to : Bridged Adapter
###Intel PRO
###Name : eth0
###Promiscous Mode : Allow All
##Adapter 2
###Attached to : Host-only adapter
###Intel PRO
###Name : vboxnet0
###Promiscous Mode : Allow All

Once you have done this, go into the main VirtualBox gui,

File -> Preferences -> Network -> vboxnet0

Change the ipv4 address to 192 168 80 10 and disable the DHCP server.

===Virtualised Core Network Settings===

These allow the core to communicate with the outside world via one network card and have an internal 80.X network that linux mce can manage. Both network cards must be physical ones on the host.

##Adapter 1
###Attached to : Bridged Adapter
###Intel PRO
###Name : eth0
###Promiscous Mode : Allow All
##Adapter 2
###Attached to : Bridged adapter
###Intel PRO
###Name : eth1
###Promiscous Mode : Allow All

When LinuxMCE boots, it should start giving out DHCP leases as normal

==Installing LinuxMCE==
#Start your VBox and boot the DVD
#Follow the instructions. Sit back and have another beer :)
==Configure LinuxMCE==
#Step 1. Choose, '''vga'' and '''800x600'''. (as of this writing, they were the only modes i could get to work).
#Step 2. Static images (I only tested that since i wasn't having luck with other resolutions. Please report if you get others working).
#Step 3. Click Ok.
#Step 5. Analog Stereo.
#Step 6. Adjust the volume if you want. Click ok.
#Step 9. Click I Agree (Yes i can count but it skips steps 7 & 8 due to it not being available)
#Now we wait for Sara!
#Once she appears, click Next
#Tell her you don't want to use a remote
#Enter in your name and click next
#Click Okay
#Click Next
#Click Next (unless it didn't select the right country)
#Enter your zip and hit next. If it doesn't find it, just hit skip and hit next.
#Select your rooms and click next.
#It now detected itself as a file server. Click on it to use it and select where it is.
#Continue without setting up light,alarm and voip setup.
#Choose MythTV
#Click DOne
#Click on Media Player
#Select where you are and choose to not control my TV
#No receiver
#Click Next
#Click Done
#Click Done
#Click Next
#Start using the system. That was easy wasn't it? :) :) You might have to wait until it's finished downloading all the crap it needs to download.

= Instructions for MD Installation =

There is a simple howto for a VirtualBox MD installation [[VirtualBox_MD|here]].

= Troubleshooting UI2 =
If you are getting "failed to initialize OpenGl" when choosing UI2 for the orbiter, try the following
It seems that the libglx.so.195.36.15 somehow does not give OpenGl in virtualbox
a quick work around:
Replace /usr/lib/xorg/modules/extensions/libglx.so with the one you can download here [http://mce.commsbyte.com/index.php?option=com_joomdoc&task=doc_details&gid=30&Itemid=25]
At this point you will only have Software rendering which is very slow and laggy, to get better performance do the following
rm /usr/lib/libGL.so.1
ln -s /usr/lib/nvidia/libGL.so.1.2.xlibmesa /usr/lib/libGL.so.1
After this reboot the machine and it should be fairly smooth

Special thanks to commsbyte for figuring this out
 
 
=Example Scenario's=
Various scenario's and example situations. I will work out this situation on the wiki, I will update the below situations with links.

#Host Linux/Windows -> Linuxmce Core in VM
#Host Linux/Windows -> Linuxmce Core and MD in VM
#Host Linux/Windows -> Linuxmce Core in VM, serving network
#Host Linux/Windows -> Linuxmce MD in VM connected to Core
== Additional links ==
[http://forum.linuxmce.org/index.php?topic=8732.0 Forum - vbox + lmce 0810-alpha + ui2 = working] 
[[Installing kubuntu 1004 on virtualbox]]