PUBLIC MARKS with search handling

This tutorial is a practical exploration of using Python coroutines (extended generators) for solving problems in data processing, event handling, and concurrent programming. The material starts off with generators and builds to writing a complete multitasking environment that can run thousands of concurrent tasks without using threads or using code based on event-driven callbacks (i.e., the "reactor" model)

Nooo! You've mangled mouse gestures!I use mouse gestures all the time. But with O11, it's half b0rked.[...] here's news to you: you never ever make a perfect gesture, Opera used to work fine with skewed mouse gestures, what's the deal taking yet another awesome feature and beating the living hell out of it?THIS USED TO WORK! WHY DID YOU MESS IT UP?!

Right now, Opera 11 mouse gestures handling is *crap*.

karl dubost said at 4:32 am on December 14th, 2010:

Matthew Gertner: “I’ll concede that I have more experience with W3C standards than with those of other organizations. ”

http://www.w3.org/Search/Mail/Public/search?keywords=Matthew+Gertner+

Matthew Gertner: “Someone at the W3C, the de facto master of all things web, decided that we needed a proper schema language for XML.”

Ah? It is usually not the way it is happening. Someone with experience of W3C knows that usually some companies being W3C members have interests in developing a market (because they need interop, because they need to sell products, because… etc.). These companies under the umbrella of W3C organize a Workshop where they gather position papers. After this Workshop, a report is written and published. If more interests, an activity proposal is drafted. This activity proposal is then sent to W3C Membership for reviews and comments. More comments, more modifications. Basically the goal is to establish if the Members have enough interests to commit resources for developing the work. WG charters are established along the same line.

XML at W3C has been pushed because companies had developed tools for handling it and thought that because invested a lot of efforts in the XML toolchain, let’s reuse pieces of it.

IMHO, the standards activities anywhere (including W3C) derail when Marketing dept/Product groups have too much impact on the specification itself. The standard is not anymore driven by the market needs, but the companies are creating the market. HTML5 starts to become known outside of the tech sphere and I think we will have surprises.

The top-down approach in a standard organization seems bit strange considering that the work is the result (usually) of a community of practice.

As for an individual or a small group is not “best” for creating technical specs, it is just easier and address the needs of this small group. So indeed it is easier to produce something which is consistent for this group, which goes faster to implement, to market, etc. That doesn’t mean the technology is better :) The bigger the committee the larger the number of issues. This is a truism. All communities are working like this.

Matthew Gertner: “I’d rather see companies get their tech out there and open it up afterward because it’s in their interest (which is usually is).”

Yes and it is what happens most of the time. That doesn’t mean it will necessary solve things. A good example has been SVG. Three “proprietary” specifications were published before the SVG work with people having things implemented in products. But the spec grew too big, with many people wanted to have their own feature, domain introduced in the specs. Standardizing means reducing diversity, and it’s sometimes take times. For SVG, Macromedia (which was bought far later by Adobe) was on the initial SVG WG… as lurkers and unfortunately not really active participants. This is another reality of standards organization.

There are many more issues. W3C (the organization) is doing a fair job at balancing the interests of everyone. There are frictions, nothing is perfect, but there has been always room for improvements. The process has always been flexible for welcoming new use cases.

Your comment is awaiting moderation.

For this project, I have a page template with several container elements that all have a 1 pixel by 1 pixel PNG background set to repeat, and it looks great when testing it in IE 7 and IE 8. So, I created my next page template with the same styling. This time, IE 7 and 8 both choked when handling the background-repeat. Instead of repeating, both of these browsers inexplicably tried to stretch the 1×1 image across the entire container. The PNG happened to have 60 percent alpha transparency, but I’m not sure that matters. A coworker suggested making it a 10×10 pixel image instead, just to see what happens. Surprise, surprise. That fixed it.

Today we’re releasing the first beta-quality version of Firefox 4, which starts us down the path to a final release of Firefox 4. We’re handling this beta differently than we’ve done other releases. In previous betas we’ve made milestone-like releases. For this beta we’ll be making more frequent updates during the beta program

Test for browser redirection handling WRT URI fragments, quick and dirty.