mapcore... mobile?

[dissonance]

well, i just got wap for my mobile, but the default mapcore layout is hard to follow.

i was wondering if anyone would mind adding a mobile css file to the site? i'll even code it, if need be.

[Mojo]

hmm novel idea

[Izuno]

yes i need mapcore on my Treo so I can keep track of posts while at client meetings...so when someone has a jackass point in a meeting that I think can be disproved via a recent mapcore post, I can show him the error of his ways.

Seriously, that would be awesome!

[hessi]

well, i just got wap for my mobile, but the default mapcore layout is hard to follow.

i was wondering if anyone would mind adding a mobile css file to the site? i'll even code it, if need be.

the problem:

mapcore uses tables instead of a proper 100% css layout. so a mobile version would require a complete layouting rework from tables to css.

[dissonance]

hmm.

well, it could still be done.

[⌐■_■]

any volounteers?

[dissonance]

i can try when i sober up

[Fletch]

pssh, don't even bother with CSS. Microsfot is going to fuck up CSS standards when they put IE7 out.

[dissonance]

slightly redundant: so? if it's not standard-compliant, why even bother considering it?

[Fletch]

slightly redundant: so? if it's not standard-compliant, why even bother considering it?

Because MS is throwing around their considerable market share to get the standards changed in their favor. IE7 will be the new defacto internet browser (downloaded via critical update and bundled with Vista). Sure, it's a dickheaded thing to do, but they're doing it anyway. Big companies can't afford to have their sites be non IE7 compliant.

[Thrik]

The CSS situation isn't as bad as you're making it out to be Fletch. Internet Explorer 6 already has bad CSS support, and web developers have gotten used to working out ways of compensating for the issues and producing pixel perfect layouts across all three browsers — or at least close enough.

IE7 is in fact a step up from IE6's poor level of compatibility and fixes a lot of CSS rendering bugs that've been tormenting the world for years. It's unlikely all browsers will render the same anytime soon, but you're acting like it's some crippling issue. IE7 is a good step forwards for CSS, not a bad one. Baby steps, but at least it's not in the wrong direction.

If the worst comes to the worst, you can use CSS that's ignored by all browsers but IE to override a few specific problem areas.

[dissonance]

Hurmmm.

Anyone know a good way of doing lists in xhtml?

seems to be buggy.

Also (as luck would have it), my phone won't turn on now, so I'm sending it in for repairrs. I'm working on a page, but it will be a while until I can test the css.

[Thrik]

There's nothing buggy about

in xhtml, it's just the browsers have trouble all rendering them the same. The best way to get them looking identical in all is to do this:

ul {

margin: 0;

padding: 0 0 26px 0;

list-style-type: none;

}

li {

background: url("/images/design_bullet.gif") 1px 10px no-repeat;

padding: 0 0 0 16px;

}

And then change the background image URL to an image of a bullet. Otherwise the browsers will use their own kind of bullets which all look different and use their own default margins, etc. With the above method they should look exactly the same across the board.

[dissonance]

ah-ha.

thanks.

working on the structure now (without frames ), and i'm close.

[Mojo]

cool beans