[Mobile Photos] Bildungsstreik Demo Potsdam
17.11.2009 | Lunch Time
Reiche Eltern für Alle!
Sent from my mobile
Reiche Eltern für Alle!
Sent from my mobile
A really great sensitive moment when Moby talks about being a nerd … *sigh*
[via Wire To The Ear]
I’m having this Nokia E51 mobile phone which basically has become my main brain extension to go, since i have abandoned all paper-based approaches. Best thing about the mobile is, that half of the day I’m on the go and I always have my mobile with me, be it on the train, on my bike or in the club. It is always not more than one quick reach into the pocket away. The other half of the day, I usually sit on my Laptop. Handling my schedule and tasks is easier on the big screen, so I prefer that when I have the chance for it. Problem is, that Laptop and Mobile have to stay in sync.
I use iSync for doing that, but the problem is, that I have to start it on my own (which I do forget always). So this is how to have regular scheduled syncing:
Put this in a file somewhere:
tell application "iSync"
synchronize
repeat while (syncing is true)
delay 5
end repeat
quit
Now go to your terminal, type in crontab -e (for hourly sync) and add:
0 * * * * osascript {full script path}
This did not work for me in the first place, but after calling osascript with arch -i386 osascript it worked on my MacBook Pro with Snow Leopard.
Now every full hour iSync pop-up in the background, syncs with my mobile and closes automatically. I do not get disturbed by it, but also do not get any error messages. Bluetooth has to be constantly turned on on mobile and mac. When it is not, sync just fails silently.
As long as I have not moved all my personal data in the cloud, which will make keeping in sync far more easier, this is a pretty convenient way.
For more infos:
An extended Version I based my approach on
Apple Script on Wikipedia
Crontab on Wikipedia
We have been watching these feature in the “Introduction to Human-Computer-Interaction” lecture. It showcases an impressive company culture …
[direct links to the three parts one / two / three]
This Motivational hung in our Bachelor project room when we got it hand over and is the only thing we did not take off the wall (yet)
Sent from my mobile
About a month ago, the Music Hackday took place, where Tracks On A Map got it’s name and saw the light as a pre-release. Last friday, we finally launched it, after putting more hard work into it. We are pretty happy with the outcome, since we created a sleek and easy-to-use application that is standing on a solid code base.
You might already know it, but check it again at http://www.tracksonamap.com and follow the Tracks On A Map account on Twitter.
Most of the stuff we have done since the Music Hackday was “making it nice“. We included sharing functionality, meaning a user is able to share a track or city on Facebook or Twitter or elsewhere. A lot of backend stuff has been re-written, made fail-prove and fast. The frontend got an improved design. We also tried to make the app responsive and fast-loading. Nearly all requests are answered from Memcache and we also implemented some client-side caching.
There are still things to be made better which we hope to fix in the near future. And there are already ideas for the next big release as well …
Check the issue tracker on the GitHub Repository and add things you’d like to see.
While developing on Google App Engine I made some good and some bad experiences, which I might write something about later. I might also talk about it on the upcoming Barcamp London …
Thank you again to Eric and Katharina, who both have a big share in making the project as great as it is today.