On a side note, it is understandable why the OP is having a rough time trying to recreate this effect: the UX design to control and create gradients is atrocious in Photoshop. It is in dire need of an update. The lack of a in-view gradient widget that remains 'live' when editing a gradient in a layer mask (even when leaving layer mask editing), for example, would be a good start. Other image editors provide for this. Photoshop's gradients are archaic in use. A terrible user experience. ... View more

It's simple: if you do not like the CC rent hike, stop paying the rent, and switch to alternatives for your work. As long as the majority keeps using Adobe, nothing will change. If half of the Adobe CC users decide to stop their CC rents, this will motivate change at Adobe.  Vote with your wallet, right? It really is up to YOU. When you rent, you give power away - it's always been that way. People here act as if they do not have a choice - well, you do. So many great inexpensive and/or free software alternatives out there now. ... View more

Yup, PhotoLine has also been applying live filters to layers without the need for smart objects for years and years now. However, Chris Cox is correct in stating that at a certain point of complexity live filters do slow down things. At that point smart objects can alleviate performance bottlenecks in your layer stack. Affinity Photo does not yet support smart objects. PhotoLine does, which gives it the best of both worlds. ... View more

The only way that attack will work is when someone actually clicks to open the file attached to a spoof email. Don't trust any email from anyone with a strange attachment and contents. But yes, back up your important files on an exernal drive (that is disconnected while working) and/or online data backup. But this ought to be done regardless of the current ransomware scare. ... View more

1) install all-in-one WP migration on your site (or perhaps another backup tool is already installed by the developer?) Download a backup of the entire site with this. 2) install a new WP installation on your local machine (you should have WAMP (win) or XAMPP (win/mac) or MAMP (mac) running on your local machine, of course) 3) install the same all-on-one WP migration plugin in the new local WP installation, and open the site backup. 4) use a code editor to make changes to the theme files in the wp-content/themes folder in your localhost copied version. 5) test, test, test 6) upload the revised theme files to your live site with FTP. Done! ... View more

Another alternative: Pinegrow with Atom. Atom is free (Atom​​) and Pinegrow (https://pinegrow.com/ ) is either $80 for a perpetual license with 1 year of free updates, or $8 a month (subscription). Pinegrow is easy visual editing, while Atom integrates seamlessly for code editing - change the code, and Pinegrow updates the visual view automatically (while you type). Edit in the visual view of Pinegrow, and the code adjusts with it. Version 3 is going to be very interesting - in my opinion Pinegrow is the direction that Dreamweaver would have taken in a better alternate universe. ... View more

Osgood, an alternative solution is to download PrePros Compile with Live Browser Reload Have it watch your css production file, and have it output an autoprefixed and minified version to a distribution folder that you link to in your html/php/etc files. And the live reload works quite nicely too (there's even an option to sync the scrolling in all open test browsers). For good compatibility, set the Autoprefixed browser support setting to "last 30 versions", or something similar. While PrePros supports CSS preprocessors too, it will happily post-process regular CSS files as well with Cssnext and Autoprefixer  (which looks at Caniuse for its information). And no obscure task runner configuration is required. Just drop your project folder in PrePros, and set up some settings. And it allows you to work with any editor, whether that editor supports all that pre/post processing jazz or not. (of course, I prefer to write my task runner scripts in NPM - but PrePros does make it incredibly accessible for anyone who is interested in integrating pre- and post processing in their workflow) ... View more

The best approach is to 'unmultiply" white. Surprisingly enough, Photoshop lacks a function like that, however. There used to be a plugin to handle this (ayato@web​ ), but it is no longer compatible, I believe, with the current version. The FilterForge plugin works, though. (Although the issue is that it only works with black - see below for alternatives) The trick is to invert the white page with black text first (negative), then apply the unmultiply black plugin, and invert back. This will remove the white from the anti-aliased pixels, resulting in perfect edges that are true to the original. Of course, D Fosse's solution will work just as well since the text is pure black only. But what if colors are present? Or it's not pure black or white? Gimp, Krita, and PhotoLine all have a built-in 'unmultiply' ('Color to Alpha/Transparency') function, though. You could download Krita (open source and free!), open the image(s), and use the simple "Color to Alpha" filter to remove the white (or any other background colour), and retain the exact anti-aliased quality of the lettering - in particular when any coloured areas are included, multiply blend mode will prove to be less helpful. Check out the example in Krita: removing the black without a "color to alpha/transparency" option takes much more time, gets technical, and is generally less effective. With Krita it is super simple and effective. The command is found in Filters-->Colors-->Color to Alpha menu.  https://krita.org/en/ ... View more

BenPleysier  wrote there is Muse and Webflow and Wordpress and Bloc and Wix Just lost another customer to WordPress. Someone had talked him into it and when I explained that I am a proper web developer, his reaction was, I don't care, I want the result. PHPMail or SMTP, Flexbox or Tables, they don't care. They want a good looking site that rates high on Google. That's why we are losing the game against the likes of Muse etc. Ten years ago my knowledge of Wordpress was zilch - then clients started to become really aware of the platform, and I began developing custom themed client sites in WP. It's merely a different approach, but the same techniques apply. I use html, scss/css, js, and php as before, but within the WP 'ecosystem'. Makes hardly any difference (excepting the transition to that ecosystem, which was frustrating). In my experience custom theme and plugin coding in WP is quite lucrative, since there aren't that many developers around who can actually code a custom theme, or convert an existing static theme/site design to WP. Of course, there are those clients who merely require a 'quick fix' and install an existing theme. But you'd be surprised how quickly clients realize they have to write some custom css to adjust the theme's design to their liking, and most have no clue how to do that. Which is where I come in again. Often I even feel like I am becoming more of a WP consultant . One-eye is truly king in the land of the blind, as the saying goes. If anything, because of the prevalence of Neanderthal-friendly mobile technology, (younger generation) users arguably are becoming less technically savvy than they seemed to be a decade ago. Nope, WP has been very, very good for my business. I still have a love-hate relationship with WP (still think its theming code is bloated and convoluted junk), but almost no-one of my clients wants a static website or hand-coded PHP back-end anymore. And I can't say I blame them. Clients can have a fully-functional and easy to manage web shop in a matter of days, rather than weeks or months. I say, follow where the wind blows. If your clients want Wordpress, give them Wordpress - and charge the same money (or more!). ... View more

glen1park  wrote Oh if only we still had Macromedia. Be careful what you wish for - Macromedia wasn't doing so well at the time Adobe acquired the company. Dreamweaver might have not survived if it hadn't been for Adobe. ... View more

If you do opt for a grid framework, I'd avoid Bootstrap, and go with Foundation. 1) it is arguably a much better grid implementation, 2) its syntax is friendlier, and 3) a flexbox-based version is also available. Also easy to download a streamlined version with just the features you will actually be using. Foundation | The most advanced responsive front-end framework in the world. Skeleton is also a simpler grid framework with an easier syntax. Skeleton: Responsive CSS Boilerplate In my opinion Bootstrap is an over-hyped framework. ... View more

pziecina  wrote The use of css variables are similar to css grids, in that they require a fallback at the moment. The reason i think that standards complient w3c css variables are important, is that variables are one of the prime reasons given for using sass or less, and along with mixins, and the autoprefixer are the three top features used in sass/less. Now there is no reason to use sass/less as far as i can see for the avarage coder, providing they are not using Dw. Dw is missing a stand-alone autoprefixer, and support for css variables along with almost everything else i mentioned, which is why i think it is still important to at least make users aware of what the specs and browsers are now supporting, even if Dw does not, and hope that once users become aware of what is possible without 3rd part plug-ins, they may ask for support. If they don't, then Dw will move even more closer to becomming an EOL product. True, good support for upcoming features (with a post-processor fallback) are important to have. And a lot can be achieved with post preprocessing nowadays, which may replace SASS at some point. Some coders have already switched. There are pros and cons. ... View more

@pziecina Why wouldn't you use a preprocessor? Sure, variables will be part of CSS in a year or five, but they aren't now - I am only interested in what makes my coding life easier NOW, not later. Why on Earth would you prefer DW snippets over scss includes? They are quite different. For one, DW snippets cannot make use of variables. But more importantly, an edit to your snippet would not automatically cascade that updated code throughout your project, which sort-of renders them useless in my opinion - certainly not up to par to scss includes. And I am not even mentioning the issues with relying on DW snippets when working in a team in which most other coders probably will be using other editors: at least with scss it is "cross-editor' compatible. It becomes more about workflow than anything else. However, I do agree scss includes should not be used for browser prefixing at this point: post processing with autoprefixer takes care of that. You'd be very unkind to yourself (in my opinion) to not make use of autoprefixing. And aside from the variables, there are a couple of things I like about using scss: @import, and compartmentalizing the css code in modules, which then creates one minified css file. @import in regular css loads sequentially, slowing down the page load, unlike the @import statement in SASS. functions. For example, easy and efficient method of working with REM values only instead of terrible px: simple function is all that is required. https://codepen.io/jelleverzijden/pen/xGYZYV the ability to nest @media queries in a rule. Much easier for code organization (granted, at a risk of larger code base at the end), and for handling @media exceptions. conditions are handy. And we can use them NOW. the option to have the task runner run autoprefixer and other routine tasks (minify the code, for example). Having said this, I completely agree that scss can be abused to write obscure and overly complicated style code that becomes unreadable to anyone except the person who wrote the code. And I have seen people write ridiculous deep nested selectors - one of the main reasons of the 20% overhead. I avoid nested (descendant) selectors as much as I can, and my compiled css code is as lenient as if I had written it without scss. Scss does not take away the responsibility to manage your coding well: neither does css. One argument you give is actually an argument in favour of using post-processors such as cssnext: you can write your css code with the latest W3 specs / features, and it will output css code that is compatible with all browsers. As time goes by, and those newer features are supported natively by all browsers, the updated cssnext post-processor will no longer need to generate alternate cross-browser compatible css code, and by then you have adapted to the new specs for years and years. Some front-end coders are intimidated by the CLI and task runners. Tools like Prepros take the heavy lifting out of your hands, and you can be up an running within a minute. And your images are optimized automatically as well. All in all, it's just so... convenient. ... View more

When you write "use DW to work on my staging site", do you mean: 1) make changes to the theme files localhost (your local machine) in order to customize/edit the theme code and upload the changes to your staging server at Godaddy or 2) add posts and pages, plugins, choose themes, etc. in your staging site at Godaddy or 3) add posts and pages, plugins, etc. in a local version installed on your machine (localhost) and upload these changes later to the staging server at Godaddy or 4) something else? ... View more

If the designer provides (and works with) design specs, then it generally takes one or two days to implement a static design. The trouble starts when designers do not provide you with those, or expect a pixel perfect responsive rendition (which falls in the Contradictio in terminis category). Demand design specs. Carefully control expectations. If the designer and client expect you to create a fully responsive page layout without providing exact design specs for mobile, tablet, and large screens (minimum), then ask for those. You cannot be expected to make up things as you develop. Communicate with the designer before he/she starts designing. For example, set up some ground rules, such as the base grid that will be used. Explain about Foundation/Bootstrap type like 12 or 18 column grids. This will also simplify the design process on the designer's side. Document everything. Before collaborating, speak to the designer in person (or over the phone) in order to assess the knowledge and experience level. Based on that conversation you decide on the risk level. I use 15-20% for low risk, 25-33% medium risk, and 50 up to 100% for high risk. I calculate the expected number of hours, and multiply with that risk factor. Also, I add an additional 10% hours per person working on a project (multi-person drag). Add a planning phase during which you communicate with the designer. DEMAND DESIGN SPECS even if he/she never worked with those before. I cannot tell you how important this bit is. You cannot be expected to hunt down every margin size, font property, and so forth, in a mockup - it is the designer's job to document this exactly for you, including differences in styling between break points. Send the designer this if he/she feels it is too much work to create design specs: “Developers at all stages of projects expect and demand strong documentation. Although documentation is never the most exciting aspect of design, it’s a critical step in ensuring smooth working relationships, timely delivery and a successful hand-off at the end. Ultimately, design documentation acts as a life-support system, ensuring that your vision is executed properly.” Introduce something like Specctr​​ to the designer. This will really make your life as a developer easier, since it also exports directly to CSS rules, which you can copy. Keep the lines of communication open at all times. Keep asking for updates. If the designer expects interactive stuff/animated effects, then he/she ought to use some kind of prototyping or animation tool to demonstrate what it should look like. If the designer and/or client opine that you are asking for too much, then it is probably not worth your time and energy to work on the project - it will just be very, very stressful in my experience. PS and everything Liam said 🙂 ... View more

You will need Illustrator, and as far as I am aware, Elements may not be able to open it in Illustrator? Not sure. Anyway, an alternative solution may be to download the trial version of PhotoLine (www.pl32.com) and open the PSD. Select the vector smart object layer, and right-mouse click the logo in the view, and choose "edit". It should open the vector smart object, and present you with a new view of the embedded vector file. Change the font colour (you might have trouble if the logo text is still real text that uses a font that is not installed on your system, but in most of these cases the text will be vector only). Save the logo file as a new file (PDF if you wish to retain full vector), and place it in your photo. Or find someone who owns Photoshop & Illustrator to save the logo for you. ... View more

Agreed, check caniuse: http://caniuse.com/#search=css3%20colors http://caniuse.com/#search=css3%20colors I'd say that with 97.88% global support you'd be fine. If you REALLY need to, provide a fallback for IE like so: background-color: #020202; /* rgb() with background-color fails in IE6&7 */ background-color rgba(f2,f2,f2,0.8); Or something similar. But I would suggest to just stick with rgba only nowadays - unless your client requires stone-age IE support. ... View more

