2 ms·
You say this now, but unless you have crystal ball you can't look into the future. I've worked in many places where something is designed, shelved, resurrected
by kamjam 15y ago
You say this now, but unless you have crystal ball you can't look into the future. I've worked in many places where something is designed, shelved, resurrected several months later, design tweeked, shelved, budget approved, resurrected...
Anyway, we're not talking about a thing between designers alone, we're talking about the fact that a lot of designs are passed on to developers to then code in html. You yourself highlight the fact that designers may not be familiar with browser incompatibility. We they can't factor these into the design then IMO it's pointless having them create the html.
That said, I agree with many points, like naming files properly (which costs almost nothing)
So naming files costs almost nothing nothing, but naming a layer correctly in the first place is a pain in the arse/takes up too much time... not much consistency to your logic here. As I recall, hitting F2 will take you into rename mode.
As gnaritas says, name it properly in the first place then there is no need to rename!
- _johnny 15y ago> not much consistency to your logic here It is logical, because there are often hundreds of layers and presumably even more during the design process. Naming each one is a lot of work. There are much less files in the end so it's totally different.