Skip to main content
Participating Frequently
October 8, 2014
Resuelto

Is there any way to display the Design View in fluid grid pages?

  • October 8, 2014
  • 24 respuestas
  • 54491 visualizaciones

After upgrading to the newest version of DW CC 2014, I noticed that the Design View is disabled in Fluid Grid pages. You can only use the Live View to edit those pages. The Design/Live button displays on non-fluid pages.

I'm wondering if there is a work-around to allow Design View editing on fluid pages. It is a major hassle to try to edit some things in the Live View. It would nice to have a choice.

Este tema ha sido cerrado para respuestas.
Mejor respuesta de rjerz

@Ron

Ron, thanks for your idea.  I just tried this to my fluid grid css file, and it worked!  The odd thing (at least in my mind) is that the code (shown below) is commented out.  So, even though my web pages ignore this commented out code, Dreamweaver does not... it uses it to control how the Dreamweaver program operates. Well, I guess that this can happen.  This code acts like a "directive" to the Dreamweaver program.

One noticeable change is that in Live view I no longer see the grey strips showing the fluid grid columns, but I can live with this.

This is my novice way of looking at the situation.  But now I am happy.

Here's my exact code (that I deleted) from my css file.  Maybe others can try this and see if it fixes the problem.

/*

  Dreamweaver Fluid Grid Properties

  ----------------------------------

  dw-num-cols-mobile: 4;

  dw-num-cols-tablet: 8;

  dw-num-cols-desktop: 12;

  dw-gutter-percentage: 15;

  Inspiration from "Responsive Web Design" by Ethan Marcotte

  http://www.alistapart.com/articles/responsive-web-design

  and Golden Grid System by Joni Korpi

  http://goldengridsystem.com/

*/

24 respuestas

Participant
October 29, 2014

I am always open for new features that said design view is a critical feature I use when I develop website.

The live view has delays and switching between code and live view is not smooth.

Adobe programmers please put back my design view because this is what separates DW from the rest of web developers tools out there!!!! Is ok to add new features but never remove the design view option ...

Sincerely,

Steven

Nancy OShea
Community Expert
Community Expert
October 29, 2014
Is ok to add new features but never remove the design view option ...

Never is an infinitely long time.  I would much prefer to see the currently feeble and outdated Design View replaced with something better.  Obviously, Live View in it's current state is not a viable replacement yet.  But it could be in the future.

Nancy O.

Nancy O'Shea— Product User & Community Expert
Participant
October 29, 2014

Thank you for reply Nancy. I said never to show how much I value design view. The difference between live view and design view is speed and local versus remote which cannot be compared. And I don't have an issue with live view it is just easier for me to use while on the road where the live view becomes rather a delay in development. The solution would be to make it rather a choice that can be enabled or disabled in preferences. Don't just remove it and force users to use some new feature.. .. is like how windows 8 removed the start menu and decided to put it back in windows 10.

Participating Frequently
October 26, 2014

I have thought about this alot since leaving my post here last night, I still stand by what I say.. every word,  but I am open to giving Adobe a bit more leeway than my narrow view of how DW should work.

I guess the shocking thing that I first found post upgrade was that when I opened a site to edit it that I could not see my layout-- I thought that my installation was broken. I searched all over looking for a place to turn design view back on , and could not find it.

So I did a full re-install, generally that is not such a huge thing except that I have a huge number of extensions that I have to reload as well, but before I started on re-installing extensions I checked and my Fluid Layout Design view was still broken~ this was the beginning of the slow burn to rage....

But after thinking about this here is the thing, I would be OK with design view going away, but the ability to toggle on fluid grid view,or toggle on some of the design view elements that are commonly used by a large cross section of users. I have learned to accept change being shoved down my throat , Microsoft does it with broken software all the time, but they loose large amounts of sales to it , and have seen an exodus of users to alternative system. If Adobe is unwilling to keep some of the features that us as end users are calling for, they may create a scenario such as that. I think that elements of the design view can be implemented that will make workflow better, and chjanges have to be instant and dynamic, not refresh and wait and see if you screwed something up.

