Missing in Dreamweaver Application, the photo crop tool with update. You REMOVED IT!!

[mbarto]

Previous Version of Dreamweave in the Property Popup allowed cropping and other tools of photoes without leaving the application.  Now I need to open Photoshop to crop an edge or something like that and then go back to Dreamweaver and update the image settings to see if the fix worked. This  change has RUIN my productivity. I pay per month for this stuff, but your program designers have a limited view to what this is being used for. We product an on going Newsletter with multiple photos update instantaneous to our web site. It is almost worth going back to the previous application to use this function. Why did you take it out. IT IS HURTING MY BPRODUCTIVITY!!!! 

[B i r n o u]

yes those tools was removed some builds ago

https://community.adobe.com/t5/dreamweaver/image-optimization-workflows-deprecation-in-dreamweaver/t...

but if your question is why... well... Sorry, I don't think we can get any answer on this type of question...

[Paul-M]

The idea behind removing these features was to improve Dreamweaver performance I believe and the assumption not many people used them

[Nancy OShea]

I wouldn't revert to an old DW version over this.  It's not worth it.   Up until a few years ago, DW had no graphics tools because DW was and still is a code editor, not a graphics app.  Use the right tools for the job.

Web images should always be cropped, resized and optimized for the web BEFORE you bring them into DW.  This is even more essential when using the <picture> element to display different sized images on various devices (aka responsive images).

https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_picture

Assuming your newsletter is based on a re-usable template, you should know exactly what the height and width of your images must be.  Whoever is responsible for preparing your web graphics should be batch processing them in Photoshop, not Dreamweaver. 

[B i r n o u]

I don't quite share your point of view, neither on the date when this feature was in place, nor on the flow principle.
At least as long as it is done in a well managed way.

In fact this kind of functionality goes back to the Macromedia days, when DW and FW were fully integrated with each other... we called it roundtrip between applications, ... besides a number of features (gone one by one since...), like Design Notes, FTP publishing from FW, shared URLs in list form, tabulated data, etc... and at the time when CSS was still in its infancy... tabular layout... let's go roundtrip...  some graphics stuff made in DW... other HTML made in FW...

Adobe came along ... added a couple of tidbits, integrated the PSD format, even swept away PNG (native) and the confusion came... and here I agree with you about not cropping an original but an export format... which was the case (even with PSD) when roundtrip was still handled correctly... time saving.

[Paul-M]

Yes, I agree B i r n o u  and Dreamweaver performance and stability was better back then too...

[Nancy OShea]

For as long as I've been doing this, graphics apps like PS and legacy FW could not be trusted to generate production-worthy HTML or JS code.  For prototyping purposes, maybe.  But not fit for real sites. 

Likewise, DW couldn't be trusted to manipulate raster images without introducing other problems: distortion, lost metadata, pixelation, bad compression, etc...  

Everyone who got paid to build websites understood the downside of these so-called "time-saving" workflows and avoided them if possible.

Fast forward to today, Dreamweaver is not equipped to mess with images, except non-raster SVGs which is a supported code type in DW.

Source: https://en.wikipedia.org/wiki/Scalable_Vector_Graphics

[B i r n o u]

Again, regarding this thread, I don't share your point of view. I am referring to the DW / FW pairing in the Macromedia era, not the Adobe era.

The graphics tools that were used from DW were just routines that used the FW API. So no problems of distortion, pixelation, metadatas or bad compression, at least not more than if the same operations had been conducted directly from FW.

Moreover all these manipulations were done on the original document (in native PNG, hear FW PNG) then exported using the settings defined directly within FW.

As for the HTML, I was referring to the HTML used by FW to make table layouts (read again the introduction of my comment)... and at this day, I can guarantee that it was a code, identical to the one generated by DW, because in its turn, FW used the APIs of DW... 🙂

it was still at the time of the shim.gif... remember ?

but of course, when these implementations were made... there was a great time saving... not to mention being able to upload from FW without coming back to DW... while preserving the synchronization... using the DW FTP API.

At that time I was producing application, I was also using Flash, Generator, Flash Remoting, Flash Communication Server, Director, I was using much roundtrip in application as I can... and I never lost any money 😉

Macromedia had been the inventor of the adage... create once, publish everywhere... and it was the first editor to package software as suit.... toolbox... I was using DW 1 and as soon as FW came out... (I think it was DW 2...) I used them together... (I confess that I was also using Homesite from Allaire...)

I persist and sign, and I understand the regret of the users used to these mechanics, who knew how to tame them and master them.

[Paul-M]

You'll be wasting your time here ... Nancy is right even when she is blatently wrong ... Fireworks produced HMTL for it's time  not for now, we  know that... I'm not sure if Nancy used the Macromedia tools back then tbh...

[B i r n o u]

You'll be wasting your time here ... Nancy is right even when she is blatently wrong ... Fireworks produced HMTL for it's time  not for now, we  know that... I'm not sure if Nancy used the Macromedia tools back then tbh...

By @Paul-M

Although I am not in favor of any categorization of things, nothing is binary ... even the computer which although it is summarized only to zero and ones, is not binary ... that is to say ... but it is true that the web was born from Macromedia, while Adobe by acquiring Aldus affirmed its focus on printing...

Macromedia was so far ahead that we see its first users taking advantage of it... Peter Small (back when he released Lingo Sorcery... about the object, in a nod to Director (at that time it was Director 4... lingo was still refering to born and kill instructions... instead of new and remove))... was writing a book about a virtual café (café - Common Access For Everybody)... Do you remember ?...

the book was called Entrepreneurial Web. If you find it and look at the first page where the project is presented... you find mostly beta testers coming from Macromedia... people from the web... this book was so amazing... so inspirational and avant-garde

In his third book, Magical A-Life Avatars (first édition 1997-8)... Peter, draws the very first line of the emerging XML, by using an external TXT document to pilot the application. His goal was to make the document useful to the application, and not to pursue the opposite spirit which consists in saying that the application is at the service of the document... and this is the specific and very particular spirit of Macromedia.

Transversality.

So... and without any hasty shortcut, between Macromedia and Peter Small... at that time (early 95) the inoculated mindset and approach didn't need to bring us back to the future... we were already there... and Paul you're right sometimes it's possible to perceive the people who have their roots at Macromedia, as those who have them at Adobe being beside the Macromedia mindset. (we may be wrong)

Adobe has unfortunately completly misunderstood this particular spirit...

Adobe is more oriented towards Projects, Marketing... https://www.lemagit.fr/actualites/252500637/Workfront-nouvel-atout-majeur-dAdobe-dans-la-collaborati...  and leaves the management and creation of web tools to others.

[B i r n o u]

Adobe is more oriented towards Projects, Marketing... https://www.lemagit.fr/actualites/252500637/Workfront-nouvel-atout-majeur-dAdobe-dans-la-collaborati...  and leaves the management and creation of web tools to others.

By @B i r n o u

look... nothing really about web development... ;], I mean stuff like we talk about usualy on this forum

https://portal.adobe.com/widget/adobe/am21/sessions

[Nancy OShea]

Macromedia era!!!  Oye I'm trapped in a time warp... Quick, get me back to the future.

Back to the Future