Jim Groom, who administers the UMW group of WordPressMU blogs has placed a whole slew of videos online, which help users with WPMU, as well as migrate from WPMU-1.3.3 to WPMU-2.6.
The inimitable Andy Rush (a.k.a. EduRush) and I have been working diligently to create a whole slew of screencasts documenting the new interface for WPMu 2.6. Weâ€™ve finished a whole bunch of them over the last week or so and published them on the now official UMW Blogs Screencasts site, so below is a list of the screencasts we have created. All of the screencasts are Creative Commons and while theyâ€™re currently published as SWF files, we will be uploading them all to Blip shortly. Keep in mind that these screencasts are specific to the UMW Blogs installation, but they still may prove useful for anyone who wants to point people to a quick overview of the administrative backend, the changes between versions WPMu 1.3.3 and 2.6, and a very tab-specific discussion of the how to manage a WordPress blog.
This seems like a bad idea to me… It’ll make domain names that much more difficult to remember… Ah well… that’s progress!
Board opens way for new top-level domains – Network World
I, Cringely . The Pulpit . It’s the Platform, Stupid | PBS
Cars are the key to U.S. energy consumption. The dominant automotive platform here, whether you drive a truck, a car, or a motorcycle, relies on gasoline-fueled internal combustion engines. That’s the platform we are unlikely to change quickly. So how do we leave that platform intact and unchanged, ask nobody to significantly sacrifice, yet still achieve the noble (and Nobel) goals of lower fuel consumption, lower greenhouse gas emissions, lower pollution levels, dramatically lower oil consumption, lower cost, and lower geopolitical vulnerability for our country? There’s only one way I know to accomplish this: change the fuel.
This happened to a certain extent in Brazil during the ’70s and ’80s by embracing ethanol. But ethanol has less energy per gallon so fuel consumption goes up and mileage goes down. Ethanol can’t be shipped in pipelines also used for oil. Cars have to be modified to run on it and even then there are issues about internal corrosion. Ethanol is far from perfect. What’s needed is a replacement for gasoline that looks and feels and tastes just like gas to your car but isn’t made from oil. Then the platform could remain completely unchanged yet my 1966 Thunderbird (and the world) could benefit starting with the very next tankful.
There is such a fuel, developed by a husband and wife team of scientists working in Indiana in cooperation with Purdue University. This new fuel, called SwiftFuel, is right now intended for airplanes, not cars, but the lessons are the same.
This is a really great article on how to hack IE7. CSS Hacks and IE7
- The Child Selector
This selector uses a “>” symbol as a “combinator” that is placed between two parts of a CSS selector, and indicates that the target of the rule is the element on the right side of the “>” combinator, but only when that element is a direct child of the element to the left of the combinator. Thus, the selector table>td can never target any element, because TD’s are never direct children of tables, only of TR’s. On the other hand, the selector tr>td would select every TD on the page, since all TD’s are direct children of TR’s.
The main difference between the Child combinator and the familiar space combinator is that the space combinator is a “descendant” combinator, meaning that the element to the right of the space only needs to be between the tags of the element on the left to be selected. So with the selector tableÂ td, all TD’s will selected, since TD’s always fall between the tag pair of one table or another.
The Child combinator is quite useful for targeting rules to direct children of an element, without also targeting the more deeply nested descendants as well. Unfortunately, up until IE7 there was no point in using it for its intended purpose, since so few of the viewing public would get the benefits of the styling.
- This selector is a “+” combinator symbol placed between parts of a selector, and is very similar to the Child combinator. The only difference between the two is that while the Child combinator points to direct children of an element, the Adjacent Sibling combinator points to an element which directly follows another element in the source.
Thus the selector tr+td cannot select anything, because no TD ever directly follows a TR. Instead, TD’s are contained inside TR’s, and that is not considered to be “following” the TR. However, the selector tr+tr would select any TR that directly followed another TR, which means that every TR within a table would be selected except for the very first TR in that table.
Get it? An adjacent sibling element not only follows its previous sibling, but is also completely separate from it. Further, if two DIV’s are in sequence and each contains a paragraph, those two paragraphs are not considered siblings, because they reside in different parent elements. The fact that one follows another means nothing unless the following sibling starts at the same point where the previous sibling ends.
- Star HTML
Oh, you want to know about that structural thing? Well, the hack that uses it is called the star-html hack, and it works by taking advantage of an oddity in Explorer’s treatment of the DocumentÂ ObjectÂ Model, or DOM for short. Simply stated, all web pages start with a root element called html, which then contains two children, the head and the body elements. Those two then contain other children, and so forth.
Most browsers obey this arrangement, but Explorer for both Win and Mac do not. They seem to think there is a mysterious element enclosing the html element! It’s pretty strange, but in fact this extra outer “root” element has no apparent ill effects on web pages, and remained unnoticed for years, until EdwardsonÂ Tan began experimenting with CSS selectors. He found that a selector written as *Â htmlÂ Â .targetelement would apply the styles to .targetelement, but only for the IE browsers.
Think about it. That star is the “universal” selector, so it points to any element, but it comes before html. Therefore, the full selector in effect says: “Select .targetelement when it is contained within html, and when html is contained within any other element”.
iBanjo Â» Blog Archive Â» Subversionâ€™s Future?
I have to say, after using Mercurial for a bit, I think distributed version control is pretty neat stuff. As Subversion tests a finalÂ release candidate for 1.5Â (which features limited merge-tracking abilities), thereâ€™s a bit of angst going on in the Subversion developer community about what exactly the future of Subversion is. Mercurial and Git are everywhere, getting more popular all the time (certainly among theÂ 20%Â trailblazers). What role does Subversion â€” a â€œbest of breedâ€ centralized version control system â€” have in a world where everyone is slowly moving to decentralized systems? Subversion has clearly accomplished the mission we established back in 2000 (â€to replace CVSâ€). But you canâ€™t hold still. If Subversion doesnâ€™t have a clear mission going into the future, it will be replaced by something shinier. It might be Mercurial or Git, or maybe something else. Ideally, Subversion would replace itself. If we were to design Subversion 2.0, how would we do it?
Last week one of our developers wrote an elegant email that summarizes a potential new mission statement very well. You should reallyÂ read the whole thing here. Hereâ€™s a nice excerpt:
Reuters CEO sees “semantic web” in its future
This is an interesting article on the Semantic Web, and where news feeds appear to be going.
Growing Pains: Can Web 2.0 Evolve Into An Enterprise Technology? — Web 2.0 — InformationWeek
Wikis, mashups, social networking, and even Second Life can have a place in business, but they need to improve legacy interoperability–and IT needs to overcome its skepticism.
TinyMCE is a powerful WYSIWYG editor control for web browsers such as MSIE or Mozilla that enables the user to edit HTML contents in a more user friendly way. The editor control is very flexible and it’s built for integration purposes (usage within systems like Intranets, CMS, and LMS, for example).
TinyMCE:Installation – Moxiecode Documentation Wiki
This is the Text Editor available for WordPress posting (Visual Edit mode). Pretty neat. Perhaps we’ll add a few items…
Here’re some more interesting TinyMCE links:
Perhaps, if I can ever find some time, I’ll be able to play around with this stuff.