In our MyGeotab Map Deeper Add-In, we're trying to avoid resource-intensive Geotab API vehicle polling using Get.DeviceStatusInfo multicalls(). In our Add-In, is there a way to attach to Vehicle "moving" MyGeotab Map events? We want to use the service.canvas.marker() method to re-draw elements on the map to any changing vehicle lat/lng? Could Geotab suggest best practice for this use-case?

MyGeotab SDK Best Practice for attaching to MyGeotab Map vehicle moving Event in our Deeper Add-In

Out Team has almost completed our development of a MyGeotab Map Deeper Add-In.Unfortunately, we're blocked with 3 issues regarding the Deeper API / SDK.  (1) How Add-In can detect in CSS/API when running on Tablet or Mobile device ?  (As Add-In is always running in a 450px width iFrame, CSS media selectors will not work) (2) Detect if Add-In Panel open / closed via API or CSS selectors ?(3) Open / Close Add-In Panel via API ?   (The panel is open / closed dynamically by MyGeotab, we're hoping to give the Add-In more capability to direct users to the presence of new hidden data in panel by opening it programmatically when it is closed) We've searched the forum hoping someone else in the community may have also experienced or reported it as a feature request? Does Geotab Dev Team / Support have any suggestions or workarounds for these issues? 

MyGeotab Map Deeper Add-in SDK Development Questions

page-user page-user-lance-mitchell-1292 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Has Anyone gotten an update from Geotab development on the implementation of this feature request?

<a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​ - Ahh. I see totally. Thanks for the Clarification. I forgot about the base64 embedded option. Yea, you're right. That is a major support upgrade headache.  One option may be to possible. If there is one Add-in app that most of your customers use that has uses admin privileges, you can write some update code to perform a get.SystemSettings() API call to scan and then update (if required) the JSON code in "customerPages" to modify the ICON URL to use an external SVG URL to your cloud service. That way the first user to run your Add-In, repairs your installation and everything is viewed correctly on the nex MyGeotab page load.  Its possible the stutter delay has been resolved with a re-prioritization of new MyGeotab UI loading. It would need to be tested and verified, of course...Just a thought.

Has anyone built a new logo for an add-in for the new MyGeotab UI?

<a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​ - Help me to understand what changed in your Add-In JSON code? Was it changing your URLs from JPG to SVG? Because I'm unclear of what else has changes n the new file format requirements. Thanks

<a href="/user/jake-jorns-8255" data-id="8255" data-value="jjake-8255" data-denotation-char="@" class="text-decoration-none mention">@jjake-8255</a>​ and <a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​ . I guess we're all in this pickle-barrel together.... sandwich between Geotab and our Customers. Does not make for a good presentation for our sales teams though.

<a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​ - I am speechless.Why would Geotab as a strategy, release a software update that intentionally breaks all Add-In icons? Unfortunately, like yourself our suite of Apps uses the feature preview to enable the Deeper Add-In functionality. So using the UI is not a choice for us and our customers. Its not a hidden feature, but a requirement that we've automated to make it easier for our customers to use our products without technicalities. This just does not seem very well thought out on Geotab part. I wonder how long we'll be telling our customers to wait for the new release. Q2 is a long ways away.

Thanks for feedback <a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​. But you raise some interesting concerns. We are not using the mypreview version as our products are live with an active customers base.Our live database (and I may presume) some of our customers databases have been recently updated to the following release with the new UI design, Version: 5.7.2004.1182-release2004-a1d3476<img src="/forum/plugins/gcs-uploads/files/0692J00000CdeZlQAJ.jpg" alt="new-myGeotab-release" />I'm presuming the attached screenshot (with our broken default icons) is the 2004 release you are referring to in your post. Are you saying that this release was rolled out without support for properly rendering icons??That there is no fix for this icon issue until they publish a 2101 release to live?

<a href="/user/jake-jorns-8255" data-id="8255" data-value="jjake-8255" data-denotation-char="@" class="text-decoration-none mention">@jjake-8255</a>​ - Our database is using the new UI Design, so we were forced to re-generate our Add-In icons. Unfortunately our design team created the AI files so I do not have that to share, but they told me that to comply there were significant changes to our SVG files. Here is what they summarized. "The biggest difference is with the uniformity requirements. All icons must be set in one-colour: #66788C and have a uniform line style with a stroke width of exactly 2px with rounded end caps and miters." We replaced the new SVGs on our server and verified it using CURL to confirm the CORS requirements<img src="/forum/plugins/gcs-uploads/files/0692J00000CdcxWQAR.jpg" alt="cors-svg" /> But even after clearing our MyGeotab browser cache + removing/re-adding our Add-In JSON in our database<code>{
 "name": "SpartanLync Tools",
 "supportEmail": "support@spartanlync.com",
 "version": "1.0.1.02",
 "items": [{
 "url": "https://help.spartansense.com/geotab/spltools/splgeotabtools.html",
 "path": "",
 "menuName": {
 "en": "SpartanLync Tools"
 },
 "icon": "https://help.spartansense.com/geotab/spltools/images/spartanlync-tools-menu.svg"
 }]
}</code>Our app icons still will not load in the new MyGeotab UI.<img src="/forum/plugins/gcs-uploads/files/0692J00000CdccdQAB.jpg" alt="new-mygeotab-ui" />But they load just fine in the old MyGeotab UI using the new style guidelines<img src="/forum/plugins/gcs-uploads/files/0692J00000CdcYEQAZ.jpg" alt="old-mygeotab-ui" />So we're not been able to prove the new guidelines work either

Hi <a href="/user/noah-mapstead-1162" data-id="1162" data-value="noahthenomad-1162" data-denotation-char="@" class="text-decoration-none mention">@noahthenomad-1162</a>​ , I too have noticed how consistently badly-off are the coordinates returned from the .attachMenu() method. Especially if you need to use the coordinates to position elements on the map.  Though your workaround to scrape better coordinates from the DOM may work in the short-term, it may not be sustainable with future versions of MyGeotab, because future MyGeotab UI changes may break your code. What I found much more reliable was to use the supplied device.id to perform a Get.DeviceStatusInfo API call and use the resulting dsi.latitude / dsi.longitude coordinates for the Map positioning (or in your case Google Maps). Just thought I should pass that along from my own experiences with the Deeper SDK for anyone else experiencing our issue.

Problem with coordinates in deeper add-in

<a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​ Thanks for the "Painting" clarification. Makes allot of sense and that event alone would serve me as well. BUT a "Painting" event MAY be too generic an event to return the relevant info (in the event object) that every integrator would need so they could implement efficient but responsive UI designs that serve their business needs. So it's my thought that event specialization would need to be balanced with generalized "something happened" events by Geotab developers. Whatever they implement must serve everyone's needs, which is hard to get that recipe right. But something is better than nothing, which is where we're at right now with Map events.

Aktivitas Terbaru

MyGeotab SDK Best Practice for attaching to MyGeotab Map vehicle moving Event in our Deeper Add-In

MyGeotab Map Deeper Add-in SDK Development Questions