Viewing Take It To The Limit...

Take It To The Limit...



User: Roddy 11 years ago
There seems to be a limit to the size of the project file that EverWeb can cope with.
I broke the widgets away from the everwebcodebox.com website when it slowed to a crawl.

The Widgetbox site project file is now 455 Mb. The file takes over 30 seconds to open in EW.

I made a widget for inserting the jQuery Panorama Viewer. It worked perfectly in two test sites using a huge image file of 2.6 Mb.
In the larger project it broke and the wheel spun every time I tried to change the widget settings.
The image file was reduced to 700kb and the settings started to work and even better when the file was reduced to 200Kb. Still the widget is broken in EW.

I then tried it in the Codebox site which has a 148 Mb size using the largest image - 2.6 Mb. It struggles a little but works OK and behaves perfectly when the smallest 200Kb file is used.

Although broken in EverWeb, the Panorama Viewer publishes fine as can be seen on the WidgetBox website here…

http://everwebcodebox.com/widgetbox/carousel/panorama.html

In this case I am using the smallest image for a faster download time but it also works with the other two larger files - just not in EW.

I am wondering what a sensible upper limit for the project file size is and if anybody has a project file that is somewhere in between the two sizes I mentioned above - 148 & 454 - of perhaps around 300Mb who would be willing to test this widget with the largest image file to see what happens?

Last edit 11 years ago

-------------------------------
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: Paul-RAGESW 11 years ago
I don't think it's the size of your project file I've worked with websites that are upwards if 2gb in file size without problems.

What we do have to improve on is the loading time of large projects in EverWeb.

I can figure out what the problem is if you send me the website project file and the steps you took to produce these issues.

I suspect it's something unrelated to the size of your project.

Last edit 11 years ago

-------------------------------
Paul
EverWeb Developer
User: Roddy 11 years ago
OK, I'll do that. I would be interested to know why this is happening because it only does this in the large file and not in any of my other smaller ones.

-------------------------------
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: Roddy 11 years ago
I put this widget into my box of broken toys and failed experiments. Tonight, I opened it up and tried a workaround that I've used before on widgets that work fine in the browser but don't display properly in EverWeb - it worked!

Sometimes EW won't load some essential piece of data from the stylesheet and I try to guess what it is and add it as an internal or inline style. In this case I had to add "overflow:hidden" to the containing div and, as a desperate measure, add the selector for height to the image inline style as well as having it in the div styles.

I still don't understand why I have to do this and even less do I understand why it worked before in a small test project file but not in the larger one. I guess the answer to that one is still blowing in the wind.

Anyway, as Paul surmised, it wasn't anything to do with the size of the project file - just my inadequate widgetmanship. Here's the result and I don't want anyone to tell me it doesn't work now!

http://everwebcodebox.com/widgetbox/carousel/panorama.html

-------------------------------
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.