On Oct 8, 2018, at 11:28 AM, [email protected] wrote: > Unexpected discovery - the picture library is still a useful thing!
This is so true. I’m still a big user and believer in the Picture Library. There are two big benefits for me: 1. If you are updating your 4D application often and using images on forms, it’s convenient to not have to worry about adding and updating image files in the Resources folder when you deploy the update. Picture Library is stored in the .4DB and .4DC file so you know every image referenced will always be found. Just copy the new .4DC and .4DIndy files and you have deployed your application update. 2. If your application is running under 4D Server your 4D Client users benefit from the built in 4D Client “download only what I need when I need it” architecture. If you use the Resources folder to store all images, and that group of images is 300MB in size, 4D Client must download the entire 300MB Resources folder at startup when you deploy a new version of your application. Could be a a noticeable delay. Picture Library works just like methods and forms. Using the Picture Library, when an image is needed, 4D Client checks its locally cached resource file to see if it exists, if not it download that single image. Not all 300MB of images. And if 290MB of images are never needed or used by a particular client they never have to download them. Tim ***************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ***************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
