I have found that "application" wise, pretty much everything works out of the box, however there are also a few packages that require a bit of poking and prodding to get "just right". These are usually what I would describe as system level applications or things that play with services. This is the nature of the overlaid .sqf filesystem, and the fact that we don't want things to always be writing to the USB/Flash. So a few saves of the 9x-snap file and restarts is often required.
I ask that you keep in mind that we are at a First Developers Release of FoxyRoxy and as such some things will change. Some architectural things may also change. The whole intent behind the First Developers Release was to get your attention and assistance. As I compose this message, I am having some re-thoughts on 99-snap and how this may affect things. By having our desktop config load as the last .sqf, this may be causing issues with stuff that was installed and loaded by 95-snap. Therefore we may need to push our 99-snap desktop/config stuff further down the startup sequence so that it is loaded before 95-snap and a filename change to xx-FoxyConfig wouldn't hurt either
Both LMS and XMBC are interesting. They both have some strange quirks and as they are both very much related to what I want to build, they have my interest. My current thought is that if I can get my system-services configuration and desktop changes configuration stuff working with them, then that stuff should work with anything.
Both LMS and XMBC are interesting. They both have some strange quirks and as they are both very much related to what I want to build, they have my interest. My current thought is that if I can get my system-services configuration and desktop changes configuration stuff working with them, then that stuff should work with anything.
Being able to easily configure the services start-up, or turning services on and off is a pretty important thing to me. While my initial thought was to have this in a separate .sqf, I am now thinking that it might be best to incorporate this into our xx-FoxyConfig which is currently 99-snap.squashfs . Regardless as to what we call it, the final file shouldn't be to large so it will load and save quickly, unless you put a heap of stuff into the Firefox directory.
To give you an idea: At the moment, I am looking at the following:
03-FoxyServices.squashfs = 76kb
99-snap.squashfs = 644kb
We also need to remember that we only have 8 .squashfs files to play with.
Any thoughts, comments, suggestions?
