I went to each of the different scenarios I didn't want under the wizard section and most of them didn't have checkboxes. I looked in the admin some more, and worked out how to disable the devices (under the devices tree). However the orbitor still shows climate/security/telecom etc. I take it there is currently no way to turn this off (maybe a skin for the orbitor that doesn't show them or something).
No, there is no way to alter the appearance of the category icons at this time without creating new skins.
I then created a bunch of links in /home/public/data and used the web admin to update.
This is the exact opposite of the approach I suggested... These links will probably be deleted on a router reload. Stop thinking like a Linux hacker... Go add the devices to the device tree properly, reload the router, and the links will be created automatically, and the media database will be kept up to date properly.
a) It seems to default to Title every time I load it up. This is not very much use when you have a lot of files, how do I set it to default to browsing by filename?
There is not currently a way to set default filters. It may be possible to look at what commands are being sent (DCERouter.log) and simulate them with a custom scenario. I tried this earlier and had no success.
b) If I want to add a new file from another machine on the network and copy it onto the server so that I can play it (say into one of my users home/data/video directories), the only way to do so seems to be to login to the web server and tell it to update that directory. Is there any way while viewing by filename to tell the core to refresh the directory? Or any way to browse the filesystem to choose a file to play? (either without adding the file to the linuxmce directory or by automatically adding it when the file is played).
All the data grids are built from what exists in the media directory, which must be synchronized to what exists on the storage devices. This happens automatically periodically. If it is too slow, for instance if you just added the file a moment ago, you can trigger the refresh manually from the web admin, as you have.
You're thinking like a Linux hacker again... The point of all this stuff is to never see the filesystem and to not care where anything is stored. The user should be presented with a single unified media library. If your media is properly tagged, there are advanced search features that should completely replace any reliance you have on the physical location of your media. Search for tschak's screen casts on media tagging - the possibilities are quite impressive.
The only issue I have with this is that my ADSL router currently also provides my wireless, so if I want to have a MD connected up wirelessly to the core then I will need to go buy another wireless access point and run two seperate wireless networks (one for my devices that I don't want to be dependent on the core being on or working to access the internet and another for any MD I want to connect to the core). Given I'm currently still just trying out linuxmce I don't really want to be purchasing new equipment at the moment that I have no use for if I decide not to use it.
You will not successfully connect an MD to the core wirelessly and have it run well. MDs pull their boot image directly from the core and all file work is done over the network since MDs don't have hard drives. A wireless link is not reliable enough to do this. Media playback is also hindered by the low reliability of wireless networks, which causes very low throughput and high packet receive error rates. Yes, I know it's theoretically possible to do all this with wireless bridges and whatever other lovely network stuff you can think up. I know this because I didn't believe that it couldn't work when I tried it. Guess what - it doesn't work in the real world. You can search up plenty of instances of people trying this this. You're welcome to try it on your own, but I can save you a lot of time by telling you what you'll find: if you're able to get the MD to boot, it will take a ridiculously long time, and then the user experience will be poor and unreliable at best. Not to mention the complexity of the setup is quite high. You will be much better off saving the money, time, and frustration by running some CAT5.
If you are talking about using other media playback devices (like somebody's laptop), you simply need to open the proper ports on the firewall to allow them to connect from the "external" network. Of course, the reliability of the network will still be a major factor in the quality of your playback.