Comments on: 7 Characterists of Web 2.0 Development Practices, from O’Reilly Radar http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/ Web professional with deep frontend engineering expertise skilled in user experience design and product strategy. Successful team leader, manager, and executive. Sought-after speaker, writer, and trainer. Mon, 24 May 2010 15:52:17 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: austin texas personal injury lawyer http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/comment-page-1/#comment-3171 austin texas personal injury lawyer Mon, 26 Jun 2006 21:24:57 +0000 http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/#comment-3171 great entry great entry

]]> By: Marc Hedlund http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/comment-page-1/#comment-1677 Marc Hedlund Sat, 20 May 2006 16:56:28 +0000 http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/#comment-1677 Thanks for the link, Nate. You might also like the <a href="http://radar.oreilly.com/archives/2006/02/three_interesting_web_developm.html" rel="nofollow">follow-up to the original piece</a>. I think there's a lot more to say about this topic -- I'm hoping we'll get more stories from the people who would know. Thanks for the link, Nate. You might also like the follow-up to the original piece. I think there’s a lot more to say about this topic — I’m hoping we’ll get more stories from the people who would know.

]]> By: Martin Hernandez http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/comment-page-1/#comment-1485 Martin Hernandez Fri, 12 May 2006 04:50:43 +0000 http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/#comment-1485 Internet Explorer Eolas changes and the Flash plugin Filed under: flash javascript usability quicktime flashobject@ 2:30 pm Microsoft recently announced (again) that they will be changing the way Internet Explorer handles plugins (more info here). So how does all of this affect you being a web developer? Basically, the functionality changes work like this: When using an applet, object, or embed tag to insert a plugin into an HTML document, that plugin will not allow user interaction until the user clicks on it. Microsoft calls this process “Activating an ActiveX Control’s Interface.“ In the case of the Flash plugin, it means that your Flash movies will not work until a user ‘activates’ it first by clicking on it. The details are still a bit fuzzy, and I can’t find a developer preview of IE 6 or IE 7 that include this new functionality to test this new functionality (If you find one, please let me know) (see below). This is a slight improvement over the previous ‘fix’ which was a small dialog prompt for each ActiveX control on a page. Now you just have to click on each control to activate it (if you want to interact with it). Microsoft says “We believe over the next six months, most customers will be running copies of Internet Explorer with this behavior.” The changes will be rolled into IE 6 through security updates to Windows, and included in IE 7. http://www.instantenet.com.ar Internet Explorer Eolas changes and the Flash plugin
Filed under: flash javascript usability quicktime flashobject@ 2:30 pm
Microsoft recently announced (again) that they will be changing the way Internet Explorer handles plugins (more info here).

So how does all of this affect you being a web developer?
Basically, the functionality changes work like this:

When using an applet, object, or embed tag to insert a plugin into an HTML document, that plugin will not allow user interaction until the user clicks on it. Microsoft calls this process “Activating an ActiveX Control’s Interface.“

In the case of the Flash plugin, it means that your Flash movies will not work until a user ‘activates’ it first by clicking on it. The details are still a bit fuzzy, and I can’t find a developer preview of IE 6 or IE 7 that include this new functionality to test this new functionality (If you find one, please let me know) (see below). This is a slight improvement over the previous ‘fix’ which was a small dialog prompt for each ActiveX control on a page. Now you just have to click on each control to activate it (if you want to interact with it).

Microsoft says “We believe over the next six months, most customers will be running copies of Internet Explorer with this behavior.” The changes will be rolled into IE 6 through security updates to Windows, and included in IE 7.

http://www.instantenet.com.ar

]]> By: Wally http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/comment-page-1/#comment-531 Wally Sun, 12 Feb 2006 18:16:26 +0000 http://nate.koechley.com/blog/2006/02/11/7-characterists-of-web-20-development-practices-from-oreilly-radar/#comment-531 I agree with the #3, building atop your API. You're testing 2 birds with a single stone by developing a single interface for your web app and external partners and those mash-up nerds. Is #1 similar to this point? Eternal beta means you can't charge for the service, right? It doesn't mean you can't make $$$ indirectly via ads. I'm not so hot on #4 which can promote erratic practices in processes. I'd rather build a framework, featuring a CMS, rather than push a build that could potentially break (Murphy's a bitch); you never know and there's too much at stake. Just my 2 cents. Thanks Nate for the link. I agree with the #3, building atop your API. You’re testing 2 birds with a single stone by developing a single interface for your web app and external partners and those mash-up nerds. Is #1 similar to this point?

Eternal beta means you can’t charge for the service, right? It doesn’t mean you can’t make $$$ indirectly via ads.

I’m not so hot on #4 which can promote erratic practices in processes. I’d rather build a framework, featuring a CMS, rather than push a build that could potentially break (Murphy’s a bitch); you never know and there’s too much at stake.

Just my 2 cents. Thanks Nate for the link.

]]>