{"id":956,"date":"2019-06-29T22:22:19","date_gmt":"2019-06-30T03:22:19","guid":{"rendered":"http:\/\/hardlikesoftware.com\/weblog\/?p=956"},"modified":"2019-12-24T14:14:35","modified_gmt":"2019-12-24T19:14:35","slug":"interactive-grid-tour-app","status":"publish","type":"post","link":"https:\/\/hardlikesoftware.com\/weblog\/2019\/06\/29\/interactive-grid-tour-app\/","title":{"rendered":"Interactive Grid Tour App"},"content":{"rendered":"

At Kscope 19 in Seattle and APEX Connect in Bonn I presented a beginners session<\/a> on interactive grid where I demonstrated an app that gives a guided tour of the interactive grid features. As promised I’m making the app available. It uses the same data as the Sample Interactive Grids app so make sure that is installed first. Then download the Interactive Grid Tour<\/a>. If you are new to interactive grid this app is a good introduction to what it can do. It takes a different approach compared to the Sample Interactive Grids app in that it guides you through just about all of the built-in capabilities with a series of popup notes.<\/p>\n

\"Interactive<\/p>\n

Even if you are already an expert on IG the app may still have some value for you. Have you ever wanted to make sure users are aware of some new feature in your app. You have probably seen apps that do this. After an upgrade they will popup a note or notes that point out some new things. There is a reusable widget in this app that does just this.<\/p>\n

<\/p>\n

[Update 24-Dec-19 there is a newer version of the showMe widget that works for 19.2 that you can find here<\/a>]<\/p>\n

Here\u2019s the scenario: You have a popular app that has been in use for years. The users are very familiar with it. You have added two new features that they get to from buttons on the home page but you are concerned that users won\u2019t notice because their navigation patterns are so ingrained. You want a popup to educate them about the new features when they use the app. This is what the showMe<\/code> widget is for. Making use of this widget will require some JavaScript and CSS skill.<\/p>\n

Here are the steps to make use of it in your own apps:<\/p>\n

    \n
  1. Download<\/a> the tour app and install it. Run the app to get a feeling for what showMe can do.<\/li>\n
  2. Go to Shared Components > Application Files and extract (download) the IGtour.css<\/code> and showme.js<\/code> files.<\/li>\n
  3. The styles needed for showMe<\/code> widget are in the IGtour.css<\/code> file. Copy all the rules after the “Show-me classes” comment into your application\u2019s CSS file. What, your app doesn\u2019t have it\u2019s own CSS file? Hmm. Must be a very straight forward app. No problem. You can add a new CSS file (recommended) or simply copy the rules into the page CSS inline attribute on any pages where showMe<\/code> is going to be used.<\/li>\n
  4. Go to your app where you want to add a tour. Or create a new app just to try this out.<\/li>\n
      \n
    1. Go to Shared Components > Static Application Files. Upload the showme.js<\/code> file and the file where you added the CSS rules. I\u2019ll assume it is called app.css<\/code>.<\/li>\n
    2. Now go to Shared Components > User Interface Attributes > Desktop.
      \nIn JavaScript File URLs enter:<\/p>\n
          #APP_IMAGES#showme.js<\/code><\/pre>\n
      In Cascading Style Sheets File URLs enter:<\/p>\n
          #APP_IMAGES#app.css.<\/code><\/pre>\n
      If you added the CSS rules to an existing file that is already loaded then this last step isn\u2019t needed. Note:<\/strong> If you are only adding a tour to one or a few specific pages then you could load these files just on those pages. The general idea is that these two files need to be loaded on any page where you want to give a tour of your app features.<\/li>\n<\/ol>\n
    3. Go to the page where you want to add the tour. I\u2019m going to assume that there are two buttons on this page that represent the new features to call out and their static ids are “feature1” and “feature2”. You can substitute any jQuery selector you like in the tour steps and even add more steps (See step 7).<\/li>\n
    4. Add an inline popup region to the page. Add a Static Content region to the Inline Dialogs position and set the Template to Inline Popup. Set the title to “Tour”. The title won\u2019t be seen. Set the templates options: Remove page Overlay and Set Dialog Size to None. The showMe<\/code> widget uses the popup functionality but doesn\u2019t include it so that you can customize the popup to fit your needs. Note:<\/strong> you won’t use the apex.theme.openRegion<\/code> API with this popup region.<\/li>\n
    5. The tour is driven by markup added to the popup. Add the following to the popup region Source Text attribute.\n
      <ul class=\"show-me\">\n    <li data-element=\"#feature1\">\n      Press this button to make a random person on the Internet a little happier today.\n    <\/li>\n    <li data-element=\"#feature2\">\n      Press this button to be <em>5% more<\/em> productive.\n    <\/li>\n<\/ul>\n<\/code><\/pre>\n
      The show-me<\/code> class causes this list to be turned into a showMe<\/code> widget automatically when the page loads. Each list element is a step in the tour. The content of the list element is shown next to the element identified by the jQuery selector in data-element<\/code>. Other attributes used to control the showMe tour steps include: data-name, data-position, data-zindex, data-width, data-height, data-url<\/code>. The position attribute controls the popup position relative to the element and can be one of “below” (default), “above”, “left”, “right”, “inside”, and “center”.<\/li>\n
    6. Add a dynamic action to start the tour when the page loads.
      \nName: start tour
      \nEvent: Page Load
      \nAdd one Execute JavaScript Code action and Add this code:<\/p>\n
          $(\".show-me\").first().showMe(\"nextStep\");<\/code><\/pre>\n<\/li>\n
    7. Add a Next button to the Next button position in the popup region created in step 6. Set the button name to TOUR_NEXT and the label to Next. Add a dynamic action to go to the next step of the tour. This looks a lot like the one in the previous step.
      \nName: next step
      \nEvent: Click
      \nSelect Type: Button
      \nButton: TOUR_NEXT
      \nAdd one Execute JavaScript Code action and Add this code:<\/p>\n
          $(\".show-me\").first().showMe(\"nextStep\");<\/code><\/pre>\n<\/li>\n
    8. Now run the page and you should see the first tour popup. Click next to see the next tour step.<\/li>\n<\/ol>\n
      See the Interactive Grid tour app for more advanced uses. It defines a number of actions and dynamic actions on the global page (page 0) because the tour is used throughout the app. The actions let you use keyboard shortcuts. The showMe<\/code> step options doBefore<\/code> and doAfter<\/code> let you handle advanced situations where the state of the page needs to be set before the step can be shown such as selecting a tab or expanding a region. The logic to open a menu so that a tour step popup can point to a menu item is complicated and not very robust. The code for it is in the IGtour.js<\/code> file.<\/p>\n
      It would be easy to add a “don\u2019t show me this again” checkbox to the popup and save that state as a hidden page item backed by a user preference. The page load DA that starts the tour would only start it if the user hasn\u2019t checked the box. There are many other possibilities for starting or continuing the tour.<\/p>\n
      Read the showme.js<\/code> source code comments to learn about the options and methods it supports. You will probably want to modify the CSS for the popup for example to change the colors.<\/p>\n
      Because the showMe<\/code> widget is driven by simple list markup it would not be unreasonable to create an APEX list template for it. I did not do this because the list is specific to a given page, contains sometimes complex jQuery selectors, and doesn\u2019t leverage app URLs much. So I found it much more convenient to simply author the list markup right on the page.<\/p>\n
      When I created showMe I wanted to leverage the popup widget as much as possible. One thing that was missing was the callout \u2013 that little triangle that points to the element that the popup is related to. So I added the callout functionality as part of showMe. Shakeeb and I liked it so much that we added it to the APEX menu<\/code> and popup<\/code> widgets and hopefully this will be in 19.2. So this showMe<\/code> widget may need to be changed when the popup has its own callout implementation.<\/p>\n
      If you add showMe to your app I would be happy to hear any feedback you have.<\/p>\n","protected":false},"excerpt":{"rendered":"
      At Kscope 19 in Seattle and APEX Connect in Bonn I presented a beginners session on interactive grid where I demonstrated an app that gives<\/p>\n
      Continue readingInteractive Grid Tour App<\/span><\/a><\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[18,13],"tags":[41,51,44,52,53],"_links":{"self":[{"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/posts\/956"}],"collection":[{"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/comments?post=956"}],"version-history":[{"count":18,"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/posts\/956\/revisions"}],"predecessor-version":[{"id":1033,"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/posts\/956\/revisions\/1033"}],"wp:attachment":[{"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/media?parent=956"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/categories?post=956"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hardlikesoftware.com\/weblog\/wp-json\/wp\/v2\/tags?post=956"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}