On 10 Jul 2008, at 01:28, hugh wrote:
Web-Kit based browsers…what on earth are they!!
Hugh, this has an air of High Court Judge about it: “The Beatles,
m’Lud? A popular beat combo, I believe.”
Well, I’m absolutely gobsmacked if some fairly basic CSS (all the
rage?) can’t be made to work in all browsers.
Well, you could say that nothing can be made to work in all browsers,
or you could say that enough can be made to work in all browsers that
it isn’t worth worrying about what can’t.
To be honest, I think I’ll ditch the CSS and go backwards and make
stuff, at least it will work in IE and Firefox!
Hugh, it’s OK to use old tech if that’s what you like, but it does
mean that you’ll run into ever-increasing problems, and that in turn
will put you off the ‘new tech’ even more, because it will look as
though it’s that that’s causing it. Kind of a vicious circle.
I haven’t followed this thread that closely, so I may be talking out
of turn, but I can’t figure out why you’re using Source Code Snooper
to make a menu that you could easily bang out in five minutes using
Freeway 5’s CSS menus? Or even the old table-based action in Freeway
4? Surely this complicates your site unecessarily, and seems to be
leading to all kinds of stuff that needn’t be.
CSS is not ‘all the rage’ as you put it, it’s the way to write Web
sites. It’s easier to troubleshoot, it’s easier to learn, it’s easier
to write, and browsers like it better. What’s not to like? You can’t
ditch Webkit, because a huge part of your audience uses it. It’s also
brilliant, and not something you’d want to avoid.
I’m no expert on CSS. For years I used to swear that I’d never code.
Didn’t have the time or inclination, and it was like another language
to me, literally, and I really thought I was too old to start learning
another language. Then I had a foray into another Web app,
Rapidweaver, and found that I needed to tweak a lot of things because
it’s template-based and, well, you do, don’t you?, so I asked
questions on the (excellent) RapidWeaver forum and, from the answers I
got, and from reading previous posts, I suddenly ‘got it’. I don’t
mean that suddenly I was an expert; I’m far from that, still. But the
way CSS and HTML work together is something you can ‘get’ in ten
minutes. It happened to me by accident, I learned the little I know by
osmosis. The surprising thing was that it was neither a chore, nor
difficult, which is rich coming from a true codeophobe. I still don’t
know all the ‘terms’, but that’s simple - I have an little free
Dashboard widget that will let me look up any ‘name-of-a-style-part’
that I’m unsure of. The main thing to know is the actual syntax, which
is the bit I ‘got’ in about ten minutes on the other forum. It’s as
easy as learning the ‘i before e except after c’ or ‘never start a
sentence with a preposition’ or ‘plurals don’t have apostrophes’
rules, although that last one seems to be giving some of us a bit of
trouble these days …
Anyway, the upshot was that, while I get a kick out of RapidWeaver,
Freeway remains firmly in my arsenal, but the CSS knowledge I picked
up there now informs what I do in Freeway, which to me is a very fine
I urge you to give it a go. I’d be happy to explain more about what it
was I suddenly ‘got’, either on-list or off. Best of all (and this
from a staunch non-coder): it’s really satisfying, and above all, it’s
fun! And I mean it about helping; I’d love to help if you want it.
Believe me, this stuff frees you up.
I’m intrigued — what’s ‘pmsl’?
freewaytalk mailing list
Update your subscriptions at: