Rainer Feike techblog

On my track to become a designer I released my first general drupal theme now. It a pretty dark theme that supports most core modules. Live test is available at http://www.gothnics.de.

Users told me they had problems with some online mail clients (like gmx and gmail) viewing mails sent with my MIMEMailxPHP4_V2 PHP class when cid (base64 coded inline) images are contained.
This bug is fixed now, you find the current (2.2) Version for download (it’s open source) here.

Testing before productive use is strongly recommended!

Actually I’ve lot’s of projects in my “web-queue” - but my favorite is EQUIRA. EQUIRA is a stock chart analyzer C++ software I wrote in 1999. It’s full of AI and FUZZY and GA (that’s Artificial Intelligence, Fuzzy Logic and Genetic Algorithms).
With the today available hosting technology and prices it’s ready for a public offering as webservice and a Drupal frontend for subscribers.

Stay tuned…

Today I read an article about IE8, the MS Internet Explorer that ships with Windows 7 (successor of Vista). The good news is, that it survives the ACID2 test, the bad news is, that it fails the ACID3 test embarrassing. While Firefox, Safari, Opera and Chrome meet about 70 to 80 of the necessary 100 goals, the IE8 meets 20/100.

So, the question is: Are Microsoft programmers lousy? Or is Microsoft still offending the Internet as far as possible? While I don’t think a great deal of them, I am sure they could do it better - BUT I am almost sure, that Ballmer is not willing to believe that times change. Fat client computing is dying, all what Microsoft does with their villainously products is delaying the agony.

They’re hurting the substantial progress of our society - just for their selfish vegetate. And they’re hurting us web developers by forcing us to support their crap.

Yesterday we went to public with another very complex Drupal 6 project. It’s kind of a “local collaboration” platform with classical news attributes.
Pretty much of the business is done in a self-developed module but we also use lot’s of contributed modules from Drupal.org:

cck - to create content types
checkbox_validate + legal - for registration issues
computed_field - for workflows and hidden attributes
content_taxonomy - for taxonomies in cck types
event - for events
fivestar - for content rating
flag - for flagging content for several reasons
flatcomments - to avoid comment-threading
image - for images
masquerade - for testing
mass_contact - for mailings
nice_menus - for some dropdowns as second level navigation
pathauto - for nice URLs
privatemsg - for user postboxes
quicktabs - for tabbed blocks in the sidebar
user_stats - for some forum enrichments
views - for customized views on cck types
votingapi - for fivestar
workflow - for workflows like published purchased content

… puh, that’s a lot - and there are still some modules missing.
Maybe you wanna take a look at isartal.info?

I’ve started to “refactor” my German IT consulting webpages with Drupal 6. Although the update frequency of V6 is still pretty annoying it’s a very stable system already. Most important contributed modules are at least in beta state.
I did a new theme from scratch and thereby got great support from the “devel” module and it’s “theme developer”.
The project runs on a multisite installation together with nine other D6 sites now.

Again I was using

• cck - for my project type and listings
• views - for views
• date - for cck date fields
• token and pathauto - for url naming
• image - for attached images

And as always I’ve written a supporting module to provide some data (like a month name array) and blocks.

(Illustration by Google)

Today Google released a new browser. Naturally I’ve downloaded it immediately (for Windows XP, here) - and it’s fantastic.
First impression: So so very fast, actually all pages are just there, there’s no progress to recognize.
Second impression: It looks different, it looks cool.

On the downside:

- There are no beloved plugins existing (firebug).
- Is Google watching me?

=> Think I’ll use it for browsing next time, but will still use Firefox for development (will never again use MS IE)

Other famous people who already took the survey:
Eloy took it
Myles took it
Thomas took it
Ashwin took it
Adam took it

And you should, too!

What we need

I am missing a syntax to apply a common ancestor to a set of rules. As far as I know, there’s no such concept in CSS selector syntax.

With the increasing usage of CSS definitions to style HTML markup, CSS files grow bigger and bigger. With this it’s getting more and more complex to find rules that apply the a special element and/or to have one’s code structured properly. When ie8 will support the more sophisticated locators like adjacent siblings or attribute selectors the locators and files likely will continue to grow.
Also CSS gets used in situations where you import content from several providers to display it inside one “mashup” site or (like in iGoogle or the Vista desktop) as “snippet”. In this situation one needs to separate the CSS rules of the different providers from each other and from the mashup’s home style.

Basically I want to grab remote content then wrap the grabbed sourcecode into a i.e. a <div id=”#GG”> and integrate that code together with it’s CSS in my site (or fridge display or whatever).

How it could work

The solution to this would be a ancestor grouping concept, i.e.:

ancestor "#GG" {
a { color: black; }
p { margin-top: 3em; }
}

This syntax should then expand to:

#GG a { color: black; }
#GG p { margin-top: 3em; }

Far more added value would be provided by the following construction:
ancestor "#GG" { @import(google.com/styles.css); }

or inside the HTML markup:
<link rel="StyleSheet" href="http://google.com/style.css" type="text/css" ancestor="#GG">

I think the goal should be clear now. Read the rest of this entry »

This is a “short as possible” reference for CSS selector syntax. Intended audience should be very familiar with XHTML, DOM and CSS Styling.

Basics

Type selector
Select all HTML elements of a special type.
Example: em {font-weight: bold;}
Class selector
Select all elements with a given class.
Example: .classname {font-weight: normal;}
ID selector
Select the one element with a given id.
Example: #idname {font-weight: normal;}
Concatenator
Select HTML elements of special type only with given class/id.
Example: em.classname, em#idname {font-weight: normal;}
Universal selector
Select all elements.
Example: * {padding:0;}
Descendent selector
Select all elements that are lower down in the DOM tree (descendants).
Example: p em {font-weight: normal;}
-> Applies to all em's within p's.

Advanced

Child selector
Select all elements that are children in the DOM tree (direct descendant).
Example: p > em {font-weight: normal;}
-> Applies to all em's directly within p's, not supported by ie6 and below.

Adjacent sibling selectors
Select all elements that are on the same DOM level in the same DOM subtree
Example: h3 + p {font-size:80%;}
-> Applies to all p's that "belong" to a h3
Read the rest of this entry »