News
-
Area Sales Director ( Healthcare Industry)
CA-Los Angeles, Sandel Medical Industries is looking for an Area Sales Director ( Healthcare Industry) in our Chatsworth facility. Sandel Medical Industries manufactures and sells innovative consumable medical safety ...........more
-
"Real-time" Linux to support new PowerPC SoCs
MontaVista plans to offer its commercially supported "real-time" Linux distribution for a pair of forthcoming AMCC SoCs (system-on-chip processors). The PPC405EX and PPC460EX respectively target WLAN and printing/imaging/networking applications, and will be the 22nd and 23rd AMCC chips supported by MontaVista Linux.
-
The CSS working group is irrelevant
Back in March, Google hosted the CSS working group for a three daymeeting.At the time, we were just starting with the HTML working group, andthe openness of the WHATWG over the past few years was just startingto be adopted by the HTML working group, after several months ofpushing for it in the W3C (mostly in secret, thoughmyownpostsonthematter were all public, as wereafewothers).One of the things I brought up in the CSS face-to-face meeting wasthe problem of the CSS working group not being open. Many of themembers of the CSS working group have a mentality that view the Webcommunity (such as those who e-mail thewww-stylemailing list) as aresource, not as potentially equal membersof the community. Of the forty or so members of the working group(those subscribed to the secret internal mailing list), only a dozensubscribe to the public list. This actually makes itharderfor members of the group to try to be more open— when someoneposts a proposal to the public list, there's a good chance that themajority of the members of the working group will miss it. During themeeting, I opined that if the group continued along in this direction,the group ran the risk of becoming irrelevant; two of the othermembers suggested that the group wasalreadyirrelevant. Sadly we were in the minority.The CSS working group right now is chronically dysfunctional, asmost close observers havenoticed.A great example of this is the difference in how the WHATWG got ablogand how the CSS workinggroup set one up. In the WHATWG, the idea was floated for a while, andthen one daysomeonevolunteeredto run it, and the blog was up and running within hours. Anyone(literally anyone) can post to the WHATWG blog (there's a moderationstep that we added to deal with the spammers, but all it takes now istoget onto IRCand askfor the post you wrote to be published). The CSS working group, on theother hand, has been discussing how to set up a blog, and what thefirst entry should say, and what tool to use, for overtwomonths! Nearly every phone call (the group has weeklyteleconferences) for the past nine weeks has had the blog discussed atsome point.The blogwas finally madeavailable last week. To post, you have to be a group member. Thefirstpostcan be summarised as follows: the CSS working group membersdon't want to bother going out of their way to get feedback on theirspecs; instead, people should post their comments on CSS to the publicCSS mailing list (despite the fact that most CSS working group membersaren't subscribed to this list). The blog post then goes on toapologise for the blog's existence, and claims that the blog's aim isto reach the people who won't subscribe to the public mailing list(the working group itself, maybe?). The post doesn't make it clearhowthe blog is expected to reach this wider audience, sincethe blog has no comment feature.Another example of the problems of the CSS group is visible on theW3C'sTechnical Reportspage. Thegroup's primary deliverables are specifications. The last candidaterecommendation published by the group was published in 2004. That wastheBasic UImodule, whichwas Tantek's baby (he has since left the group). Meanwhile, draftslike theBackgroundsand Bordersdraft, which has had big parts implemented by Safarifor months, and small parts implemented by Mozilla for years, haveiterated several times but make no public process (the backgrounds andborders draft was published in 2005, but the internal draft was lastmodified in February of this year).Meanwhile, CSS2.1, the working group's most important deliverable,keeps getting tied up, with the group discussing irrelevant detailsand some members repeatedly reopening old resolved issues. The W3Cprocess doesn't help much here either; the group actually tried takingCSS 2.1 to Candidate Recommendation stage recently, but was blocked bythe W3C management over an issue which was already present inCSS2. (In all fairness toTim, the issue heraised is one which was already raised by several other people, butwhich the group had dismissed. I actually agree with him that itshould be resolved. The group has since resolved to change the spec ina way that continues to leave the issue undefined, but at least it nolonger contradicts what Web browsers do.)The group is also supposed to work on test suites. I hadvolunteered to work on the CSS 2.1 test suite, but due to lack oftime, I bailed on that last year (Google mainly employs me to work onHTML5; any test work that I do is done in my free time, which ismostly spent nearaquariumsnow). Sincethen basically nothing has happened.Being public would expose a lot of these problems, forcing theworking group to act more responsibly. It would also allow people tocontribute— as specification editors, as test suite editors, asreviewers, as community leaders, and in other roles.But to be honest, the problems go even further than what I'vedescribed above.The CSS specs show their age; they come from a time wherespecifications were much vaguer than those of the modern day. Someonereally needs to do to CSS what the WHATWG has been doing to HTML,defining everything in detail, explicitly, with strict and clearnormative conformance criteria, taking implementations into account,defining things like quirks mode. (The WHATWG community refers to sucha hypothetical project as"CSS 5", as a reference to the way thecurrent WHATWG specs define HTML5, XHTML5, and DOM5 HTML.)The CSS working group also doesn't really have the nimblenessneeded to respond to threats to the Web platform like Silverlight. Weneed things like flowing-to-shapes, automatic declarative transitionanimations, gradients, filters, styling of form controls, and soon. (The WHATWG is already handling some related, non-presentational,things, likeclient-sideSQL databases,video,andrichcontrols.)We need these thingsthis year, in enough detail that theycan be implemented. An open group can iterate much faster than aclosed group. With an open group we can get test implementations,feedback, tests, and discussion straight away, instead of waitingmonths and then pulling back the curtain and presenting afaitaccompli, at which points comments are perceived more as a painthan a help.One way to address this would be for theWHATWGto start a"subproject"to address CSS, while we wait for the W3C CSS group tolearn from the W3C HTML group and become open. The biggest problemwould be finding editors who would be willingand capableofdoing the incredible work of rewriting CSS from scratch.
-
Four more cops arrested for drug trafficking in Mexico
Xinhua News Agency Sep 19 2007 2:57AM GMT
-
Lisya Anggraini - Siar : (3) Etalase Ramadan
Etalase RamadanLisya Anggraini (Jurnalis, Penulis, Wakil Ketua KPID Kepri) MARHABAN Ya Ramadhan…Alhamdulillah, kita masih diberkahi panjang umur untuk menjelang Ramadan tahun ini. Bulan untuk mengisi kekurangan-keurangan ibadah-ibadah yang compang-camping, dan ritme turun naik kebeningan hati, sekaligus saatnya untuk melabuhkan segala kesah dengan harapan pintu keberkahan dibukakan lebih-lebih luas lagi, untuk mohon ampunan. Persiapan Ramadan pun dilangsungkan dimana-mana dalam bentuk macam ragam. Sekalipun persiapan yang paling inti hanyalah niat untuk memperbaiki ibadah. Tapi apa lacur, jika kemeriahan penyambutannya justru membungkus yang hakikinya. Rumah-rumah hiburan ditutup, rumah makan juga dihimbau serupa jika pun tetap berjualan jangan terlalu menyolok. Namun, kota ini masih lebih tolerir dibanding Kota Banjarmasin yang lebih saklek. Atas dasar hokum berupa Perda no 4 tahun 2004 tentang Ramadan, menyiapkan sanksi hukuman kurungan tiga bulan dan hukuman dend...