Notices

jolouis, I would love to see a writeup of what you've done in this area. This is something I've been interested in, but I don't know exactly where to get started. Could you do a blog post, or start a thread, or something, on "Linux Home Automation 101," explaining what equipment you've used and how you wire it up? Or maybe post a set of links to the best stuff that you've found?

As for the dimming lights... My biggest complaint here is that I'm trying to switch to the environmentally friendly CFL lights, and they just don't do dimming. Not even the ones that say they do dimming.

Pshhh, CFL is so last year. Its all about LED lights now...

actually what i had in mind was for security-the n810 used as a monitor for remote wireless webcams that pickup any person entering my property-the technology is already there-all that is needed is the software

Please keep flip clock basic, I love this project and I would hate to see it trying to do everything. There is nothing wrong with a clock just being a clock.

http://www.footprintsecurity.com.au/...a_packages.php

check this out -connecting cameras by wirless to the nokia n810 would be great

Ok this is getting waaay off topic here, I'll start a new thread for home automation/etc over in the general section (should really be in "off-topic", but it relates to using the tablets as controllers, so general makes sense). Let's leave the flipclock thread for flipclock discussions; we can always bring ideas from the other thread back over later if they are relevant. New thread is here:
http://www.internettablettalk.com/fo...806#post266806

Before I go though, a few points to address:
1) qole, CFLs... I know, tell me about it... however, I found that CFLs for things like outdoor lights/etc where I never wanted to do dimming were great, and just use regular old incandecants until the LEDs come down in price. The energy savings for CFLs VS regular for the most part was offset by the fact that I tied the lights in with the motion sensors of the alarm panel and a few other bits and pieces so that lights would automatically turn off if there was nobody around/nothing happening/alarm system armed/etc. It's not a direct $ for $ energy matchup, but it's pretty close. At the end of the day, installing CFLs everywhere saves you money if you're used to leaving lights on for long periods of time when you didn't need lights; if you're careful with your lighting, the cost savings in energy of CFLs is nowhere near as significant. I'm still waiting for great LED lighting though...
2) yukop4... you need IP-based cameras. The cheapie "wireless 2.4Ghz" cameras are not IP addressable or accessible in any way. While I agree about monitoring cameras with the tablet (I have a buddy who wants to do exactly that when he gets some more cash), you need to make sure you've got some actual networkable cameras that will display properly on the tablets. In your scenario you'd also want to have some kind of backend system beyond the tablet to actually monitor/record the cameras and notify you when somebody was approaching/etc so that you would know when to pull the camera feeds up on your tablet.

Anyways, in all cases, if it's not directly related to Flipclock, leave it off this thread and go to the other one...

oh, the home automation topic was taking over the thread
Thank you jolouis for being a moderator.
The AM/PM modify is almost completed.
I tried to test to upload to extra-develop without success.
When Ill have a bit of time Ill ask some advice to someone on irc.
The only things still 'open' are the alarmd and a better ringing section (let user choose mp3s or maybe to (risky) trigger an internet stream.
Since the clock already check for the model I could put an option for the FM radio of the N800 but I have no idea how test it (I have a N810).

@Rassilon7: dont worry, the clock code is so basic that will always remain a basic app (watch back the thread all the modifies it survived ). The clock was, since the beginning, just a pretext to check what I could be able to do with the tablet (see the led, the experiment with the gestures, the trasparencies, the battery, the light sensor, full screen, window, os integration and so on).
If I ll be able to re-learn a bit of C I would probably make a version even more stripped down but since the python foorprint is so HUGE 1 or 2 more features dont change too much how the app feel

I finally managed to spend some time really working on this the other day and have at last "cracked" the whole alarmd/Dbus/power management/etc problems by re-organizing the main loop (the old pygame.event.wait() thing is no more, which opens up all kinds of better options). To give an idea, I've now modified it so that when the tablet's screen is off the clock is no longer updating and wasting CPU/battery power, but it's still running and as soon as you touch the screen it's back to life again with correct time/etc. The next step now is to setup some DBus tie-ins to monitor for custom Alarmd events, and finally to update the "alarm setting" code to use Dbus signals to the alarmd daemon instead of just storing internally as it's doing right now. I'm going to keep "butchering" my version of the clock here for a bit longer till I get all of these things sorted out and working, and once that's done then I'll send you the updated code that you can merge with your latest version there Ciro, or I can grab your latest sources and make the changes... either way, whatever's best. Once the alarmd stuff and Dbus stuff is integrated properly though is should be very easy to also add some Dbus calls for alarm events so that an alarm can do things like trigger the native media player with a given sound file, whatever (going to need some more interface design work when that comes along tho! ;o) )

feel free to modify directly last version (0.1.2). the code should be enough modular to let me keep working on the AM/PM thing (in ci.gfx) without touching the rest. In any case in a couple of days I should probably be able to put the 0.1.3 in garage.
Tell me if I should add you on garage to the developer list (so u can add directly there the new version).
Yes I know the interface will need to be modified but if you followed the thing since the beginning you probably understand that is not an issue
All the graphics elements are pretty simple so is matter of minutes.
Since the very 1st day the plan was to to write a better way to add an alarm event and substitute the crippled default OS interface then the things toke some weird turns. Now im not satisfact at all of the actual ringing routine so that part have to be touched in any case (like usual I keep the important parts at the end).
Buon lavoro

Hey guys, I really like this project. I am not following current development, but I noticed these bugs/feature requests in the current build.

1) When I select the green LED option, it just changes to blue. Other colors work. (p.s., I really like the led control, 1st app i have seen actually use it!)
2)Sometimes, if it crashes, the LED keeps flashing, even though the program is "dead." Probably a loop or something.
3) What is that weird thingy picture in the non-fullscreen mode?
4) How come the numbers don't actually "flip"

Really cool graphics wise, smooth as butter...