Viewing Image folders redesign please...
Image folders redesign please...
|
User: Peter B. 10 years ago
|
|
|
Hi Paul, I would like to see a total redesign of the image folders used in EW. As things are now the images used in a website are copied over and over again, resulting in websites that could be around 10 mb ending up being 50 mb just due to all the excess images. Can we please get to a situation where images are using relative file paths like ../Images/filename.jpg. This would have various added effects like: - cache ability of the images - faster loading of the pages - less impact on webserver storage size Master pages The same goes for the Master pages. Right now when a new page is made using a Master page, the contents of the Master page are added to the folder structure that is created, while a simple referencing to ../Master/Images/imagename.jpg would also work ( if not better ). Peter |
|
|
User: Roddy 10 years ago
|
|
|
I assume that a master page works the same as an includes folder used when designing sites via code. An includes folder contains all the code which is used on a group of pages so that they can all be edited in one place to save time. These code snippets are then added to each page automatically. If you use an image such as an icon in the header of each page of the site, the browser only has to download it once. It caches the file so that it doesn't have to download it again when another page is opened. Images do use relative file paths. I don't have any "Image " folders since I insert all the images using widgets. Publishing the entire website will delete any redundant images for you. The fact that an image is in another folder - or not - won't effect download speed. Proper optimization of images before importing them will. ------------------------------- Roddy Website: http://everwebwidgets.com Contact: http://everwebwidgets.com/ewWidgets-home/contact.html NOTE: I am an EverWeb user and NOT affiliated with EverWeb! Any opinions expressed in this forum are my own. |
|
|
User: Peter B. 10 years ago
|
|
|
Quote: Roddy - 08/07/2015 9:14:02 I assume that a master page works the same as an includes folder used when designing sites via code. An includes folder contains all the code which is used on a group of pages so that they can all be edited in one place to save time. These code snippets are then added to each page automatically. You would expect this, but it's used as a template rather then an code insert action. So the Master page actually does nothing more then be a template for your next page. It allows you to change the look and feel of the page in a family easy way and allow you to change things like menu structure and header and footer rapidly. So the functionality is nice, but due to it being treated as a template, it copies itself and every image related to itself into each and every images folder that is created. Quote: If you use an image such as an icon in the header of each page of the site, the browser only has to download it once. It caches the file so that it doesn't have to download it again when another page is opened. Sorry, but this is not the case in EW. It should be...that's true, but it isn't right now. Quote: Images do use relative file paths. I don't have any "Image " folders since I insert all the images using widgets. Publishing the entire website will delete any redundant images for you. The fact that an image is in another folder - or not - won't effect download speed. Proper optimization of images before importing them will. I agree that image sizes matter, but EW creates a set of folders for each page . An example: On sitename.ext there is a contact.html page. In the website itself of Sitename.ext there are the following folders for this page: ./Contact ( contains index.html and any extra pages you create under it ) ./Contact/EwExternalFIles ( contains some images, possibly also related to the Master Page ) ./Contact/Images/Contact ( contains copies of all images used in the Master page ) ./Contact/Image/Contact/Browser ( contains the browser background image referred to in the Master page ) This structure is there for each and every page in EW. So when you have 20 pages, all the files in the folders containing Master page content, will be copied 20 times !!!) It should be like this: ./Images ( should contain all commonly used images for all pages ) ./Images/Masterpage ( should contain any images used in the Master page ) ./Images/Pagename ( should contain images unique to this page ) Peter |
|
|
User: Paul-RAGESW 10 years ago
|
|
|
You cannot make each page that uses an image use the same image because what if you resize that image? Or rotate it? Or add any other kind of effect? The image would be different. What I can tell you is that in version 1.9 Master Page assets (media and CSS) will be included in one central location rather than duplicated for each page. Websites will publish and load faster because of caching. I am personally very excited about this feature. Plus we have other optimizations we are including in 1.9. The EverWeb site alone is about 35% - 40% smaller just on a republish. ------------------------------- Paul EverWeb Developer |
|
|
User: James G. 10 years ago
|
|
| Sweet! | |
|
User: Raf P. 10 years ago
|
|
|
Hi Paul, past days, I read about the coming of 1.9. Can you give us some more information? The new features, when, ... ? You made every EW user curious don't you think? ------------------------------- Kind regards, Raphael Pairoux |
|
|
User: Paul-RAGESW 10 years ago
|
|
|
Quote: past days, I read about the coming of 1.9. Can you give us some more information? The new features, when, ... ? The above is all I can offer at this point. I know this is a big feature and I'm very excited about it as well :) ------------------------------- Paul EverWeb Developer |
|
| Post Reply |
| You must login or signup to post. |