Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/class.wp-dependencies.php on line 15

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method adsensem::init() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/plugin.php on line 311

Strict Standards: Non-static method adsensem::setup_is_valid() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-content/plugins/adsense-manager/adsense-manager.php on line 117

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method adsensem::init_widgets() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/plugin.php on line 311

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-content/plugins/adsense-manager/adsense-manager.php on line 152

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

Strict Standards: Non-static method adsensem::register_widget() should not be called statically in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-content/plugins/adsense-manager/adsense-manager.php on line 158

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 /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/plugin.php on line 311

Warning: Cannot modify header information - headers already sent by (output started at /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-settings.php:472) in /nfs/c03/h05/mnt/52932/domains/retiredblog.gkaindl.com/html/wordpress/wp-includes/feed-rss2-comments.php on line 8
Comments on: Reinventing the Web for the iPhone http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/ nerd nouveau Thu, 24 Sep 2020 02:07:21 +0000 http://wordpress.org/?v=2.6.2 By: Fred http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3134 Fred Thu, 26 Jul 2007 13:57:08 +0000 http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3134 It looks alot like the Vista hype: too soon released and very unstable. I think I'll wait for a year or so... It looks alot like the Vista hype: too soon released and very unstable. I think I’ll wait for a year or so…

]]>
By: Barry Welford http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3127 Barry Welford Thu, 26 Jul 2007 02:14:43 +0000 http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3127 Indeed, Georg, we certainly are thinking along the same lines. Since I wrote some of that early 'stuff', I'm including now the possibility that input might come either from voice commands or from barcodes via the camera. I'm sure the list will get even longer as time goes on. Indeed, Georg, we certainly are thinking along the same lines. Since I wrote some of that early ’stuff’, I’m including now the possibility that input might come either from voice commands or from barcodes via the camera. I’m sure the list will get even longer as time goes on.

]]>
By: georg http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3126 georg Wed, 25 Jul 2007 23:19:02 +0000 http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3126 Thanks, Barry. Yes, it's interesting to see how much our views align with each other. I really like your description of different device classes, but I think it's important to not only classify them by screen space and connection speed and bandwidth costs/constraints, but also by the applied usage paradigm. For example, on a PDA, we generally don't have a mouse. Thusly, there is no constantly moving cursor on the screen. Instead, we only have discrete "click" events. But this, in turn, renders "rollover" events non-functioning on such devices because there is no such thing as a "rollover" when we only have discrete clicks. However, it's easy to dig up some websites that make extensive use of "rollover" events, such as when expanding menus when the mouse rolls over a headline etc... All this does not work (or would feel awkward, since we don't want to drag our finger or stylus over the screen like a mouse) on a handheld. Instead, the more diverse web-browsing devices become, the more we have to employ what you refer to as 'Multi-Web Practice', in order to create website front-ends that blend in well with the usage paradigm of each device, as well as its physical (and possibly economic) properties. Thanks, Barry. Yes, it’s interesting to see how much our views align with each other.

I really like your description of different device classes, but I think it’s important to not only classify them by screen space and connection speed and bandwidth costs/constraints, but also by the applied usage paradigm. For example, on a PDA, we generally don’t have a mouse. Thusly, there is no constantly moving cursor on the screen. Instead, we only have discrete “click” events. But this, in turn, renders “rollover” events non-functioning on such devices because there is no such thing as a “rollover” when we only have discrete clicks. However, it’s easy to dig up some websites that make extensive use of “rollover” events, such as when expanding menus when the mouse rolls over a headline etc… All this does not work (or would feel awkward, since we don’t want to drag our finger or stylus over the screen like a mouse) on a handheld.

Instead, the more diverse web-browsing devices become, the more we have to employ what you refer to as ‘Multi-Web Practice’, in order to create website front-ends that blend in well with the usage paradigm of each device, as well as its physical (and possibly economic) properties.

]]>
By: Barry Welford http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3125 Barry Welford Wed, 25 Jul 2007 21:27:07 +0000 http://retiredblog.gkaindl.com/2007/07/25/reinventing-the-web-for-the-iphone/#comment-3125 I really enjoyed this post, Georg. I guess that's becaues I've been spouting the same view for some time. Instead of the One Web Principle, I'm pushing for the <a href="http://www.staygolinks.com/?page_id=66" rel="nofollow">Multi-Web Practice</a>. That was written when the iPhone was very much in the development stage, but I think it's the only way to go if you follow your different paradigms notion. I really enjoyed this post, Georg. I guess that’s becaues I’ve been spouting the same view for some time. Instead of the One Web Principle, I’m pushing for the Multi-Web Practice. That was written when the iPhone was very much in the development stage, but I think it’s the only way to go if you follow your different paradigms notion.

]]>