http://wiki.linuxmce.org/api.php?action=feedcontributions&user=ChuckMcB&feedformat=atomLinuxMCE - User contributions [en]2024-03-28T19:22:33ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=LinuxMCE:General_disclaimer&diff=9552LinuxMCE:General disclaimer2008-03-06T22:19:32Z<p>ChuckMcB: Undo revision 9528 by AlletOelac (Talk)spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:About&diff=9551LinuxMCE:About2008-03-06T22:19:18Z<p>ChuckMcB: Undo revision 9527 by ElborAccab (Talk)spam</p>
<hr />
<div>This Wiki will help you get what you need to use, program or participate in LinuxMCE.<br />
<br />
Please give some of your knowledge back by adding to this Wiki.</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Category:Input&diff=9550Category:Input2008-03-06T22:19:07Z<p>ChuckMcB: Undo revision 9530 by RolacTroct (Talk)spam</p>
<hr />
<div>[[Category: Hardware]]</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Current_events&diff=9549Current events2008-03-06T22:18:32Z<p>ChuckMcB: Undo revision 9533 by EltcaOrric (Talk)spam</p>
<hr />
<div>Visit the [http://forum.linuxmce.org/index.php?board=350.0 Upcoming features forum] to discuss new features, changes or ideas. If you are willing to offer some cash or other compensation to a developer to get something done right away, visit the [http://forum.linuxmce.org/index.php?board=349.0 Help Wanted forum].<br />
<br />
When a developer has decided to implement some new feature or change, please edit this wiki to add a brief summary including a link to the original forum topic for this new idea, so other users can post to that topic to discuss this, and where you will post updated progress info. Visit the [http://wiki.linuxmce.org/index.php/Contacts Contacts Page] to find developers who can commit your work to the main LinuxMCE branch, or to request svn write access.<br />
<br />
This page lists the features which developers we are working to implement in the next release. There is also a forum dedicated to discussing features here . Please post to this page only those features which have been decided to be included.<br />
<br />
Read about the long-term goals and strategy here: [[History|History of LinuxMCE, why I started this project, and the goals]]<br />
<br />
<br />
----<br />
== Google Summer of Code Ideas: ==<br />
<br />
'''internet radio''' <br />
Integrate internet radio into the existing media menu option so radio stations can be browsed the same way local media can.<br />
<br />
'''internet tv / videos.google / youtube'''<br />
Integrate these online video sources into the existing media menu option so this video can be browsed the same way local media can.<br />
<br />
'''gsd events'''<br />
The embedded Ruby interpretor presently only handles controlling devices; ie processing commands. The same code could be adapted in reverse to respond to events.<br />
<br />
'''Standardized to be included in Ubuntu'''<br />
LinuxMCE still has a lot of non-standard scripts that Pluto wrote for use in commercial, black-box systems, which need to be rewritten in a more standard manner so that LinuxMCE plays nicely by Ubuntu's rules and be accepted into Ubuntu's main repository and included in their build.<br />
<br />
'''Download audio podcast/video podcast'''<br />
A way with the GUI to subscribe to podcasts, and have them automatically downloaded and aggregated with the media in the home. Including playcount so a list of not listened to podcasts can be created.<br />
<br />
Would it be possible to harness Miro/DemocracyTV for this functionality? I've succeeded personally in getting the Miro client to download videos into the LinuxMCE directory structure, but the filenames are non-intuitive and not all of them show up correctly (needs more testing). - dragon_788<br />
<br />
'''Capture video from firewire camera'''<br />
The current plug and play detection engine already recognizes firewire digital camcorders. There should be a very rudimentary, simple 'capture' option that appears on screen to do basic video capture and save it to the managed media. Users can use a video editor like Kino for real editing; this is just for quick capture.<br />
<br />
'''Better organize and manage photos'''<br />
The current UI could use some optimization to make it work better for managing photos.<br />
<br />
== Current Development ==<br />
[[What modules are in development?]]</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Privacy_policy&diff=9548LinuxMCE:Privacy policy2008-03-06T22:18:17Z<p>ChuckMcB: Undo revision 9537 by NoricC4tou (Talk)spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Site_support&diff=9547LinuxMCE:Site support2008-03-06T22:18:02Z<p>ChuckMcB: Undo revision 9539 by MonvaRtaac (Talk)spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Template:Cleanup&diff=9454Template:Cleanup2008-03-03T23:42:07Z<p>ChuckMcB: Undo revision 9439 by DelliLicli (Talk)</p>
<hr />
<div>'''This article needs a cleanup'''</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Known_Issues&diff=9453Known Issues2008-03-03T23:41:47Z<p>ChuckMcB: Undo revision 9438 by DelliSitca (Talk)</p>
<hr />
<div>== Known issues with LinuxMCE 0710 ==<br />
Check this page [[KnownIssues_0710]]<br />
<br />
<br />
== Known issues with LinuxMCE 0704 ==<br />
<br />
Be sure to read [[Video#network]] because if you don't enable your network connection you won't have gallery art or be able to add extra software.<br />
<br />
The QuickInstall DVD is not correctly handling an installation with a single network interface card. If you have only 1 network interface card, then as explained in [[Video#network]] when you go to test your network, go into the Admin site. Choose Advanced, Configuration, Devices. Click the 'Core' in the left device tree. Scroll down to 'Network Settings', and carefully edit that line changing the text that says "eth1" to instead say "eth0:0". Then save the changes on that page. Now go to Advanced, Network, Network Settings. If you're using a static IP specify it now. Whether or not you made any changes, click the update button which will cause it to reset your network. Confirm you now have an internet connection. The network settings should show that eth0 is your normal network (dhcp or static), and eth1 is 192.168.80.1. If you don't want LinuxMCE to be your DHCP server, you can disable that option here.<br />
<br />
LMCE 0704 will not use windows shares with spaces in them, e.g. "DISK 1".<br />
<br />
== Known issues with LinuxMCE 1.1 Beta ==<br />
<br />
* if you get the following error:<br />
<br />
pluto-dcerouter: Depends: pluto-confirm-dependencies (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-confirm-dependencies (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-createdevice (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-createdevice (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-install-scripts (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-install-scripts (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-local-database (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-local-database (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-std-plugins (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-std-plugins (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-system-database (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-system-database (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-website-admin (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-website-admin (< 2.0.0.45) but it is not going to be installed<br />
Depends: pluto-boot-scripts (>= 2.0.0.44) but it is not going to be installed<br />
Depends: pluto-boot-scripts (< 2.0.0.45) but it is not going to be installed<br />
PreDepends: samba but it is not going to be installed<br />
E: Broken packages<br />
<br />
Solution: the quickest solution is to skip the use of the cache cd or to have latest samba package installed before starting the installation.<br />
<br />
* sometimes it's better to kill the network manager and add the network settings manually. I found that the network settings are overwritten when the installation of Linux MCE is finished. and you don't have internet connection anymore. This may lead to problems like the one above, with the samba package.<br />
<br />
<br />
* if you are rebooting the system after installing LinuxMCE 1.1 and the system hangs up at "'''Running local boot scripts (/etc/rc.local) [ OK]'''"<br />
<br />
Solution: rename kdm.saved from /etc/init.d to kdm and then reboot.<br />
<br />
== Known issues with LinuxMCE 1.0 ==<br />
<br />
It is best to install version 1.0 on a separate box, rather than your main Ubuntu system because of the following issues:<br />
<br />
* The installer is messing up Ubuntu's xorg.conf file by removing the nvidia driver and replacing it with vesa. This was actually a necessary hack that got forgotten about. There is a bug in the nVidia drivers (it has been reported) that causes them to crash when two X sessions are running and try to open the same card. Using the 'nv' driver on one and the 'nvidia' on the other still doesn't work, but using vesa on one and nvidia on the other does. So the hack changes Ubuntu's xorg.conf from nVidia to Vesa. If you install a dedicated LinuxMCE box this isn't an issue, but it can be a problem when you are a Ubuntu user and want better performance on your Ubuntu desktop than the vesa driver allows.<br />
<br />
* The installer will revert the Ubuntu sources.list back to the default, removing any non-standard repositories, when it does the upgrade before installing itself.<br />
<br />
* As mentioned in other places, the scripts carried from Pluto were written to be run on a dedicated system and 'take over' completely. It was a huge task just getting LinuxMCE 1.0 out the door, and the Ubuntu integration is still a work in progress and the scripts are still too invasive. If this is a dedicated system, or if you're not a Linux user, this is perhaps still a good thing because you'll never need to touch your configuration files: LinuxMCE will setup the dhcp server, samba network shares, network settings, and so on. But, if you are a Ubuntu user, be warned that it will override some of your settings until we get the Ubuntu integration improved.<br />
<br />
Additional issues:<br />
<br />
* Most of the problems reported so far are caused by using UI2, which requires OpenGL, on video cards without good Linux OpenGL support. The solution is to use UI1 instead. nVidia 6xxx and higher are preferred and will run UI2 with the 3d effects and alpha blending.<br />
<br />
* A bug in the media browser was identified that is causing it to run very slow and consume a lot of memory. A 1.01 patch will be out soon.<br />
<br />
* In the haste to release the updated LinuxMCE 1.0 that didn't use the website for downloading the software after the Digg story brought the server down, there was a sloppy error building the package for the Windows binaries. Most of them are empty. This means the Windows orbiter that runs on web pads, pda's and ms smart phones, as well as some other windows applets which are also on the download page in your Core's admin web site, are missing.<br />
<br />
* Some of the users reported having broken packages during the installation of LinuxMCE, usually 'pluto-orbiter' package. This could happen from a number of reasons. We have identified a few of them, such as: <br />
- the vim package cannot be installed because of a conflict at 'vim-common'. For details on how to fix that, please follow: [http://wiki.linuxmce.com/index.php/Installer_Problems]<br />
- The Ubuntu repositories are sometimes unavailable. You should try reinstalling, or installing the packages by hand</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Privacy_policy&diff=9452LinuxMCE:Privacy policy2008-03-03T23:41:31Z<p>ChuckMcB: Undo revision 9440 by LetodArchi (Talk)</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Community_Portal&diff=9451LinuxMCE:Community Portal2008-03-03T23:41:25Z<p>ChuckMcB: Undo revision 9441 by RolraCchia (Talk)</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 />
I have added a new section for coding Media Components. In addition, I have also added a new template stub called <nowiki>{{Needs Programmer Review}}</nowiki> which automatically categorizes the article. This is intended for programming primers and information that needs to be verified and refined by other programmers. --[[User:Tschak909|Tschak909]] 10:39, 3 February 2008 (PST)<br />
<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 />
*''12/12-07''' - Dan Damron knows a little about templates.. Offer to help with this section. dan at damron period ca<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 />
#<strike>Fix hardware pages</strike><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 categories)<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>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:General_disclaimer&diff=9450LinuxMCE:General disclaimer2008-03-03T23:41:15Z<p>ChuckMcB: Removing all content from page</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Control_a_TV_or_cable/satellite_box&diff=9449Control a TV or cable/satellite box2008-03-03T23:41:08Z<p>ChuckMcB: Undo revision 9444 by LetorOmona (Talk)</p>
<hr />
<div>[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
[[Category: Programmer's Guide]]<br />
<br />
==How to set it up==<br />
<br />
In the [[LinuxMCE Admin Website]], go to '''Wizard > Devices > A/V equipment'''. If you haven't already added the TV and whatever cable/satellite box you use for the tuning, click 'Add Device'. Choose the manufacturer, category, and then model of the device. Then click 'Add Device'.<br />
<br />
If your model is not in the list, then after choosing the manufacturer and category, type the model name in the box under the models column and click 'Add' to create your own Device Template, which means a definition of a device that explains the properties of this model. Be sure popups are not blocked--a popup window will appear asking how many tuners this TV has (see next paragraph for an explanation). After you add the Device Template for this model, then select it from the model list and click 'Add Device' to add it to your installation. Since this is a new Device Template, on the A/V equipment page be sure to click the 'A/V Properties' button for this device to tell LinuxMCE about this Device Template, such as what inputs it has, whether you will control it with infrared, and so on.<br />
<br />
'''Note:''' You will see that a TV is actually treated as multiple devices: the display device, and also a separate device for the tuner(s) inside the TV. This may seem confusing, but it's necessary. Many TV's have multiple tuners, and different tuners may have different video sources; one may be hooked up to cable, and another one to an antenna. And those tuners use different inputs on the TV. Therefore, LinuxMCE treats the tuners as "embedded devices" within the TV. When you want to watch TV, you will actually be telling LinuxMCE you want to use a tuner within the TV. For example, you will say you want to use Tuner #1 (cable), or Tuner #2 (antenna), etc. Therefore when you add a new Device Template for a TV, LinuxMCE Admin will ask how many tuners it has. Receivers are treated the same way since they can also have multiple tuners inside, like FM, AM, Weather Band, Satellite, etc.<br />
<br />
On the A/V equipment page you also need to specify the A/V Connections, also known as "Pipes". You can do it using the "Edit" link in the "Pipes" column, or do it graphically by drawing lines between your devices by clicking the "Connection Wizard" link. If you added a cable or satellite box, the video pipe from the box will be the TV that it's connected to, and you choose the input on the TV you used, such as "Video 2". If you want the sound to come out of the TV too, the audio pipe will also go to the TV on the same input. If you want the sound to come out of your receiver, then the audio pipe goes to the receiver. If you're not using an external satellite/cable box, but rather the TV's internal tuner, you'll see that the internal tuner already has an audio/video pipe to the TV. If you don't want the sound to come out of the TV's internal speakers but rather use a stereo receiver, then change the audio pipe for the tuner to go to the receiver instead.<br />
<br />
The "Controlled Via" pull-down should be set to whatever device is going to be responsible for controlling this piece of equipment. If this is controlled via infrared the "Controlled Via" device is the infrared device you are using to control it (added on the '''Wizard > Devices > [[Interfaces]]''' page). If this a/v equipment is controllable by RS232 or USB, the Controlled Via should be the PC computer it is connected to. If it is controlled via Ethernet, it can be any computer on which you want to run the device driver, usually it's the Core.<br />
<br />
If you have multiple TV sources in your home, such as Cable and Satellite, you may want to click the "Media Providers" link to specify the providers. This step isn't necessary. However if you do add Media Providers, then for each piece of a/v equipment that is a source device you can specify what Media Provider it uses (this box provides "Cable TV" and this "Satellite TV"). The advantage of doing this is that then follow-me media, move media and broadcast are more accurate. If LinuxMCE is able to know that you were watching channel 35 on a device that uses Media Provider "satellite tv", then when the user wants to move or broadcast this media to other rooms, LinuxMCE knows to find devices in those rooms that also use provider "satellite tv". Otherwise LinuxMCE may end up picking a cable tv device instead. If you only have one provider for tv then there is no reason to worry about specifying a provider.<br />
<br />
Next go to the '''Wizard > Scenarios > [[Media Scenarios]]''' page. Every media scenario will appear as a button on the Orbiters, so we need to add a media scenario in the room (aka Entertainment Area) where you want to use this TV. Under 'Add Scenario' type the description you want on the button, such as "Live TV", "Cable, etc". Choose the Entertainment Area, or room, then choose the source device. This should be the tuner in the TV, or a satellite or cable box. Also choose the type of media, "Live TV" in this case. If there is more than one remote control interface that will wok with this device you'll have a pull-down for that too. The next time you regen the UI for this Orbiter (see '''Wizard > Devices > [[Orbiters]]'''), the button will appear.<br />
<br />
After you add new devices, you need to go to '''Wizard > [[Restart]]''' and click "Quick Reload Router" so DCERouter starts using the new devices you just added.<br />
<br />
==How to use it==<br />
<br />
Just touch the button you created with the Media Scenarios above. It will appear on all the Orbiters for the room (Entertainment Area) you added it to. LinuxMCE will automatically turn on all the appropriate devices and set their inputs based on the A/V connections you specified in LinuxMCE Admin.<br />
<br />
If the A/V equipment is controlled in some way that LinuxMCE can get feedback from it, such as RS232 or Ethernet, then you can also physically turn on or adjust any relevant device and LinuxMCE will figure out automatically what you want to do. For example, if you turn on the satellite box by hand, LinuxMCE knows you want to use it and will automatically turn on the tv and receiver, set the inputs, and put the remote control on the orbiters for you. Or, if you switch the input on the receiver to "DBS", which your satellite box is connected, LinuxMCE also knows that means you want to watch Satellite TV and will set everything up for you. However this functionality is not possible with a/v equipment that is controlled via infrared since i/r is 1-way communication; LinuxMCE can only send it commands, but has no way to know when you are controlling it manually.<br />
<br />
==Programmer's guide==<br />
<br />
The Media Scenario will send a "MH Play Media" command to the media plugin. The media plugin will then find a media handler plugin that knows how to handle that type of media. Tightly integrated media devices, like Xine or Myth, have their own media handler plugins that are intelligent and know how to do things like synchronize multiple rooms to the same media, move media between rooms and respect stopping/starting at the same place and so on. Generic A/V devices like TV's and satellite boxes are nearly always by the media handler "Generic NonLinuxMCE Media", which is built into the media plugin itself. This media handler is very simple--it just forwards the command to the device.<br />
<br />
When a device gets an "ON" command, DCERouter router calls the function "HandleCommandPipes". This is what knows how to turn on all the devices and set their inputs based on the a/v pipes you specified on the a/v equipment page. This is also why the tuners need to be treated as separate embedded devices within the TV, since each one will use different inputs.<br />
<br />
The table MediaType_DesignObj has the standard remote controls for each type of Media, and the table DeviceTemplate_MediaType_DesignObj has custom remote controls more appropriate for a given device. When adding the media scenario if there is more than 1 remote control that can be used to control this type of media on this device, the user can choose from the list.<br />
<br />
The message translation class is used within the infrared devices (like gc100), and within [[GSD]] (generic serial device) to translate commands and handle things like toggle vs discrete inputs. Devices which are controlled using GSD and a serial/ethernet interface will fire events AV_Input_Changed and Device_OnOff which Media_Plugin has interceptors for and will use the a/v pipes to figure out what device you're trying to use.</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=User_talk:217.72.199.106&diff=9379User talk:217.72.199.1062008-03-02T22:47:57Z<p>ChuckMcB: Undo revision 9375 by LigetElolo (Talk)spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Privacy_policy&diff=9378LinuxMCE:Privacy policy2008-03-02T22:47:39Z<p>ChuckMcB: Undo revision 9373 by LetodArchi (Talk)spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Talk:Control_regular_A/V_equipment&diff=9377Talk:Control regular A/V equipment2008-03-02T22:47:18Z<p>ChuckMcB: Undo revision 9371 by DelbaSalch (Talk)Spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=GlobalCache_GC-100&diff=9376GlobalCache GC-1002008-03-02T22:46:38Z<p>ChuckMcB: Undo revision 9367 by BasolOrico (Talk)Spam</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Hardware]]<br />
[[Category: Automation]]<br />
[[Category: Infrared]]<br />
<br />
[[Image:GC100.jpg|right]]<br />
<br />
GC100 is a device which allows you to have remote connection almost anywhere. It's a network device which will forward all your data to :<br />
* couple of serial ports<br />
* [[IR]] senders and/or sensors<br />
* several relays<br />
For more details about the product check [http://www.globalcache.com/products/gc-index.html manufacturer web site].<br />
<br />
== Send IR codes ==<br />
LinuxMCE implementation of GC100 assumes that in device tree we'll have children and the messages are actually addressed to them instead of GC100 itself. <br />
<br />
So when you are sending "ON" to TV controlled by GC100, the message is routed to the GC100, it finds [[infrared]] code for "ON" for that specific TV, sends a command to gc100 to send a specific [[infrared]] sequence, which will blink IR sender connected to specific port, and the TV will turn on.<br />
<br />
The only two commands that GC100 implements itself are : '''CMD_Send_Code''' used to test which IR is suitable for your equipment and '''CMD_Learn_IR''' used to learn new IR codes.<br />
<br />
== Learn IR codes ==<br />
The learning device is actually unrelated to GC100. It may be plugged into one of GC100's serial ports (don't forget to set them to 9600 bps), or in regular serial port, just be sure you specified right port in GC100 device data.<br />
<br />
There are several other devices that support learning of infrared codes : [[IRTrans]], [[Tira]], [[USB_UIRT]].<br />
<br />
Learning is done from [[LinuxMCE-admin|web page]]. When clicking "Learn" gc100 will start a thread that will try to get data from the port. If nothing is received in 30 seconds the thread will die. The page will continue to refresh trying to see if anything was added, but after 30 seconds it's useless.<br />
<br />
== Sensors ==<br />
The gc100 jacks are by default configured as IR transmitters, but they can be configured to function as sensors. The sensors are, in their most basic form, two wires connected to a jack plug. When you cross them, a "sensor tripped" event is emitted. I am not currently aware of how this is supposed to function, who will intercept the event and how will it react to it. One idea for using a sensor is attaching a doorbell button to it, which, when pressed, will notify you in some way.<br />
<br />
You must go into the gc100's web panel and set the input jack to 'sensor w/ auto notify' to use an i/r jack for a sensor.<br />
<br />
== How to ==<br />
=== Install ===<br />
The device is not quite [[plug&play]]. You have to perform a factory reset and to add it from orbiter ("Add GC100" button).<br />
<br />
A script will do some tricks with IP, will submit some pages on GC100's interface and so on. It will install needed software and after that it should say that device is ready to use (don't forget to [[quickreload]])<br />
<br />
=== Before the first use ===<br />
* Insert proper wires in relays, devices in serial ports, [[IR]] LEDs and/or sensors.<br />
* Go to device's webpage and set proper inputs/outputs, baud rates and so on.<br />
* Add child devices in [[LinuxMCE-admin]] webpage and set proper device data to match the wiring.<br />
<br />
This should do it.<br />
<br />
=== Changes in LinuxMCE 0710 beta 4 ===<br />
The way the gc100 is configured in the database changes in LinuxMCE 0710 beta 4. If you are upgrading from a previous release and have a gc100 set up, you will have to reconfigure it.<br />
<br />
The device tree will now have children for each relay, transmitter and sensor port. These are autodetected depending on the settings made to the gc100 itself and updated as the settings change.<br />
<br />
If until now you would put a TV directly under the gc100, you will have to put it under a transmitter child from now on. This will tell the gc100 which port to use to send the code, instead of sending it using all available transmitters like it did until now. This will allow you to add more IR devices which use the same codes without stepping on each other's toes, since the IR codes will be routed just to the target device. The old functionality is still in place and you can still add a TV directly under the gc100, but make sure you mark the checkbox that says "Don't autoconfigure" if you don't want the gc100 to manage its children, so your device remains in its place.<br />
<br />
This is also true for relays. Add your lights, or other devices that support On and Off commands, under the relay children. The On and Off commands will be routed to the right relay this way.<br />
<br />
=== Known Problems ===<br />
<br />
==== MAC detection ====<br />
<br />
--[[User:Nite man|Nite man]] 06:03, 25 January 2008 (PST) To solve the MAC detection problem replace the function ''get_gc100mac()'' in the script ''/usr/pluto/bin/gc100-conf.pl'' by new one below:<br />
<br />
sub get_gc100mac {<br />
my($mac, $page, $ret);<br />
<br />
`curl http://192.168.1.70/Commands.cgi -o gc100mac1 --silent`;<br />
`curl http://192.168.1.101/Commands.cgi -o gc100mac2 --silent`;<br />
<br />
open FILE, "gc100mac1";<br />
$ret = read FILE, $page, -s "gc100mac1";<br />
close FILE;<br />
<br />
unless($page) {<br />
open FILE, "gc100mac2";<br />
$ret = read FILE, $page, -s "gc100mac2";<br />
close FILE;<br />
}<br />
<br />
($mac) = $page =~ /((?:[\dA-F]{2}-){5}[\dA-F]{2})/i;<br />
<br />
if($mac) {<br />
$mac =~ tr/\-/\:/;<br />
loggc("Mac Found $mac\n");<br />
system "rm -f gc100mac1 gc100mac2";<br />
return $mac;<br />
} else { exit 1 }<br />
<br />
}<br />
<br />
or apply that [[http://smart-home-blog.com/wp-content/plugins/wp-downloadMonitor/download.php?id=18 gc100-conf.pl.patch]]<br />
<br />
Currently the support for the gc100 in LinuxMCE is broken, at least for some models or firmware versions. The ''/usr/pluto/bin/gc100-conf.pl'' script is for some reason unable to determine the gc100's MAC Adress after it has been reset to factory defaults. As a result it is only half configured and not added to the system properly.<br />
<br />
The only known workaround [http://smart-home-blog.com/archives/688] [http://forum.linuxmce.org/index.php?topic=1990.msg9161#msg9161] at this time is to manually edit the perl script, and hardcode the MAC address of your gc100. In short, find this line in the script:<br />
sub get_gc100mac {<br />
Then insert this line immediately following it (replace ''00:00:00:00:00:00'' with the adress of your gc100):<br />
'''return "''00:00:00:00:00:00''";'''<br />
As a result it should look something like this now:<br />
exit(4);<br />
}<br />
} <br />
<br />
sub get_gc100mac {<br />
<br />
'''return "''00:00:00:00:00:00''"''';<br />
<br />
`curl <nowiki>http://192.168.1.70/Commands.cgi</nowiki> -o gc100mac1 --silent`;<br />
`curl <nowiki>http://192.168.1.101/Commands.cgi</nowiki> -o gc100mac2 --silent`;<br />
open(FILE,"gc100mac1");<br />
@data1 = <FILE>;<br />
close(FILE);<br />
<br />
Reset the gc100 to factory defaults if necessary and you should be able to add it from an orbiter as described above.<br />
<br />
Another possible workaround ''might'' be described on the [http://plutohome.com/wiki/index.php/Gc100 Plutohome wiki for the gc100], under '''Complete Manual Install'''.<br />
<br />
Firmware versions known to be affected:<br />
* 2.4-06 (GC100-06)<br />
<br />
==== Serial Port ====<br />
<br />
The GC100's serial port does not work under LinuxMCE without a small modification, see: [http://forum.linuxmce.org/index.php?topic=2161.msg10140#msg10140 Re: GC100 + CM11 setup]<br />
<br />
The following commands should correct this issue (and make a backup copy just in case):<br />
mv /usr/pluto/bin/gc100-serial-bridge.sh /usr/pluto/bin/gc100-serial-bridge.sh.backup<br />
sed -e 's/false/0/g' /usr/pluto/bin/gc100-serial-bridge.sh.backup >/usr/pluto/bin/gc100-serial-bridge.sh<br />
<br />
It basicly replaces '''false''' with '''0''' in the ''/usr/pluto/bin/gc100-serial-bridge.sh'' file. Afterwards a reboot may be in order.<br />
<br />
==== Firmware version 3.0 and later ====<br />
<br />
gc100 with firmware version 3.0 and later is Plug&Play, but not yet supported as such by LinuxMCE. It implements a DHCP client and also has a discovery beacon. Because it is able to get an IP address from the DHCP server, you won't be able to add it using the manual method describe here when using a default installation. You either have to use the completely manual installation procedure described on the [http://plutohome.com/wiki/index.php/Gc100#Complete_Manual_Install Plutohome Wiki for gc100], if you know what IP address the DHCP server gave it, or temporarily disable the DHCP server on the core (write down the DHCP settings, because they are erased from the database when you disable the DHCP server from Pluto-Admin - you can also /etc/init.d/dhcp3-server stop, add the gc100 and /etc/init.d/dhcp3-server start, without erasing the database).<br />
<br />
== Implementation details ==<br />
In ''gc100.cpp'' there is a lot of code for format conversion and other stuff. Practically it's not a big deal it receives a command, find a proper IR sequence and sends it to gc100.<br />
<br />
==== Operating the relays, IR transmitters, and sensors ====<br />
The gc100 software architecture uses two threads to communicate with the gc100 regarding relays, IR transmitters and sensors, one for sending messages (SocketThread) and one for receiving (EventThread). The reason for this is that the gc100 protocol isn't completely a request-reply protocol, even if it seems like that at first. The gc100 can initiate a transmission when a sensor is tripped, enough to break the request-reply paradigm. The program was designed to treat the communication as asynchronous. Messages are sent to the device without expecting a reply, and the replies are treated as independent events and state change reports, without linking a request to a reply in the program logic (except for the initialization phase).</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Template:Cleanup&diff=9332Template:Cleanup2008-03-01T22:28:27Z<p>ChuckMcB: Undo revision 9317 by DelliLicli (Talk) Spam</p>
<hr />
<div>'''This article needs a cleanup'''</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Help:Contents&diff=9295Help:Contents2008-02-29T19:35:53Z<p>ChuckMcB: Undo revision 9291 by OloreLtroc (Talk)</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Current_events&diff=9267Current events2008-02-28T20:04:42Z<p>ChuckMcB: Undo revision 9266 by EltcaOrric (Talk)Removed spam</p>
<hr />
<div>Visit the [http://forum.linuxmce.org/index.php?board=350.0 Upcoming features forum] to discuss new features, changes or ideas. If you are willing to offer some cash or other compensation to a developer to get something done right away, visit the [http://forum.linuxmce.org/index.php?board=349.0 Help Wanted forum].<br />
<br />
When a developer has decided to implement some new feature or change, please edit this wiki to add a brief summary including a link to the original forum topic for this new idea, so other users can post to that topic to discuss this, and where you will post updated progress info. Visit the [http://wiki.linuxmce.org/index.php/Contacts Contacts Page] to find developers who can commit your work to the main LinuxMCE branch, or to request svn write access.<br />
<br />
This page lists the features which developers we are working to implement in the next release. There is also a forum dedicated to discussing features here . Please post to this page only those features which have been decided to be included.<br />
<br />
Read about the long-term goals and strategy here: [[History|History of LinuxMCE, why I started this project, and the goals]]<br />
<br />
<br />
----<br />
== Google Summer of Code Ideas: ==<br />
<br />
'''internet radio''' <br />
Integrate internet radio into the existing media menu option so radio stations can be browsed the same way local media can.<br />
<br />
'''internet tv / videos.google / youtube'''<br />
Integrate these online video sources into the existing media menu option so this video can be browsed the same way local media can.<br />
<br />
'''gsd events'''<br />
The embedded Ruby interpretor presently only handles controlling devices; ie processing commands. The same code could be adapted in reverse to respond to events.<br />
<br />
'''Standardized to be included in Ubuntu'''<br />
LinuxMCE still has a lot of non-standard scripts that Pluto wrote for use in commercial, black-box systems, which need to be rewritten in a more standard manner so that LinuxMCE plays nicely by Ubuntu's rules and be accepted into Ubuntu's main repository and included in their build.<br />
<br />
'''Download audio podcast/video podcast'''<br />
A way with the GUI to subscribe to podcasts, and have them automatically downloaded and aggregated with the media in the home. Including playcount so a list of not listened to podcasts can be created.<br />
<br />
Would it be possible to harness Miro/DemocracyTV for this functionality? I've succeeded personally in getting the Miro client to download videos into the LinuxMCE directory structure, but the filenames are non-intuitive and not all of them show up correctly (needs more testing). - dragon_788<br />
<br />
'''Capture video from firewire camera'''<br />
The current plug and play detection engine already recognizes firewire digital camcorders. There should be a very rudimentary, simple 'capture' option that appears on screen to do basic video capture and save it to the managed media. Users can use a video editor like Kino for real editing; this is just for quick capture.<br />
<br />
'''Better organize and manage photos'''<br />
The current UI could use some optimization to make it work better for managing photos.<br />
<br />
== Current Development ==<br />
[[What modules are in development?]]</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Talk:Control_regular_A/V_equipment&diff=9260Talk:Control regular A/V equipment2008-02-28T09:43:01Z<p>ChuckMcB: Spam removal.</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Control_a_TV_or_cable/satellite_box&diff=9259Control a TV or cable/satellite box2008-02-28T09:42:10Z<p>ChuckMcB: Undo revision 9252 by LetorOmona (Talk) Spam removal</p>
<hr />
<div>[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
[[Category: Programmer's Guide]]<br />
<br />
==How to set it up==<br />
<br />
In the [[LinuxMCE Admin Website]], go to '''Wizard > Devices > A/V equipment'''. If you haven't already added the TV and whatever cable/satellite box you use for the tuning, click 'Add Device'. Choose the manufacturer, category, and then model of the device. Then click 'Add Device'.<br />
<br />
If your model is not in the list, then after choosing the manufacturer and category, type the model name in the box under the models column and click 'Add' to create your own Device Template, which means a definition of a device that explains the properties of this model. Be sure popups are not blocked--a popup window will appear asking how many tuners this TV has (see next paragraph for an explanation). After you add the Device Template for this model, then select it from the model list and click 'Add Device' to add it to your installation. Since this is a new Device Template, on the A/V equipment page be sure to click the 'A/V Properties' button for this device to tell LinuxMCE about this Device Template, such as what inputs it has, whether you will control it with infrared, and so on.<br />
<br />
'''Note:''' You will see that a TV is actually treated as multiple devices: the display device, and also a separate device for the tuner(s) inside the TV. This may seem confusing, but it's necessary. Many TV's have multiple tuners, and different tuners may have different video sources; one may be hooked up to cable, and another one to an antenna. And those tuners use different inputs on the TV. Therefore, LinuxMCE treats the tuners as "embedded devices" within the TV. When you want to watch TV, you will actually be telling LinuxMCE you want to use a tuner within the TV. For example, you will say you want to use Tuner #1 (cable), or Tuner #2 (antenna), etc. Therefore when you add a new Device Template for a TV, LinuxMCE Admin will ask how many tuners it has. Receivers are treated the same way since they can also have multiple tuners inside, like FM, AM, Weather Band, Satellite, etc.<br />
<br />
On the A/V equipment page you also need to specify the A/V Connections, also known as "Pipes". You can do it using the "Edit" link in the "Pipes" column, or do it graphically by drawing lines between your devices by clicking the "Connection Wizard" link. If you added a cable or satellite box, the video pipe from the box will be the TV that it's connected to, and you choose the input on the TV you used, such as "Video 2". If you want the sound to come out of the TV too, the audio pipe will also go to the TV on the same input. If you want the sound to come out of your receiver, then the audio pipe goes to the receiver. If you're not using an external satellite/cable box, but rather the TV's internal tuner, you'll see that the internal tuner already has an audio/video pipe to the TV. If you don't want the sound to come out of the TV's internal speakers but rather use a stereo receiver, then change the audio pipe for the tuner to go to the receiver instead.<br />
<br />
The "Controlled Via" pull-down should be set to whatever device is going to be responsible for controlling this piece of equipment. If this is controlled via infrared the "Controlled Via" device is the infrared device you are using to control it (added on the '''Wizard > Devices > [[Interfaces]]''' page). If this a/v equipment is controllable by RS232 or USB, the Controlled Via should be the PC computer it is connected to. If it is controlled via Ethernet, it can be any computer on which you want to run the device driver, usually it's the Core.<br />
<br />
If you have multiple TV sources in your home, such as Cable and Satellite, you may want to click the "Media Providers" link to specify the providers. This step isn't necessary. However if you do add Media Providers, then for each piece of a/v equipment that is a source device you can specify what Media Provider it uses (this box provides "Cable TV" and this "Satellite TV"). The advantage of doing this is that then follow-me media, move media and broadcast are more accurate. If LinuxMCE is able to know that you were watching channel 35 on a device that uses Media Provider "satellite tv", then when the user wants to move or broadcast this media to other rooms, LinuxMCE knows to find devices in those rooms that also use provider "satellite tv". Otherwise LinuxMCE may end up picking a cable tv device instead. If you only have one provider for tv then there is no reason to worry about specifying a provider.<br />
<br />
Next go to the '''Wizard > Scenarios > [[Media Scenarios]]''' page. Every media scenario will appear as a button on the Orbiters, so we need to add a media scenario in the room (aka Entertainment Area) where you want to use this TV. Under 'Add Scenario' type the description you want on the button, such as "Live TV", "Cable, etc". Choose the Entertainment Area, or room, then choose the source device. This should be the tuner in the TV, or a satellite or cable box. Also choose the type of media, "Live TV" in this case. If there is more than one remote control interface that will wok with this device you'll have a pull-down for that too. The next time you regen the UI for this Orbiter (see '''Wizard > Devices > [[Orbiters]]'''), the button will appear.<br />
<br />
After you add new devices, you need to go to '''Wizard > [[Restart]]''' and click "Quick Reload Router" so DCERouter starts using the new devices you just added.<br />
<br />
==How to use it==<br />
<br />
Just touch the button you created with the Media Scenarios above. It will appear on all the Orbiters for the room (Entertainment Area) you added it to. LinuxMCE will automatically turn on all the appropriate devices and set their inputs based on the A/V connections you specified in LinuxMCE Admin.<br />
<br />
If the A/V equipment is controlled in some way that LinuxMCE can get feedback from it, such as RS232 or Ethernet, then you can also physically turn on or adjust any relevant device and LinuxMCE will figure out automatically what you want to do. For example, if you turn on the satellite box by hand, LinuxMCE knows you want to use it and will automatically turn on the tv and receiver, set the inputs, and put the remote control on the orbiters for you. Or, if you switch the input on the receiver to "DBS", which your satellite box is connected, LinuxMCE also knows that means you want to watch Satellite TV and will set everything up for you. However this functionality is not possible with a/v equipment that is controlled via infrared since i/r is 1-way communication; LinuxMCE can only send it commands, but has no way to know when you are controlling it manually.<br />
<br />
==Programmer's guide==<br />
<br />
The Media Scenario will send a "MH Play Media" command to the media plugin. The media plugin will then find a media handler plugin that knows how to handle that type of media. Tightly integrated media devices, like Xine or Myth, have their own media handler plugins that are intelligent and know how to do things like synchronize multiple rooms to the same media, move media between rooms and respect stopping/starting at the same place and so on. Generic A/V devices like TV's and satellite boxes are nearly always by the media handler "Generic NonLinuxMCE Media", which is built into the media plugin itself. This media handler is very simple--it just forwards the command to the device.<br />
<br />
When a device gets an "ON" command, DCERouter router calls the function "HandleCommandPipes". This is what knows how to turn on all the devices and set their inputs based on the a/v pipes you specified on the a/v equipment page. This is also why the tuners need to be treated as separate embedded devices within the TV, since each one will use different inputs.<br />
<br />
The table MediaType_DesignObj has the standard remote controls for each type of Media, and the table DeviceTemplate_MediaType_DesignObj has custom remote controls more appropriate for a given device. When adding the media scenario if there is more than 1 remote control that can be used to control this type of media on this device, the user can choose from the list.<br />
<br />
The message translation class is used within the infrared devices (like gc100), and within [[GSD]] (generic serial device) to translate commands and handle things like toggle vs discrete inputs. Devices which are controlled using GSD and a serial/ethernet interface will fire events AV_Input_Changed and Device_OnOff which Media_Plugin has interceptors for and will use the a/v pipes to figure out what device you're trying to use.</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Why_dual_network_cards%3F&diff=9249Why dual network cards?2008-02-27T19:50:45Z<p>ChuckMcB: typo</p>
<hr />
<div>[[Category: Hardware| ]]<br />
<br />
If you have multiple computers connected in a network, every computer needs to have a unique IP address that identifies itself to the network. The DHCP server has the responsibility of assigning IP addresses. Normally one computer or device--and only one--will be the DHCP server. Whenever a computer or other device is plugged into the network it will normally ask the DHCP server for a unique IP address. In a typical home network the DSL or Cable Modem acts as the DHCP server and gives IP addresses.<br />
<br />
If you want to use LinuxMCE's plug-and-play, which allows you to just plug any device into any jack (camera, phone, media director, etc.) and have LinuxMCE automatically configure the device, then the LinuxMCE Core needs to be the DHCP server. The same is true if you want the media directors to be dual purpose media director appliances and normal pc's.<br />
<br />
If your existing cable or DSL modem is configured to be the DHCP server you will need to disable its internal DHCP server if you want the Core to be the DHCP server--there can only be 1 DHCP server on the network. If you have dual network cards in the Core this is not an issue. Hookup your internet connection (DSL/Cable modem, etc.) to one network card. This is your 'external' network where the internet comes in. And connect your other network card to the Ethernet switch where all your media directors and other computers are connected--your 'internal' network. The DSL/Cable modem is then the DHCP server for the 'external' network, and the Core is the DHCP server for your 'internal' network. If you don't understand this, don't worry--the Core will configure itself for you and you won't need to change any settings in your DSL/Cable Modem<br />
<br />
Another advantage of dual network cards is that then all internet traffic is forced to go through the Core. The Core then handles allocating your bandwidth automatically, giving higher priority to telephone and video calls so the connection is very smooth. It's all automatic if you use the Kick-Start CD and have dual network cards--there is nothing to configure.</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Talk:Known_Issues&diff=9248Talk:Known Issues2008-02-27T19:42:21Z<p>ChuckMcB: Spam removed - Time to install ReCAPTCHA folks.</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=User:Lic4tTacaa&diff=9247User:Lic4tTacaa2008-02-27T19:41:07Z<p>ChuckMcB: Common tactic to just add a small change to a page to test before sending in the main link spammer....</p>
<hr />
<div>[[Category: Spammer]]</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=GlobalCache_GC-100&diff=9246GlobalCache GC-1002008-02-27T19:39:15Z<p>ChuckMcB: Undo revision 9243 by BasolOrico (Talk) Spam removal - Time to install ReCAPTCHA folks.</p>
<hr />
<div> {| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Hardware]]<br />
[[Category: Automation]]<br />
[[Category: Infrared]]<br />
<br />
[[Image:GC100.jpg|right]]<br />
<br />
GC100 is a device which allows you to have remote connection almost anywhere. It's a network device which will forward all your data to :<br />
* couple of serial ports<br />
* [[IR]] senders and/or sensors<br />
* several relays<br />
For more details about the product check [http://www.globalcache.com/products/gc-index.html manufacturer web site].<br />
<br />
== Send IR codes ==<br />
LinuxMCE implementation of GC100 assumes that in device tree we'll have children and the messages are actually addressed to them instead of GC100 itself. <br />
<br />
So when you are sending "ON" to TV controlled by GC100, the message is routed to the GC100, it finds [[infrared]] code for "ON" for that specific TV, sends a command to gc100 to send a specific [[infrared]] sequence, which will blink IR sender connected to specific port, and the TV will turn on.<br />
<br />
The only two commands that GC100 implements itself are : '''CMD_Send_Code''' used to test which IR is suitable for your equipment and '''CMD_Learn_IR''' used to learn new IR codes.<br />
<br />
== Learn IR codes ==<br />
The learning device is actually unrelated to GC100. It may be plugged into one of GC100's serial ports (don't forget to set them to 9600 bps), or in regular serial port, just be sure you specified right port in GC100 device data.<br />
<br />
There are several other devices that support learning of infrared codes : [[IRTrans]], [[Tira]], [[USB_UIRT]].<br />
<br />
Learning is done from [[LinuxMCE-admin|web page]]. When clicking "Learn" gc100 will start a thread that will try to get data from the port. If nothing is received in 30 seconds the thread will die. The page will continue to refresh trying to see if anything was added, but after 30 seconds it's useless.<br />
<br />
== Sensors ==<br />
The gc100 jacks are by default configured as IR transmitters, but they can be configured to function as sensors. The sensors are, in their most basic form, two wires connected to a jack plug. When you cross them, a "sensor tripped" event is emitted. I am not currently aware of how this is supposed to function, who will intercept the event and how will it react to it. One idea for using a sensor is attaching a doorbell button to it, which, when pressed, will notify you in some way.<br />
<br />
== How to ==<br />
=== Install ===<br />
The device is not quite [[plug&play]]. You have to perform a factory reset and to add it from orbiter ("Add GC100" button).<br />
<br />
A script will do some tricks with IP, will submit some pages on GC100's interface and so on. It will install needed software and after that it should say that device is ready to use (don't forget to [[quickreload]])<br />
<br />
=== Before the first use ===<br />
* Insert proper wires in relays, devices in serial ports, [[IR]] LEDs and/or sensors.<br />
* Go to device's webpage and set proper inputs/outputs, baud rates and so on.<br />
* Add child devices in [[LinuxMCE-admin]] webpage and set proper device data to match the wiring.<br />
<br />
This should do it.<br />
<br />
=== Changes in LinuxMCE 0710 beta 4 ===<br />
The way the gc100 is configured in the database changes in LinuxMCE 0710 beta 4. If you are upgrading from a previous release and have a gc100 set up, you will have to reconfigure it.<br />
<br />
The device tree will now have children for each relay, transmitter and sensor port. These are autodetected depending on the settings made to the gc100 itself and updated as the settings change.<br />
<br />
If until now you would put a TV directly under the gc100, you will have to put it under a transmitter child from now on. This will tell the gc100 which port to use to send the code, instead of sending it using all available transmitters like it did until now. This will allow you to add more IR devices which use the same codes without stepping on each other's toes, since the IR codes will be routed just to the target device. The old functionality is still in place and you can still add a TV directly under the gc100, but make sure you mark the checkbox that says "Don't autoconfigure" if you don't want the gc100 to manage its children, so your device remains in its place.<br />
<br />
This is also true for relays. Add your lights, or other devices that support On and Off commands, under the relay children. The On and Off commands will be routed to the right relay this way.<br />
<br />
=== Known Problems ===<br />
<br />
==== MAC detection ====<br />
<br />
--[[User:Nite man|Nite man]] 06:03, 25 January 2008 (PST) To solve the MAC detection problem replace the function ''get_gc100mac()'' in the script ''/usr/pluto/bin/gc100-conf.pl'' by new one below:<br />
<br />
sub get_gc100mac {<br />
my($mac, $page, $ret);<br />
<br />
`curl http://192.168.1.70/Commands.cgi -o gc100mac1 --silent`;<br />
`curl http://192.168.1.101/Commands.cgi -o gc100mac2 --silent`;<br />
<br />
open FILE, "gc100mac1";<br />
$ret = read FILE, $page, -s "gc100mac1";<br />
close FILE;<br />
<br />
unless($page) {<br />
open FILE, "gc100mac2";<br />
$ret = read FILE, $page, -s "gc100mac2";<br />
close FILE;<br />
}<br />
<br />
($mac) = $page =~ /((?:[\dA-F]{2}-){5}[\dA-F]{2})/i;<br />
<br />
if($mac) {<br />
$mac =~ tr/\-/\:/;<br />
loggc("Mac Found $mac\n");<br />
system "rm -f gc100mac1 gc100mac2";<br />
return $mac;<br />
} else { exit 1 }<br />
<br />
}<br />
<br />
Currently the support for the gc100 in LinuxMCE is broken, at least for some models or firmware versions. The ''/usr/pluto/bin/gc100-conf.pl'' script is for some reason unable to determine the gc100's MAC Adress after it has been reset to factory defaults. As a result it is only half configured and not added to the system properly.<br />
<br />
The only known workaround [http://smart-home-blog.com/archives/688] [http://forum.linuxmce.org/index.php?topic=1990.msg9161#msg9161] at this time is to manually edit the perl script, and hardcode the MAC address of your gc100. In short, find this line in the script:<br />
sub get_gc100mac {<br />
Then insert this line immediately following it (replace ''00:00:00:00:00:00'' with the adress of your gc100):<br />
'''return "''00:00:00:00:00:00''";'''<br />
As a result it should look something like this now:<br />
exit(4);<br />
}<br />
} <br />
<br />
sub get_gc100mac {<br />
<br />
'''return "''00:00:00:00:00:00''"''';<br />
<br />
`curl <nowiki>http://192.168.1.70/Commands.cgi</nowiki> -o gc100mac1 --silent`;<br />
`curl <nowiki>http://192.168.1.101/Commands.cgi</nowiki> -o gc100mac2 --silent`;<br />
open(FILE,"gc100mac1");<br />
@data1 = <FILE>;<br />
close(FILE);<br />
<br />
Reset the gc100 to factory defaults if necessary and you should be able to add it from an orbiter as described above.<br />
<br />
Another possible workaround ''might'' be described on the [http://plutohome.com/wiki/index.php/Gc100 Plutohome wiki for the gc100], under '''Complete Manual Install'''.<br />
<br />
Firmware versions known to be affected:<br />
* 2.4-06 (GC100-06)<br />
<br />
==== Serial Port ====<br />
<br />
The GC100's serial port does not work under LinuxMCE without a small modification, see: [http://forum.linuxmce.org/index.php?topic=2161.msg10140#msg10140 Re: GC100 + CM11 setup]<br />
<br />
The following commands should correct this issue (and make a backup copy just in case):<br />
mv /usr/pluto/bin/gc100-serial-bridge.sh /usr/pluto/bin/gc100-serial-bridge.sh.backup<br />
sed -e 's/false/0/g' /usr/pluto/bin/gc100-serial-bridge.sh.backup >/usr/pluto/bin/gc100-serial-bridge.sh<br />
<br />
It basicly replaces '''false''' with '''0''' in the ''/usr/pluto/bin/gc100-serial-bridge.sh'' file. Afterwards a reboot may be in order.<br />
<br />
==== Firmware version 3.0 and later ====<br />
<br />
gc100 with firmware version 3.0 and later is Plug&Play, but not yet supported as such by LinuxMCE. It implements a DHCP client and also has a discovery beacon. Because it is able to get an IP address from the DHCP server, you won't be able to add it using the manual method describe here when using a default installation. You either have to use the completely manual installation procedure described on the [http://plutohome.com/wiki/index.php/Gc100#Complete_Manual_Install Plutohome Wiki for gc100], if you know what IP address the DHCP server gave it, or temporarily disable the DHCP server on the core (write down the DHCP settings, because they are erased from the database when you disable the DHCP server from Pluto-Admin - you can also /etc/init.d/dhcp3-server stop, add the gc100 and /etc/init.d/dhcp3-server start, without erasing the database).<br />
<br />
== Implementation details ==<br />
In ''gc100.cpp'' there is a lot of code for format conversion and other stuff. Practically it's not a big deal it receives a command, find a proper IR sequence and sends it to gc100.<br />
<br />
==== Operating the relays, IR transmitters, and sensors ====<br />
The gc100 software architecture uses two threads to communicate with the gc100 regarding relays, IR transmitters and sensors, one for sending messages (SocketThread) and one for receiving (EventThread). The reason for this is that the gc100 protocol isn't completely a request-reply protocol, even if it seems like that at first. The gc100 can initiate a transmission when a sensor is tripped, enough to break the request-reply paradigm. The program was designed to treat the communication as asynchronous. Messages are sent to the device without expecting a reply, and the replies are treated as independent events and state change reports, without linking a request to a reply in the program logic (except for the initialization phase).</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=User:TadomOrrob&diff=9245User:TadomOrrob2008-02-27T19:38:35Z<p>ChuckMcB: New page: Category: Spammer</p>
<hr />
<div>[[Category: Spammer]]</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Template:Cleanup&diff=9236Template:Cleanup2008-02-27T09:20:48Z<p>ChuckMcB: Undo revision 9235 by DelliLicli (Talk) Spam removal - Time to install ReCAPTCHA folks.</p>
<hr />
<div>'''This article needs a cleanup'''</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE:Privacy_policy&diff=9222LinuxMCE:Privacy policy2008-02-26T21:34:07Z<p>ChuckMcB: Link spam removal.</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=LinuxMCE_talk:Community_Portal&diff=9221LinuxMCE talk:Community Portal2008-02-26T21:33:13Z<p>ChuckMcB: New section: Think it's time to add "Spam prevention" back into the To-Do list.</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)<br />
<br />
: This is not going to be that simple. Take a look at [[Rip a CD/DVD to the Core]]. I have been working on reorganizing the User's Manual and most of the original pages from Pluto are formated in this manner. One would have to go through every single page and remove the programmer related information and move it to Trac. Certainly there are several pages that can simply be moved, but the vast majority of the Programmer related information co exists on user related information page as well.--[[User:Rwilson131|Rwilson131]] 08:14, 20 October 2007 (MST)<br />
= Where are all of the Wiki Admins =<br />
I have been working on updating the documentation and updating the screenshots. There was all of this discussion, but it has been very quiet lately. I am planning on continuing to update the pages and continue to piece together a working [[User Manual]]. Is there a way that I can get the ability to delete some of the images that I uploaded? I pulled from the wrong directory and I would like to delete the older images as they do not match with the current design of either the orbiters or the LinuxMCE Admin Website. --[[User:Rwilson131|Rwilson131]] 22:08, 2 November 2007 (MST)<br />
:You shouldn't need to delete, just use "Upload a new version of this file"<br />
<br />
== Think it's time to add "Spam prevention" back into the To-Do list. ==<br />
<br />
I've used [http://www.mediawiki.org/wiki/Extension:ReCAPTCHA ReCAPTCHA] on a couple of wiki to great effect: stop the bots signing up for new accounts, stop the spam. --[[User:ChuckMcB|ChuckMcB]] 13:33, 26 February 2008 (PST)</div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Help:Contents&diff=9220Help:Contents2008-02-26T21:29:07Z<p>ChuckMcB: Undo revision 9190 by DrontRmonl (Talk) Link spam</p>
<hr />
<div></div>ChuckMcBhttp://wiki.linuxmce.org/index.php?title=Category:Infrared&diff=9219Category:Infrared2008-02-26T21:23:55Z<p>ChuckMcB: Undo revision 9122 by DomalLibov (Talk) Link spam removed.</p>
<hr />
<div>[[Category: Hardware]]<br />
[[Category: Input]]<br />
<br />
Infrared devices and other related stuff should be here</div>ChuckMcB