LinuxMCE - User contributions [en]

Media Plugin

2007-03-29T20:34:16Z

T0ny:

{{Plutoperm|This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.}}[[Media Pictures (mediapics)]]

AOpen MiniPC

2007-03-27T09:48:48Z

T0ny:

[http://minipc.aopen.com/Global/spec.htm aOpen MiniPC]
Mini PC is coming to my table in the next few days. Like anything else it has pros and cons. Let me do initial evaluation...

*Pros
**???
*Cons
**no digital audio (SPDIF) - it seems like SPDIF is present on motherboard and soldering connector can help...
**no com port to control A/V equipment over Rs232C (workaround is USB to rs232 but haven't tested it)...

Update --[[User:Tinia|Tinia]] 10:25, 7 June 2006 (BST) :

AOpen is running as MD. Playing ripped DVD chokes it : 72% for Xine player and 26% for XFree...

--[[User:Nite man|Nite man]] 02:33, 4 July 2006 (MST) [http://shopper.cnet.com/AOpen_MiniPC_MP915_B_SuperMulti/4014-11485_9-31664595.html The price] is $334.

Update --[[User:Totallymaxed|Totallymaxed]] 08:56, 22 July 2006 (MST)
The Aopen MiniPC performs beautifully once it has the i810 drivers installed. MD playback of DVD's, Ripped DVD's from the core and streamed TV are all delivered very smoothly (once that vesa driver is out of the way!). A great looking, very small, slick Media Director. One caveate currently... there is an intermittant bug in either the i810 driver or Xine's handling of xv that exhibits itself as video that looks like its been through a Photoshop 'solarising' filter. This only affects machines using the i810 driver ie i915/945/855 Intel chipsets.

[[Image:aOpen-front.jpg]] [[Image:aOpen-back.jpg]]

Apex Destiny-6100

2007-03-27T09:47:28Z

T0ny:

{{Plutoperm}}
== Installation ==

In order to setup the Apex system, you first need to connect it to a power supply, set the sensors and tie them to the inputs on the board from the panel, and also connect the wall panel to the main panel. You can find a very thorough description in the installation manual supplied by HoneyWell (can be downloaded in [http://www.security.honeywell.com/hsce/resources/literature/index.html the support section] of the security site).

The configuration can be done either using the wall panel, or a computer and then upload it with the special software HoneyWell supplies. What interests us more, though, is communicating with the panel directly through the serial RS232 protocol.

== Destiny 6100 RS232 protocol ==

In the same support section, you can also download the specification for communicating to the panel through RS232 (filename k1231.pdf at this time). There is also a simple application you can use to verify the command string syntax (explained in k1231.pdf), as well the fact that the panel is set up to receive commands through the serial port.

There is a special board that has to be mounted on the main board in the panel's case, in order to get a RS232 connector. You can plug an RJ45 cable there, witch goes to a serial converter (or any other way you can plug it into your computer, we used the to serial converter as well as a RadioShack USB Serial cable).

After setting this, use the software to make sure the panel is set up correctly. You first have to connect to the correct port, then start sending commands. If everything is ok, you should here the vocal confirmations from the panel. If you don't, check the yellow led on the board, the one that's the closest to the RS232 extension. This one should blink the instant you send a command. If this happens. most probably you don't have the proper jumper setting on the RS232 extension board. It should connect the pins that are closer to the box edge.

In the document you can also find a short C program that builds command strings (there is a checksum that has to be added to the command string) that can be sent directly through the serial port once you got it working.

== Figuring the protocol up ==

The communication protocol is pretty simple, but there is a section not so well documented, more exactly section 5.8. You can find the specifications for most memory locations in the Installation Instructions (page 36). Still, there's no info about fetching zone data in there (they say configuring the zones can only be done through the wall panel control - page 23 of the same document).

Using the memory location access commands, we took a snapshots of the memory (you can only query 32 - 0x20 - bytes at a time, so getting a snapshot over the serial port takes a bit of a time) and reverse-engineered the memory map.

Orbiter

2007-03-27T08:47:37Z

T0ny:

{{Plutoperm}}

Here's a simplified [[UML]] for Orbiter (pocketfrog implementation).

[[Integrating custom controls in Orbiter]]

[[Orbiter refactoring - the new design]]

Devel notes:

* [[SDL's TextWrapper and TextSplitter]]
* [[OpenGL implementation]]
* [[Building Orbiter for the Nokia 770]]
* [[Computing screen]]
* [[FileSave screen]]
* [[Child devices]]

User notes:

*[[Web Orbiter]]
*[[Add CISCO 7078 Orbiter]]
[[Category: Programmer's Guide]]

Image properties

2007-03-27T08:46:05Z

T0ny:

{{Plutoperm}}
'''Top''' : '''''Integer'''''

The top coordinate of the Image control.

'''Left''' : '''''Integer'''''

The left coordinate of the Image control.

'''Width''' : '''''Integer'''''

The width (in pixels) of Image control. If width is not specified, the width will be image's source size.

'''Height''' : '''''Integer'''''

The Height (in pixels) of Image control. If height is not specified, the height will be image's source size.

'''Picture''' : '''''String'''''

That describe path to a file that will be loaded to be displayed.

ASUS DIGIMatrix

2007-03-27T08:43:47Z

T0ny: Removed the that are not needed

__toc__

Asus Digimatrix has pros and cons. Let me do initial evaluation...

I've also added Panel utility that lets you control LCD display...

*Pros:
**Small factor
**Nice front panel
**Integrated IR Remote
**Clock and Temp display (although Time under LinuxMCE is not right at the moment)
*Cons:
**Cannot PXE boot (I simulate this with boot CD that is always in tray)
**Wake on LAN still doesn't work properly (but can be wrong on this one)...

[[Image:asus-fromt.jpg]] [[Image:asus_back.jpg]]

== HW clock problem ==

Digimatrix has nice little VFD screen that shows hardware clock. The problem is that when it is powered off that time is in GMT rather than local time (in my case this is two hours behind). This comes from default handling of time in Linux - HW clock keeps GMT time and software then handles it when powered on. But after power down it goes back to GMT.

'''''Solution'''''

Entry UTC=yes in /etc/default/rcS (for that particular MD and not on the core) has to be changed to UTC=no.

I have no idea if this breaks any automatic daylight time saving feature or anything else, but works on my Digimatrix now - so I can see proper time when powered off

== Adding remote control==

It seems pretty straightforward, but I it seems it starts to work only after few hard reboots...

Two additional kernel modules are required for remote to operate properly (lirc_dev, lirc_it87). They should be added as additional kernel modules on Media Directors page. As I'm writing this, this feature doesn't work, so you must manually add them to /etc/modules and watch, cause that file could get overwritten (particularly if you click on 'Rebuild image')...

1. Add 'Digimatrix' remote control in the bottom of corresponding entry in Media directors LinuxMCE-admin page. 

2. Select 'default' driver

Those actions will add two devices to Digimatrix MD parent device : 'Digimatrix' (remote) and 'default' which will start actual lircd daemon. Now some of buttons should work (left,right,up,down) but not all of them. There is another further step necessary :

3. Setting up remote mapping in MySQL database pluto_main, RemoteMapping (where keys from lircd.conf on Digmatrix remote page have to be added to trigger proper DCE messages, but please read [http://linuxmce.com/wiki/index.php/Control_LinuxMCE_using_an_Infrared_remote this] first - if you make changes on your own, you'll lose upgrading feature of table entries!!!)

I've already sent email with suggested additions for Digimatrix remote :
<pre>
--------------------- suggested additions to table are listed in ()-------
(os_start)Power;|0 -203 1 194
1;One;|0 -203 1 28 26 16
2;Two;|0 -203 1 28 26 17
3;Three;|0 -203 1 28 26 18
4;Four;|0 -203 1 28 26 19
5;Five;|0 -203 1 28 26 20
6;Six;|0 -203 1 28 26 21
7;Seven;|0 -203 1 28 26 22
8;Eight;|0 -203 1 28 26 23
9;Nine;|0 -203 1 28 26 24
0;Zero;|0 -203 1 28 26 25
enter;|0 -203 1 28 26 5
(next)SkipNext;skipfwd;|0 -106 1 65 5 +1
(pre)SkipPrior;skipback;|0 -106 1 65 5 -1
(ch+)chup;ChanUp;|0 -106 1 65 5 +1
(ch-)chdown;ChanDown;|0 -106 1 65 5 -1
(step+)fastforward;Forward;|0 -106 1 41 43 +2
(step-)Rewind;|0 -106 1 41 43 -2
Pause;|0 -106 1 39
Play;|0 -106 1 37
Mute;|0 -106 1 97
Stop;|0 -106 1 95 203 1
Down;|0 -203 1 201
Up;|0 -203 1 200
Left;|0 -203 1 202
Right;|0 -203 1 203
ok;|0 -203 1 190
(vol-)voldn;VolDown;|0 -106 1 90
(vol+)VolUp;|0 -106 1 89
recorded_tv;RecTV;|0 -203 1 401 29 5
(dvd_vcd;dvd_audio)DVD;|0 -106 1 43
menu;|0 -106 1 548
tv;live_tv;LiveTV;|0 -106 1 43 29 1
Back;|0 -203 1 240
Clear;|0 -203 1 363
(subtitle)epg;Guide;|0 -106 1 126
start;Home;|0 -203 1 741 159 1
Music;|0 -203 1 401 29 4
(ui_size)Radio;|0 -106 1 43 29 6
(rec)Record;|0 -106 1 102
(ui_on_off)display;info;list;|0 -203 1 399
green;|0 -203 1 28 26 177
yellow;|0 -203 1 28 26 178
red;|0 -203 1 28 26 179
blue;|0 -203 1 28 26 180

----- suggestions to change in digimatrix remote entry
on_off 0x000000000000B04F
</pre>
to change to 'music' - there is alternate sign on remote that is more useful than on_off feature (os_start is for that)

I also suggested new entry in table :
photo (music,tv,dvd are already in)...

(to be expanded)

== Power ON/OFF from remote control !!!==
 
Currently not many PCs can do this. But digitools package (look below) includes digiwake utility that must be run on system's shutdown (anytime after lircd, but it disables it so shutdown is best place) and Digimatrix will then wake up on Music (On/Off) button on remote - if it stays in idle power of course..
 
Currently for 1.03 Digiwake, you must run digiwake -w to write default values. On on/off remote button Digimatrix starts booting but it doesn't read CD to PXE boot (maybe my BIOS is not the right version...
 
Radu suggests putting script in /etc/init.d, and make symlinks in /etc/rc6.d and /etc/rc0.d (rc6 = reboot; rc0 = halt/poweroff); use the existing symlinks as reference - I think only rc0 symlink is necessary.

'digiwake.sh' content (in /etc/init.d ) 
#
# digiwake.sh Prepares Digmatrix to be powered on by remote on/off button.
#
/usr/local/sbin/digiwake -w

and make this :
ln -s /etc/init.d/digiwake.sh /etc/rc0.d/S80digiwake

== Getting VFD panel to display time, temperature (with volume) and volume knob to work ==

You need to compile [http://www.geexbox.org/src/devel/ Digitools ] 
My notes:
wget http://www.geexbox.org/src/devel/digitools-1.03.tar.gz
tar zxvf digitools-1.03.tar.gz
cd digitools
apt-get install libc6-dev
apt-get install libasound2-dev
make install

Then I add this line to /etc/inittab (not sure if this is proper and nice way of doing it - but it works) :

FP:2345:once:/usr/local/sbin/digipanel -l -s -t &> /dev/null & echo "Starting panel control"

(to be expanded)

MirrorsOld

2007-03-27T08:31:05Z

T0ny: Removed the two links at the bottom

The md5sum for the LinuxMCE 1.0 Install CD (linuxmce-1.0-packages.iso) is: 0c925976b65ba481271cbb133051fe3a

This wiki page is editable so users can add additional mirrors. To prevent the addition of malware to the .iso, the md5sum is also shown on the home page in the news section, which is not editable by the public.

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"
|- style="background: lightsteelblue"
|-
!Official Torrent:
|
* http://torrents.thepiratebay.org/3646881/linuxmce-1.0-packages.iso.3646881.TPB.torrent
|-
!U.S.:
|
* http://www.neversfw.com/linux/ (new installer .deb posted)
* http://www.robogoat.com/rampage/linuxmce/linuxmce-1.0-packages.iso
* http://mirror.chibiko.net/linuxmce-1.0-packages.iso - Dreamhost Mirror, 2TB/mo - Atreidae
* http://server2.cpl1337.net/linuxmce-1.0-packages.iso
* http://proyectos.pixelamigo.com/software/Ubuntu/linuxMCE/ By donation ( Linux MCE + Ubuntu Ultimate Edition 1.3 + Ubuntu Gamers Edition )
* http://coblitz.codeen.org:3125/linuxmce.com/linuxmce-1.0-packages.iso - ( [http://codeen.cs.princeton.edu/ CoDeen] & [http://www.planet-lab.org PlanetLab])
|-
!Australia:
|
* [http://linuxmce.rtfm.net.au/ Packages ISO and Installer - RTFM Computing Melbourne Australia]
|-
!Europe:
|
* http://www.netzwelt.de/software/4459-linuxmce.html
* http://mirror.hgkz.ch/ftp/iso/linuxmce/linuxmce-1.0-packages.iso
* ftp://mirror.hgkz.ch/iso/linuxmce/linuxmce-1.0-packages.iso
* rsync://mirror.hgkz.ch/linuxmce/
|-
!FileFront Mirror:
|
* http://hosted.filefront.com/linuxmce/1925781 To help take some load of paid websites...
|-
![http://www.pando.com/ Pando] (a P2P app):
|
* [http://cache.pando.com/soapservices/Package/package.pando?id=93C79E269A55BE14C7F68A859B0EF336B2CF4849&key=AAE42C36492B011477091337338945CB724B32ADC6F975597A261448318B620B&tt=S2W Pando Link]
|-
!MediaFire Direct Links:
|
* Files are direct downloads, use [http://www.freebyte.com/hjsplit/ HJ-Split] to combine.
* [http://www.mediafire.com/?014wq4mgmki Part 1]
* [http://www.mediafire.com/?9ozzyltiimt Part 2]
* [http://www.mediafire.com/?a5q5yfdyzqy Part 3]
* [http://www.mediafire.com/?1uwzzzzu0xm Part 4]
* [http://www.mediafire.com/?czzmq5jzygu Part 5]
* [http://www.mediafire.com/?64dw2mzz3km Part 6]
* [http://www.mediafire.com/?5ygynmnnqfr Part 7]
|}

MirrorsOld

2007-03-25T06:47:47Z

T0ny:

The md5sum for the LinuxMCE 1.0 Install CD (linuxmce-1.0-packages.iso) is: 0c925976b65ba481271cbb133051fe3a

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"
|- style="background: lightsteelblue"
|-
!Official Torrent:
|
* http://torrents.thepiratebay.org/3646881/linuxmce-1.0-packages.iso.3646881.TPB.torrent
|-
!U.S.:
|
* [http://www.cyburdinehosting.com/linuxmce/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - Cyburdine Hosting CA Data Center]
* http://www.neversfw.com/linux/ (new installer .deb posted)
* http://www.robogoat.com/rampage/linuxmce/linuxmce-1.0-packages.iso
|-
!Australia:
|
* [http://linuxmce.rtfm.net.au/ Packages ISO and Installer - RTFM Computing Melbourne Australia]
(Please note this is a very new site, it's DNS records may not have yet propagated.)
|-
!Switzerland:
|
* http://mirror.hgkz.ch/ftp/iso/linuxmce/linuxmce-1.0-packages.iso
* ftp://mirror.hgkz.ch/iso/linuxmce/linuxmce-1.0-packages.iso
* rsync://mirror.hgkz.ch/linuxmce/
|-
!FileFront Mirror:
|
* http://hosted.filefront.com/linuxmce/1925781 To help take some load of paid websites...
|-
![http://www.pando.com/ Pando] (a P2P app):
|
* [http://cache.pando.com/soapservices/Package/package.pando?id=93C79E269A55BE14C7F68A859B0EF336B2CF4849&key=AAE42C36492B011477091337338945CB724B32ADC6F975597A261448318B620B&tt=S2W Pando Link]
|}

MirrorsOld

2007-03-25T06:46:48Z

T0ny:

The md5sum for the LinuxMCE 1.0 Install CD (linuxmce-1.0-packages.iso) is: 0c925976b65ba481271cbb133051fe3a

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"
|- style="background: lightsteelblue"
|-
!Official Torrent:
|
* http://torrents.thepiratebay.org/3646881/linuxmce-1.0-packages.iso.3646881.TPB.torrent
|-
!U.S.:
|
* [http://www.cyburdinehosting.com/linuxmce/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - Cyburdine Hosting CA Data Center]
* http://www.neversfw.com/linux/ (new installer .deb posted)
* http://www.robogoat.com/rampage/linuxmce/linuxmce-1.0-packages.iso
|-
!Australia:
|
* [http://linuxmce.rtfm.net.au/ Packages ISO and Installer - RTFM Computing Melbourne Australia]
(Please note this is a very new site, it's DNS records may not have yet propagated.)
|-
!Switzerland:
|
* http://mirror.hgkz.ch/ftp/iso/linuxmce/linuxmce-1.0-packages.iso
* ftp://mirror.hgkz.ch/iso/linuxmce/linuxmce-1.0-packages.iso
* rsync://mirror.hgkz.ch/linuxmce/
|-
!FileFront Mirror:
|
* http://hosted.filefront.com/linuxmce/1925781 To help take some load of paid websites...
|-
!Pando (a P2P app):
|
* [http://cache.pando.com/soapservices/Package/package.pando?id=93C79E269A55BE14C7F68A859B0EF336B2CF4849&key=AAE42C36492B011477091337338945CB724B32ADC6F975597A261448318B620B&tt=S2W Pando Link]
|}

MirrorsOld

2007-03-25T04:53:34Z

T0ny:

The md5sum for the LinuxMCE 1.0 Install CD (linuxmce-1.0-packages.iso) is: 0c925976b65ba481271cbb133051fe3a

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"
|- style="background: lightsteelblue"
|-
!Official Torrent:
|
* http://torrents.thepiratebay.org/3646881/linuxmce-1.0-packages.iso.3646881.TPB.torrent
|-
!U.S.:
|
* [http://www.cyburdinehosting.com/linuxmce/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - Cyburdine Hosting CA Data Center]
* [http://63.228.213.140/linuxmce/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - Cyburdine Hosting UT Data Center]
* http://www.neversfw.com/linux/ (new installer .deb posted)
* http://www.robogoat.com/rampage/linuxmce/linuxmce-1.0-packages.iso
|-
!Australia:
|
* [http://linuxmce.rtfm.net.au/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - RTFM Computing Melbourne Australia]
|-
!Switzerland:
|
* http://mirror.hgkz.ch/ftp/iso/linuxmce/linuxmce-1.0-packages.iso
* ftp://mirror.hgkz.ch/iso/linuxmce/linuxmce-1.0-packages.iso
* rsync://mirror.hgkz.ch/linuxmce/
|-
!FileFront Mirror:
|
* http://hosted.filefront.com/linuxmce/1925781 To help take some load of paid websites...
|}

Integrating custom controls in Orbiter

2007-03-25T04:31:30Z

T0ny:

{{Plutoperm}}

== The concept of screen in Orbiter ==
A ''DesignObj'' is a graphic object from Orbiter. Each ''DesignObj'' may be a collection of ''DesignObj'' children and so on. A parent ''DesignObj'' can be associated with a ''screen'', which gives the programmer the possibility to do custom additional actions with that ''DesignObj''.

=== How to associate a ''DesignObj'' to a ''screen'' ===

Once the parent ''design object'' is created with the Designer, go in ''pluto_main'' database and insert into ''Screen'' table a record with a description and few comments about the new screen. Then check Screen_DesignObj table and add a recording to link the screen with the designobj. You might also want to specify the UI and the Skin.

=== How to use ScreenGen to regenerate screens and how to use it ===

Run ScreenGen with ''-h <host>'' command line parameter and you should see in src/Gen_Devices/AllScreens.h that handlers for your need screens were added.

Let's say your screen has PK_Screen = 39, with the description "Computing":
[[Image:A_record_from_screen_table.PNG]]

In Screen_DesignObj, you should have something like this:
[[Image:records_from_screen_designobj.PNG]]

=== Understand AllScreens.h and ScreenHandlerBase class. ===

There is another table in the database, ''Screen_CommandParameter'' which allows you to associate a screen with a collection of command parameters. This means you can send a "go to screen" command and attach to it this collection of parameters.

AllScreens.h header file contains inline definitions for wrapper command classes (SCREEN_* classes) which allow you to send a "go to screen" command with additional parameters, without creating the message "by hand". An example:
[[Image:Screen_wrapper_class.PNG]]

From other application, the class can be used like this:

''SCREEN_SingleCameraViewOnly screenSingleCameraViewOnly(DeviceIDFrom, DeviceIDTo, iPK_Device);''

''SendCommand(screenSingleCameraViewOnly);''

ScreenHandler class is derived from ScreenHandlerBase class. The ScreenHandlerBase has a basing implementation for each ''screen'', like this:

''virtual void SCREEN_QuadViewCameras(long PK_Screen, string sList_PK_Device){ GotoScreen(PK_Screen); }''

ScreenHandlerBase already demultiplexes each "go to screen" command and calls the right SCREEN_* method and also deserializes the command parameters. In order to add extrafunctionality for that screen, you will need to derive that virtual method in ScreenHandler class (for screens available for all orbiter) or OSDScreenHandler class (which has the handlers only for linux OSD Orbiter).

== ScreenHandler and how to register a callback ==

Once you have derivated a SCREEN method in a ScreenHandlerBase's derived class, you may register few callbacks.
So far, this is the list with callback types you can register:

<pre>
enum CallBackType
{
cbUnused,
cbDataGridSelected,
cbObjectSelected,
cbOnDialogCreate, // create a unique dialog
cbOnDialogDelete, // close dialog without saving data
cbOnDialogRefresh, // refresh dialog with new data
cbOnDialogSave, // save data from dialog
cbOnDialogWaitUser, // wait for an user action
cbOnKeyDown,
cbOnKeyUp,
cbOnMouseDown,
cbOnMouseUp,
cbCapturedKeyboardBufferChanged,
cbOnTimer,
cbMessageIntercepted,
cbOnRenderScreen,
cbOnGotoScreen
};
</pre>

For each type of callback, your registered callback can be notified when an event is fired with extra data. That extra data is actually a derived class from CallBackData class.

Let's say we want to register a callback for "orbiter selected" event in SCREEN_CountryWizard method. We'll do something like this:

[[Image:Screenhandler_method.PNG]]

where :

[[Image:Callback_function_sample.PNG]]

First time an event is fired, the registered callbacks of that type are executed first and then Orbiter's code for that event. Returning true in your callback will cancel Orbiter's code executing. Returning false will make Orbiter continue to process the event executing its internal code.

== How to send tasks to task manager. ==

Task manager is a proxy between Orbiter and wx widgets. Since Orbiter is running in a different thread then wx widgets's dialogs, we needed a asynchronous method of communicating with WX.
TaskManager is a thread-safe singleton, which means that only one instance of TaskManager will be available, it can be access from anywhere and it can manager multithreaded requests safetly.

Orbiter sends "tasks" to WX via TaskManager. A task has associated info about the dialog type, callback type, callback data and a task id (which is generated and managed by TaskManager). To do this, there are two methods in TaskManager :

void AddTask(Task *Event);
void AddTaskAndWait(Task *Event);

AddTask allows you to send info to WX asynchronously. AddTaskAndWait allows you to send info to WX synchronously. Once the task is added in the queue, a conditional wait is made in the queue and when a task is processed, it wakes up and verifies if the task with the id added was processed or not. If yes, the method returns.

To create a task, you'll have to use TaskManager's CreateTask method.

Let's take an example:

To create a "speed control" wxdialog, we'll do a :

SpeedControlCallBackData *pSpeedControlData = new SpeedControlCallBackData(plutoRect);

Task *pTask = TaskManager::Instance().CreateTask(cbOnDialogCreate, E_Dialog_SpeedControl, pSpeedControlData);

TaskManager::Instance().AddTaskAndWait(pTask);

To delete the dialog, we'll use cbOnDialogDelete callback type and to refresh, cbOnDialogRefresh.
If we want to now there to create and delete the dialog, we may want to create a screen for the parent object of wx control and register callbacks in overriden SCREEN_* method from the screen handler class like this:

RegisterCallBack( cbOnDialogCreate, (ScreenHandlerCallBack)&OSDScreenHandler::SpeedControlCreate, new PositionCallBackData() );

RegisterCallBack( cbOnDialogDelete, (ScreenHandlerCallBack)&OSDScreenHandler::SpeedControlDelete, new PositionCallBackData() );

The new UI will allows you to manage wx widget's dialog as popups, via PopupManager class. ***comming soon***

Integrating custom controls in Orbiter

2007-03-25T04:31:17Z

T0ny:

WebDT 366

2007-03-25T04:31:01Z

T0ny:

{{Plutoperm}}
[[Image:WebDT366.jpg]]

[http://dtresearch.com/prod_webDT366.html Official site]

- Windows® Embedded and Windows XP with Windows Media Player and Internet Explorer; ICA & RDP Terminal clients; Terminal Emulation software 
- Compatible with Windows CE or Windows XP applications 
- Brilliant 8.4" TFT Active Matrix LCD at 800 x 600 SVGA resolution 
- Integrated touch screen display with "on screen" soft keyboard support 
- CompactFlash™ slot; PC Card slot; USB port 
- Built-in HDD, 802.11 b/g WLAN adapter and Bluetooth available 
- Full 16-bit audio with stereo; headset jack; built-in stereo speakers and microphone 

----

Price: $1800

Template:Plutoperm

2007-03-25T04:30:42Z

T0ny:

<noinclude>'''Example:'''</noinclude>
{| style="background: #FFCFCF; border: 1px dotted black;"
|-
|This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
|}

Template:Plutoperm

2007-03-25T04:30:30Z

T0ny:

<noinclude>'''Example:'''</noinclude>{| style="background: #FFCFCF; border: 1px dotted black;"
|-
|This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
|}

WebDT 366

2007-03-25T04:28:02Z

T0ny:

{| style="background: #FFCFCF;"
|This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
|}

[[Image:WebDT366.jpg]]

[http://dtresearch.com/prod_webDT366.html Official site]

- Windows® Embedded and Windows XP with Windows Media Player and Internet Explorer; ICA & RDP Terminal clients; Terminal Emulation software 
- Compatible with Windows CE or Windows XP applications 
- Brilliant 8.4" TFT Active Matrix LCD at 800 x 600 SVGA resolution 
- Integrated touch screen display with "on screen" soft keyboard support 
- CompactFlash™ slot; PC Card slot; USB port 
- Built-in HDD, 802.11 b/g WLAN adapter and Bluetooth available 
- Full 16-bit audio with stereo; headset jack; built-in stereo speakers and microphone 

----

Price: $1800

Integrating custom controls in Orbiter

2007-03-25T04:25:51Z

T0ny: /* ScreenHandler and how to register a callback */

{| style="background: #FFCFCF; border: 1px dotted black;"
|-
|This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
|}

== The concept of screen in Orbiter ==
A ''DesignObj'' is a graphic object from Orbiter. Each ''DesignObj'' may be a collection of ''DesignObj'' children and so on. A parent ''DesignObj'' can be associated with a ''screen'', which gives the programmer the possibility to do custom additional actions with that ''DesignObj''.

=== How to associate a ''DesignObj'' to a ''screen'' ===

Once the parent ''design object'' is created with the Designer, go in ''pluto_main'' database and insert into ''Screen'' table a record with a description and few comments about the new screen. Then check Screen_DesignObj table and add a recording to link the screen with the designobj. You might also want to specify the UI and the Skin.

=== How to use ScreenGen to regenerate screens and how to use it ===

Run ScreenGen with ''-h <host>'' command line parameter and you should see in src/Gen_Devices/AllScreens.h that handlers for your need screens were added.

Let's say your screen has PK_Screen = 39, with the description "Computing":
[[Image:A_record_from_screen_table.PNG]]

In Screen_DesignObj, you should have something like this:
[[Image:records_from_screen_designobj.PNG]]

=== Understand AllScreens.h and ScreenHandlerBase class. ===

There is another table in the database, ''Screen_CommandParameter'' which allows you to associate a screen with a collection of command parameters. This means you can send a "go to screen" command and attach to it this collection of parameters.

AllScreens.h header file contains inline definitions for wrapper command classes (SCREEN_* classes) which allow you to send a "go to screen" command with additional parameters, without creating the message "by hand". An example:
[[Image:Screen_wrapper_class.PNG]]

From other application, the class can be used like this:

''SCREEN_SingleCameraViewOnly screenSingleCameraViewOnly(DeviceIDFrom, DeviceIDTo, iPK_Device);''

''SendCommand(screenSingleCameraViewOnly);''

ScreenHandler class is derived from ScreenHandlerBase class. The ScreenHandlerBase has a basing implementation for each ''screen'', like this:

''virtual void SCREEN_QuadViewCameras(long PK_Screen, string sList_PK_Device){ GotoScreen(PK_Screen); }''

ScreenHandlerBase already demultiplexes each "go to screen" command and calls the right SCREEN_* method and also deserializes the command parameters. In order to add extrafunctionality for that screen, you will need to derive that virtual method in ScreenHandler class (for screens available for all orbiter) or OSDScreenHandler class (which has the handlers only for linux OSD Orbiter).

== ScreenHandler and how to register a callback ==

Once you have derivated a SCREEN method in a ScreenHandlerBase's derived class, you may register few callbacks.
So far, this is the list with callback types you can register:

<pre>
enum CallBackType
{
cbUnused,
cbDataGridSelected,
cbObjectSelected,
cbOnDialogCreate, // create a unique dialog
cbOnDialogDelete, // close dialog without saving data
cbOnDialogRefresh, // refresh dialog with new data
cbOnDialogSave, // save data from dialog
cbOnDialogWaitUser, // wait for an user action
cbOnKeyDown,
cbOnKeyUp,
cbOnMouseDown,
cbOnMouseUp,
cbCapturedKeyboardBufferChanged,
cbOnTimer,
cbMessageIntercepted,
cbOnRenderScreen,
cbOnGotoScreen
};
</pre>

For each type of callback, your registered callback can be notified when an event is fired with extra data. That extra data is actually a derived class from CallBackData class.

Let's say we want to register a callback for "orbiter selected" event in SCREEN_CountryWizard method. We'll do something like this:

[[Image:Screenhandler_method.PNG]]

where :

[[Image:Callback_function_sample.PNG]]

First time an event is fired, the registered callbacks of that type are executed first and then Orbiter's code for that event. Returning true in your callback will cancel Orbiter's code executing. Returning false will make Orbiter continue to process the event executing its internal code.

== How to send tasks to task manager. ==

Task manager is a proxy between Orbiter and wx widgets. Since Orbiter is running in a different thread then wx widgets's dialogs, we needed a asynchronous method of communicating with WX.
TaskManager is a thread-safe singleton, which means that only one instance of TaskManager will be available, it can be access from anywhere and it can manager multithreaded requests safetly.

Orbiter sends "tasks" to WX via TaskManager. A task has associated info about the dialog type, callback type, callback data and a task id (which is generated and managed by TaskManager). To do this, there are two methods in TaskManager :

void AddTask(Task *Event);
void AddTaskAndWait(Task *Event);

AddTask allows you to send info to WX asynchronously. AddTaskAndWait allows you to send info to WX synchronously. Once the task is added in the queue, a conditional wait is made in the queue and when a task is processed, it wakes up and verifies if the task with the id added was processed or not. If yes, the method returns.

To create a task, you'll have to use TaskManager's CreateTask method.

Let's take an example:

To create a "speed control" wxdialog, we'll do a :

SpeedControlCallBackData *pSpeedControlData = new SpeedControlCallBackData(plutoRect);

Task *pTask = TaskManager::Instance().CreateTask(cbOnDialogCreate, E_Dialog_SpeedControl, pSpeedControlData);

TaskManager::Instance().AddTaskAndWait(pTask);

To delete the dialog, we'll use cbOnDialogDelete callback type and to refresh, cbOnDialogRefresh.
If we want to now there to create and delete the dialog, we may want to create a screen for the parent object of wx control and register callbacks in overriden SCREEN_* method from the screen handler class like this:

RegisterCallBack( cbOnDialogCreate, (ScreenHandlerCallBack)&OSDScreenHandler::SpeedControlCreate, new PositionCallBackData() );

RegisterCallBack( cbOnDialogDelete, (ScreenHandlerCallBack)&OSDScreenHandler::SpeedControlDelete, new PositionCallBackData() );

The new UI will allows you to manage wx widget's dialog as popups, via PopupManager class. ***comming soon***

Integrating custom controls in Orbiter

2007-03-25T04:25:23Z

T0ny: Converted table to wiki from html

{| style="background: #FFCFCF; border: 1px dotted black;"
|-
|This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
|}

== The concept of screen in Orbiter ==
A ''DesignObj'' is a graphic object from Orbiter. Each ''DesignObj'' may be a collection of ''DesignObj'' children and so on. A parent ''DesignObj'' can be associated with a ''screen'', which gives the programmer the possibility to do custom additional actions with that ''DesignObj''.

=== How to associate a ''DesignObj'' to a ''screen'' ===

Once the parent ''design object'' is created with the Designer, go in ''pluto_main'' database and insert into ''Screen'' table a record with a description and few comments about the new screen. Then check Screen_DesignObj table and add a recording to link the screen with the designobj. You might also want to specify the UI and the Skin.

=== How to use ScreenGen to regenerate screens and how to use it ===

Run ScreenGen with ''-h <host>'' command line parameter and you should see in src/Gen_Devices/AllScreens.h that handlers for your need screens were added.

Let's say your screen has PK_Screen = 39, with the description "Computing":
[[Image:A_record_from_screen_table.PNG]]

In Screen_DesignObj, you should have something like this:
[[Image:records_from_screen_designobj.PNG]]

=== Understand AllScreens.h and ScreenHandlerBase class. ===

There is another table in the database, ''Screen_CommandParameter'' which allows you to associate a screen with a collection of command parameters. This means you can send a "go to screen" command and attach to it this collection of parameters.

AllScreens.h header file contains inline definitions for wrapper command classes (SCREEN_* classes) which allow you to send a "go to screen" command with additional parameters, without creating the message "by hand". An example:
[[Image:Screen_wrapper_class.PNG]]

From other application, the class can be used like this:

''SCREEN_SingleCameraViewOnly screenSingleCameraViewOnly(DeviceIDFrom, DeviceIDTo, iPK_Device);''

''SendCommand(screenSingleCameraViewOnly);''

ScreenHandler class is derived from ScreenHandlerBase class. The ScreenHandlerBase has a basing implementation for each ''screen'', like this:

''virtual void SCREEN_QuadViewCameras(long PK_Screen, string sList_PK_Device){ GotoScreen(PK_Screen); }''

ScreenHandlerBase already demultiplexes each "go to screen" command and calls the right SCREEN_* method and also deserializes the command parameters. In order to add extrafunctionality for that screen, you will need to derive that virtual method in ScreenHandler class (for screens available for all orbiter) or OSDScreenHandler class (which has the handlers only for linux OSD Orbiter).

== ScreenHandler and how to register a callback ==

Once you have derivated a SCREEN method in a ScreenHandlerBase's derived class, you may register few callbacks.
So far, this is the list with callback types you can register:

enum CallBackType
{
cbUnused,
cbDataGridSelected,
cbObjectSelected,
cbOnDialogCreate, // create a unique dialog
cbOnDialogDelete, // close dialog without saving data
cbOnDialogRefresh, // refresh dialog with new data
cbOnDialogSave, // save data from dialog
cbOnDialogWaitUser, // wait for an user action
cbOnKeyDown,
cbOnKeyUp,
cbOnMouseDown,
cbOnMouseUp,
cbCapturedKeyboardBufferChanged,
cbOnTimer,
cbMessageIntercepted,
cbOnRenderScreen,
cbOnGotoScreen
};

For each type of callback, your registered callback can be notified when an event is fired with extra data. That extra data is actually a derived class from CallBackData class.

Let's say we want to register a callback for "orbiter selected" event in SCREEN_CountryWizard method. We'll do something like this:

[[Image:Screenhandler_method.PNG]]

where :

[[Image:Callback_function_sample.PNG]]

First time an event is fired, the registered callbacks of that type are executed first and then Orbiter's code for that event. Returning true in your callback will cancel Orbiter's code executing. Returning false will make Orbiter continue to process the event executing its internal code.

== How to send tasks to task manager. ==

Task manager is a proxy between Orbiter and wx widgets. Since Orbiter is running in a different thread then wx widgets's dialogs, we needed a asynchronous method of communicating with WX.
TaskManager is a thread-safe singleton, which means that only one instance of TaskManager will be available, it can be access from anywhere and it can manager multithreaded requests safetly.

Orbiter sends "tasks" to WX via TaskManager. A task has associated info about the dialog type, callback type, callback data and a task id (which is generated and managed by TaskManager). To do this, there are two methods in TaskManager :

void AddTask(Task *Event);
void AddTaskAndWait(Task *Event);

AddTask allows you to send info to WX asynchronously. AddTaskAndWait allows you to send info to WX synchronously. Once the task is added in the queue, a conditional wait is made in the queue and when a task is processed, it wakes up and verifies if the task with the id added was processed or not. If yes, the method returns.

To create a task, you'll have to use TaskManager's CreateTask method.

Let's take an example:

To create a "speed control" wxdialog, we'll do a :

SpeedControlCallBackData *pSpeedControlData = new SpeedControlCallBackData(plutoRect);

Task *pTask = TaskManager::Instance().CreateTask(cbOnDialogCreate, E_Dialog_SpeedControl, pSpeedControlData);

TaskManager::Instance().AddTaskAndWait(pTask);

To delete the dialog, we'll use cbOnDialogDelete callback type and to refresh, cbOnDialogRefresh.
If we want to now there to create and delete the dialog, we may want to create a screen for the parent object of wx control and register callbacks in overriden SCREEN_* method from the screen handler class like this:

RegisterCallBack( cbOnDialogCreate, (ScreenHandlerCallBack)&OSDScreenHandler::SpeedControlCreate, new PositionCallBackData() );

RegisterCallBack( cbOnDialogDelete, (ScreenHandlerCallBack)&OSDScreenHandler::SpeedControlDelete, new PositionCallBackData() );

The new UI will allows you to manage wx widget's dialog as popups, via PopupManager class. ***comming soon***

MirrorsOld

2007-03-25T04:19:47Z

T0ny: I added a table, I hope you like.

The md5sum for the LinuxMCE 1.0 Install CD (linuxmce-1.0-packages.iso) is: 0c925976b65ba481271cbb133051fe3a

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"
|- style="background: lightsteelblue"
|-
!Official Torrent:
|
* http://torrents.thepiratebay.org/3646881/linuxmce-1.0-packages.iso.3646881.TPB.torrent
|-
!U.S.:
|
* [http://www.cyburdinehosting.com/linuxmce/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - Cyburdine Hosting CA Data Center]
* [http://63.228.213.140/linuxmce/linuxmce-1.0-packages.iso linuxmce-1.0-packages.iso - Cyburdine Hosting UT Data Center]
* http://www.neversfw.com/linux/ (new installer .deb posted)
* http://www.robogoat.com/rampage/linuxmce/linuxmce-1.0-packages.iso
|-
!Australia:
|
* http://linuxmce.rtfm.net.au/linuxmce-1.0-packages.iso [Melbourne Australia]
|-
!Switzerland:
|
* http://mirror.hgkz.ch/ftp/iso/linuxmce/linuxmce-1.0-packages.iso
* ftp://mirror.hgkz.ch/iso/linuxmce/linuxmce-1.0-packages.iso
* rsync://mirror.hgkz.ch/linuxmce/
|-
!FileFront Mirror:
|
* http://hosted.filefront.com/linuxmce/1925781 To help take some load of paid websites...
|}