So I have rolled back to CC the only version available in CC Manager, and will install my tools into that. I may just stick with this version,if that is the case a ala carte version of DW will work out much better than a CC version. Everyone that has posted frustration in this forum will have to decide how to move on in the future, if the big corporate "USE WHAT WE GIVE YOU AND LIKE IT" attitude is what we experience from Adobe, Then each of us will have to choose how we design in the future. Will you just use the current version and learn the methods to suffer through it, will you stick with a old version until they wont support it any longer,will you move to an alternative design software? These are the choices we are all faced with.

Participating Frequently
October 26, 2014

I have read through this thread, and am just getting MAD now, I have read other threads with feed back from Adobe personnel   and there is a sideways answer to any issue that a end user has.

But I am posting to LOG my disappointment in the 2014.1 version, I have several sites that I used the fluid grid design , and one that I am currently working on and I just want to face palm with every action I attempt to do,

this is SLOW, CLUNKY and maddening, with a fair simple layout I was absolutely beside myself trying to figure out where my grids where and how to place stuff in them , I kept getting lost and bad formatted text, and I ended up screwing up a site that I had to go back to a backup copy. THIS SUCKS, All we all need is design new back, Live view is good for what it is , to inspect the Live output while designing, I use that as a tool , but having that forced into my primary workspace is JUST STUPID...

give back design view and we can all just move on. I understand giving wysiwyg formatting to newbies , that is great, but for most designers a combination of WYSIWYG, CODE , and Design view to control your workflow is a full set of tools , I now feel like I have been tasked with changing a tire with NO other tools than a cresant wrench..... If this stays , I will probably go back to  just using notepad like I did in the old days...

Remember Notepad, Save then open the html file in a browser, as it is right now this would be faster than trying to refresh Live view.

I understand that everyone uses DW in different ways and has different uses and that this change to specifically fluid grid designs does not effect alot of people except those of us that decided to follow the Adobe method...

In closing I am much less satisfied with my subscription now...I am not really patient as I have alot of web design backlog that I need to work on , and I had chosen that I would do most in Fluid Grids, yes I create simple designs that are simple to edit, and worked flawlessly before.

ok 'nuff said

Fix it , or I will move to something less superior to previous versions of DW

Herbert2001
Inspiring
October 26, 2014

I understand the frustration with the latest version - and I do think it is part of anyone's responsibility to be aware that new versions of the software one uses can potentially severely break one's workflow. Which means rolling back to a previous version, and waiting for the kinks to be ironed out.

I cannot count the times I installed the newest version of some software package, only to find out something was changed that broke my workflow in some manner. Either adjust, or roll back. (Or change direction, and start researching other alternatives ;-) )

Hopefully DW's Live View will become a great/improved version of the design view in an upcoming version.

Participating Frequently
October 26, 2014

"Which means rolling back to a previous version, and waiting for the kinks to be ironed out."

There is always that, but frankly I am torn about rolling back wondering what choices that Adobe will make in this matter. The other problem is I can't think of another product out there that is as effective as DW with tools like Design view. The cloest thing I can think of is Visual Studio, but getting aclimated to that makes dealing with this required live view seem easy. So sucking it up and dealing with it may be the only option.

Participant
October 24, 2014

I'm currently taking a Web Design class. The brand new CC text book was just released a few weeks ago, and the assignments are written using Design View. Can't follow along with the book. Just not cool.

Herbert2001
Inspiring
October 24, 2014

Then why not install and use the slightly older version to do the assignments? Books are often one version late.

Participating Frequently
October 26, 2014

I agree, but normally the newest version does not have this dramatic of a change to it. So I get Katebarts irritation.

Stevefas
Participating Frequently
October 21, 2014

I am also struggling with the removal of design view - not so much that I need it for previewing, but that it was great for editing text blocks.

An issue that stood out for me most (and made me abandon 2014.1) is that I can no longer add paragraphs of text from my clipboard and have each imported paragraph formatted with beginning and closing p tags.

I can't even select multiple paragraphs at all in live view.

For me, the gray responsive boxes, and the ability to clear and block the divs visually was a winning design view feature. I want to move forward, but I think there needs work done to be able to edit in live view.

