If you really want to disable that Guided Access pop-up message, I think there's a way to do it. It's called "Single App Mode". You use Apple's Configurator to enable it through a configuration profile, and it literally locks the iPad into booting directly into that app, and you cannot disable it without connecting the iPad to (presumably the same?) computer and removing the profile.
The downsides are:
1. You have to put the iPad into supervised mode, which requires a full factory reset through the Configurator. This is because it enables a bunch of enterprise controls that they don't want enabled without the user's knowledge, such as the ability to configure a global HTTP proxy, etc.
2. As I mentioned before, there is literally no way out of the app other than removing the configuration profile. This sounds like it interferes with your use case, but maybe it's a worthwhile tradeoff for you?
3. Probably something else I didn't think of.
Here are a couple articles I found that mention how to do this:
[0] and [1] are articles from some app that this feature is useful for, explaining how to do it for that app.
Disclaimer: I have never tried this myself, I have simply happened to have heard of it. I found the two articles above because I knew the term to Google (not a shot at you, sometimes you just need to know the right search). There may be some unintended consequences because it's an enterprise feature and all.
Another way to address the original problem is jailbreaking and using the Activator app to assign the home button to "unlock", which effectively auto-unlocks the device to whatever app you had open.
I find it quite a usability improvement, when using the tablet as a cookbook for example.
Ever have a look at OpenHab[1]? It's a bit finicky at first but would make a dashboard with whatever you want on it, either in a browser or using their native app. There's also a really cool automation guide I saw recently[2].
I really want to do something like this when I get my old house back this summer. Thanks for the inspiration!
For the lighting, you should totally make a "party" mode that involves sending color-changing messages to all the lights, over and over. Bonus points if the colors fade into eachother.
You are correct. I did not read very carefully. Thank you for pointing that out. I focused on the pretty pictures before reading all of the text. I can say with extreme confidence that I am not the only person who made the mistake of not reading carefully so I thought it worthwhile to mention.
Mine ( https://github.com/sartak/ ) is currently a 558 day streak. I'm studying Japanese, so I've been committing the new words I learn (at least one every day!) to my "vocabulary" repo. I started a while before GitHub even started tracking streaks.
Great article but I'm confused about this bit: "Jesse McReynolds, a graduate of Caltech, had finished coding a low-level network library to send IPX packets over a local-area network. The code was written based on knowledge gleaned from the source code to Quake, which had been recently open-sourced by John Carmack at id software."
Warcraft was released in 1994. Quake in 1996. Quake's code was released under the GPL in 1999. So code was Jesse McReynolds cribbing from?
You're correct; the article should have read "Doom", not "Quake". And further, Doom had not yet been open-sourced. I'm checking with Jesse now but my assumption is that he talked to someone at id and they sent along a snippet of code that showed how to talk to the IPX network driver.
I've made corrections and -- once I've heard back from Jesse -- will include additional details.
I've been developing a similar system for accelerating my Japanese study, and I haven't been able to release it yet either. It has nothing to do with the quality of the code, it's that right now it's designed specifically for myself. It practically hardcodes my username and other details like that. Maybe other programmers could use it, but preparing such a package for general consumption takes lots more time and energy.
Same situation here as well. I started with eventual distribution in mind (yet another Japanese study app) but it's still a long way away from being what I'd consider releasable. Too many features coded in that I forced myself to try out and will eventually be modified, reconfigured, or whatever. I'll run out of excuses soon enough ;)
The module documentation doesn't mention error handling. Perl has no consistent exception system and this makes it very difficult to build reliable programs in the language. The standard library has inconsistent error handling. And CPAN modules like this usually have none at all.