https://forums.adobe.com/people/Nancy+OShea  wrote Use padding instead of margins. Review the CSS box model. CSS Box Model A position fixed division requires a stated width. Nancy No, a position fixed element does not require a specific width set. When left and right with values of 0 are used, the width is inferred. Padding will not allow for instances when white space is required around a fixed positioned element. While a width of 100% will work in most cases, it is not the most flexible solution. For example: header.page-header-->row-->h1 .page-header {     position: fixed;     top:0;     left: 0;     right: 0;     height: 5.5rem;     background-color: #f2f2f2;     margin: 0 5rem; /* or use percentage */ } .row {     margin: 0 auto;     width: 60rem; } ... View more

Not to be nit-picky, but setting a width of 100% is arguably not the most optimal method in this case. Instead, prefer left: 0; right: 0; A width of 100% causes issues along the way if/when margins are applied, for example. ... View more

It's too easy to blame Adobe's management - they are merely in the business of making as much money as they can for their share holders - that is part of the world humanity made for itself.  Also too easy to blame support staff - I am sure they are told by management to make it as difficult as they can within legal limits to cancel subscriptions. In the end no-one is forcing any of us to subscribe to Adobe's services. And before signing any contract READ it and UNDERSTAND it. I suppose this is a lesson everyone must learn sooner or later. ... View more

First, did you get a reminder about the renewal? Adobe states in their contract that they will. Many CC users wishing to cancel have complained that they never received one. If you did not get a reminder, you should mention that to the Adobe chat. My guess is you did not get one? Secondly, according to consumer rights (depending on the country, though), in most Western countries, you have the right to cancel that renewal within two weeks at no additional cost. Nowhere is it stated in the Adobe contracts that this is not the case. Other CC users who complained to Adobe support have used consumer law to cancel their Adobe CC sub. If you are within the two weeks of your renewal date you should still be able to cancel without the hefty 50% cancellation fee. EU: Under EU rules, a trader must repair, replace, reduce the price or give you a refund if goods you bought turn out to be faulty or do not look or work as advertised. If you bought a good or a service online or outside of a shop (by telephone, mail order, from a door-to-door salesperson), you also have the right to cancel and return your order within 14 days, for any reason and with no justification. Guarantees, cancelling and returning your purchases - Your Europe For US citizens the rules are less clear. There is a 3-day cooling off period, but I am not certain whether that is viable in this case. I do know of one case where the CC user used consumer protections laws in the US to fend off the renewal within two weeks. ... View more

Wow, please calm down. I merely responded to your post regarding Krita, and I experience no performance issues on my system at all in my work with it. It is Photoshop's paint tools which feel less responsive to me - nothing against Photoshop, it is part of my toolbox as well - just not for drawing or painting digitally (anymore - used to be my main painting app until a couple of years ago). I prefer the other alternatives which offer a bunch of specific features for digital painting that Photoshop lacks. Likewise I would never use Photoshop to paint 3d objects - again, I use more specialized software for that. Perhaps I should have added the "in my opinion" disclaimer? It's been a while since I visited the Adobe forums - used to be a much friendlier place. The 'troll' remark is out of bounds, I think. Anyway, I was just trying to offer some alternatives for painting on a Surface tablet to the OP. Logging out and staying away. ... View more

I work in higher resolutions that that: A4@600ppi 16bpc. I experience no major issues in regards to performance 🙂 Krita's new instant preview mode allows for real-time painting even with computationally complex brushes - try drawing with a simple textured 1000px brush in Photoshop and a spacing of 1%: a very laggy experience. Photoshop just cannot keep up. In Krita I am able to work with a zoomed out canvas and very complex brushes and still have real-time feedback. Granted, after drawing all the strokes it takes some time until Krita finishes calculating the final result in the background- but still. I'd rather have real-time feedback than a laggy stroke that cannot keep up with my hand. To be fair, it is true Krita's performance is quite dependent on the hardware you throw at it. It also still runs best on a Linux box in my experience. On a side note: one thing I always found annoying about Photoshop's brush engine is the lack of support for coloured brushes. Krita and other painting software (even Gimp!) support fully coloured brush textures, while Photoshop only allows for a grey-scale texture. Frustrating. As for canvas navigation: pan the view with the middle mouse button, hold down shift and the middle mouse button to rotate the canvas. Btw why, after all this time, is it still not possible in Photoshop to use the middle mouse button to pan the view? Anyway, drawing software is like clothing: it's quite an individual preference. Photoshop has competent painting tools - just not the best-in-class in the industry at this point. Which is not necessary, of course - Photoshop merely needs to be good enough in all areas, not the best. I would never think of using Krita as an all-round image editor, nor do the devs pretend it is. They decided years ago to focus on creating one of the best digital painting applications, and avoid competing as an image editor. Have you ever tried ClipStudio? I do a lot of work in ClipStudio and switch to Krita depending on the job, or combine both. ClipStudio is beyond excellent, in particular in terms of natural drawing feel. Nothing compares to it, in my opinion (and many others after they tried ClipStudio). ... View more