Firefox is NOT a supported browser for Wed Direct because of how it handles HTML5
Start here for how to think about and build for WebDirect
Implement themes (youll see why in the RCC video)
Design for less objects on a layout.
Design with a workflow in mind so you can have minimal functionality on a layout.
What works good in client might not play so well with WebD
If you search the forums you will find lots of information on how to build for WebD and the most common and sensible is to isolate the WebD versions from any other versions by building a file just for WebD
I would try with another, supported browser on the same machine, about the same time. If that browser doesn't flicker, it's a browser issue.
By raw images You mean logo's etc? (I'm on a celluar network, did not view the movie)
- could also be network related
We have used Filemaker since 2004, Filemaker 5, more than 11 years now, so we are not really newbies.
We just converted the FM12 application to Webdirect.
That was not enough apparenlty.
We now applied standard FM themes, and that caused the flickering to stop.
Thanks for your replies!
oh yes... the 'classic' theme eats all Your bits in the wire. There is a really good doc about performance, available on 'downloads', technet (here)
Glad you have a correct answer, but noted that you using an i5 processor for Windows 2012 and FileMaker server? I'm sure it'll work, but just won't be optimal performance when compared to an i7 processor, which doesn't cost that much more money (see a comparison of i5 to i7 by PC Magazine at Which CPU Should You Buy? Comparing Intel Core i5 vs. i7 | PCMag.com ). Hopefully it is for light duty or maybe a development server. Also, while 8 gig is minimum recommended.... I generally recommend clients go with at least 16 if they want a well performing FileMaker server. Then again, maybe you have a light duty use server and this meets your needs.
searched for another thread - found this.
after doing some tests under Windows 8.1 and FileMaker 14.03, this seems to be just not true.
- calculating is faster when not using classic, so far it is true
- but rendering takes much more time with the new themes
means: From the users point of view, classic is MUCH faster. Difference in calculating is 50% - but thats milliseconds. Rendering can take a second... (will be dependent of the hardware (graphics card..) - but in the tested environment, we keep off of rewriting layouts!)