Are there any issues with regarding using the new Studio 8 with the latest version of Actinic? Is it still fully compatible? Cheers, Richard
Announcement
Collapse
No announcement yet.
Macromedia Studio 8
Collapse
X
-
Hello Richard,
You might want to check out this thread http://community.actinic.com/showthr...ht=Dreamweaver
Myles
-
I have just moved up from DW 4 to DW 8 and it has changed a lot. I like the dynamic links to the CSS file, was this in earlier versions? This will certainly improve productivity.
I have always done most of my work in code so all these bells and whistles are quite remarkable. The validation comes up with some unexpected results, such as not liking <BR /> and other similar closed tags.
Having read another thread about a possible issue with the Actinic extension I have not tried this yet. So far I am quite please with what I have seen.
BobSupporting the environment. This post uses 100% recycled electrons.
Bob Isaac
Director/Web Admin
Volvo Owners Club Ltd
Actinic MS Business Version 8.5.2
Comment
-
Originally posted by jontRichard - how do you find the new CSS stuff in Dreamweaver?
Comment
-
Originally posted by Stealth-F117I have started to use Dreamweaver MX2004 after using Netobject Fusion for over a year - have to say Dreamweaver is miles better
Comment
-
I have stuck with the 'old ways' of doing things for a long time, never liked the way some of the web design apps have taken control away. But with the more complex designs that can now be created I find that DW8 is going to get a lot of use.
The way it handles CSS is simply great. I only use the 'enter', space bar and down arrows keys now most of the time.
One thing that puzzles me is that with the automated system of inserting values and attributes, the validator still pops an error that the value/attribute it just inserted is not valid??
BobSupporting the environment. This post uses 100% recycled electrons.
Bob Isaac
Director/Web Admin
Volvo Owners Club Ltd
Actinic MS Business Version 8.5.2
Comment
-
Originally posted by Bob IsaacThe validation comes up with some unexpected results, such as not liking <BR /> and other similar closed tags.
Comment
-
To be very very pedantic you should use <br /> as this is an empty selector tag and will future proof you - but it will work as <br>.... the XHTML rules say you should use <br /> to be syntactically correct ... although <br> will work just fine at the moment.
I've used <BR /> for some time now. I would be interested in others views on this.
BobSupporting the environment. This post uses 100% recycled electrons.
Bob Isaac
Director/Web Admin
Volvo Owners Club Ltd
Actinic MS Business Version 8.5.2
Comment
-
-
You say the validation throws up <br /> as invalid - are you validating using XHTML or HTML specs? That's about the only reason i can think of that it wouldn't like it.
And yep, if you're writing XHTML-compliant code, all tags should be closed. The examples i would have given are the same as on the W3 site that Jont posted above, <img /> and <br />
<br> and most other older or deprecated tags (<font>, et al) will continue to work in most browsers, but only because they still support old tags for ... backwards compatibility, i guess.
I've been creating XHTML-compliant sites for a whiley now (not my work one, sadly impossible) - it keeps you honest and encourages a solid coding style (nesting elements properly, and promotes the use of CSS).
Comment
-
Thanks for the links. I have tried using all the options in DW8 for validation of XHTML but it still throws up the error. Never mind, the pages display correctly in all the regular browsers.
BobSupporting the environment. This post uses 100% recycled electrons.
Bob Isaac
Director/Web Admin
Volvo Owners Club Ltd
Actinic MS Business Version 8.5.2
Comment
Comment