Пробная запись с картинками про время

another_one — Thu, 26 Jan 2006 19:11:17 +0000

Since a few months I have been ignoring the support forums on drupal.org almost completely. Same for the support mailinglists.
However, my amount of support has increased a lot. I have been spending an enormous amount of hours on a much «lower» and more personal level of support. Mostly in Dutch, nearly completely on skype, jabber and by mail.

I was very reluctant in the beginning, about this way of support. First of all, the forums are considered to be better, because they are archived, and available for future. In reality, however, I see the same questions popping up more and more. I see an increasing number of questions asked that are never answered, too. The mailinglists support issues, are most of the time either completely RTFM questions or are of a higher level, a level that is very specific for the sender.

NowPublic launched their new website today! Think of NowPublic as a combination of Slashdot, Digg and Flickr (albeit not as popular yet). Contributors share the news they read as well as original content that they write, creating a popularity index or «best of the news» which readers can then view by the subjects and locations that interest them. In addition, members can also contribute to any story by adding audio, video, and photos. Of course, they are using Drupal.

(Disclaimer: I am an advisor to Nowpublic.)

Еще одна проверка от еще одного

another_one — Wed, 25 Jan 2006 22:59:13 +0000

Common JavaScript character sequences get transformed into something strange, as Textile uses a lot of character sequences which are highly rare in written English, but not so rare in JavaScript. An example would be the use of the plus sign for inserted text – causes problems when demonstrating string concatenation. Again, this sort of stuff should be ignored within a code block.

The other main issue I had was that no every Textile device allows for the application of an arbitrary class name. Or at least, if they do it’s not properly documented. This was particularly a problem when it came to using Microformats, which rely heavily on classes. This left me mixing and matching Textile formatting with regular HTML, which was fine for my purposes, but would cause problems in situations where you’re not always planning to transform to HTML.

Of course, nothing was compelling me to use Textile – I could have happily continued using Textpattern and formatted everything myself in HTML – but I figured that even with messing around that would take me longer.

Textile is immensely useful for so many things, but having hit some of its limitations, I think that it could really benefit from almost being a project of its own, with people focussing on developing it and maintaining the various releases and applications. Its adoption is becoming so widespread, I think without being actively maintained we’ll end up in a mess in a few years time. And Textile is something the world really needs.

another_one's blog

Пробная запись с картинками про время

Еще одна проверка от еще одного