Herbert2001
Inspiring
October 20, 2014

It is as Nancy stated earlier in this thread: you cannot trust the Design View. It is the first thing I tell any of my students who wants to use Dreamweaver as the main code editor: "Stay away from the Design View!".

Not saying DW is bad - by no means: it's a very good code environment. But no longer the best, unfortunately (although this is up to personal taste as well, obviously. Code editors are like clothing: everyone has his or her own taste). And almost all my students tend to favour the newer kids on the block. SublimeText, phpStorm, or Netbeans.

Of course, these students predominantly code their pages manually.

However! I do realize being able to quickly change text and content in a wysiwyg design view can give a boost in speed to update static html pages and do quick visual changes in styling. Although I do 90% of my front end development  work in a code view (Netbeans is my favourite), I also spend the remainder of that time in the code inspector in Chrome, Firefox, and Netbeans' Live view with CSS inspectors to change css parameters visually, because it regularly makes more sense to do it that way (much less trial and error).

As a matter of fact I also use Pinegrow and Macaw to complement my pure code editing with quick wysiwyg edits at times. But I also understand that this workflow is not for everyone, and many users just want one environment to deal with web pages.

Dreamweaver's Live view should become the new Design View. If you have ever worked with Macaw's or Pinegrow's live views, than you will realize how powerful such a thing can be - it is the correct decision on the part of the DW development team to put the legacy Design view out of its misery, because DW is starting to lag quite a bit compared to what else is out there. It is crucial for DW's continued survival in this tough market to migrate the wysiwyg part to the live view.

...Which leaves anyone currently depending on the Design View with a couple of simple choices:

- do not update (or roll back to the previous version). Simple enough. But I hear ya: why does Adobe send out a half-baked version then?

