What's in Store for Dreamweaver's next release

[haleyt88803336]

Does anyone know what future features and functions will be in the next Dreamweaver release of update ?

Just curious

[pziecina]

I do enjoy it when we have these discussions Ben, so please don't take any offence as none is intended .

If we always agreed then such discussions would be boring.

[pziecina]

http2, would you belive because it is still only a draft spec from the, 'internet engineering task force' -

http://http2.github.io/http2-spec/index.html

as are all the other items you mention in that section. Keep up with who is now responsible for what please.

The reason i object to open source being built into the core of Dw, is because they change over time, and the Dw team has no control over them. Naming those other failed items, shows the folly of including features that will become outdated.

Editing the sass/less files from bootstrap, and using those to create the css file means that without Dw including a feature to strip out all the unused css, they are creating an exessively large css file for the end user to download. Great if you know all your users are on hi-speed connections and unlimited data plans, lousy for those who have to develop for unknown connection speeds and end users with limited data plans.

Design/live view as many users have said is not up to the job anymore. As for extensions, as has been pointed out before, they are necessary for many users, but are also limiting in what they can do. Great if they do everything you require, no use if they do not. Brackets does not discover dynamically related files, visual studio code, (which is also free) does, it even discovers related javascript files, does Dw do that?

As for flexbox, take all of it serious, if Dw does update bootstrap to version 4, then how does the visual user create flexbox, then what about css grid layouts, multi-column layouts. As i have said previously they may as well get rid of css designer. Also have a good look at many of the css code hints, that require css properties in a specific order, flex-flow should not allow a user to enter 'wrap row', Dw does. It may not seem important but if such incorrect usage is included in the css file the parser must resolve that usage, and if it is used multiple times and inside media-queries, then it can force a re-draw of the browser if the screen orientation changes, (portrait to landscape).

As for saying Dw supports only 30% of the w3c specs, yes that was an exageration, it is too high.

[BenPleysier]

http2, would you belive because it is still only a draft spec from the, 'internet engineering task force' -

http://http2.github.io/http2-spec/index.html

as are all the other items you mention in that section. Keep up with who is now responsible for what please.

Perhaps I was too subtle. When you say that Dw 2017 has less that 30% of the w3c specs supported it makes me wonder about the relevance of W3C. Most browsers have incorporated the protocol i.e. you can use it now if the server allows it, yet W3C has not caught up. There are W3C specs that browsers have not or have partially incorporated. All along, I have used the W3C specs as a guide, but my implementations have been guided by the browsers.

As for saying Dw supports only 30% of the w3c specs, yes that was an exaggeration, it is too high.

I prefer facts to emotional statements.

they may as well get rid of css designer.

I agree, but mainly because I do not use the Designer. However, for those that do need it and do not want to use the likes of Muse, it may be better for Adobe to improve the CSS Designer. But to which standard, W3C or browsers?

[BenPleysier]

As you may have noticed, I needed a break from my workload, hence my replies under the influence of a Cognac and a cigar. All that's missing is a cuddling female.

[pziecina]

BenPleysier  wrote

As you may have noticed, I needed a break from my workload, hence my replies under the influence of a Cognac and a cigar. All that's missing is a cuddling female.

Not certain about the cigar, but a cigarette maybe. As for the cuddling female, i have no problems cuddling myself, (not the same as someone else though, is it) .

[BenPleysier]

Not certain about the cigar, but a cigarette maybe. As for the cuddling female, i have no problems cuddling myself, (not the same as someone else though, is it) .

There may be a future in an amalgamation, professionally that is.

[pziecina]

[pziecina]

I have for years said that if a browser supports a feature, then Dw and any other code editor should support it. When a W3C spec covers the usage then it should be supported in accordance with that spec. but if the usage differs, that is why an autoprefixer is required. The typical Dw team, and many of those who represent Dw users, response though says that what i have written will never happen.

As for the 30%, simply go to the w3c site and look through the specs, and check what Dw does and does not support. If you then look at proprietary items from the browser and device manufacturers, that 30% falls even lower.

As for css designer, browser support must take precedence these days, (statement above applies).

[BenPleysier]

that is why an autoprefixer is required

You have won me over.