uoba
Re: member
Serp... the CSS is now more easily worked with by using the CSS panel, rather than having to either open a window everytime you wanted to edit the css, or open the actual css file.
However, it pains me to say also that this version is now slower than the last! Okay, I have a 400Mhz G4, but I'm not the only one!
I am reckoning that MM's attempt to get the lovely anti-aliased text in DWMX 2004 has blinded them... I don't care about anti-aliased text inside what I'm working on! I actually like the effect of being non-aliased and then going into Safari and seeing the fruits of your labour aliased correctly.
However, the interface is a hell of lot better/intuitive/logical. Anyway, back to testing in it (and saving up for a g5 to run it )
EDIT:
Actually, I think it's MM's labour in trying to make CSS render correctly within the app rather than just in your browser, that's slowing the whole thing down. Whilst we need css rendered correctly (rather than having to constantly go to the browser to check small css changes), I'd rather it not be at the cost of speed.
However, it pains me to say also that this version is now slower than the last! Okay, I have a 400Mhz G4, but I'm not the only one!
I am reckoning that MM's attempt to get the lovely anti-aliased text in DWMX 2004 has blinded them... I don't care about anti-aliased text inside what I'm working on! I actually like the effect of being non-aliased and then going into Safari and seeing the fruits of your labour aliased correctly.
However, the interface is a hell of lot better/intuitive/logical. Anyway, back to testing in it (and saving up for a g5 to run it )
EDIT:
Actually, I think it's MM's labour in trying to make CSS render correctly within the app rather than just in your browser, that's slowing the whole thing down. Whilst we need css rendered correctly (rather than having to constantly go to the browser to check small css changes), I'd rather it not be at the cost of speed.