Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/37/d13445233/htdocs/wordpress/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/37/d13445233/htdocs/wordpress/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/37/d13445233/htdocs/wordpress/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/37/d13445233/htdocs/wordpress/wp-includes/http.php on line 61

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/functions.php on line 17

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/k2.php on line 64

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2SBM::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2SBM::load_modules() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/widgets.php on line 41

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_width() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/header.php on line 15

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::add_custom_query_vars() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::dynamic_content() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339
Todo mit Nutella « Webwatch Onvion
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_image_url() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/header.php on line 113


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 41
class="post hentry category-tools tag-cloud tag-produktivitat tag-schweiz tag-teuxdeux tag-todo tag-web-20 tag-webdienst tag-werkzeug tag-wolke p1 y2011 m05 d04 h13">

Todo mit Nutella


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Eine der großen Herausforderungen in unserer derzeitigen Gesellschaft ist die Organisation und Strukturierung der Aufgaben, die täglich auf uns zu kommen. Werkzeuge dazu gibt es viele, das einfachste ist sicher die Kombination aus Stift und Zettel, mit der wir schon seit langer Zeit zum Beispiel Einkaufszettel schreiben. Haben wir früher Kalender, Planer und Notizzettel genutzt, so haben sich mit der Verbreitung der Computer diese Werkzeuge ins Digitale übersetzt. Leider wurde die Sache damit nicht einfacher: Computer konnte man lange Zeit nicht mit sicher herum tragen, zumindest nicht komfortabel, PDAs hatten andere Betriebssysteme und mussten aufwändig mit Desktopgeräten synchronisiert werden. Selbst heute noch, zur Zeiten von iPhone, Android- und WebOS-Smartphones, die PDS abgelöst haben, finden sich noch immer Applikationen, die zwar wunderschön aussehen, oder auf ihrem Ursprungssystem perfekt funktionieren, aber leider für Multisystemnutzer wenig Sinn machen. In Zeiten von Web 2.0 und der sogenannten “Cloud” kann man sich allerdings die Frage stellen, ob es man nicht gleich auf Programminstallationen verzichtet und statt dessen auf Webdienste setzt. Grade im Bereich der Produktivitätstools hat die Anzahl dieser Dienste in den letzten Jahren einen großen Boom erlebt, so sehr, dass es schwierig ist einen Überblick zu bekommen, wenn man sich damit auseinander setzen möchte. An dieser Stelle werden wir ab und zu einen dieser Dienste vorstellen. Den Anfang macht heute TeuxDeux, aus der breiten Sparte der ToDo-Dienste.

teuxdeux-screenshoot

Todo-Listen sind ein ganz eigenes Ding. Die einen schwören drauf, andere halten sie für reine Zeitverschwendung. Es kommt sicherlich sehr auf den persönlichen Geschmack an, und darauf was man von so einer Liste erwartet. Zudem, eine Todo-List allein ändert noch nichts, es darf auch dem Willen und die Disziplin, die Liste zu führen und umzusetzen.

Wer sich schon einmal mit dem Thema beschäftigt hat, dem werden Namen wie remember-the-milk oder producteev etwas sage. Normalerweise trägt man bei solchen Diensten eine Aufgabe, ein Todo ein, setzt einen Ablaufzeitpunkt, gibt eine Priorität an oder sortiert es in bestimmte Rubriken ab. Der aus der Schweiz stammende Dienst TeuxDeux kommt da erst einmal viel schlichter daher. Es gibt eigentlich nur eine Seite, auf der die nächsten Tage in Spalten angezeigt werden. Jede Spalte zeigt eine Liste der anstehenden Aufgaben. Der aktuelle Tag ist rot hervor gehoben. Das ist eigentlich alles. So einfach, aber grade deswegen so gut.

Tatsächlich hat jede Tagesspalte ihr eigenes Eingabefeld über der Liste. Dort werden neue Aufgaben eingetragen. Aber auch bestehende Aufgaben können dort einfach per drag&drop abgelegt werden, um sie zu bearbeiten, zu korrigieren oder auf andere Tage zu verschieben. Hat man eine Aufgabe erledigt, reicht es sie einfach anzuklicken und sie wird durchgestrichen. Dem Nutzer bleibt also im Blick, was schon erledigt wurde. Aufgaben, die mit Ablauf des aktuellen Tages nicht gestrichen wurden, werden automatisch in die Liste des nächsten Tages übernommen. Zusätzlich gibt es noch eine List für Aufgaben, die nicht termingebunden sind. Dinge ohne festen Zeithorizont bleiben damit auch immer im sichtbaren Bereich der Website.

TeuxDeux ist nichts für Leute die vielfälltige Einstellungsoptionen für ihre Todos haben möchten, und TeuxDeux ersetzt auch keinen Planer. Aber, es ist eine wundervolle Ergänzung, um kleinere Dinge mal eben schnell ein- und austragen zu können. Wenig Aufwand, viel Ertrag. Die Webversion ist kostenlos. Ach, und wenn ihr schon dabei seit euch TeuxDeux einmal anzuschauen, schaut in FAQ und findet heraus, was Nutella mit dem Dienst zu tun hat.

0 Response to “Todo mit Nutella”


  • No Comments

Leave a Reply





Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339