Property Images
ProMaps.PropertyImages History
Hide minor edits - Show changes to output
April 14, 2020, at 04:10 PM
by - Updated thumbnail creation details
Changed line 21 from:
The field Media::Thumbnail is set to an auto-enter calc, so thumbnails are created for you automatically as Media records are populated with images. Change the definition of this auto-enter calc to change the thumbnail size.
to:
The field Media::Thumbnail is a container field that is populated when you manually add an image using the Properties Detail layout. There is a script trigger on the image container that runs the "Process Image..." script.
Added line 17:
Instructions for making that change are %newwin% [[https://www.seedcode.com/filemaker-maps-swap-container-fields-google-street-view/ | here]].
Changed line 15 from:
%newwin width=500% [[ https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewSmall.jpg | https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewLarge.jpg]]
to:
%newwin width=500% [[ https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewLarge.jpg | https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewSmall.jpg]]
Changed line 15 from:
https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewSmall.jpg
to:
%newwin width=500% [[ https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewSmall.jpg | https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewLarge.jpg]]
Added lines 10-16:
!! Dynamic Images
The path to your image is defined in the "gm_MapData” field in your properties table. You can get creative here and show images from other URLs when you don't have an image. A customer submitted %newwin% [[https://www.seedcode.com/filemaker-maps-swap-container-fields-google-street-view/ | this cool mod]] showing how to use Google Street View images of the address:
https://www.seedcode.com/wp-content/uploads/2017/12/ProMapsStreetViewSmall.jpg
Changed line 9 from:
If none of your records will have photos, just delete this placeholder image and ProMaps won't attempt to show it. (Another way to remove images from then popover is to comment out the line setting our $sc_ImageURL variable in the script "Compile Map Data" in ProMaps' mobile file.
to:
If none of your records will have photos, just delete this placeholder image and ProMaps won't attempt to show it.
Changed lines 7-8 from:
If only some of your records have images, ProMaps will show a "no image" slide for the ones missing images. You can change the placeholder image used by altering the "Default Property Image" in Setup (navigate to the Setup layout in FileMaker Pro, before distributing the mobile file to your users).
to:
If only some of your records have images, ProMaps will show a "no image" slide for the ones missing images. You can change the placeholder image used by altering the "Default Property Image" in Settings / General Settings.
Changed lines 13-23 from:
On mobile, the field Media::Thumbnail is set using a script trigger upon modification of the Media::MediaContainer field. The script used in the ProMaps mobile file is called "Process Image..." and you can edit the parameter coming into that script to make you thumbnails larger or smaller.
Note that thumbnails are synced DOWN to the mobile ProMaps file (so you don't have to build them on iPad if we already have them on the server) but not synced up to the hosted file: only the MediaContainer field is sent up. And, of course, the auto-enter calc in the hosted file will make that thumbnail as soon as new photos are received.
!! Thumbnails and sync speed
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
More general notes about speeding up GoZync can be found %newwin% [[GoZync3.Speed | here]]
to:
The field Media::Thumbnail is set to an auto-enter calc, so thumbnails are created for you automatically as Media records are populated with images. Change the definition of this auto-enter calc to change the thumbnail size.
Changed lines 9-10 from:
If none of your records will have photos, just delete this placeholder image and ProMaps won't attempt to show it.
to:
If none of your records will have photos, just delete this placeholder image and ProMaps won't attempt to show it. (Another way to remove images from then popover is to comment out the line setting our $sc_ImageURL variable in the script "Compile Map Data" in ProMaps' mobile file.
Added lines 5-10:
!! What if I don't have an image?
If only some of your records have images, ProMaps will show a "no image" slide for the ones missing images. You can change the placeholder image used by altering the "Default Property Image" in Setup (navigate to the Setup layout in FileMaker Pro, before distributing the mobile file to your users).
If none of your records will have photos, just delete this placeholder image and ProMaps won't attempt to show it.
If only some of your records have images, ProMaps will show a "no image" slide for the ones missing images. You can change the placeholder image used by altering the "Default Property Image" in Setup (navigate to the Setup layout in FileMaker Pro, before distributing the mobile file to your users).
If none of your records will have photos, just delete this placeholder image and ProMaps won't attempt to show it.
Changed lines 13-15 from:
!! Thumbnails and speed
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
to:
!! Thumbnails and sync speed
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
More general notes about speeding up GoZync can be found %newwin% [[GoZync3.Speed | here]].
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
More general notes about speeding up GoZync can be found %newwin% [[GoZync3.Speed | here]].
Changed lines 7-8 from:
On the hosted side the field Media::Thumbnail is set to an auto-enter calc, so thumbnails are created for you automatically as Media records are populated with images. Change the definition of this auto-enter calc to change the thumbnail size.
to:
On the hosted side, the field Media::Thumbnail is set to an auto-enter calc, so thumbnails are created for you automatically as Media records are populated with images. Change the definition of this auto-enter calc to change the thumbnail size.
Changed lines 3-15 from:
Images are in a separate table (media). Thumbnail of first related media record is used. Thumbnails are made where?
to:
Images are in a separate table (media) related to the properties table. The thumbnail of the first related media record is used in the map popover.
!! When / Where are thumbnails created?
On the hosted side the field Media::Thumbnail is set to an auto-enter calc, so thumbnails are created for you automatically as Media records are populated with images. Change the definition of this auto-enter calc to change the thumbnail size.
On mobile, the field Media::Thumbnail is set using a script trigger upon modification of the Media::MediaContainer field. The script used in the ProMaps mobile file is called "Process Image..." and you can edit the parameter coming into that script to make you thumbnails larger or smaller.
Note that thumbnails are synced DOWN to the mobile ProMaps file (so you don't have to build them on iPad if we already have them on the server) but not synced up to the hosted file: only the MediaContainer field is sent up. And, of course, the auto-enter calc in the hosted file will make that thumbnail as soon as new photos are received.
!! Thumbnails and speed
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
!! When / Where are thumbnails created?
On the hosted side the field Media::Thumbnail is set to an auto-enter calc, so thumbnails are created for you automatically as Media records are populated with images. Change the definition of this auto-enter calc to change the thumbnail size.
On mobile, the field Media::Thumbnail is set using a script trigger upon modification of the Media::MediaContainer field. The script used in the ProMaps mobile file is called "Process Image..." and you can edit the parameter coming into that script to make you thumbnails larger or smaller.
Note that thumbnails are synced DOWN to the mobile ProMaps file (so you don't have to build them on iPad if we already have them on the server) but not synced up to the hosted file: only the MediaContainer field is sent up. And, of course, the auto-enter calc in the hosted file will make that thumbnail as soon as new photos are received.
!! Thumbnails and speed
It is faster to Push your syncs up than to do Round Trips: in Round Trips the iPad's (slower) processor actually makes the thumbnails on the host for new or edited Media records. In a Push, the iPad drops off the MediaContainer and then disconnects: it's a server side script that processes the InBox and thus ends up making the thumbnail. More on %newwin% [[http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.InboxProcessing | InBox Processing]].
Changed lines 1-2 from:
!! How to I specify an image for my property.
to:
!! How do I specify an image for my property?
Added lines 1-3:
!! How to I specify an image for my property.
Images are in a separate table (media). Thumbnail of first related media record is used. Thumbnails are made where?
Images are in a separate table (media). Thumbnail of first related media record is used. Thumbnails are made where?
