http://wiki.linuxmce.org/api.php?action=feedcontributions&user=Chriss&feedformat=atomLinuxMCE - User contributions [en]2024-03-28T18:48:45ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=User:Chriss&diff=20147User:Chriss2009-08-03T09:01:23Z<p>Chriss: /* LMCE 0810 virtualized on Ubuntu 9.04 and KVM */</p>
<hr />
<div>= Setup =<br />
== Core ==<br />
== MDs ==<br />
<br />
= Notes to myself =<br />
Don't care about the following stuff and beware to use anything if you don't know exactley what you are doing...<br />
<br />
== proper image support for UpdateMedia ==<br />
http://svn.linuxmce.org/trac.cgi/ticket/217<br />
<br />
=== Updates to pluto_media.MediaType_AttributeType ===<br />
<br />
* Added by pos on 2009-07-31:<br />
INSERT INTO `MediaType_AttributeType` (`EK_MediaType`, `FK_AttributeType`, `Identifier`, `CombineAsOne`, `MediaSortOption`) VALUES<br />
(7, 16, 0, 0, NULL),<br />
(7, 29, 0, 0, NULL),<br />
(7, 37, 0, 0, NULL),<br />
(7, 47, 0, 0, NULL),<br />
(7, 48, 0, 0, NULL);<br />
<br />
=== move pluto_media.MediaType_AttributeType ===<br />
ALTER TABLE `pluto_media`.MediaType_AttributeType RENAME `pluto_main`.`MediaType_AttributeType`;<br />
ALTER TABLE `pluto_main`.`MediaType_AttributeType` CHANGE `EK_MediaType` `FK_MediaType` INT( 11 ) NOT NULL DEFAULT '0';<br />
ALTER TABLE `pluto_main`.`MediaType_AttributeType` CHANGE `FK_AttributeType` `EK_AttributeType` INT( 11 ) NOT NULL DEFAULT '0';<br />
ALTER TABLE `pluto_main`.`MediaType_AttributeType` DROP INDEX `FK_AttributeType` , ADD INDEX `EK_AttributeType` ( `EK_AttributeType` );<br />
CREATE VIEW `pluto_media`.`MediaType_AttributeType` AS SELECT `FK_MediaType` AS 'EK_MediaType', `EK_AttributeType` AS 'FK_AttributeType', `Identifier`, `CombineAsOne`, `MediaSortOption` FROM `pluto_main`.`MediaType_AttributeType`;<br />
<br />
== LMCE 0810 virtualized on Ubuntu 9.04 and KVM ==<br />
<br />
* inspired by http://forum.linuxmce.org/index.php?topic=8233.0<br />
* installed Ubuntu 9.04 alternate amd64, basic text system<br />
* downloaded kernel 2.6.30.4 from kernel.org, build according to https://wiki.ubuntu.com/KernelTeam/GitKernelBuild<br />
* install kvm and stuff: https://help.ubuntu.com/community/KVM/Installation<br />
* install kubuntu 8.10<br />
** download kubuntu 8.10 i386 desktop .iso<br />
** create an image file (<tt>qemu-img create -f qcow lmce0810.img 25G</tt>) or use an empty and unmounted partition (that's what I'm doing in the following)<br />
** create a file (lmce0810.xml) with the definition of your KVM domain:<br />
<pre><br />
<domain type='kvm'><br />
<name>lmce0810</name><br />
<memory>2097152</memory><br />
<currentMemory>2097152</currentMemory><br />
<vcpu>1</vcpu><br />
<os><br />
<type arch='x86_64' machine='pc'>hvm</type><br />
<boot dev='cdrom'/><br />
</os><br />
<features><br />
<acpi/><br />
</features><br />
<clock offset='utc'/><br />
<on_poweroff>destroy</on_poweroff><br />
<on_reboot>restart</on_reboot><br />
<on_crash>destroy</on_crash><br />
<devices><br />
<emulator>/usr/bin/kvm</emulator><br />
<disk type='block' device='disk'><br />
<source dev='/dev/sda5'/><br />
<target dev='hda' bus='ide'/><br />
</disk><br />
<disk type='file' device='cdrom'><br />
<source file='/home/chris/kubuntu-8.10-desktop-i386.iso' /><br />
<target dev='hdc' bus='ide' /><br />
<readonly /><br />
</disk><br />
<interface type='bridge'><br />
<source bridge='brlmceext' /><br />
</interface><br />
<input type='mouse' bus='ps2'/><br />
<graphics type='vnc' port='5500' listen='192.168.177.24'/><br />
</devices><br />
</domain><br />
</pre><br />
** on the shell: <tt>virsh --connect qemu:///system</tt><br />
** in virsh: <tt>define lmce0810.xml</tt>, <tt>start lmce0810</tt><br />
** connect via VNC and do the installation<br />
* modify the definition of the KVM domain to not use the kubuntu installation CD and to have two ethernet connections:<br />
<pre><br />
<domain type='kvm'><br />
<name>lmce0810</name><br />
<memory>2097152</memory><br />
<currentMemory>2097152</currentMemory><br />
<vcpu>1</vcpu><br />
<os><br />
<type arch='x86_64' machine='pc'>hvm</type><br />
<boot dev='hd'/><br />
</os><br />
<features><br />
<acpi/><br />
</features><br />
<clock offset='utc'/><br />
<on_poweroff>destroy</on_poweroff><br />
<on_reboot>restart</on_reboot><br />
<on_crash>destroy</on_crash><br />
<devices><br />
<emulator>/usr/bin/kvm</emulator><br />
<disk type='block' device='disk'><br />
<source dev='/dev/sda5'/><br />
<target dev='hda' bus='ide'/><br />
</disk><br />
<interface type='bridge'><br />
<source bridge='brlmceext' /><br />
</interface><br />
<interface type='bridge'><br />
<source bridge='brlmceint' /><br />
</interface><br />
<input type='mouse' bus='ps2'/><br />
<graphics type='vnc' port='5500' listen='192.168.177.24'/><br />
</devices><br />
</domain></pre><br />
* in virsh: <tt>undefine lmce0810</tt>, <tt>define lmce0810.xml</tt>, <tt>start lmce0810</tt><br />
* connect again via VNC and follow the LMCE0810-Alpha2 installation steps<br />
<br />
===Conclusion===<br />
After all this seemed to work. After finishing the LMCE installation, both AVWizard and the configuration wizard started and I was able to configure the system. One thing I noted was that not all videos from the wizard were played but this might also be a problem with my VNC setup. However, finally the system setup was done and the system came up showing orbiter (UI1).<br />
<br />
Next steps will be to<br />
* map physical devices into the domain (tuner cards, usb devices, serial ports)<br />
* setup FreeNAS and connect it to LMCE's internal network in another KVM domain<br />
* try to attach MDs and stuff to the internal network and see if that works<br />
<br />
I will keep documenting my efforts here.<br />
<br />
== Links to keep in mind ==<br />
[[Creating_a_Media_Plug-in]]<br />
<br />
http://forum.linuxmce.org/index.php?topic=3433.60<br />
<br />
== ideas ==<br />
* improve media tagging in webadmin<br />
* picture media player<br />
* media transcoding plugin</div>Chrisshttp://wiki.linuxmce.org/index.php?title=User:Chriss&diff=20146User:Chriss2009-08-02T16:15:25Z<p>Chriss: /* move pluto_media.MediaType_AttributeType */</p>
<hr />
<div>= Setup =<br />
== Core ==<br />
== MDs ==<br />
<br />
= Notes to myself =<br />
Don't care about the following stuff and beware to use anything if you don't know exactley what you are doing...<br />
<br />
== proper image support for UpdateMedia ==<br />
http://svn.linuxmce.org/trac.cgi/ticket/217<br />
<br />
=== Updates to pluto_media.MediaType_AttributeType ===<br />
<br />
* Added by pos on 2009-07-31:<br />
INSERT INTO `MediaType_AttributeType` (`EK_MediaType`, `FK_AttributeType`, `Identifier`, `CombineAsOne`, `MediaSortOption`) VALUES<br />
(7, 16, 0, 0, NULL),<br />
(7, 29, 0, 0, NULL),<br />
(7, 37, 0, 0, NULL),<br />
(7, 47, 0, 0, NULL),<br />
(7, 48, 0, 0, NULL);<br />
<br />
=== move pluto_media.MediaType_AttributeType ===<br />
ALTER TABLE `pluto_media`.MediaType_AttributeType RENAME `pluto_main`.`MediaType_AttributeType`;<br />
ALTER TABLE `pluto_main`.`MediaType_AttributeType` CHANGE `EK_MediaType` `FK_MediaType` INT( 11 ) NOT NULL DEFAULT '0';<br />
ALTER TABLE `pluto_main`.`MediaType_AttributeType` CHANGE `FK_AttributeType` `EK_AttributeType` INT( 11 ) NOT NULL DEFAULT '0';<br />
ALTER TABLE `pluto_main`.`MediaType_AttributeType` DROP INDEX `FK_AttributeType` , ADD INDEX `EK_AttributeType` ( `EK_AttributeType` );<br />
CREATE VIEW `pluto_media`.`MediaType_AttributeType` AS SELECT `FK_MediaType` AS 'EK_MediaType', `EK_AttributeType` AS 'FK_AttributeType', `Identifier`, `CombineAsOne`, `MediaSortOption` FROM `pluto_main`.`MediaType_AttributeType`;<br />
<br />
== LMCE 0810 virtualized on Ubuntu 9.04 and KVM ==<br />
<br />
'''work in progress'''<br />
<br />
* inspired by http://forum.linuxmce.org/index.php?topic=8233.0<br />
* installed Ubuntu 9.04 alternate amd64, basic text system<br />
* downloaded kernel 2.6.30.4 from kernel.org, build according to https://wiki.ubuntu.com/KernelTeam/GitKernelBuild<br />
* install kvm and stuff: https://help.ubuntu.com/community/KVM/Installation<br />
* install kubuntu 8.10<br />
** download kubuntu 8.10 i386 desktop .iso<br />
** create an image file (<tt>qemu-img create -f qcow lmce0810.img 25G</tt>) or use an empty and unmounted partition (that's what I'm doing in the following)<br />
** create a file (lmce0810.xml) with the description for your domain:<br />
<pre></pre><br />
** on the shell: <tt>virsh --connect qemu:///system</tt><br />
** in virsh: <tt>define lmce0810.xml</tt>, <tt>start lmce0810</tt><br />
** connect via VNC and do the installation<br />
<br />
== Links to keep in mind ==<br />
[[Creating_a_Media_Plug-in]]<br />
<br />
http://forum.linuxmce.org/index.php?topic=3433.60<br />
<br />
== ideas ==<br />
* improve media tagging in webadmin<br />
* picture media player<br />
* media transcoding plugin</div>Chrisshttp://wiki.linuxmce.org/index.php?title=User:Chriss&diff=20145User:Chriss2009-08-02T08:03:42Z<p>Chriss: progress with virtualisation</p>
<hr />
<div>= Setup =<br />
== Core ==<br />
== MDs ==<br />
<br />
= Notes to myself =<br />
Don't care about the following stuff and beware to use anything if you don't know exactley what you are doing...<br />
<br />
== proper image support for UpdateMedia ==<br />
http://svn.linuxmce.org/trac.cgi/ticket/217<br />
<br />
=== Updates to pluto_media.MediaType_AttributeType ===<br />
<br />
* Added by pos on 2009-07-31:<br />
INSERT INTO `MediaType_AttributeType` (`EK_MediaType`, `FK_AttributeType`, `Identifier`, `CombineAsOne`, `MediaSortOption`) VALUES<br />
(7, 16, 0, 0, NULL),<br />
(7, 29, 0, 0, NULL),<br />
(7, 37, 0, 0, NULL),<br />
(7, 47, 0, 0, NULL),<br />
(7, 48, 0, 0, NULL);<br />
<br />
=== move pluto_media.MediaType_AttributeType ===<br />
<br />
== LMCE 0810 virtualized on Ubuntu 9.04 and KVM ==<br />
<br />
'''work in progress'''<br />
<br />
* inspired by http://forum.linuxmce.org/index.php?topic=8233.0<br />
* installed Ubuntu 9.04 alternate amd64, basic text system<br />
* downloaded kernel 2.6.30.4 from kernel.org, build according to https://wiki.ubuntu.com/KernelTeam/GitKernelBuild<br />
* install kvm and stuff: https://help.ubuntu.com/community/KVM/Installation<br />
* install kubuntu 8.10<br />
** download kubuntu 8.10 i386 desktop .iso<br />
** create an image file (<tt>qemu-img create -f qcow lmce0810.img 25G</tt>) or use an empty and unmounted partition (that's what I'm doing in the following)<br />
** create a file (lmce0810.xml) with the description for your domain:<br />
<pre></pre><br />
** on the shell: <tt>virsh --connect qemu:///system</tt><br />
** in virsh: <tt>define lmce0810.xml</tt>, <tt>start lmce0810</tt><br />
** connect via VNC and do the installation<br />
<br />
== Links to keep in mind ==<br />
[[Creating_a_Media_Plug-in]]<br />
<br />
http://forum.linuxmce.org/index.php?topic=3433.60<br />
<br />
== ideas ==<br />
* improve media tagging in webadmin<br />
* picture media player<br />
* media transcoding plugin</div>Chrisshttp://wiki.linuxmce.org/index.php?title=User:Chriss&diff=20137User:Chriss2009-07-31T17:00:49Z<p>Chriss: Time to keep some notes about what I'm doing</p>
<hr />
<div>= Setup =<br />
== Core ==<br />
== MDs ==<br />
<br />
= Notes to myself =<br />
Don't care about the following stuff and beware to use anything if you don't know exactley what you are doing...<br />
<br />
== proper image support for UpdateMedia ==<br />
http://svn.linuxmce.org/trac.cgi/ticket/217<br />
<br />
=== Updates to pluto_media.MediaType_AttributeType ===<br />
<br />
* Added by pos on 2009-07-31:<br />
INSERT INTO `MediaType_AttributeType` (`EK_MediaType`, `FK_AttributeType`, `Identifier`, `CombineAsOne`, `MediaSortOption`) VALUES<br />
(7, 16, 0, 0, NULL),<br />
(7, 29, 0, 0, NULL),<br />
(7, 37, 0, 0, NULL),<br />
(7, 47, 0, 0, NULL),<br />
(7, 48, 0, 0, NULL);<br />
<br />
=== move pluto_media.MediaType_AttributeType ===<br />
<br />
== LMCE 0810 virtualized on Ubuntu 9.04 and KVM ==<br />
<br />
* inspired by http://forum.linuxmce.org/index.php?topic=8233.0<br />
* installed Ubuntu 9.04 alternate amd64, basic text system<br />
* downloaded kernel 2.6.30.4 from kernel.org, build according to ...<br />
<br />
== Links to keep in mind ==<br />
[[Creating_a_Media_Plug-in]]<br />
<br />
http://forum.linuxmce.org/index.php?topic=3433.60<br />
<br />
== ideas ==<br />
* improve media tagging in webadmin<br />
* picture media player<br />
* media transcoding plugin</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Creating_New_Datagrid&diff=20074Creating New Datagrid2009-07-27T19:10:37Z<p>Chriss: </p>
<hr />
<div>How do I create a new '''games plugin''' that generates a [[datagrid]] showing games on the screen?<br />
<br />
Here is how I would do it:<br />
<br />
* Add a device template for the 'Games Plugin'. Use Climate Plugin as the template; it's the simplest of the plugins.<br />
* Do an apt-get install pluto-dcegen, and run: /usr/pluto/bin/DCEGen -d [device template] from the bin directory where your sources are (cd /home/sources/trunk/src/bin for example).<br />
* In Games_Plugin.h add an ! after the //<-dceag-decl-b-> line so that block of auto-gen'd code won't get overriden, and co-derive teh class from , public DataGridGeneratorPlugIn like climate plugin.<br />
* Add the member: <pre>class Datagrid_Plugin *m_pDatagrid_Plugin;</pre> and a function for your data grid: <pre>class DataGridTable *ClimateScenariosGrid(string GridID,string Parms,void *ExtraData,int *iPK_Variable,string *sValue_To_Assign,class Message *pMessage);</pre><br />
* Add the code that initializes the datagrid engine like in climate plugin:<br />
<pre><br />
m_pDatagrid_Plugin=( Datagrid_Plugin * ) m_pRouter->FindPluginByTemplate(DEVICETEMPLATE_Datagrid_Plugin_CONST);<br />
if( !m_pDatagrid_Plugin )<br />
{<br />
LoggerWrapper::GetInstance()->Write(LV_CRITICAL,"Cannot find sister plugins to climate plugin");<br />
return false;<br />
}<br />
<br />
m_pDatagrid_Plugin->RegisterDatagridGenerator(<br />
new DataGridGeneratorCallBack(this,(DCEDataGridGeneratorFn)(&Climate_Plugin::ClimateScenariosGrid))<br />
,DATAGRID_Climate_Scenarios_CONST,PK_DeviceTemplate_get());<br />
</pre><br />
* Add a record in teh pluto_main.DataGrid table for your new datagrid, and edit pluto_main/Define_DataGrid.h to add your new record, and change the RegisterDataGrid to use your function for the datagrid and your DATAGRID_X_CONST.<br />
<br />
* In Designer add a new DesignObj for the screen that will display your datagrid. Use one of the other screens as a template. To see what screens are being used, edit /etc/pluto.conf, comment out the LogLevels line, do: <pre>/usr/pluto/bin/MessageSend dcerouter 0 -1000 7 11</pre> to force all devices to recheck the log levels and start logging verbosely. Tail the <pre>/var/log/pluto/20_LaunchOrbiter.log | grep Goto_DesignObj</pre> Then as you change screens in Orbiter you can see what designobj's are being used. Note that Designer is nasty, unfriendly, finicky, and only runs on Windows. Sorry, this really needs work, but has been neglected since it's an in-house tool.<br />
<br />
* When you add the new design obj of type datagrid, add your new data grid id.<br />
<br />
* Add to the pluto_main.Screen table a record for this new screen and set the 'autoinclude' field to 1 for now so that screen will be generated even though nothing calls it. Then add to Screen_DesignObj a record associating this screen with your new DesignObj. <br />
<br />
* In the admin site, add an instance of your game plugin under DCERouter (next to the other plugins).<br />
<br />
* Go into the admin site and under Advanced, Configuration, Scenarios, add a scenario with a command going to "the local orbiter" "Goto Screen" with our new screen as teh parameter for PK_Screen.<br />
<br />
Now, after you reload the router and regen the Orbiter's UI, then when the user navigates to your screen by choosing the scenario you created, it will call that data grid generator function, and you can populate the grid with data like in Climate_Plugin::ClimateScenariosGrid and it will appear.<br />
<br />
Designer is in trunk/src/designer. It's a c# app requiring vs.net to compile. You can get a zip file at: http://linuxmce.org/HADesigner.zip with them already compiled so you should be able to run it on any windows box. first on your core's console run: <br />
mysql<br />
grant all on *.* to 'root'@'%.%.%.%' (or use an ip mask)<br />
so designer can access the mysql databases.<br />
<br />
Install the Mysql ODBC client for windows, and the attached Microsoft ODBC for .NET: http://linuxmce.org/odbc_net.msi<br />
<br />
Also, what I do is:<br />
ln -sf /usr/pluto/orbiter/ /home/orbiter<br />
<br />
and then from windows, start, run: \\192.168.80.1<br />
<br />
and in the /home/orbiter folder, copy the skins directory to c:\[whatever]\skins.<br />
<br />
When Designer runs give it the login information for accessing the database on the core, and the path to the skins directory. <br />
<br />
[[Category:Tutorials]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=LinuxMCE8.10_Alpha&diff=19964LinuxMCE8.10 Alpha2009-07-18T07:56:42Z<p>Chriss: </p>
<hr />
<div>[[Category:Versions]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
Currently (as of Feb 2009), the team is working hard on LinuxMCE-0810-Alpha2.<br />
<br />
The current alpha is available for download. Anyone wishing to do so, however, should understand that alpha-releases are a work in progress to be used by those who are willing to test a system and provide feedback to the team. It should not be used in an environment that you depend on to be reliable.<br />
<br />
For more information, see the Alpha1 page at [[LinuxMCE-0810_alpha1]]<br />
<br />
The instructions below are expected to remain the same for all alpha releases from Alpha2 onwards.<br />
<br />
==Installation==<br />
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. ([http://www.kubuntu.org/getkubuntu/download download Kubuntu 8.10 release])<br />
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.<br />
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz here], unpack them and change into the freshly created ''new-installer'' directory.<br />
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.<br />
# Reboot, wait for the activity to stop (see progress on console 8).<br />
<br />
In other words, after installing Kubuntu and upgrading it etcetera:<br />
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.<br />
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz<br />
tar xvf new-installer-alpha-latest.tar.gz<br />
cd new-installer<br />
./pre-install-from-repo.sh<br />
./mce-install.sh<br />
./post-install.sh<br />
reboot<br />
<br />
== Setup Diskless MD ==<br />
# On core from a terminal run sudo /usr/pluto/bin/Diskless_BuildDefaultImage.sh<br />
# Boot MD<br />
# Rundiskless setup fails, but the device gets created<br />
# Change md to i386 in webadmin -> rebuild image<br />
# On the core<br />
## Set a password for root on MD<br />
###chroot /usr/pluto/diskless/<##><br />
### run passwd.... enter password for root<br />
#On MD Switch to a terminal session<br />
## Login to MD as root<br />
## apt-get install nvividia-glx-177<br />
#From core copy valid xorg.conf from etc/X11 to /usr/pluto/diskless/##/etc/X11<br />
# Reboot MD. Now, the AV Wizard should come up<br />
# After the AV Wizard it takes a longer time to launch devices. No not need to reboot.<br />
<br />
=== Note ===<br />
If you don't happen to have a running xorg.conf, copy over the existing /etc/X11/xorg.conf.pluto-avwizard to /etc/X11/xorg.conf. <br />
<br />
You have to remove a single line RgbPath from the xorg.conf file, and change the line<br />
driver nv<br />
<br />
to<br />
driver nvidia<br />
<br />
== Known Problems ==<br />
=== Upgrading pluto-storage-devices ===<br />
If apt-get upgrade does cause problems with pluto-boot-scripts, do the following<br />
dpkg -r --force-all pluto-storage-devices<br />
apt-get install pluto-storage-devices<br />
apt-get upgrade<br />
<br />
=== VDR Installation ===<br />
VDR does not yet install a working setup. Follow [[VDR Manual Install]] regarding configuration files.<br />
<br />
=== VDR and sqlCVS Update ===<br />
A sqlCVS update will reset the selection from VDR back to MythTV. Re-running the Setup wizard and re-selecting VDR rectifies this glitch.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19655Translate the GUI into another language2009-07-07T20:39:19Z<p>Chriss: /* Working with Designer */</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
Never (!) update/overwrite an existing row when creating a new translation. Only change existing rows when you make a correction to an already existing translation.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Finally enter a comment to describe what you are checking in and hit ''Next''. Watch the progress in the pop-up window.<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations. Check the linked page and the wiki on how to get hold of Designer and how to make it start up.<br />
<br />
The process of updating your database before editing and committing your changes after editing are the same as described above.<br />
<br />
''Note: IMHO there currently is no option to define new languages in HADesigner [[User:Chriss|chriss]] 22:26, 7 July 2009 (CEST)''<br />
<br />
Designer has a comfortable interface for changing and translating text elements. First select the text tab on the DesignObj Browser:<br />
[[Image:Designer_obj_browser.png]]<br />
<br />
Find the items to translate in the categories and double-click on the element to open up the editor window. The editor window will expand if there are more languages defined.<br />
[[Image:Designer_edit_text.png]]<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19652Translate the GUI into another language2009-07-07T20:33:53Z<p>Chriss: /* How to translate */</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
Never (!) update/overwrite an existing row when creating a new translation. Only change existing rows when you make a correction to an already existing translation.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Finally enter a comment to describe what you are checking in and hit ''Next''. Watch the progress in the pop-up window.<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations. Check the linked page and the wiki on how to get hold of Designer and how to make it start up.<br />
<br />
The process of updating your database before editing and committing your changes after editing are the same as described above.<br />
<br />
Designer has a comfortable interface for changing and translating text elements. First select the text tab on the DesignObj Browser:<br />
[[Image:Designer_obj_browser.png]]<br />
<br />
Find the items to translate in the categories and double-click on the element to open up the editor window. The editor window will expand if there are more languages defined.<br />
[[Image:Designer_edit_text.png]]<br />
<br />
''Note: IMHO there is no option to define new languages in HADesigner [[User:Chriss|chriss]] 22:26, 7 July 2009 (CEST)''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=TV_Card_Comparison&diff=19650TV Card Comparison2009-07-07T20:27:54Z<p>Chriss: </p>
<hr />
<div>{{stub}}<br />
[[Category: Hardware ]]<br />
[[Category: Video Capture Boards]]<br />
[[Category: TV Cards ]]<br />
<br />
The purpose of this page is to summarize the currently supported / tested TV cards. This is intended to allow a quick comparison for those who are not necessarily familiar with all the available models.<br />
<br />
Please get involved and update as appropriate!<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center" class = "sortable"<br />
! Model<br />
! Make / Manufacturer<br />
! Connection Type<br />
! DVB-S<br />
! DVB-S2<br />
! DVB-T<br />
! DVB-C<br />
! Analog<br />
! Composite<br />
! 710<br />
! 810<br />
! MythTV<br />
! VDR<br />
|-<br />
| [[Hauppauge_WinTV_Nova-SE2|WinTV Nova-SE2]]<br />
| Hauppauge<br />
| PCI<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| No<br />
| No<br />
| bgcolor="red"| Unknown<br />
| Supported<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
|-<br />
| [[Hauppauge_WinTV-Nova-HD-S2|WinTV Nova-HD-S2]]<br />
| Hauppauge<br />
| PCI<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| No<br />
| No<br />
| Working<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
|-<br />
| [[Hauppauge_WinTV-PVR-150_MCE|WinTV PVR-150 MCE]]<br />
| Hauppauge<br />
| PCI<br />
| No<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Supported<br />
| Supported<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
|-<br />
| [[Hauppauge_WinTV-PVR-250|WinTV PVR-250]]<br />
| Hauppauge<br />
| PCI<br />
| No<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
|-<br />
| Pinnacle PCTV 310i<br />
| Pinnacle<br />
| PCI<br />
| No<br />
| No<br />
| Yes<br />
| No<br />
| Yes<br />
| No<br />
| Working<br />
| Working<br />
| bgcolor="red"| Unknown<br />
| Working<br />
|-<br />
| [[Kworld_KW-DVB-T_399U|KWorld U399]]<br />
| KWorld<br />
| USB<br />
| No<br />
| No<br />
| Yes x2<br />
| No<br />
| No<br />
| No<br />
| Working<br />
| In development<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
|-<br />
| [[DViCO_FusionHDTV7_Dual_Express|FusionHDTV7 Dual Express]]<br />
| DViCO<br />
| PCI Express x1<br />
| No<br />
| No<br />
| No (2x ATSC)<br />
| No<br />
| Yes NTSC<br />
| Yes<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
| bgcolor="red"| Unknown<br />
|}<br />
<br />
Statuses:<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! Status<br />
! Meaning<br />
|-<br />
| bgcolor="red"| Unknown<br />
| The status of this card with this version is not known to whoever added this card. If you know otherwise, '''PLEASE UPADTE!'''<br />
|-<br />
| Unsupported<br />
| No work has yet been done integrating on this version<br />
|-<br />
| Working<br />
| Works with this version, but requires manual configuration / driver updates etc.<br />
|-<br />
| In development<br />
| As Working, but development work is in progress to add this card and make it PNP<br />
|-<br />
| Supported<br />
| Works "Out of the box" so a good choice for newbies :-)<br />
|}</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19649Translate the GUI into another language2009-07-07T20:26:42Z<p>Chriss: Described translation process in Designer</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Finally enter a comment to describe what you are checking in and hit ''Next''. Watch the progress in the pop-up window.<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations. Check the linked page and the wiki on how to get hold of Designer and how to make it start up.<br />
<br />
The process of updating your database before editing and committing your changes after editing are the same as described above.<br />
<br />
Designer has a comfortable interface for changing and translating text elements. First select the text tab on the DesignObj Browser:<br />
[[Image:Designer_obj_browser.png]]<br />
<br />
Find the items to translate in the categories and double-click on the element to open up the editor window. The editor window will expand if there are more languages defined.<br />
[[Image:Designer_edit_text.png]]<br />
<br />
''Note: IMHO there is no option to define new languages in HADesigner [[User:Chriss|chriss]] 22:26, 7 July 2009 (CEST)''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=File:Designer_edit_text.png&diff=19647File:Designer edit text.png2009-07-07T20:22:34Z<p>Chriss: </p>
<hr />
<div></div>Chrisshttp://wiki.linuxmce.org/index.php?title=File:Designer_obj_browser.png&diff=19646File:Designer obj browser.png2009-07-07T20:19:30Z<p>Chriss: </p>
<hr />
<div></div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19645Translate the GUI into another language2009-07-07T18:30:02Z<p>Chriss: Completed description for work with database tools</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Finally enter a comment to describe what you are checking in and hit ''Next''. Watch the progress in the pop-up window.<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19644Translate the GUI into another language2009-07-07T18:29:23Z<p>Chriss: /* Check in translation */</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
'''Work in progress!!!''' [[User:Chriss|chriss]] 11:39, 7 July 2009 (CEST)<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Finally enter a comment to describe what you are checking in and hit ''Next''. Watch the progress in the pop-up window.<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19643Translate the GUI into another language2009-07-07T18:28:02Z<p>Chriss: Details on checking in changes</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
'''Work in progress!!!''' [[User:Chriss|chriss]] 11:39, 7 July 2009 (CEST)<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Watch the progress in the pop-up window.<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19642Translate the GUI into another language2009-07-07T18:22:16Z<p>Chriss: Details on updating database</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
'''Work in progress!!!''' [[User:Chriss|chriss]] 11:39, 7 July 2009 (CEST)<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
<br />
The database should be updated before starting any work on it. You can easily do this in web admin. Go to ''Advanced->sqlCVS->Update''. Leave the configuration fields with the default values<br />
sqlCVS Host: schema.linuxmce.org<br />
Port: 3999<br />
Username: anonymous<br />
Password: nopass<br />
Database: pluto_main<br />
Scroll down and click on ''Designer->Select All'' and than hit the ''Next'' button. Wait until the process is finished (wait until "Status: success" appears in the pop-up window.<br />
<br />
More details on sqlCVS usage can be found [[SqlCVS|here]].<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
''TBD''<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [[Trac]], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19640Translate the GUI into another language2009-07-07T18:13:26Z<p>Chriss: /* How to translate */</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
'''Work in progress!!!''' [[User:Chriss|chriss]] 11:39, 7 July 2009 (CEST)<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
Note: this howto is made for LinuxMCE 0810. Other versions may require changes in specific steps.<br />
<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
Basically there are two different ways to perform the translation - you can directly work with the database or you can use Designer as a desktop application.<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
''TBD''<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
''TBD''<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [[Trac]], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Text_LS&diff=19638Database.pluto main.Text LS2009-07-07T18:03:16Z<p>Chriss: Database.pluto main.TextLS moved to Database.pluto main.Text LS</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.TextLS contains overlays for the text elements defined in [[Database.pluto_main.Text|Text]] to allow for localization of the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Text_LS` (<br />
`FK_Text` int(11) NOT NULL default '0',<br />
`FK_Language` int(11) NOT NULL default '0',<br />
`Description` longtext NOT NULL,<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`FK_Text`,`FK_Language`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
<br />
===Field description===<br />
: FK_Text : Reference to [[Database.pluto_main.Text|pluto_main.Text.PK_Text]]. Defines the text item that is translated<br />
: FK_Language : Reference to [[Database.pluto_main.Language|pluto_main.Language.PK_Language]]. Defines the language the translation belongs to<br />
: Description : Translated text<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.TextLS&diff=19639Database.pluto main.TextLS2009-07-07T18:03:16Z<p>Chriss: Database.pluto main.TextLS moved to Database.pluto main.Text LS</p>
<hr />
<div>#REDIRECT [[Database.pluto main.Text LS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.TextCategory&diff=19637Database.pluto main.TextCategory2009-07-07T17:58:27Z<p>Chriss: </p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.TextCategory describes a tree-like category system for the GUI text elements defined in [[Database.pluto_main.Text|pluto_main.Text]]<br />
<br />
===SQL definition===<br />
CREATE TABLE `TextCategory` (<br />
`PK_TextCategory` int(11) NOT NULL auto_increment,<br />
`FK_TextCategory_Parent` int(11) default NULL,<br />
`Description` varchar(100) default NULL,<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_TextCategory`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
<br />
===Field description===<br />
: PK_TextCategory : Identification of the text item (primary key)<br />
: FK_TextCategory_Parent : Reference to PK_TextCategory to define the parent element of the current category. NULL for top level elements<br />
: Description : Name of the category<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.TextCategory&diff=19636Database.pluto main.TextCategory2009-07-07T17:57:23Z<p>Chriss: DB table pluto_main.TextCategory</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.TextCategory describes a tree-like category system for the GUI text elements defined in [[Database.pluto_main.Text|pluto_main.Text]]<br />
<br />
===SQL definition===<br />
CREATE TABLE `TextCategory` (<br />
`PK_TextCategory` int(11) NOT NULL auto_increment,<br />
`FK_TextCategory_Parent` int(11) default NULL,<br />
`Description` varchar(100) default NULL,<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_TextCategory`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
<br />
===Field description===<br />
: PK_TextCategory : Identification of the text item (primary key)<br />
: FK_TextCategory : Reference to PK_TextCategory to define the parent element of the current category. NULL for top level elements<br />
: Description : Name of the category<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Text&diff=19635Database.pluto main.Text2009-07-07T17:54:34Z<p>Chriss: Maybe I should use the preview button :(</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.Text contains all text elements displayed in the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Text` (<br />
`PK_Text` int(11) NOT NULL auto_increment,<br />
`FK_TextCategory` int(11) NOT NULL default '0',<br />
`Description` varchar(40) NOT NULL,<br />
`Define` varchar(40) NOT NULL,<br />
`AddToOrbiter` tinyint(1) default '0',<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_Text`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
===Field description===<br />
: PK_Text : Identification of the text item (primary key)<br />
: FK_TextCategory : Reference to [[Database.pluto_main.TextCategory|pluto_main.TextCategory.PK_TextCategory]] to select the category the text item belongs to<br />
: Description : Text string displayed in the GUI<br />
: Define : ''TBD''<br />
: AddToOrbiter : ''TBD''<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Text&diff=19634Database.pluto main.Text2009-07-07T17:53:43Z<p>Chriss: Corrected field description</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.Text contains all text elements displayed in the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Text` (<br />
`PK_Text` int(11) NOT NULL auto_increment,<br />
`FK_TextCategory` int(11) NOT NULL default '0',<br />
`Description` varchar(40) NOT NULL,<br />
`Define` varchar(40) NOT NULL,<br />
`AddToOrbiter` tinyint(1) default '0',<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_Text`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
===Field description===<br />
: PK_Text : Identification of the text item (primary key)<br />
: FK_TextCategory : Reference to [[Database.pluto_main.TextCategory||pluto_main.TextCategory.PK_TextCategory]] to select the category the text item belongs to<br />
: Description : Text string displayed in the GUI<br />
: Define : ''TBD''<br />
: AddToOrbiter : ''TBD''<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19633Translate the GUI into another language2009-07-07T17:51:34Z<p>Chriss: Added links to database descriptions</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
'''Work in progress!!!''' [[User:Chriss|chriss]] 11:39, 7 July 2009 (CEST)<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
''TBD''<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
''TBD''<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [[Trac]], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Text_LS&diff=19632Database.pluto main.Text LS2009-07-07T17:50:31Z<p>Chriss: DB table pluto_main.TextLS</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.TextLS contains overlays for the text elements defined in [[Database.pluto_main.Text|Text]] to allow for localization of the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Text_LS` (<br />
`FK_Text` int(11) NOT NULL default '0',<br />
`FK_Language` int(11) NOT NULL default '0',<br />
`Description` longtext NOT NULL,<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`FK_Text`,`FK_Language`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
<br />
===Field description===<br />
: FK_Text : Reference to [[Database.pluto_main.Text|pluto_main.Text.PK_Text]]. Defines the text item that is translated<br />
: FK_Language : Reference to [[Database.pluto_main.Language|pluto_main.Language.PK_Language]]. Defines the language the translation belongs to<br />
: Description : Translated text<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Category:Database&diff=19631Category:Database2009-07-07T17:45:44Z<p>Chriss: New page: Documentation for the different databases and tables</p>
<hr />
<div>Documentation for the different databases and tables</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Text&diff=19630Database.pluto main.Text2009-07-07T17:44:17Z<p>Chriss: DB table pluto_main.Text</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.Text contains all text elements displayed in the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Text` (<br />
`PK_Text` int(11) NOT NULL auto_increment,<br />
`FK_TextCategory` int(11) NOT NULL default '0',<br />
`Description` varchar(40) NOT NULL,<br />
`Define` varchar(40) NOT NULL,<br />
`AddToOrbiter` tinyint(1) default '0',<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_Text`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
===Field description===<br />
: PK_Text : Identification of the text item (primary key)<br />
: FK_Language_TextPlacement : ''TBD''<br />
: Description : Text string displayed in the GUI<br />
: Define : ''TBD''<br />
: AddToOrbiter : ''TBD''<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Language&diff=19629Database.pluto main.Language2009-07-07T17:41:22Z<p>Chriss: Added categories</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Database]]<br />
<br />
The table pluto_main.Language contains definitions for all available languages for the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Language` (<br />
`PK_Language` int(11) NOT NULL auto_increment,<br />
`Description` varchar(30) NOT NULL,<br />
`FK_Language_TextPlacement` int(11) default NULL,<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_Language`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
===Field description===<br />
: PK_Language : Identification of the language (primary key)<br />
: Description : Name of the language to be displayed for selection<br />
: FK_Language_TextPlacement : ''TBD''<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Database.pluto_main.Language&diff=19628Database.pluto main.Language2009-07-07T17:36:41Z<p>Chriss: Documentation for DB table pluto_main.Language</p>
<hr />
<div>The table pluto_main.Language contains definitions for all available languages for the GUI.<br />
<br />
===SQL definition===<br />
CREATE TABLE `Language` (<br />
`PK_Language` int(11) NOT NULL auto_increment,<br />
`Description` varchar(30) NOT NULL,<br />
`FK_Language_TextPlacement` int(11) default NULL,<br />
`psc_id` int(11) default NULL,<br />
`psc_batch` int(11) default NULL,<br />
`psc_user` int(11) default NULL,<br />
`psc_frozen` tinyint(1) default '0',<br />
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,<br />
`psc_restrict` int(11) default NULL,<br />
PRIMARY KEY (`PK_Language`),<br />
UNIQUE KEY `psc_id` (`psc_id`)<br />
) ENGINE=InnoDB DEFAULT CHARSET=latin1;<br />
<br />
===Field description===<br />
: PK_Language : Identification of the language (primary key)<br />
: Description : Name of the language to be displayed for selection<br />
: FK_Language_TextPlacement : ''TBD''<br />
: psc_* : All related to version control by [[sqlCVS]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=TV_Card_Comparison&diff=19609TV Card Comparison2009-07-07T13:16:22Z<p>Chriss: </p>
<hr />
<div>{{stub}}<br />
[[Category: Hardware ]]<br />
[[Category: Video Capture Boards]]<br />
[[Category: TV Cards ]]<br />
<br />
The purpose of this page is to sumarise the currently supported / tested TV cards. This is intended to allow a quick comparison for those who are not neccessarily familiar with all the available models.<br />
<br />
Please get involved and update as appropriate!<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! Model<br />
! Make / Manufacturer<br />
! Connection Type<br />
! DVB-S<br />
! DVB-S2<br />
! DVB-T<br />
! DVB-C<br />
! Analog<br />
! Composite<br />
! 710<br />
! 810<br />
|-<br />
| [[Hauppauge_WinTV-PVR-150_MCE|PVR-150 MCE]]<br />
| Hauppauge<br />
| PCI<br />
| No<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Supported<br />
| Supported<br />
|-<br />
| Pinnacle PCTV 310i<br />
| Pinnacle<br />
| PCI<br />
| No<br />
| No<br />
| Yes<br />
| No<br />
| Yes<br />
| No<br />
| Working<br />
| Working<br />
|}<br />
<br />
Statuses:<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! Status<br />
! Meaning<br />
|-<br />
| Unsupported<br />
| No work has yet been done integrating on this version<br />
|-<br />
| Working<br />
| Works with this version, but requires manual configuration / driver updates etc.<br />
|-<br />
| In development<br />
| As Working, but development work is in progress to add this card and make it PNP<br />
|-<br />
| Supported<br />
| Works "Out of the box" so a good choice for newbies :-)<br />
|}</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19605Translate the GUI into another language2009-07-07T09:39:21Z<p>Chriss: mark the page as work in progress</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
<br />
'''Work in progress!!!''' [[User:Chriss|chriss]] 11:39, 7 July 2009 (CEST)<br />
<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "Text", "Text_LS" and "Language". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
''TBD''<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
''TBD''<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [[Trac]], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Translate_the_GUI_into_another_language&diff=19604Translate the GUI into another language2009-07-07T09:36:54Z<p>Chriss: Starting step-by-step howto on translations</p>
<hr />
<div>[[Category:Languages]]<br />
[[Category:Tutorials]]<br />
<br />
=Selecting the language for an Orbiter=<br />
To select the Language for an Orbiter, use [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Orbiter.<br />
<br />
=How to translate=<br />
LinuxMCE uses a smart system for translating GUI text elements. All text bits are stored in the main database as well as the translations. The text elements are picked up when generating orbiter screens. LinuxMCE selects the text elements corresponding to the language setting of the orbiter and whenever a piece of the GUI is not translated yet, it does a fallback to the English text.<br />
<br />
To perform a translation always follow these steps:<br />
# update your database (sqlCVS update)<br />
# create your language if it does not exist yet<br />
# do the translation (or parts of it)<br />
# commit your database changes (sqlCVS commit)<br />
<br />
<br />
==Working with the database==<br />
As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "Text", "Text_LS" and "Language". <br />
: "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text<br />
: "Language" : Defines the available languages for the GUI. The single languages consist of an identifier PK_Language and a descriptive string, e.g, "English", "German", "French"<br />
: "Text_LS" : Contains the translated text elements which are linked to "Text" and "Language" tables via the foreign keys FK_Language and FK_Text<br />
<br />
To work with the database you can use several programs, e.g., mysql command line client, phpmyadmin web frontend, mysql browser desktop application... I will not go into details how to work with databases here.<br />
<br />
When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.<br />
<br />
===Update database=== <br />
''TBD''<br />
<br />
===Create a new language definition===<br />
If you would like to do a translation to a currently unsupported language you first have to create a definition for that language. To do this, create a new row in pluto_main.Language with the name of the language and remember the ID PK_Language.<br />
<br />
''I suggest to use the native spelling of the language name and not the English term, e.g. use "Deutsch" instead of "German" or "Française" instead of "French" to make the selection more user friendly. [[User:Chriss|chriss]] 11:36, 7 July 2009 (CEST)<br />
''<br />
<br />
===Translating===<br />
For every term that needs to be translated (remember, there is a smart fallback system, e.g., you do not need to translate the letters for the on-screen keyboard ;)) create a new row in pluto_main.Text_LS where FK_Language has to contain the ID of your language and FK_Text has to contain the ID of the translated row from pluto_main.Text. Best way for translating is to iterate through all entries in pluto_main.Text and create the translation.<br />
<br />
===Check in translation===<br />
''TBD''<br />
<br />
After successfully translating the GUI and checking in all changes please create a ticket in [[Trac]], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.<br />
<br />
<br />
==Working with Designer==<br />
[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.<br />
''TBD''<br />
<br />
=For developers=<br />
The text which you see on the Orbiter is stored in the LinuxMCE_main database in the "Text" and "Text_LS" tables. Each block of text or phrase has an entry in the text table. The Text_LS table has text in the language specified.<br />
<br />
To add a new language you need to add a new record to the Language table, and then add new records to Text_LS, with the translated version of each text blocked. It is easiest to do this in the [[Designer]] program. Designer will show you all the text blocks logically laid out in folders and categories. It is not necessary to translate the entire user interface all at once. You can translate only certain phrases and when [[Orbiter Generator|OrbiterGen]] rebuilds the User Interface it will use English for any phrases that are not translated.</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Graphics_Test&diff=19196Graphics Test2009-05-27T14:15:51Z<p>Chriss: SPAM: Undo revision 19193 by Diyaseb (Talk)</p>
<hr />
<div>[[Category: Hardware| ]]<br />
[[Category: Tutorials]]<br />
[[Category: Testing]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
==Testing Graphics Capabilities of Video Card==<br />
There are two ways to reach the graphics test tool for your system: LinuxMCE installer and LinuxMCE Launch Manager. This tool will test the video capabilities of your system (depending on your CPU and graphic card).<br />
<br />
'''NOTE''': Depending by how fast the images are running on your screen, you will choose the correct UI. For example, if the images are running slow, choose a lower graphic interface like UI1 or UI2 (masking). If the images are running fast without any problem, then use UI2 (masking) or UI2 (alpha blending).<br />
<br />
===LinuxMCE Installer===<br />
'''1.''' ''The first way to test your graphic system is from LinuxMCE installer. One of the last steps of the installation will ask you about what UI you want on your system. There, you have two buttons. One of them, '''Read Online Documenation''' will open this wiki web page. The second button, '''Run Graphical Test Application''' will open the graphical test tool. For testing, the tool will need the Xine player which will be downloaded and installed automatically. Then, you can run the test. Here is a screenshot with what you should get when you reach that step in LinuxMCE installation:''<br />
<br />
<br />
[[Image:Installertool.jpg|400px]]<br />
<br />
====Run Graphical Test Application====<br />
'''a.''' If you are pressing '''Run Graphical Test Application''', you'll see this initial screen.<br />
<br />
<br />
[[Image:Initial111.jpg|400px]]<br />
<br />
====Check for Composite Capabilities====<br />
'''b.''' Pressing c key will test video capabilities for composite.<br />
<br />
<br />
[[Image:Initial112.jpg|400px]]<br />
<br />
====Check for Masking Capabilities====<br />
'''c.''' To test your system for masking possibilities you have to press m key.<br />
<br />
<br />
[[Image:Initial113.jpg|400px]]<br />
<br />
====Check for Masking and Composite Together====<br />
'''d.''' To test composite and masking together, press first c and after that press m<br />
<br />
<br />
[[Image:Initial114.jpg|400px]] <br />
<br />
====This is What you should See====<br />
'''e.''' And this is how it should look when you are running the tool in full screen.<br />
<br />
<br />
[[Image:Initial115.jpg|400px]] <br />
<br />
<br />
===LinuxMCE Launch Manager===<br />
'''2.''' T''he other way to run the graphics test tool is from Linux MCE Launch Manager. In the following lines, you'll see every test, how it should look (using a Nvidia card). Please remember that the same tests images and keys combinations are applied also to the first way of running the test tool. <br />
''<br />
====Start UI Diagnostic Tool====<br />
'''a.''' This is the initial display of Linux MCE Launch Manager. Choose an UI type and then Start UI diagnostic tool to test the video capabilities of your system.<br />
<br />
<br />
[[Image:Initial2.jpg|400px]]<br />
<br />
====Check for Composite Capabilities====<br />
'''b.''' The next image will show you the Composite capabilities of your graphic system.<br />
<br />
<br />
[[Image:Composite.jpg|400px]]<br />
<br />
====Check for Masking Capabilities====<br />
'''c.''' This image will test the Masking capabilities of the graphical system, which is used by LinuxMCE interface.<br />
<br />
<br />
[[Image:Masking.jpg|400px]]<br />
<br />
====Check for Masking and Composite Together====<br />
'''d.''' This is how it should look when you are using masking and composite in the same time. The test will show if the system can run successfully Linux MCE interface<br />
<br />
<br />
[[Image:Comp-mask.jpg|400px]]<br />
<br />
====This is What you should See====<br />
'''e.''' Any of the tests can be run also in full screen. This picture shows one of the tests in action.<br />
<br />
<br />
[[Image:Full_screen.jpg|400px]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Community_Portal&diff=6741LinuxMCE:Community Portal2007-10-20T12:10:47Z<p>Chriss: /* News */</p>
<hr />
<div>__NOTOC__<br />
<div align="center"><br />
<h1>'''[http://linuxmce.org LinuxMCE]''' community portal</h1><br />
</div><br />
<br />
==Request for comment==<br />
Comments and ideas welcomed in a [[LinuxMCE Wiki talk:Community Portal|debate about categorization]].<br />
<br />
==News==<br />
*'''19/10-07''' - Danielk has set up a public development area ([http://svn.charonmedia.org/ Trac], [http://www.charonmedia.org dev mailing list]). Please do also comment on moving development related stuff on the [[LinuxMCE_Wiki_talk:Community_Portal#Separating_development-related_stuff_into_the_Trac_Wiki|discussion page]]. Thanks --[[User:Chriss|chriss]] 05:08, 20 October 2007 (MST)<br />
*'''27/9-07''' - [[User:Lozzo|Lozzo]] and [[User:Trout|Trout]] are now also admins.<br />
*'''24/9-07''' - New template added, [[:Template:Delete]], add this to pages that you propose for deletion, these pages will also be added to the category [[:Category:Delete Page|Delete Page]]. --[[User:Samme|Samme]] 06:09, 24 September 2007 (MST)<br />
*'''24/9-07''' - I have now blocked the known spammers, another thing I've done is that I've added the category [[:Category: NeedsToBeFixed|NeedsToBeFixed]], look at the page for further information. --[[User:Samme|Samme]] 02:48, 24 September 2007 (MST)<br />
*'''22/9-07''' - Is there somebody out there who knows how to make templates? If so we need you're help!!!<br />
*'''15/9-07''' - [[User:Trout|Trout]] has now also volunteered as admin.<br />
*'''14/9-07''' - I, [[User:Samme|Samme]] is now administrator of the wiki, after a discussion with Paul, other interested in helping, mail me, you'll find my adress under the [[Contacts|contact page]].<br />
<br />
==To do==<br />
#<strike>Spam prevention</strike><br />
#<strike>Recruit a second admin and also volunteers, up for the task? Contact me!</strike><br />
#<strike>Delete garbage pages all can be found in the category [[:Category:Delete Page|Delete Page]]</strike><br />
#Set up rules & guidelines for the wiki<br />
#<strike>New first page</strike><br />
#Fix hardware pages<br />
#[[LinuxMCE Wiki:Community Portal:Category Proposal|Categories, proposal]], very important<br />
#Various guides maybe replace FAQ?<br />
#Dictionary?<br />
#Join associated pages by unision or cross-referencing (if they are definately in different cathegories) exampe: [[Nokia_770]], [[Nokia_770_Orbiter]], [[Building_Orbiter_for_the_Nokia_770]]<br />
<br />
Feel free to add things to do, after all it is a wiki :o)<br />
<br />
==Pages needing attention==<br />
*[http://wiki.linuxmce.com/index.php?title=Special:Lonelypages&limit=500&offset=0 Orphaned articles] (65 as of 29 September)<br />
*[http://wiki.linuxmce.com/index.php?title=Special:Uncategorizedpages&limit=500&offset=0 Uncategorized articles] (241 as of 29 September)<br />
*[http://wiki.linuxmce.com/index.php?title=Special:Deadendpages&limit=500&offset=0 Dead-end articles] (279 as of 29 September)<br />
*[[:Category:Articles needing categorization|Articles needing categorization]] <nowiki>{{nocat}}</nowiki><br />
*[[:Category:Articles needing expansion|Articles needing expansion]] <nowiki>{{stub}}</nowiki><br />
*[[:Category:Articles with sections needing expansion|Articles with sections needing expansion]] <nowiki>{{sectstub}}</nowiki><br />
*[http://wiki.linuxmce.com/index.php?title=Special:Shortpages&limit=500&offset=0 Short articles]<br />
*[[:Category:NeedsToBeFixed|Articles needing to be fixed in some way]] <nowiki>{{NeedsToBeFixed}}</nowiki><br />
*[http://wiki.linuxmce.com/index.php/Special:Uncategorizedcategories Categories with no parent] (currently one root category but needs checking periodically)<br />
*[[:Category:Delete Page|Articles and categories to be deleted]] <nowiki>{{delete}}</nowiki><br />
<br />
==Handy templates==<br />
* <nowiki>{{stub}}</nowiki> used to specify articles which need expanding<br />
* <nowiki>{{sectstub}}</nowiki> used to specify sections which need expanding<br />
* <nowiki>{{uncat}}</nowiki> used to specify articles which need to be categorized<br />
* <nowiki>{{delete}}</nowiki> article nominated for deletion<br />
* <nowiki>{{merge|articlename}}</nowiki> specifies article with which the current article should be merged<br />
* <nowiki>{{NeedsToBeFixed}}</nowiki> article needs to be fixed in some way - ''better to use more descriptive templates if possible''<br />
<br />
==Some useful links==<br />
<br />
*[http://LinuxMCE.com LinuxMCE homepage]<br />
*[http://forum.linuxmce.com LinuxMCE Forums]<br />
*[http://ubuntuforums.org/ Ubuntu Forums]<br />
<br />
[[Category:Wiki administration]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Community_Portal&diff=6740LinuxMCE:Community Portal2007-10-20T12:08:16Z<p>Chriss: /* News */</p>
<hr />
<div>__NOTOC__<br />
<div align="center"><br />
<h1>'''[http://linuxmce.org LinuxMCE]''' community portal</h1><br />
</div><br />
<br />
==Request for comment==<br />
Comments and ideas welcomed in a [[LinuxMCE Wiki talk:Community Portal|debate about categorization]].<br />
<br />
==News==<br />
*'''19/10-07''' - Danielk has set up a public development area (http://svn.charonmedia.org/, http://www.charonmedia.org). Please do also comment on moving development related stuff on the [[LinuxMCE_Wiki_talk:Community_Portal#Separating_development-related_stuff_into_the_Trac_Wiki|discussion page]]. Thanks --[[User:Chriss|chriss]] 05:08, 20 October 2007 (MST)<br />
*'''27/9-07''' - [[User:Lozzo|Lozzo]] and [[User:Trout|Trout]] are now also admins.<br />
*'''24/9-07''' - New template added, [[:Template:Delete]], add this to pages that you propose for deletion, these pages will also be added to the category [[:Category:Delete Page|Delete Page]]. --[[User:Samme|Samme]] 06:09, 24 September 2007 (MST)<br />
*'''24/9-07''' - I have now blocked the known spammers, another thing I've done is that I've added the category [[:Category: NeedsToBeFixed|NeedsToBeFixed]], look at the page for further information. --[[User:Samme|Samme]] 02:48, 24 September 2007 (MST)<br />
*'''22/9-07''' - Is there somebody out there who knows how to make templates? If so we need you're help!!!<br />
*'''15/9-07''' - [[User:Trout|Trout]] has now also volunteered as admin.<br />
*'''14/9-07''' - I, [[User:Samme|Samme]] is now administrator of the wiki, after a discussion with Paul, other interested in helping, mail me, you'll find my adress under the [[Contacts|contact page]].<br />
<br />
==To do==<br />
#<strike>Spam prevention</strike><br />
#<strike>Recruit a second admin and also volunteers, up for the task? Contact me!</strike><br />
#<strike>Delete garbage pages all can be found in the category [[:Category:Delete Page|Delete Page]]</strike><br />
#Set up rules & guidelines for the wiki<br />
#<strike>New first page</strike><br />
#Fix hardware pages<br />
#[[LinuxMCE Wiki:Community Portal:Category Proposal|Categories, proposal]], very important<br />
#Various guides maybe replace FAQ?<br />
#Dictionary?<br />
#Join associated pages by unision or cross-referencing (if they are definately in different cathegories) exampe: [[Nokia_770]], [[Nokia_770_Orbiter]], [[Building_Orbiter_for_the_Nokia_770]]<br />
<br />
Feel free to add things to do, after all it is a wiki :o)<br />
<br />
==Pages needing attention==<br />
*[http://wiki.linuxmce.com/index.php?title=Special:Lonelypages&limit=500&offset=0 Orphaned articles] (65 as of 29 September)<br />
*[http://wiki.linuxmce.com/index.php?title=Special:Uncategorizedpages&limit=500&offset=0 Uncategorized articles] (241 as of 29 September)<br />
*[http://wiki.linuxmce.com/index.php?title=Special:Deadendpages&limit=500&offset=0 Dead-end articles] (279 as of 29 September)<br />
*[[:Category:Articles needing categorization|Articles needing categorization]] <nowiki>{{nocat}}</nowiki><br />
*[[:Category:Articles needing expansion|Articles needing expansion]] <nowiki>{{stub}}</nowiki><br />
*[[:Category:Articles with sections needing expansion|Articles with sections needing expansion]] <nowiki>{{sectstub}}</nowiki><br />
*[http://wiki.linuxmce.com/index.php?title=Special:Shortpages&limit=500&offset=0 Short articles]<br />
*[[:Category:NeedsToBeFixed|Articles needing to be fixed in some way]] <nowiki>{{NeedsToBeFixed}}</nowiki><br />
*[http://wiki.linuxmce.com/index.php/Special:Uncategorizedcategories Categories with no parent] (currently one root category but needs checking periodically)<br />
*[[:Category:Delete Page|Articles and categories to be deleted]] <nowiki>{{delete}}</nowiki><br />
<br />
==Handy templates==<br />
* <nowiki>{{stub}}</nowiki> used to specify articles which need expanding<br />
* <nowiki>{{sectstub}}</nowiki> used to specify sections which need expanding<br />
* <nowiki>{{uncat}}</nowiki> used to specify articles which need to be categorized<br />
* <nowiki>{{delete}}</nowiki> article nominated for deletion<br />
* <nowiki>{{merge|articlename}}</nowiki> specifies article with which the current article should be merged<br />
* <nowiki>{{NeedsToBeFixed}}</nowiki> article needs to be fixed in some way - ''better to use more descriptive templates if possible''<br />
<br />
==Some useful links==<br />
<br />
*[http://LinuxMCE.com LinuxMCE homepage]<br />
*[http://forum.linuxmce.com LinuxMCE Forums]<br />
*[http://ubuntuforums.org/ Ubuntu Forums]<br />
<br />
[[Category:Wiki administration]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=LinuxMCE_talk:Community_Portal&diff=6739LinuxMCE talk:Community Portal2007-10-20T12:04:59Z<p>Chriss: /* Same old, same old */</p>
<hr />
<div>==Moved from Zaerc's talk page==<br />
=== Categorization ===<br />
<br />
Hi Zaerc,<br />
I have noticed that you have moved a number of hardware articles from more specific categories, such as [[:Category:TV tuner cards]] to the more general category [[:Category:hardware]] and that you have nominated the more specific categories for deletion. Why was this? Surely the more specific categorization is helpful, especially when product codes often do not explain the nature of the equipment [[User:Lozzo|Lozzo]] 00:37, 7 October 2007 (MST)<br />
:Can we please hold fire on further re-categorization until further community consensus is sought. Many thanks [[User:Lozzo|Lozzo]] 00:59, 7 October 2007 (MST)<br />
::Why did you de-categorize everything from the TV tuner card category? [[User:Lozzo|Lozzo]] 01:05, 7 October 2007 (MST)<br />
<br />
<br />
Because I wanted to get back to where I was with organising things before people started to re-organise everything. See also the "community-proposal" page. I suppose I went a little overboard as I had to go through just about all the pages under "hardware" again anyway, which I wasn't to happy about in all honesty (I was getting tired, having to put everything back, and obviously didn't gave it enough thought).<br />
<br />
The original idea was to dump hardware into the main categories untill there is a bunch similar and then put them into their own sub-category as well. When I went through all the pages again I felt that would leave the "video" category as good as empty but now I realize I could have just added the tv-cards to both "video" and "tv-cards".<br />
<br />
My thought also was that categories with 1 or 2 pages in them wouldn't be very usefull and spread them out to much (the video category would be almost empty with the tv-cards removed) but now I see that wouldn't be a problem if they remain in the parent categories as well. So I agree with you on putting (at least) the TV-cards category back in, that makes it a lot easier to specificly find them. <br />
<br />
Unless you want to take categories away from pages again, I see no reason to hold fire, we can just add new (sub-)categories to the pages wherever suitable. And if anyone feels that a page really does not belong in a certain category they can just remove it with a little note on the talk page (see Nokia770 for example).<br />
<br>--[[User:Zaerc|Zaerc]] 05:16, 7 October 2007 (MST)<br />
<br />
:Firstly, yes I agree with you that there needs to be a critical mass of articles in a certain area before a sub-category is created.<br />
<br />
:Secondly, yes, I do want to make sure that articles do not appear once in a category and then again ''in a more general category''. This would involve, as you put it, 'taking categories away from pages'. I understand that this is not Wikipedia and I'm not suggesting that we should do everything the same. But the Wikimedia projects have conventions which have been subjected to a large amount of thought and debate and can be very useful guides for less mature documentation projects such as this.<br />
<br />
:Wikipedia sets the de-facto standard for how wikis should be organised - especially when we are using the same software (MediaWiki). Regardless of that, I think that having article A in one category and then a more general category is confusing and runs counter to the intention of how the category function was designed. It makes for general categories which are needlessly cluttered with articles which should be (and are) also categorized more specifically higher up the tree.<br />
<br />
:Having a list of articles in one place (so they are as you claim) may be appropriate for a small number of articles but this is not scalable for a large amount of documentation like we have. To quote directly from the Wikimedia guidelines:<br />
<br />
:''Each page is typically in at least one category. It may be in more, but it may be wise not to put a page in a category and also in a more general category.''[http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Using_Categories#Category_considerations]<br />
<br />
:I do not think you have given a good enough reason to deviate from this. Of course, articles can be in more than one category. You give the examples of phones and orbiters. With the following category structure<br />
<br />
-Hardware<br />
|-Phones<br />
|-Orbiters<br />
<br />
: A device as you describe (which is not exclusively a phone or an orbiter) can appear in both the phone and orbiter category - but ''not'' hardware as this is a more general category. Pleas can we hold fire on further changes in this area until there is more agreement. I will ask others for comment. Cheers [[User:Lozzo|Lozzo]] 06:55, 7 October 2007 (MST)<br />
<br />
===Succinctly===<br />
In my opinion (and following established conventions) this is fine:<br />
<br />
-HARDWARE<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
This is not fine and makes for clutter:<br />
<br />
-HARDWARE --> Cisco smart phone article<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
[[User:Lozzo|Lozzo]] 07:05, 7 October 2007 (MST)<br />
<br />
::A phone is just as much hardware as it is a phone or an orbiter. And it is extremely convenient to have a category listing all the known hardware. As for the other more general categories, they make it easy to quickly find related solutions. Apart from that it is a lot easier to remove tags from pages then to add them, should they prove to be unecessary.<br />
<br />
::I see no reason to comply with policies of unrelated wikis, and: ''but '''it may be wise not to''' put a page in a category and also in a more general category'', does not seems like a very convincing argument. Even if it is an "established convention" elsewhere.<br />
<br />
::I just wish we could focus more on expanding and organizing instead of endless re-organization and debate on how it should be done. And why exactly do we need to have several threads discussing this on my talk page and not the forum or the hardware-category's talk page? --[[User:Zaerc|Zaerc]] 08:45, 7 October 2007 (MST)<br />
<br />
:::Okay I've now moved everything here. Forget other wikis for the time being. There is still obviously some disagreement here which we need to resolve by coming to some kind of consensus decision. Can we ''please'' hang fire on further changes in this area for the time being? [[User:Lozzo|Lozzo]] 10:19, 7 October 2007 (MST)<br />
::::You are completely correct to say "A phone is just as much hardware as it is a phone or an orbiter." But this is accounted for in the example below because both phones and orbiters are '''subclasses''' of hardware. It doesn't need to be repeated again in the hardware category - this is implicit.<br />
<br />
-HARDWARE<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
::::As a compromise, how about we have a list of all hardware as an article in itself? This would surely satisfy your requirement for a complete hardware list in one place? [[User:Lozzo|Lozzo]] 10:24, 7 October 2007 (MST)<br />
<br />
::I'm in favor with Lozzos proposal at the top here, I think this makes sense and also as Lozzo says we could have a long alphabetical list with all hardware that's easy to search through if it's needed. --[[User:Samme|Samme]] 11:03, 7 October 2007 (MST)<br />
<br />
<br />
Unless somebody comes up with some good reasons to remove all the pages describing hardware from the hardware category, I see little reason for me to stop organizing the hardware section as I have been doing since before you came along (no offence intended). I'm really not that interested in acedemic debate on grouping theory, whether something "isn't needed" or "implict" seems hardly worth the discussion. As for pages with lists, that simply does not work, you can find a whole bunch of attempts in the "hardware lists" category. --[[User:Zaerc|Zaerc]] 11:30, 7 October 2007 (MST)<br />
<br />
<br />
:Zaerc, I'm not saying we should necessarily go one way or the other for the time being. But I think it would be reasonable and proper to have a little bit of a discussion with a few of us to get some group consensus before we press on in any particular direction with regards the way we categorize/list things. I'd be very interested to hear your further thoughts on why you believe a hardware list is unworkable.<br />
<br />
:Also, what do you reckon should be the minimum number of articles to justify a category?<br />
<br />
:[[User:Lozzo|Lozzo]] 14:20, 7 October 2007 (MST)<br />
<br />
<br />
::I think the absolute minimum would be one, but ideally the more the merrier. If you look at the [[RCS TXB16]] for example, it is the only thermostat we have (afaik) in the wiki. Still I think it is a good idea to give this device a Thermostats category so that the people looking through automation subcategories (for example) will find it there. And somebody looking for info on that particular device instead will be able to find it in the hardware category without having to go through sub-categories first.<br />
<br />
::Now if you want to make and maintain a seperate list that is fine with me, I'm not having that discussion again. And so far I still haven't seen any good argument to remove all the hardware from the hardware category. --[[User:Zaerc|Zaerc]] 15:53, 7 October 2007 (MST)<br />
<br />
<br />
:::Zaerc, as far as I am aware, you don't have executive fiat on this wiki. With all due respect, what I'm hearing from you at the moment is: "I've decided what's going to happen with regards categorization, I don't care what anyone else says and I'm not going to debate the matter further". I've outlined my arguments at length and in a civil manner. This has included a compromise proposal (supported by Samme) and I do not feel you have given a proper explanation of why you don't think it's workable. You have instead responded by saying you won't discuss the matter further ("I'm not having that discussion again"). [[User:Lozzo|Lozzo]] 11:18, 8 October 2007 (MST)<br />
<br />
<br />
::::You have outlined your opinion over and over, I still see no real arguments why the hardware has to be removed from the hardware category per se. Apart from that, why exactly do I need to go over the hardware-list discussion again? I see no obligation on my part to explain to you why hardware-lists do not work. --[[User:Zaerc|Zaerc]] 05:56, 9 October 2007 (MST)<br />
<br />
<br />
==Lozzo's compromise proposal==<br />
Re-iterating the above...<br />
<br />
<br />
:''Just to point out the obvious, this is no compromise at all.'' --[[User:Zaerc|Zaerc]] 05:56, 9 October 2007 (MST)<br />
<br />
<br />
===Current situation===<br />
# Zaerc wants somewhere where there is "a category listing all the known hardware."<br />
# He has achieved this as follows by listing articles in one category and also in its more general parent category as follows:<br />
<br />
-HARDWARE --> Cisco smart phone article<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
===Disagreement===<br />
#Lozzo believes that this:<br />
##Violates the [http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Using_Categories#Category_considerations generally accepted convention for how categories should be structured]<br />
##Goes against the elegant principle of categories - the whole reason the function was added to MediaWiki<br />
##Makes for very cluttered general categories the further down the category tree you go<br />
##In the more general categories, for example harware, the user is presented with an arbitrary list of product names which do not necessarily describe what a product is. How are we supposed to know what an ''LG 42LB5D'' is or a ''Leadtek DTV1000T'' if they are in one big homogenous general category?<br />
<br />
===Proposed compromise solution===<br />
*'''To satisfy Zaerc's requirement for a single place to list all known hardware, we can maintain a single list article'''. I (lozzo) am very happy to help construct this in partnership with Zaerc. In fact, this would be better than putting all harware in the general hardware category because it would allow notation.<br />
<br />
*The articles should be tagged with categories as follows and according to convention: <br />
<br />
-HARDWARE<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
This compromise is supported by Lozzo and Samme (see above).<br />
<br />
Please comment below. [[User:Lozzo|Lozzo]] 11:18, 8 October 2007 (MST)<br />
<br />
==Comments==<br />
I am actually in agreement with Zaerc on this one. As the system is now. the Subcategories show up first, so the initial impression is to click the subcategory. I think a list would be to difficult to maintain as more and more people start adding content to the site. I vote for putting the articles in as many categories as they fit, including Hardware. <br />
<br />
Do you know why there is a Category: Hardware List and Hardware?<br />
--[[User:Rwilson131|Rwilson131]] 14:49, 8 October 2007 (MST)<br />
<br />
I still see no valid argument whatsoever to remove all the hardware from the hardware category, no matter how often you repeat your opinions. And "my requirement" is perfectly satisfied the way things are now. --[[User:Zaerc|Zaerc]] 16:08, 8 October 2007 (MST)<br />
<br />
'''''What the hell are you doing [http://wiki.linuxmce.org/index.php?title=LinuxMCE_Wiki_talk:Community_Portal&diff=next&oldid=6575 indenting my comments to be reactions to other comments???]''''' --[[User:Zaerc|Zaerc]] 15:12, 9 October 2007 (MST)<br />
<br />
::Yes, but ''mine isn't''. I am trying to propose a reasonable compromise where we can both achieve what we want. Please find below stuff from RWilson form my talk page. I will respond when I have time. [[User:Lozzo|Lozzo]] 17:03, 8 October 2007 (MST)<br />
<br />
I think we always need to start at the Main Page and determine how is the person most likely going to get to the proper information. Currently, we are confusing ourselves. Take for instance<br />
<br />
Person wants to find out if his system is going to work?(Try and imagine your first visit here were you confused?)<br />
* [[Main Page]]<br />
::The only link for the main page is to<br />
* [[Hardware]] an article about the basics<br />
::Here there are several links to Information about hardware.<br />
**[[What hardware I will need]]<br />
**[[:Category:Hardware]]<br />
::I logical next choose is [[What hardware I will need]]<br />
*[[What hardware I will need]]<br />
::Now this page has several links including [[Tested good hardware]] [[Tested bad hardware]] and [[Suggested hardware]], but the Category at the bottom is [[:Category:Hardware Lists]]<br />
::The [[Suggested hardware]] has items that state they do not work (this should not be there in my opinion)<br />
<br />
I think if we are going to have lists, then there should only be two, Bad Hardware and Suggested Hardware.<br />
Currently we also have [[Recommended Accessories]] which is essentially worthless.<br />
<br />
I can really see no need for [[:Category:Hardware Lists]] as the Categories page is already a list, which is self generated. I am a firm believer in KISS (Keep It Simple Stupid). The software is complicated enough, so our wiki should be simple and reflect the most common problems people are currently facing. ie Display issues, MythTV issues.<br />
Just my two cents worth!<br />
--[[User:Rwilson131|Rwilson131]] 15:01, 8 October 2007 (MST)<br />
<br />
:: I agree with you on this one, it feels to me that this category (Hardware lists and Recommended accessories) isn't necessary at all, I also agree with you that we should keep things simple and also we should make this wiki a simple place to navigate, nopt clutter it up with loads and loads of unnecessary categories etc. --[[User:Samme|Samme]] 00:09, 9 October 2007 (MST)<br />
<br />
:'''A category system is a tree-structure'''. If categories ANTS and SPIDERS are in category CREEPYCRAWLIES then the red ant can be put in the ANT category and it will follow logically that it is ''also in the category CREEPYCRAWLIES''. What you are effectively doing is listing things twice. The MediaWiki category system was never intended to be used in this way - i.e. to create large lists. This is what list articles are for!<br />
<br />
:To pick up on the point made by RWilson, a new user may click on the hardware category. Under the scheme you advocate he will be presented with a page that includes every single piece of hardware entered into the wiki. This includes many brand names and product numbers/codes which will make no sense at all - they didn't to me when I arrived which is why I set about working out what they were and categorizing them (as per nearly every other wiki on the planet). With respect, suggesting that an exhaustive list of hardware will be helpful to a new user is analgous to reading a book by starting at the index: needlessly confusing and overwhelming.<br />
<br />
:'''I am not suggesting that the current lists we have on board are any good''' - they aren't. But that doesn't mean that they have to stay that way. If you want an exhaustive list of hardware then create one in an article. If it has proper sections then it shouldn't take long to keep it up to date - just compare categories with sections in the long list [[User:Lozzo|Lozzo]] 17:50, 8 October 2007 (MST)<br />
<br />
::To emphasise once more, a category is not an "automatically generated list" as has been claimed above; they are two distinct concepts - go and ask anyone on another wiki using the MediaWiki software. If anyone is interested, take a look at this[http://en.wikipedia.org/wiki/Wikipedia:Categories%2C_lists%2C_and_series_boxes]. I am only linking to it because we are using the ''same software'' for our wiki, which is designed to be used in a particular way.<br />
<br />
:::I am not sure I really understand this point as anytime I have ever put something in a category it automatically shows up on the Category's Page. --[[User:Rwilson131|Rwilson131]] 09:07, 9 October 2007 (MST)<br />
<br />
::Another relevant point, each category page can only hold 200 articles before you have to start going through them page by page. [[User:Lozzo|Lozzo]] 18:05, 8 October 2007 (MST)<br />
<br />
:::This is worth noticing, cause I doubt someone will go through endless amount of pages to find there make/model of a tv in the articles listed under hardware category, it's much simple going like "hardware > tv > my model". --[[User:Samme|Samme]] 00:09, 9 October 2007 (MST)<br />
:::This is probably the most noteworthy reason for making this change I have seen. If an actually list solves this problem then I am for a List and taking Items out of the Hardware Section. If this does not fix this issue then leave them alone. --[[User:Rwilson131|Rwilson131]] 09:07, 9 October 2007 (MST)<br />
<br />
<br />
Like I said before, I am not interested in acedemic grouping theory, nor am I interested in how other, totally unrelated wikis are organized (whether they use the same software or not). Please come up with a good reason why all the hardware should be removed from the hardware category, until then I feel there is little use in rehashing your opinions over and over and over again. --[[User:Zaerc|Zaerc]] 04:46, 9 October 2007 (MST)<br />
<br />
<br />
:I have tried to outline my arguments in a clear, detailed, patient way. I have given several reasons why I believe we should change the current system advocated by Zaerc. I am sorry he does not agree or work with me or my compromise proposals but at least I have outlined my ideas at length and tried to explain (again at length) why the current system doesn't work. The arguments given in favour of keeping the status quo are as follows (please let me know if I've missed some off):<br />
<br />
#This is how things were done before up to now<br />
#A big list of hardware is useful, we have decided to use categories to do this and are going to stick with that<br />
<br />
:'''I have proposed a compromise solution where everyone can get what they want''' - we'll have an exhaustive list (which I don't deny is very useful) ''and'' we'll have an elegant clean taxonomy of articles by using the category system as it was intended. I cannot resist commenting that repeatedly describing my comments as "acedemic grouping theory" is a straw man argument and an excuse to not properly engage in a discussion. The onus is not only only on me to come up with something that Zaerc agrees with - he has to defend his position as well. [[User:Lozzo|Lozzo]] 07:00, 9 October 2007 (MST)<br />
<br />
<br />
::'''Your "compromise" is no compromise at all, and certainly not a "solution".''' Just in case you haven't noticed by now, the only one really interested in this discussion is you. --[[User:Zaerc|Zaerc]] 08:24, 9 October 2007 (MST)<br />
<br />
<br />
The more that I think about this topic, the more it seems like we are missing the point. If the way the mediawiki software was designed is to not use the Categories as list then we need to best utilize the software. After all we are trying to educate people on the best way to utilize LinuxMCE. It would not make any sense for us to tell people to do it one way even if the system was not designed that way. <br />
<br />
Personally, I think we need a list of Hardware that works and a list of hardware that does not. How all this is categorized is really semantics. I think that the the admins need to make a decision and go with it. Most of us will follow suit, as this does matter to us, and as admins you will have to figure out how to handle those that do not. I just need to know when I post next time, how you want it done. Let us move on. --[[User:Rwilson131|Rwilson131]] 09:07, 9 October 2007 (MST)<br />
<br />
:Thanks for your comments. I agree that we need lists of hardware that works and does not, and perhaps also a list of hardware broken down by type (TV card, X10 devices etc) so we can see it in one big list. I suppose the debate here is how we achieve this (with categories or lists).<br />
<br />
:You're right, we do need to move on and I hope we can reach a decision - preferably a compromise if one can be found. This is something I feel strongly about but I'm honestly not trying to prolong this discussion needlessly. Thanks again for your thoughts :-) [[User:Lozzo|Lozzo]] 14:13, 9 October 2007 (MST)<br />
<br />
<br />
::I agree that we already have those things, neatly categorized, so can we now finaly please get back to adding ''our'' experience with the hardware ''we'' have? --[[User:Zaerc|Zaerc]] 15:12, 9 October 2007 (MST)<br />
<br />
==Reasons why we shouldn't use lists as categories==<br />
*You can only order articles in a category alphabetically.<br />
*The articles cannot be ordered into sections or subsections to reflect different types of hardware.<br />
*A category with hundreds of items cannot be moved except by editing hundreds of articles.<br />
*After 200 articles you have to keep clicking to view the next page.<br />
*No annotation is possible at all.<br />
*The product code names for electronic hardware are often arcane and give ''no indication whatsoever'' about what the hardware actually does. How is it helpful to have [[RCA HC60RX]] and [[Caddx NX-8E]] in the same category? It isn't even obvious WHAT they are! In fact, one is an alarm panel and the other is a piece of automation equipment. But you certainly wouldn't know this from looking at the root hardware category!<br />
<br />
[[User:Lozzo|Lozzo]] 07:00, 9 October 2007 (MST)<br />
<br />
==Reasons why we should maintain a hardware list==<br />
*The different types of hardware can be ordered in any way which helps user understanding - not just alphabetically but my manufacturer or type for example.<br />
*You can have sections for different types of hardware/manufacturers.<br />
*A list is releatively easy to maintain. Instead of putting <nowiki>[[Category:Hardware]]</nowiki> in the article we simply add in a reference to the new hardware article in the appropriate section of the hardware list.<br />
*You can add additional notation.<br />
*Everything appears on the same page without having to click 'next'<br />
*Lists are much easier to build (fill up) than categories, because entries can be gathered, cut and pasted in from searches and other sources. For example, we could use this to have a list (or section) of hardware without articles in our wiki.<br />
<br />
[[User:Lozzo|Lozzo]] 07:00, 9 October 2007 (MST)<br />
<br />
== Same old, same old ==<br />
<br />
Excuse me but I have things to do besides filling talk pages with endless (not to mention pointless and utterly boring) discussion. --[[User:Zaerc|Zaerc]] 08:24, 9 October 2007 (MST)<br />
<br />
<br />
:I'm not going to be [[Talk:Serial Hack|goaded into a flame war]] no matter how rude you are. You are clearly incapable or unwilling to engage in a constructive way with other editors with whom you have a disagreement. If you "have better things to do" then I suggest you leave this talk page alone until you decided you actually want to engage with the arguments I have put forward. RWilson disagrees with me - do you see him flinging insults around? [[User:Lozzo|Lozzo]] 14:04, 9 October 2007 (MST)<br />
<br />
<br />
::I have already engaged your arguments earlier but all you seem to want to do is rewording your opinions over and over again. If pointing that out is "flinging insults around" then maybe you should just leave the hardware category alone, it was doing just fine without your "help". And yes, it is getting a bit annoying to have to convince new people like you (who aparently have little else to contribute) not to keep taking things away, I for one would rather spend that time and effort adding usefull things instead. --[[User:Zaerc|Zaerc]] 15:49, 9 October 2007 (MST)<br />
<br />
<br />
= Separating development-related stuff into the Trac Wiki =<br />
All,<br />
I suggest to move all development-related pages and information from this wiki to the Trac environment danielk has set up. This would lead to a clear separation between a user wiki (with information on supported hardware, manuals, howtos and so on) and a development wiki (howto build, documentation of sources...). Any comments? --[[User:Chriss|chriss]] 05:04, 20 October 2007 (MST)</div>Chrisshttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=6722User talk:Samme2007-10-16T11:36:11Z<p>Chriss: /* moving all development-related information */</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
::::How about that admin access for me? [[User:Trout|Trout]] 12:44, 25 September 2007 (MST)<br />
:::::Please block all the spammers. I've set a category on them Categories: Spammer [[User:Trout|Trout]] 17:30, 25 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)<br />
<br />
If <strong>categorization</strong> is one issue and <strong>weak content</strong> is another, maybe we could have two or more different ones. [[User:Trout|Trout]] 10:55, 25 September 2007 (MST)<br />
<br />
:Good point, what I mean the most with those are that they need to be categorized and wikified and often make them more readable. Maybe we should start by setting up some guidelines how articles should look etc? What do you think? Maybe we could somehow gather the ones that edit the wiki most and agree on some rules/guidelines, maybe via irc? --[[User:Samme|Samme]] 13:44, 25 September 2007 (MST)<br />
<br />
::IRC is fine. server/room/time ? [[User:Trout|Trout]] 17:31, 25 September 2007 (MST)<br />
<br />
I am not sure why the need to make so many changes. Pluto did most of the work for us. Take a look at there site to see how the pages were originally laid out and connected. http://plutohome.com/wiki/index.php/Main_Page<br />
<br />
There are many pages that are excellent that are not being linked to currently and I think that most of the information needed is already here it just needs to be found. [[Getting Started]] is packed full of good useful information that just really needs to be better organized. [[Features]] and just looking at http://wiki.linuxmce.org/index.php?title=Special:Uncategorizedpages reveals numerous pages that contain content that needs to be made available. IMHO --[[User:Rwilson131|Rwilson131]] 21:20, 25 September 2007 (MST)<br />
<br />
::Rwilson, do you have any ideas on categories? I've made a little proposal, but it's far from complete and may change alot, take alot, make additions, make changes. [[LinuxMCE Wiki:Community Portal:Category Proposal|Categories, proposal]] --[[User:Samme|Samme]] 23:49, 25 September 2007 (MST)<br />
:::Samme, I think the Proposed Categories are excellent. My commit was more about not reinventing the wheel. Pluto has put together a pretty thorough set of documentation and most of needs to be documented is already documented. The biggest problem I can foresee is re-organization and clean up/updating the content on these pages. Another problem I see is we need someone who can confirm that the programming information is still indeed correct. Take for instance the very difficult task of building from source. There is no good page for this. I am not a coder. I am someone who has been using this software for almost 18 months when it was pluto. There have been alot of changes since the migration from pluto, so we need to make sure that we are able to get the ''correct'' information out on the wiki.--[[User:Rwilson131|Rwilson131]] 17:10, 26 September 2007 (MST)<br />
<br />
== Request for comment ==<br />
<br />
I'm having a discussion with Zaerc about how categories should be organized. Please could you take a look at his talk page at [[User talk:Zaerc]] and comment? [[User:Lozzo|Lozzo]] 07:00, 7 October 2007 (MST)<br />
:The idea that Zaerc is pressing on with will result in a hardware category with ''every piece of hardware'' listed in the hardware root category - creating a mess with dozens of unidentifiable pieces of hardware lumped together. How is it helpful to have [[RCA HC60RX]] and [[Caddx NX-8E]] in the same category? It isn't even obvious WHAT they are!! In fact, one is an alarm panel and the other is a piece of automation equipment. But you certainly wouldn't know this from looking at the root hardware category!!<br />
<br />
:This is complete madness and the antithesis of what the designers of MediaWiki intended the category function to be used for. I have pointed this out on several occasions only to receive a response such as (to paraphrase) "well this isn't wikipedia - we do things differently here". Why on earth can't they create a list?! [[User:Lozzo|Lozzo]] 18:23, 8 October 2007 (MST)<br />
<br />
== New Users ==<br />
<br />
Can you honestly expect someone who has NO experience in Home Automation, or Media Center PCs to actually be able to look at the system without being confused by a mixture of both introductory and architectural technical texts? --[[User:Tschak909|Tschak909]] 17:45, 12 October 2007 (MST)<br />
<br />
== moving all development-related information ==<br />
<br />
[[user:danielk|danielk]] and [[user:chriss| I]] are working on setting up a public SVN along with a Trac environment. What do you think about moving all the development related sites into the Trac-wiki? I.e. this wiki would be a "user wiki" while the Trac-wiki becomes a "developer wiki" --[[User:Chriss|chriss]] 01:11, 13 October 2007 (MST)<br />
<br />
:I think this sounds like a good idea, this will make users less confused when coming to this wiki. I'm positive, have you talked to someone else about this? --[[User:Samme|Samme]] 00:14, 16 October 2007 (MST)<br />
<br />
::Nope, I just made the suggestion right here. I will open a discussion in the forum as soon as we can make the systems public, i.e. as soon as the sources are in sync with the current releases --[[User:Chriss|chriss]] 04:36, 16 October 2007 (MST)</div>Chrisshttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=6639User talk:Samme2007-10-13T08:11:47Z<p>Chriss: moving all development-related information</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
::::How about that admin access for me? [[User:Trout|Trout]] 12:44, 25 September 2007 (MST)<br />
:::::Please block all the spammers. I've set a category on them Categories: Spammer [[User:Trout|Trout]] 17:30, 25 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)<br />
<br />
If <strong>categorization</strong> is one issue and <strong>weak content</strong> is another, maybe we could have two or more different ones. [[User:Trout|Trout]] 10:55, 25 September 2007 (MST)<br />
<br />
:Good point, what I mean the most with those are that they need to be categorized and wikified and often make them more readable. Maybe we should start by setting up some guidelines how articles should look etc? What do you think? Maybe we could somehow gather the ones that edit the wiki most and agree on some rules/guidelines, maybe via irc? --[[User:Samme|Samme]] 13:44, 25 September 2007 (MST)<br />
<br />
::IRC is fine. server/room/time ? [[User:Trout|Trout]] 17:31, 25 September 2007 (MST)<br />
<br />
I am not sure why the need to make so many changes. Pluto did most of the work for us. Take a look at there site to see how the pages were originally laid out and connected. http://plutohome.com/wiki/index.php/Main_Page<br />
<br />
There are many pages that are excellent that are not being linked to currently and I think that most of the information needed is already here it just needs to be found. [[Getting Started]] is packed full of good useful information that just really needs to be better organized. [[Features]] and just looking at http://wiki.linuxmce.org/index.php?title=Special:Uncategorizedpages reveals numerous pages that contain content that needs to be made available. IMHO --[[User:Rwilson131|Rwilson131]] 21:20, 25 September 2007 (MST)<br />
<br />
::Rwilson, do you have any ideas on categories? I've made a little proposal, but it's far from complete and may change alot, take alot, make additions, make changes. [[LinuxMCE Wiki:Community Portal:Category Proposal|Categories, proposal]] --[[User:Samme|Samme]] 23:49, 25 September 2007 (MST)<br />
:::Samme, I think the Proposed Categories are excellent. My commit was more about not reinventing the wheel. Pluto has put together a pretty thorough set of documentation and most of needs to be documented is already documented. The biggest problem I can foresee is re-organization and clean up/updating the content on these pages. Another problem I see is we need someone who can confirm that the programming information is still indeed correct. Take for instance the very difficult task of building from source. There is no good page for this. I am not a coder. I am someone who has been using this software for almost 18 months when it was pluto. There have been alot of changes since the migration from pluto, so we need to make sure that we are able to get the ''correct'' information out on the wiki.--[[User:Rwilson131|Rwilson131]] 17:10, 26 September 2007 (MST)<br />
<br />
== Request for comment ==<br />
<br />
I'm having a discussion with Zaerc about how categories should be organized. Please could you take a look at his talk page at [[User talk:Zaerc]] and comment? [[User:Lozzo|Lozzo]] 07:00, 7 October 2007 (MST)<br />
:The idea that Zaerc is pressing on with will result in a hardware category with ''every piece of hardware'' listed in the hardware root category - creating a mess with dozens of unidentifiable pieces of hardware lumped together. How is it helpful to have [[RCA HC60RX]] and [[Caddx NX-8E]] in the same category? It isn't even obvious WHAT they are!! In fact, one is an alarm panel and the other is a piece of automation equipment. But you certainly wouldn't know this from looking at the root hardware category!!<br />
<br />
:This is complete madness and the antithesis of what the designers of MediaWiki intended the category function to be used for. I have pointed this out on several occasions only to receive a response such as (to paraphrase) "well this isn't wikipedia - we do things differently here". Why on earth can't they create a list?! [[User:Lozzo|Lozzo]] 18:23, 8 October 2007 (MST)<br />
<br />
== New Users ==<br />
<br />
Can you honestly expect someone who has NO experience in Home Automation, or Media Center PCs to actually be able to look at the system without being confused by a mixture of both introductory and architectural technical texts? --[[User:Tschak909|Tschak909]] 17:45, 12 October 2007 (MST)<br />
<br />
== moving all development-related information ==<br />
<br />
[[user:danielk|danielk]] and [[user:chriss| I]] are working on setting up a public SVN along with a Trac environment. What do you think about moving all the development related sites into the Trac-wiki? I.e. this wiki would be a "user wiki" while the Trac-wiki becomes a "developer wiki" --[[User:Chriss|chriss]] 01:11, 13 October 2007 (MST)</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Contacts&diff=6589Contacts2007-10-09T20:46:04Z<p>Chriss: </p>
<hr />
<div>LinuxMCE is a hot new open source project. It's stable, practical and usable, and really cool. Just check out the [[Screenshots|Screen Shots]] to see for yourself. [[I]]'m looking for developers and maintainers to '''[[Contribute|join the team]]'''. New LinuxMCE team members, please add your name, contact info, and a brief bio or description of what you're working on. Thanks!<br />
<br />
----<br />
'''Paul Webber''' -- contact: webpaul1 -at- gmail (.com)<br><br />
Responsibilities: Installer, Ubuntu packaging, build system, linuxmce.com site<br><br />
I launched LinuxMCE on March 15, 2007. [[History|'''History of LinuxMCE, why I started this project, and the goals''']]<br />
----<br />
'''Justin Burdine''' -- contact: justin -at- cyburdinehosting (.com)<br><br />
Offering: Hosting/Bandwidth, Graphic Design (see [[http://cbvfx.com cbvfx.com]]), Video Editing/Promotion (see [[http://cbvfx.com cbvfx.com]]), install/testing<br><br />
----<br />
'''John Botte''' -- contact: qualityinterfaces -at- gmail (.com)<br><br />
Offering: Forum moderation help. Conceptual ideas, help with firewire support, UI help and testing<br><br />
----<br />
'''Jonathan Iannone''' -- Contact: thorn168 -at- yahoo (.com)<br><br />
Offering: Help with documentation<br />
----<br />
'''Michael Stepanov''' -- Contact: stepanov.michael -at- gmail (.com)<br><br />
Offering: Build and test SDL Orbiter for Linux-based PC and Nokia770/N800.<br />
----<br />
'''Paul D''' aka Trout -- Contact: linuxmce.gqn@gishpuppy.com<br><br />
Offering: Help with documentation, Wiki participation, Testing and feedback.<br />
----<br />
'''Pete Kalogiannis''' -- Contact: pkalogiannis -at- gmail (dot) com<br><br />
Offering: [[Insteon]] Integration<br />
----<br />
'''Nat''' -- Contact Paul Webber to relay messages to Nat<br />
Offering: Nat has some access to some free or low-cost hardware, like TV Tuners, Video Cards, etc., which he can make available for developers actively working on a project.<br />
----<br />
'''Pierre Hansson''' aka Samme -- Contact: 316097 at gmail dot com<br><br />
Offering: Wiki-admin<br />
----<br />
'''Lozzo''' -- Contact via [[User talk:Lozzo|his talk page]]<br/><br />
Offering: wiki admin & documentation<br />
----<br />
'''Chriss''' <br/><br />
Offering: SVN hosting (see [http://forum.linuxmce.org/index.php?topic=2277.msg13677#msg13677 forum])<br />
<br />
[[Category:Development]]<br />
[[Category:Wiki administration]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Talk:Innovatek_TM-868&diff=5479Talk:Innovatek TM-8682007-09-17T08:57:43Z<p>Chriss: </p>
<hr />
<div>I am interested in getting something like this working as part of a dual display option.<br />
ie: Obiter displays on the touchscreen but all Media is on the TV/Monitor<br />
Anyone tried anything like that? [[User:DarrenMason|DarrenMason]]<br />
<br />
This means you need two X-screens, one running an orbiter and the other one running a media director (with on-screen orbiter). I'm planning to try something similar as well, i.e. I wanna run two MDs plus one orbiter on the same machine. This should be possible somehow, I remember that someone wrote something in the forums.<br />
<br />
How about using a mobile orbiter/web pad/Nokia 770/N800? [[User:Chriss|chriss]] 01:55, 17 September 2007 (MST)</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Talk:Innovatek_TM-868&diff=5478Talk:Innovatek TM-8682007-09-17T08:57:15Z<p>Chriss: </p>
<hr />
<div>I am interested in getting something like this working as part of a dual display option.<br />
ie: Obiter displays on the touchscreen but all Media is on the TV/Monitor<br />
Anyone tried anything like that? [[User:DarrenMason|DarronMason]]<br />
<br />
This means you need two X-screens, one running an orbiter and the other one running a media director (with on-screen orbiter). I'm planning to try something similar as well, i.e. I wanna run two MDs plus one orbiter on the same machine. This should be possible somehow, I remember that someone wrote something in the forums.<br />
<br />
How about using a mobile orbiter/web pad/Nokia 770/N800? [[User:Chriss|chriss]] 01:55, 17 September 2007 (MST)</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Talk:Innovatek_TM-868&diff=5477Talk:Innovatek TM-8682007-09-17T08:55:23Z<p>Chriss: </p>
<hr />
<div>I am interested in getting something like this working as part of a dual display option.<br />
ie: Obiter displays on the touchscreen but all Media is on the TV/Monitor<br />
Anyone tried anything like that?<br />
<br />
This means you need two X-screens, one running an orbiter and the other one running a media director (with on-screen orbiter). I'm planning to try something similar as well, i.e. I wanna run two MDs plus one orbiter on the same machine. This should be possible somehow, I remember that someone wrote something in the forums.<br />
<br />
How about using a mobile orbiter/web pad/Nokia 770/N800? [[User:Chriss|chriss]] 01:55, 17 September 2007 (MST)</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Innovatek_TM-868&diff=5464Innovatek TM-8682007-09-16T12:54:50Z<p>Chriss: </p>
<hr />
<div>== Hardware description ==<br />
<br />
THis is an 8" touchscreen with a resolution of 640x480. It has a VGA, a RCA video, two RCA audio and a USB connector. It works with the eGalax drivers<br />
<br />
== Installation ==<br />
<br />
The installation was pretty easy, since Ubuntu seems to support touchscreens out of the box. However, because the axis were swapped and I had to calibrate that thing I had to manually configure it.<br />
<br />
First, download the driver files from http://www.nextabyte.com/support/touchscreen/evtouch-current.tar.gz, after extracting them copy the driver file "evtouch_drv.so" to the input driver directory of xorg (/usr/lib/xorg/modules/input) and than switch to KDE desktop and from xterm run the program "calibrator" from the driver package. After touching the four points on the screen it will output the coordinates you have to add to your xorg.conf. In my case I had to swap the Y-values. This is, what I added to my xorg.conf:<br />
<br />
Section "InputDevice"<br />
Identifier "TouchScreen0"<br />
Driver "evtouch"<br />
Option "Device" "/dev/input/touchscreen"<br />
Option "MinX" "1925"<br />
Option "MinY" "41"<br />
Option "MaxX" "97"<br />
Option "MaxY" "1721"<br />
Option "ReportingMode" "Raw"<br />
Option "SendCoreEvents"<br />
EndSection<br />
<br />
and to make the beast work as an input device I added the line about the touchscreen here:<br />
<br />
Section "ServerLayout"<br />
Identifier "XFree86 Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
# add the following line<br />
InputDevice "TouchScreen0" "CoreTouch"<br />
EndSection<br />
<br />
after reloading the X-server it works like charm...<br />
<br />
A word on configuring the output: I ran the AV-Wizard selected VGA, 640x480, 60 Hz and it works fine :)<br />
<br />
[[Category:Hardware]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Innovatek_TM-868&diff=5463Innovatek TM-8682007-09-16T12:52:39Z<p>Chriss: </p>
<hr />
<div>== Hardware description ==<br />
<br />
THis is an 8" touchscreen with a resolution of 640x480. It has a VGA, a RCA video, two RCA audio and a USB connector. It works with the eGalax drivers<br />
<br />
== Installation ==<br />
<br />
The installation was pretty easy, since Ubuntu seems to support touchscreens out of the box. However, because the axis were swapped and I had to calibrate that thing I had to manually configure it.<br />
<br />
First, download the driver files from http://www.nextabyte.com/support/touchscreen/evtouch-current.tar.gz, after extracting them copy the driver file "evtouch_drv.so" to the input driver directory of xorg (/usr/lib/xorg/modules/input) and than switch to KDE desktop and from xterm run the program "calibrator" from the driver package. After touching the four points on the screen it will output the coordinates you have to add to your xorg.conf. In my case I had to swap the Y-values. This is, what I added to my xorg.conf:<br />
<br />
Section "InputDevice"<br />
Identifier "TouchScreen0"<br />
Driver "evtouch"<br />
Option "Device" "/dev/input/touchscreen"<br />
Option "MinX" "1925"<br />
Option "MinY" "41"<br />
Option "MaxX" "97"<br />
Option "MaxY" "1721"<br />
Option "ReportingMode" "Raw"<br />
Option "SendCoreEvents"<br />
EndSection<br />
<br />
and to make the beast work as an input device I added the line about the touchscreen here:<br />
<br />
Section "ServerLayout"<br />
Identifier "XFree86 Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
# add the following line<br />
InputDevice "TouchScreen0" "CoreTouch"<br />
EndSection<br />
<br />
after reloading the X-server it works like charm...<br />
<br />
[[Category:Hardware]]</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Innovatek_TM-868&diff=5462Innovatek TM-8682007-09-16T12:51:20Z<p>Chriss: </p>
<hr />
<div>== Hardware description ==<br />
<br />
THis is an 8" touchscreen with a resolution of 640x480. It has a VGA, a RCA video, two RCA audio and a USB connector. It works with the eGalax drivers<br />
<br />
== Installation ==<br />
<br />
The installation was pretty easy, since Ubuntu seems to support touchscreens out of the box. However, because the axis were swapped and I had to calibrate that thing I had to manually configure it.<br />
<br />
First, download the driver files from http://www.nextabyte.com/support/touchscreen/evtouch-current.tar.gz, after extracting them copy the driver file "evtouch_drv.so" to the input driver directory of xorg (/usr/lib/xorg/modules/input) and than switch to KDE desktop and from xterm run the program "calibrator" from the driver package. After touching the four points on the screen it will output the coordinates you have to add to your xorg.conf. In my case I had to swap the Y-values. This is, what I added to my xorg.conf:<br />
<br />
Section "InputDevice"<br />
Identifier "TouchScreen0"<br />
Driver "evtouch"<br />
Option "Device" "/dev/input/touchscreen"<br />
Option "MinX" "1925"<br />
Option "MinY" "41"<br />
Option "MaxX" "97"<br />
Option "MaxY" "1721"<br />
Option "ReportingMode" "Raw"<br />
Option "SendCoreEvents"<br />
EndSection<br />
<br />
and to make the beast work as an input device I added the line about the touchscreen here:<br />
<br />
Section "ServerLayout"<br />
Identifier "XFree86 Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
# add the following line<br />
InputDevice "TouchScreen0" "CoreTouch"<br />
EndSection<br />
<br />
after reloading the X-server it works like charm...</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Talk:Version_1_1&diff=3943Talk:Version 1 12007-05-21T14:54:18Z<p>Chriss: /* 64-bit? */</p>
<hr />
<div>I changed the "alt torrent" link so that it still uses TPB (even though TPB is down at the moment). More peers!<br />
- daath</div>Chrisshttp://wiki.linuxmce.org/index.php?title=Talk:Version_1_1&diff=3942Talk:Version 1 12007-05-21T14:05:04Z<p>Chriss: 64-bit?</p>
<hr />
<div>I changed the "alt torrent" link so that it still uses TPB (even though TPB is down at the moment). More peers!<br />
- daath<br />
<br />
== 64-bit? ==<br />
<br />
Is it possible to install v1.1. on a 64-bit linux system?</div>Chriss