Viewing Feature requests, additions, changes.

  1. Portal Home
  2. Forum
  3. EverWeb
  4. Feature Requests

Feature requests, additions, changes.



User: Kurt L. 3 years ago
Please take the following as what it's meant to be - constructive criticism.

1. A setting to tell EverWeb to scale images in a responsive row, and not only in a responsive gallery. Reason:

A responsive gallery does not give you a way to add hyperlinks to images. Only in a responsive row can where you just drop the images in. You can then add hyperlinks to each image, but they won't scale. Only slide under each other at specified break points.

Can it be done? Yes, but only if you manually add anchor links to the generated HTML file, as I did here on under the Retouching tab:

http://jklstudios.com/portfolio/retouching.html

All built using the Responsive Gallery widget so the images will scale, and the hyperlinks manually added afterwards. Now the page responsively scales to fit almost any browser width, whether it's a desktop browser or an iPad, and includes hyperlinks. This much work wouldn't be necessary if EverWeb would simply add a scale function to a standard responsive row.

2. Get rid of responsive rows. Seriously. Muse has been able to build responsive web sites for years without anything being trapped in specific, horizontal-only rows. Literally anything, anywhere on the page can be responsive. If they could do it, EverWeb's engineers should be able to do the same thing. You tout EverWeb as a Muse replacement. It would then be nice if it behaved much more like it. You'd draw a LOT more former Muse users to your app if it did.

3. Get rid of the message about high resolution files when adding images. I can't imagine your staff doesn't know image resolution means absolutely nothing to a browser. Only pixel height and width. There's no need whatsoever to mention an image's resolution, much less even check it.

Last edit 3 years ago
User: Paul-RAGESW 3 years ago
Hi Kurt,

Thank you for your feedback, we really appreciate you taking the time to provide it and we take it very seriously here in order to improve EverWeb.

1. So you want a gallery where instead of opening a slide show, you can assign a link to a specific image?

There are various ways you can do this, including with the responsive row.

a. Responsive Row Method:

Add the responsive row to your page and then add your images to the responsive row. I recommend setting them to Fill->Scale to Fill under Inspector->Shape Options.

Then set them to full width from the Inspector->Metrics and give them a Maximum Width. Then you can assign links to each image.

b. FlexBox widget: With this widget you can assign max and min widths for all images and gives you a lot more flexibility to each image. Under image settings you can then select a link for each specific image.

c. We can also add a link option to the Responsive Image Gallery widget if needed.

d. You can use one of the third party widgets at EverWebWidgets.com or EverWebGarden.com


Quote:
2. Get rid of responsive rows. Seriously. Muse has been able to build responsive web sites for years without anything being trapped in specific, horizontal-only rows. Literally anything, anywhere on the page can be responsive. If they could do it, EverWeb's engineers should be able to do the same thing. You tout EverWeb as a Muse replacement. It would then be nice if it behaved much more like it. You'd draw a LOT more former Muse users to your app if it did.


You can do most of this with or without the responsive row. You can either use the Fixed Width layout and use the options under Inspector->Metrics->Responsive Hide/Show on various devices. You can do this also on a responsive layout but you have less flexibility.

We are working on the Responsive Layout option to provide a lot more flexibility. We wanted to avoid having to use Breakpoints since they become tedious to adjust your website on every single device. But we have an idea that will combine the best of Muse/EverWeb's ability to place objects anywhere, with the ability to create a responsive website that doesn't have to be edited on every breakpoint when you make a change.

We do realize that Responsive sites can be less flexible in terms of design. It is a balance between design complexity and creating efficient websites. We are working on various additions here to make it much easier so your feedback is appreciated in this regard. Our goal is to have near complete freedom of design while also offering a way to easily create websites for any device without having to edit pages for all breakpoints.

Quote:
3. Get rid of the message about high resolution files when adding images. I can't imagine your staff doesn't know image resolution means absolutely nothing to a browser. Only pixel height and width. There's no need whatsoever to mention an image's resolution, much less even check it.


So with this feature, the problem is that images with a resolution above 144DPI shouldn't be added to websites for display purposes. For downloading, users may want them to be if they want to offer a high resolution version of their website. Image resolution is important because the higher the resolution, the larger the image and the longer it would take to download and display for a user.

However, I do agree that we need an option to remove the warning that always appears.

Again, thank you for your feedback. We are using it seriously to improve EverWeb's flexibility and features.

-------------------------------
Paul
EverWeb Developer
User: Kurt L. 3 years ago
Thank you for the very quick, and detailed response. I fully admit I haven't been using EverWeb for more than a couple of weeks (if even quite that long since purchasing it). So I'll have to dig into your notes on points one and two.

Per resolution though, your information isn't correct. This is a very much repeated argument that has no meaning. Resolution does not, and never has had anything to do with file size. Only the number of pixels in the image do. Such as this:

300 dpi image with 1000 pixels in the width and 600 in the height.
72 dpi image with 1000 pixels in the width and 600 in the height.

Which will be a larger file? The answer of course is neither. They will be exactly the same size. Only output devices (like printers) care about resolution as it tells that device how many pixels should be used in a linear inch. A web site will display a 150 x 100 pixel image the same way no matter what its resolution is set at.
User: Paul-RAGESW 3 years ago
Quote:
Which will be a larger file? The answer of course is neither. They will be exactly the same size. Only output devices (like printers) care about resolution as it tells that device how many pixels should be used in a linear inch. A web site will display a 150 x 100 pixel image the same way no matter what its resolution is set at.


Hmm, this has been in EverWeb since the beginning. I think we need to re-evaluate this. Thanks for the additional information Kurt!

-------------------------------
Paul
EverWeb Developer
User: Kurt L. 3 years ago
You're welcome. Proof that I've learned something in forty years of professional image retouching and color. 😁

And thank you again for your information. Haven't had a chance to try any of it yet. Can't wait to see how they work!
User: Kurt L. 3 years ago
Yay! Took a few minutes to figure out the FlexBox widget, but that was far, far easier getting images to scale with the browser than the Responsive Gallery widget. And you can assign links! See? That's what I get for not reading the manual. 😊

And hokey smokes! What a raft of widgets you can add via the links you provided! More and more I'm very happy I went with EverWeb.

I also remembered a couple of items I originally wanted to add.

1. There's a bug that happens pretty frequently. You go to add a new blank responsive page and you instead get a message about downloading a template, which it fails on because the page it wants to download from doesn't exist. The only fix I've found is to shut down the app, extract EverWeb from the .dmg download and replace the corrupt copy in the Applications folder.





2. Image saving during publishing. EverWeb insists on rewriting all of your images, even when it doesn't need to. I do understand why it's there. You can't know who's trying to insert TIFFs and other formats that don't work in a browser, and automatically generating everything to the published folder as a JPEG makes the resulting web data "just work".

My somewhat minor complaint with it is that it also dumbs down your color to sRGB. This archaic color space was fine for the era it was designed for - cheap, short gamut CRTs. But it's greatly out of date for today's wide gamut displays. I'd much prefer the color stay where I have it in Adobe RGB. As long as an image is tagged, a browser will still display the color as intended. It doesn't need to be sRGB for that to work.

So an option would be nice to either copy JPEGs as is to the publishing folder, or at least tell EverWeb to maintain the embedded color profile.

Last edit 3 years ago


Post Reply
You must login or signup to post.