Stephane Bortzmeyer wrote:
> On Mon, Feb 05, 2007 at 06:47:29PM -0800,
> Diane Ross <[EMAIL PROTECTED]> wrote
> a message of 39 lines which said:
>
>> SAVE EVERY STEP with an OWN VERSION NUMBER!
>>
> A better advice may be to use a real Version Control System, for your
> HTML pages and your CSS stylesheets. A version number does not tell
> much ("What is version 567?" "When did I change the color scheme?"). A
> VCS is much more powerful (for instance, you can attach a text to each
> change, the date is automatically set, etc).
> [...]
>
Hi Stephane,
The most important part of my advise is "save every step": do it! The
way _how_ do to this, is at choice. Can be with a version #, can be with
a VCS. While I'm not working in huge projects with many contributors,
I'm happy to give just quick version numbers without spending time to
describe what I changed.
But it's true: to be 100% correct, I should have written: "... with an
OWN VERSION _INDICATION_ (version number, or version date, changing
description, and so on; or a combination of these)". - So thanks: I'll
add the VCS-option to the Golden Rule as another option.
> [...]
> The page you mention has other strange advices such as:
>
>> To see where you are: use TEMP BACKGROUND COLORS for the div-boxes,
>> ul's, li's and other elements.
>>
>> Sometimes a TEMP {border: 1px dashed red;} can do the same. - But
>> that is a bit more risky, because adding or removing borders can
>> influence the layout (suddenly dropping or lifting of an element can
>> be the result, or appearing or disappearing of paddings with
>> unintended backgrounds).
>>
>
> While it is much simpler (and cleaner!) to use a browser extension
> such as Firefox's WebDeveloper (with its Outline function).
>
For a quick problem shooting sometimes the Outline function in the FF
WebDev (apart, or in combination with the edit functions) can be very
handy, but to be sure, I prefer a real change in my code, and real
testing in different browsers:
* The Outline function sometimes causes a dropdown of one or more
elements (because of the with of the border line), in case a page
has a narrow layout. [1]
AFAIK, a background color is never changing the width or height of
an element, and even for IE there is no risk.
* With the FF WebDev under my WinXP (and before under Win98SE),
sometimes background-img parts of the page are disappearing when
the window format is changed on the fly; then the Outline alone
can be not enough for analyzing and playing with margins and paddings.
* I cannot save the outline version of the WebDev.
* I want to see the result of a change in hard coded html /css, to
compare browsers - often a browser difference has to be eliminated.
With respect to my "strange advices": I agree, they aren't all "clean
coded". - But that's just for building, bug hunting and testing purposes.
As long as "unallowed methods" (as the X-out method) are helping me to
get a page faster to what I desire, then a tmp pollution doesn't matter
for me. [2]
Afterwards the strange elements can easily be deleted: to get clean,
valid and crossbrowser pages in the end. - Nobody knows! :-)
Greetings,
francky
[1] Yes, I always should make pages which have some liquid freedom; but
I'm testing pages of others too. ;-)
[2] Together with tools as the WebDev extension, the dirty comment-out
methods are saving about 40% of my analyzing time, I guess. But maybe
for more experienced coders it doesn't make any difference. Let
everybody follow his/her heart...
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7 information -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
