[Michel Fortin]

I'm using the trial version of Golive CS but my experience with it is not great at all. Here are my two problems:

1. In the site view, it seems there is a bug that makes every folder repeated two times the second time I load the site in the application. I can refresh the view so that it eliminates the duplicates but then the folders shows up empty. That's for a newly created site. :-(

2. CSS rendering is much better in this version, but for me that's worse. In fact, Golive now use all the tricked styles that make the site work well in IE, but shows them all different than in IE making pages almost uneditable. There is a way to disable some rules in the stylesheet so that Golive ignore them but that's forgotten after the site is closed. Fortunately it's as perfect as it can be in preview pane, but I'm not buying that thing for the preview.

I'm sincerely disappointed and I'm not sure how the real product (that should arrive soon) would be better... any suggestions?

[philzilla]

Originally posted by Michel Fortin:
any suggestions?

here's one

[york28]

Doesn't the built in preview use Opera's rendering? (Not sure, but I think Dreamweaver does too.)My suggestion would be to preview in an external browser, which you'll probably be doing anyhow.

Who knows why they did this instead of using Safari, probably due to project deadlines. But it's not really very useful, since most of the time web developers have to make sure things look good in Windows IE. the more standards complient browsers seem to mostly take care of themselves.

(edit: completely misread your post, Sorry about that.)

[Michel Fortin]

Well, I managed to recover from the first problem by refreshing the view. It worked this time but it's still misterious.

The second problem would be solved if I was able to hide some style rules from Golive. It seams that Golive implemented it's CSS parsing to match in some part the one Internet Explorer. Something totally non-standard compilent like below is treated as it was valid... but since I used it to put some rules to correct bugs in IE with floats, they contain things Golive would better be not seeing.

Code:
* html #container { some rules here }

The other major problem I have is that the max-width rule is interpreted by Golive as a width rule and that's not good for layout.

And I can't switch software so easily since I'm not the one who update the site. I somewhat doubts Dreamweaver would be better with these stylesheets.

[daload]

Dreamweaver in a design aspect point of view is much more superb than GoLive could be in any soon to be moment.

Seriously as an Avid designer/coder I have used both extensivly on many a proj.

But when it comes down to it, dreamweaver (MX) does a much more clean and simpler job, and quicker.

It works nicer and has a few little things I really like, such as the ability to make SSI pages editable directly in a design view.

Im not biased, just I have learned enough from both programs to offer insight on both.

Is it just me or does (did) GoLives file structuring technique piasse any one else off either?

[RGB]

Extensive use of both over the years has led me to love GoLive's editing of tables, and hate Dreamweaver's. But since I'm not laying out sites with tables anymore, I can use either, preferrably Dreamweaver for hand coding though.

[MacDog]

The thing that annoys me the most about GoLive CS is that the entire user interface seems to have shrunk, as in "I need to get better glasses, or perhaps a high-powered microscope to see what the hell all the buttons, menus and palettes do"

And that's the other thing... wtf is with all the palettes? This app used to be a pleasure to use, but it's gotten way out of control now.