Viewing V1.9 Master Page

V1.9 Master Page

10 years ago	User: Roddy 10 years ago Report \| Post #1
User: Roddy Title: User Location: GB Posts: 5843	Quote: Master file assets and css are stored in one global folder making websites significantly smaller and faster to load in your browser. Also, publishing will be much faster due to less files needing to be published. What folder? This website uses an external stylesheet for the navigation and other items. When I insert it in a test project in V1.9 the stylesheet is inserted into all the ewExternalFiles folders as it did with V1.8. Also, the new feature which optimises the HTML is a bit of a failure since it doesn't optimize the code for the custom navigation which is probably the only code that actually needs to be optimised. This is probably due to the fact that I have commented it so that I can find sections when adding new pages. To sum up, the optimisation has the downside of making it near impossible to troubleshoot the source code and doesn't actually work where it is most needed. ------------------------------- 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.

10 years ago	User: Paul-RAGESW 10 years ago Report \| Post #2
User: Paul-RAGESW Title: Admin Location: CA Posts: 5525	Quote: This website uses an external stylesheet for the navigation and other items. When I insert it in a test project in V1.9 the stylesheet is inserted into all the ewExternalFiles folders as it did with V1.8. You mean it uses an internal stylesheet using the style tags for each? Widget code is not changed. However, you can include code in an external style sheet with widgets but I think I am confused with what you are describing here. The changes in EverWeb here are for EverWeb generated code. There are different ways to optimize for widgets as you can include all common code in external files anyways. I can help you wit this if you like. Quote: Also, the new feature which optimises the HTML is a bit of a failure since it doesn't optimize the code for the custom navigation which is probably the only code that actually needs to be optimised. Calling it a "bit of a failure" is a strange way to describe it. Perhaps you may think that we should do further optimizations, which we may do in the future but it is difficult to start optimizing external code that is not ours. Right now the optimizations we do will reduce the file size for both uploading websites and for visitors. There is no need for extra white space within HTML or CSS documents. Quote: To sum up, the optimisation has the downside of making it near impossible to troubleshoot the source code There are very few people looking at the source code of EverWeb created websites. The best way, which is what I do, is to use the Inspect Element in Safari or Chrome and when clicking the triangle next to the top most html tags, hold down the option key. This will display the entire source code for you. For me, this is significantly better as the code is laid out nicely, you can easily spot any element within the browser, you can use the find feature and you can make quick edits to the source code from here. You can't do much of that using the View Source Code option of the browsers. I hope this information helps. ------------------------------- Paul EverWeb Developer

10 years ago	User: Roddy 10 years ago Report \| Post #3
User: Roddy Title: User Location: GB Posts: 5843	The stylesheet is inserted into the SIte WIde Head Code box like so... <link href="{!-ASSETSPATH-!}External%20Files/widgetbox3.css" rel="stylesheet" type="text/css"> Incidentally, even copying a line of code out of this box turns every page of the site to red and requires them all to be republished. Large sites with several directories also often required completely republishing too. This happens when a new directory is added and the whole site is published. The next time the project file is opened, the whole site needs published again. The HTML for the navigation is inserted via an HTML Snippet. It is this code which is not being optimised. On a large site with in excess of 150 pages, the navigation HTML is a large chunk of code. Since EverWeb won't optimise this for me I still have to run the files through an optimiser app before uploading. As I have pointed out before, I get a lot of EverWeb users contacting me with problems. Very often these are caused by code they have inserted themselves. If they think the problem is being caused by a widget, I usually ask then to publish a test page with just that on it. Most often, it's something else in their code that is actually causing the problem. JotForm is one of the main culprits since its javascript screws up quite a lot of other things. Most people who code websites are very sloppy and leave too much white space - that includes some of the code inserted by EverWeb. I have no quarrel with removing white space but I can't see any benefit in removing all the returns. I see many user websites who use litterally dozens of shape images on each page which don't need to be there. Removing returns in the HTML isn't going to offset all that stuff! ------------------------------- 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.

10 years ago	User: Paul-RAGESW 10 years ago Report \| Post #4
User: Paul-RAGESW Title: Admin Location: CA Posts: 5525	Quote: <link href="{!-ASSETSPATH-!}External%20Files/widgetbox3.css" rel="stylesheet" type="text/css"> Incidentally, even copying a line of code out of this box turns every page of the site to red and requires them all to be republished. Yes of course it does since it has to be removed from all the pages it was once on. There are ways to make this better, and it's on the to do list but this is not affected by the changes in EW 1.9. The changes in EW 1.9 move all the code from a master page into a single directory so that images and CSS are cached and only uploaded once instead of each time per page. Quote: Large sites with several directories also often required completely republishing too. This happens when a new directory is added and the whole site is published. The next time the project file is opened, the whole site needs published again. I'll have to test this. It will be marked as needs to publish the entire site if the directory is to be set to be used in the navigation bar. Quote: As I have pointed out before, I get a lot of EverWeb users contacting me with problems. Very often these are caused by code they have inserted themselves. If they think the problem is being caused by a widget, I usually ask then to publish a test page with just that on it. Most often, it's something else in their code that is actually causing the problem. JotForm is one of the main culprits since its java script screws up quite a lot of other things. Yes, this is a very difficult thing to debug. If customers are contacting you, you should be compensated for your time, but that is your decision. You are very generous with your time. Quote: Most people who code websites are very sloppy and leave too much white space - that includes some of the code inserted by EverWeb. I have no quarrel with removing white space but I can't see any benefit in removing all the returns. There is no benefit in having them. Quote: I see many user websites who use litterally dozens of shape images on each page which don't need to be there. Removing returns in the HTML isn't going to offset all that stuff! This is improved drastically with the master page optimizations. Likewise further optimizations we will be adding will improve this as well. ------------------------------- Paul EverWeb Developer

10 years ago	User: Roddy 10 years ago Report \| Post #5
User: Roddy Title: User Location: GB Posts: 5843	Quote: Yes of course it does since it has to be removed from all the pages it was once on. I wasn't removing it - just copying it. Try it yourself and you will see what I mean. Quote: I'll have to test this. It will be marked as needs to publish the entire site if the directory is to be set to be used in the navigation bar. It's nothing do do with adding a directory to the navigation. The site it just did this on uses a custom navigation - not the EverWeb widget. Quote: There is no benefit in having them. There is to me and, with the general increase in internet download speeds, many argue that removing returns does not give much advantage. Too many, too large image and other media files are the main problem. Quote: This is improved drastically with the master page optimizations I'm not seeing any benefit but I only use a master page for the header and its content - such as the navigationand - and the footer. As I mentioned before, my navigation HTML doesn't get optimised and the stylesheet is still placed in every instance of the ewExternalFiles folder. ------------------------------- 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.

Post Reply

You must login or signup to post.

FROM THE BLOG

CONNECT

SUBSCRIBE

OUR OFFICE

1136-3 Centre St. Suite #262
Thornhill, Ontario, Canada L4J 3M8
Phone: 1-888-500-2901