Accéder au contenu principal

Using Oracle Apex with Google APIs maps and blogger

In order to add some google feature inside an Apex page, one have just to had some piece of code in header or footer part of a static region.

  • Add a new blank page or go the second step if there is an existing page
  • Add a static region into body content
  • Add the following piece of code in the HEADER TEXT part (in the right property sheet)

For a MAP

<div id="map1" style="min-height: 700px" width="100%"></div>
<script>
      var map;
      function initMap() {
        map = new google.maps.Map(document.getElementById('map1'), {
          center: {lat: -14.245413, lng: -72.477596},
          zoom: 7,
            mapTypeControl: false,
        mapTypeControlOptions: {
        style: google.maps.MapTypeControlStyle.DROPDOWN_MENU
        },
        navigationControl: true,
        navigationControlOptions: {
           style: google.maps.NavigationControlStyle.SMALL,
           position: google.maps.ControlPosition.TOP_RIGHT
        },
        scaleControl: true,
        streetViewControl: false,
        mapTypeId: google.maps.MapTypeId.ROADMAP        
        });
         
// Optionnal: Draw a circuit 
          circuit();            
      }
</script>

<script src="https://maps.googleapis.com/maps/api/js?key=<YOUR KEY>&callback=initMap"
    async defer>
   
</script>

Optionnal: Drawing of a circuit:


function circuit() {
var myCoordinates = [
new google.maps.LatLng(-12.060809,-77.014160),
new google.maps.LatLng(-16.425548,-71.520996), 
..... 
new google.maps.LatLng(-12.060809,-77.025146)
];


var polyOptions = {
path: myCoordinates,
strokeColor: "#FF0000",
strokeOpacity: 1,
strokeWeight: 3
}
var it = new google.maps.Polyline(polyOptions);
it.setMap(map);
}


For a BLOG

<div id="blog"></div>
    <script>
      function displayBlog(response) {
        document.getElementById("blog").innerHTML += response.content;
      }
    </script>

<script src="https://www.googleapis.com/blogger/v3/blogs/<YOUR BLOG ID>/posts/<YOUR POST ID>?key=<YOUR KEY>&fields=content&callback=displayBlog"
    async defer>
   
</script>



Notes: It's mandatory to get before an API key from the Google developper console.
Depending tke kind of API, there are some daily quotas (not a big deal for personal user sites)

In the above MAP sample, there is not yet a resize feature.

Commentaires

Posts les plus consultés de ce blog

Auschwitz

 Quelques livres à propos des camps d'Auschwitz La mort est mon métier (Robert Merle) - 1952 Roman avec Rudolf Hoess (responsable camps d'Auschwitz) comme personnage principal Si c'est un homme (Primo Levi) - 1947 Témoignage de Primo Levi sur sa captivité à Auschwitz Les médecins d'Auschwitz (Bruno Halioua) - 2022 Etude sur l'organisation des services de médecine à Auschwitz Je me suis évadé d'Auschwitz (Rudolf Vrba) - 2004 Récit d'un captif qui a réussi à s'échapper d'Auschwitz Shoah  (Claude Lanzmann) - 1985 Dialogues du film "Shoah" Sonderkommando : Dans l'enfer des chambres à gaz  (Shlomo Venezia ) Entretien avec un ancien prisonnier qui a tenu le rôle de sonderkommando (manipulation des corps dans les chambres à gaz) Auschwitz I Birkenau Birkenau

Oracle Documents Cloud Service - Using Upload File REST API

If the Upload File sample given in ODCS documentation is used "as is", we get a http 400 error. The syntax is strict and every blank line must be empty (no space character for instance). If we cust and paste the sample, there are residual space characters which must be removed. So, use this pattern instead: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID": " " } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain Hello World! -----1234567890-- instead the original one: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID":"FB4CD874EF94CD2CC1B60B72T0000000000100000001" } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain -----1234567890-- Tests can be...

Oracle Sites Cloud Service - Apps

It's possible to add kinds of widgets (named APPS) inside any page of a site built with Oracle Sites Cloud Service (SCS). Any app is materialized by two URL: a Renderer Url which will render any HTML fragment inside an iframe tag at runtime a settings url which will be rendrered at design time in the settings menu. all URLs must be called through https (meaning that the called server has to be ssl enabled) In the following samples, we integrate: a dummy app (a simple html page produced with node.js) which demonstrates the parameteres caried by the Sites Cloud engine when calling the backend server,  a regular Apex report or form,  a custom report which calls a rest api generated by Apex /ORDS Sample node.js server.js below is a sample of parameter values get from a dummy node.js server Main call id=26e45e21-dbb6-4877-9886-482b37213d2f instance=eyJpbnN0YW5jZWlkIjoiQTI0NUNFNUNFNjA5MjE1REZBRTA2RTQyRjExOThBNThFNzc4RDc5NzFDMkIiLCJzaWduZGF0ZSI6IjE0NTAxMDg1M...