Well, welcome to the grand new world of CC - where everyone becomes part of the beta tester team! (At least, that's how I see it). Never update to a new version until you hear from others it is safe to do so. If you want to be cutting edge: well, there are risks involved. Things might break. Workflows may collapse. That is the price you pay for installing the newest version immediately without a thought.

This, of course, also holds true for non-CC subscription software (fair is fair). However, I do feel Adobe's applications were more thoroughly tested before the advent of CC. I've seen some REALLY odd buggy behaviour in Photoshop lately during classes. Really odd. I've not seen the like in all my time with PS since version 3(!). Anyway. I am digressing.

- if you really cannot stand where the newest DW is going, start testing the waters elsewhere. No-one is keeping you hostage: vote with your wallet. Or combine DW with other software to get what you need. Pinegrow works well together with other code editors, including DW. Luckily we have so much choice in terms of web design/dev software - DW is only one capable fish in the water. There are many other very big fish. Some work well together indeed.

But I understand that removing a number of basic features is going to hurt - same happened to Flash CC where the dev team removed many basic features users depended on. After more than a year some of these features were implement back in Flash in a better way - but in the process some users decided to move away, and others stayed, and really love the newly modernized features.

As far as I can tell, the DW dev team responded to many users complaining about the antiquated design view, and how it should be modernized. Well, that is happening as of this version. Growing pains, indeed.

Participating Frequently
October 20, 2014

Where you state your points clearly, I can't agree with most of it. Because your methods of product delivery to your clients work for you, they don't necessarily work for everyone else. When it comes down to it the only opinion that matters is the clients you serve.

Herbert2001
Inspiring
October 20, 2014

That is very much true - which is why I wrote that it depends on who you are as a user, and your workflow/process.

Most of my clients could not care less about the tools I use to create their websites, web applications, and mobile apps. Code is code. No-one ever asked me, outside of developers themselves, which dev tools and frameworks I worked with during a project. Things change, of course, when I work in a team with people - but even then, depending on the project, the choice of code editor is often left to the programmer.

GA_
Participating Frequently
October 15, 2014

As I've mentioned above, when I first feel ill of 2014.1 I raised the issue with support. Perhaps Preran's reassuring words are just empty promises...

Adobe Case Update

Your Case
Case Description:DW 2014.1 Design view

With this response, we believe your issue is resolved and have therefore closed your case.  If your support case has not been completed to your satisfaction or you need to contact us on this issue again, please reference your case number. You can reopen your case up to 14 days after it has been closed.

It seems all Adobe need to do to close a case is IGNORE the originator and do nothing.

I would love nothing more than to write to the Chairman of Adobe and complain. I actually telephoned the Maidenhead offices in the UK asking for details of who to complain to. They refused to give me the names of ANY members of staff, including the board members (public record, people). They also cut me off twice, passed me over to India twice and finally gave me an email address that doesn't work! If anyone can furnish me with a specific name and postal address (not just dedicated "complaints" department, trained to ignore customers - but a real, high ranking official), I will be pleased to write directly to them and voice the concerns that we are all raising here.

We're being ignored people!

Participating Frequently
October 15, 2014

But what was the response they are talking about as reason why they said 'we believe your issue is resolved?'

Unfortunately the large companies lately employ the technique of ignoring a complaint in hopes it goes away. From this small group that seems to be an easy option for them to try and do.

I am going to raise a support ticket regarding Jquery menus and this soon to see if I get any traction.

GA_
Participating Frequently
October 15, 2014

Hi madwebllc,

I posted the email as was, other than removing the case number. The issue I raised was the inability to use design view. They feel that by saying, "you can't use it" the issue is resolved, presumably. I maintain that as design view works very well in 2014.1 on all NEW responsive documents, but then ceases to work when DW is restarted, there is clearly a FAULT present.

If it doesn't work, it should ALWAYS not work. If it works SOME of the time, it should work ALL the time.

Try it. Create a NEW responsive file and design away using Code, Live and Display. All work fine. Then close down DW, reopen it and try to access Design View. Suddenly it doesn't exists and Live view will not edit.

Result: Programming fault - not and feature.

Participating Frequently
October 14, 2014

Forgive me if this has already been posted here. 

Nancy O. pointed me to this idea for a vote.  We are indeed getting some traction with Adobe on this thread, but it couldn't hurt to vote on this here as well:

Solidarity, people!

GA_
Participating Frequently
October 15, 2014

In response to B Carson, thanks for the prompt re the vote.

I've already registered my vote but I'm disturbed at how few have. I can't believe we're the only people noticing this problem.

Come on folks, nag your colleagues. Votes are useless without numbers.

Joshbiz
Participating Frequently
October 14, 2014

I AM GUTTED. Havfe used DW every day of my life since Macromedia DW 3.1. The removal of Design View is a massive error of judgement. I have to update hundreds of static HTML pages and Design View has always made this fast and easy. What berk decided to remove this. I'm almost crying!

So like others, even though I have a CC sub, I am stuck on DW CC for now. Thank goodness it stayed on my system.

Come on Adobe sort this out. You're losing it...

Participating Frequently
October 14, 2014

Joshbiz:

If your web pages are fluid or responsive, you can delete the hidden DW code in your CSS file. If they are not fluid pages, the Design View toggles with the Live View.

Joshbiz
Participating Frequently
October 15, 2014

Thanks Ron. This helps as it restores the Design View option. Much appreciated.

Participating Frequently
October 14, 2014

After the latest DW update I have been trying to figure out what was "broke". Couldn't figure out why I couldn't edit anything except in code view. Alas, here I am, frustrated and not happy with the direction the latest update has taken us.

I have all of the issues, problems and frustrations expressed by others. I will be reverting to the old DW CC. The fix for removing the grid layout information may work for me since a few of the designs that I have are stable and div editing is not an issue.

I hate the new "live only" feature for Fluid designs. You cant even add a simple paragraph with a CR any longer. Seems I must go to code view and "code" the new paragraph. PITA !! I make a lot of extra income from older customers by convincing them to upgrad their sites to responsive designs. Not being able to edit a page in "almost" WYSISWYG mode is not acceptable. I like everyone else always previewed pages in a real web browser or mobile device.

This is what we get for our monthly CC membership....features that go away and the need to go backwards and not forward with software versions.

Participating Frequently
October 14, 2014

Just to clarify: Just went back to Dreamweaver CC. I will not use the new Dreamweaver 2014