Comments on: Building a Twitter widget, part 1: setting-up the code and displaying a single status http://dev.netvibes.com/blog/2007/06/04/building-a-twitter-widget-part-1-setting-up-the-code-and-displaying-a-single-status/ News and articles about the Netvibes API Thu, 21 Aug 2008 18:15:03 +0000 http://wordpress.org/?v=2.5 By: PHP-UWA Widget Library | Technik, Gothic und Anderes http://dev.netvibes.com/blog/2007/06/04/building-a-twitter-widget-part-1-setting-up-the-code-and-displaying-a-single-status/#comment-2095 PHP-UWA Widget Library | Technik, Gothic und Anderes Mon, 26 Nov 2007 15:04:00 +0000 http://dev.netvibes.com/blog/2007/06/04/building-a-twitter-widget-part-1-setting-up-the-code-and-displaying-a-single-status/#comment-2095 [...] Homepage und ist gut dokumentiert. Es gibt Beispiele, ein Code-Skelett mit Erklärung, ein Schritt-für-Schritt Tutorial, ein Forum und sogar ein Cheat-Sheet. Der Einstieg wird einem wirklich so einfach wie möglich [...] […] Homepage und ist gut dokumentiert. Es gibt Beispiele, ein Code-Skelett mit Erklärung, ein Schritt-für-Schritt Tutorial, ein Forum und sogar ein Cheat-Sheet. Der Einstieg wird einem wirklich so einfach wie möglich […]

]]> By: Toby Beresford http://dev.netvibes.com/blog/2007/06/04/building-a-twitter-widget-part-1-setting-up-the-code-and-displaying-a-single-status/#comment-92 Toby Beresford Wed, 27 Jun 2007 14:24:13 +0000 http://dev.netvibes.com/blog/2007/06/04/building-a-twitter-widget-part-1-setting-up-the-code-and-displaying-a-single-status/#comment-92 "However, there are times when you’d rather not have to build the whole interface using JavaScript - which will be the case for us when our widget gets more complex. Nothing keeps you from directly setting up the HTML code, maybe hiding it using CSS while the content is loading.." This seems to me to be important when keeping code clean by separating view(s) and controller... Please can you do a case study / uwa user manual page that demos best practice for this technique too? Thanks Toby “However, there are times when you’d rather not have to build the whole interface using JavaScript - which will be the case for us when our widget gets more complex. Nothing keeps you from directly setting up the HTML code, maybe hiding it using CSS while the content is loading..”

This seems to me to be important when keeping code clean by separating view(s) and controller… Please can you do a case study / uwa user manual page that demos best practice for this technique too?

Thanks

Toby

]]>