Working on this as well...
Which paths are you 'hard coding'?
I hard coded the paths in the _edgetPreload.js and it worked. I found this great tutorial here: http://www.danielhanly.com/blog/tutorial/adobe-edge-embedding-animations-page/. I followed all of the steps and I got the animation to run on my test site. Did you have any luck?
@ti2m - Do you plan on making your plugin available for production?
if the plugin is considered to be ready for production doesn't really depend on me but on - well basically on you and the community ;-) People are actively testing it right now and the feedback has been good. I'm doing more feature implementation then bugfixing, which is a good sign I guess. I'm not marking it to be ready for production yet, but I have seen plugins out there that are way worse then this one. I'm just really conservative when it comes to offical statements. Hope that answers your question.
Thanks ti2m! I will load the plugin and give it a shot.
This plugin looks great. I also tried to use the tutorial on how to embed an adobe edge animation, however I have been embedding with iframes instead. With iframes I had some issues with older IE browsers. Unfortunately, my client uses one when the site doesn't work it doesn't reflect well on the web design!
I have integrated a couple of edge animations into this site: http://www.jackpurcellmeats.com.au/beef-cuts-guide/
I was just wondering what were the main benefits of using a plugin as opposed to iframes. Compatability? Page load speed?
I guess I have two answer on two levels. The wordpress plugin (EdgeSuite) allows you to place compositions inline or use iframes, so it is not really plugin vs. iframes.
EdgeSuite brings various benefits (if you ask me):
- First of all, it comes down to just uploading stuff, place it, done. No ftp upload, filehandling or whatsoever.
- More over that the plugin enables sharing of core edge libraries. E.g. if you place two compositions on a page without modifying them, all the edge libraries (edge.js, jquery, yep, easings...) will be loaded twice as they sit in different directories. Same with viewing compositions on different pages, each composition loads its own set of libraries. 10 different compositions results in 10x loading of all libs. Edge Suite on the other hand alters the path for the resources and places them in one directory. Libs are only loaded once, for the whole page.
- If you have a simple website cluttering your webspace at root level might be an option. If you are using a CMS and have 10 compositions that is just awful. EdgeSuite places all composition files in a clean file structure within subfolders, no cluttering.
That's just from the top of my head.
The iframe topic is a bit more difficult. Personally I think iframes are mostly bad practice. It's like in the early days of the web with table layouts and framesets. There are cases where iframes make total sense and are the best way to go and that's why EdgeSuite can also render iframes. But I personally only want to "see" an iframe when there is no other option. If you can do it inline, do it inline. Bad SEO, loading times, semantic fragmentation... security aspects, sandboxing on the other hand are just a couple of the most common arguments. Most of the arguments don't directly apply to the context of Edge Animate, but still... decide for yourself
Hope that answers your question to some degree.
just to say I'm launching (very soon) a new brand for my business, here and I would appreciate any advice or feedback on this, since I'm using the plug-in Edge suite. all comps using iframes... sorry its the only way I manage to make it the best way to work all together...
every thing seems globally quite fine, although I have sometimes difficulties to load the comps, don't know if it's the cache playing with my nerves or anything else...
Le site prend beaucoup de temps à apparaitre.
The site takes a long time to load. There is no visual to say that it is loading assets. This could be a problem.
not entirely sure what your question is. Is the comp not loading at all from time to time or is the page just slow?
If it's slow, use yslow for FF or pagespeed for Chrome to get an idea of whats going on when loading your page. Your site is a total of 2,4 Mb with 80 requests and compression doesn't seem to be activated on your server. For me here in Germany the site loading time wasn't to bad, it depends on how much effort you want to put in optimizing the loading time. CSS sprites are always a really good starter and as mentioned the compression!
yes the comps not loading from time to time... and visuals are there .. I mean the preloaders are well set on every comps ... sometimes it actually stays stuck onto the preloaders... nothing comming until, we have to reload entire page. ...
Site is on a ovh mutualized server, in north of France...
Thanks for the feedback anyway, I did the optimized images thing, but i still did'nt get trough the whole classic compression and optimizing steps ; http compression, yslow, cache plug-in, code kit and all that stuff...
I've fixed up compression now, as far as I could, according to my skills, things should go faster... (looks faster my side anyway)
- enabled gzip http compression on the server side and enabled W3 total Cache plug-in, (didn't quite get every settings of that Plug-in though) and finally optimized every images using imageOptim
Now comps don't seem to be stuck in anyway now. But this is my only point of view, if anyone could give me a little feedback that would be very much appreciated, thanks.
1 person found this helpful
On my side (Texas), in Firefox 14.0.:
1st time - took a while to load.
2nd time after clearing cache:
loaded pretty fast.
Loaded about as fast as the second time in Firefox.
Chrome latest version
Loaded a little slower than the others