If you have two documents that you want to compare, winmerge does an
excellent job. It highlights the differences between the two documents
and then you can choose what you want to copy back and forth between the
two. I have used it extensively for programming and all sorts of other
little pr
Spike, et al
On Jan 19, 2006, at 05:08 AM, Spike Spencer wrote:
>I recently consolidated a 30KB CSS file form over 1300 lines
>of code to just under eight hundred.
With all this talk of text editors, I sure don't see how that is going to be
much help at all. Spike needs some way to see the OUT
Eric, et al
On Jan 19, 2006, at 11:49 AM, Eric Vann wrote:
> Yep. The product I use is called BBEdit and runs on the Mac. It has an
> automated DIFFERENCE (i.e. DIFF) function which displays each file
> in a
> separate window and shows the lines which differ. Clicking on that
> line in
> the
Joe Otten <[EMAIL PROTECTED]> on Thursday, January 19, 2006 at 10:42 AM
-0600 wrote:
>WinMerge has saved me hours of time in regards to comparing scripts
>[ http://winmerge.sourceforge.net/ ]http://winmerge.sourceforge.net/
>
>Good Luck
Yep. The product I use is called BBEdit and runs on the Mac.
I often compare two files like yours using a simple text editor that
allows me to do a line-by-line comparison of both files. Of course if you
have altered the new file structure enough even this doesn't work.
__
css-discuss [EMAI
Spike Spencer wrote:
> Thanks for any help.
Not to be cruel -- sounds like you spent some time to do this, but
perhaps in the future a better method would be to pick smaller segments
of the css, make your changes, then test, repeat. It is always easier
to divide big problems into little pro
On 1/19/06, Spike Spencer <[EMAIL PROTECTED]> wrote:
> Is there any quick and easy way
> for me to compare the stylesheets and see what style information has
> changed? The structure of the document has changed entirely so I can't
> do a quick and dirty VBScript unfortunately.
Are your files stor
you could try running them both through a formatting tool and perhaps
alphabetically arranging them (which ruins the order css is read in,
so don't keep it this way. but it will be easier to compare).
http://www.lonniebest.com/FormatCSS/
___
I recently consolidated a 30KB CSS file form over 1300 lines of code
to just under eight hundred. I was doing it on autopilot and without
XHTML from the gimps in the programming office to check it on -
predictably, something has gone wrong. Is there any quick and easy way
for me to compare the styl
