Information Systems:Notes on Infonet Development - Revision history

Norwinu at 17:16, 16 May 2017

2017-05-16T17:16:20Z

Norwinu: /* SQL PML functions */

2016-11-19T00:30:10Z

SQL PML functions

Norwinu: /* SQL PML functions */

2016-11-19T00:10:16Z

SQL PML functions

Norwinu: /* Overview */

2016-11-08T22:15:52Z

Overview

Norwinu: /* Google Analytics - PML include */

2016-11-08T22:14:23Z

Google Analytics - PML include

Norwinu: /* JSON */

2016-11-08T21:57:59Z

JSON

Norwinu: /* Code standardization */

2016-11-08T21:56:39Z

Code standardization

Norwinu: /* Google Analytics - PML include */

2016-11-08T21:56:15Z

Google Analytics - PML include

Norwinu: /* Code standardization */

2016-11-08T21:55:51Z

Code standardization

Norwinu: /* Google Analytics - PML include */

2016-11-08T21:55:10Z

Google Analytics - PML include

@@ Line 52: / Line 52: @@
 [[Category: Infonet]]
 [[Category: WebSmart]]
 [[Category: Norwin]]

@@ Line 40: / Line 40: @@
 There are two main PML query functions - sqlquery and sqlexec, with the latter being polymorphic. Polymorphism, in this context, can be best described as when a field/column in a table has the same name as a PML variable/work field. For example, the table UWDASWPRDD.XXITEMP has the column/field "ITPRDC", but when working with the file in WebSmart, ITPRDC also becomes a programming variable. <sub>(P.S. I'm dating myself by explaining this here - no one is ever going to read this. In fact, I'll give you $5 if you're reading this. Just come and ask me for $5. I'll know exactly what you're talking about.)</sub>
-The syntax for working with polymorphic names,  sqlexec is done through the following syntax (memorize this!):
+The syntax for working with polymorphic names, sqlexec is done through the following syntax (memorize this!):
 <code>sqlexec("select column1, column2 into :some_variable from some_table where POTATO=:POTATO")</code>
 I've forgotten this a million and one times.
 [[Category: Infonet]]

@@ Line 37: / Line 37: @@
 ==SQL PML functions==
-Polymorphism in sqlexec is done through the following syntax (memorize this!):
+The syntax for working with polymorphic names,  sqlexec is done through the following syntax (memorize this!):
-<code>sqlexec("select column1, column2 into :some_variable from some_table where pml_variable_column_name='" + PML_variable + "'") </code>
+<code>sqlexec("select column1, column2 into :some_variable from some_table where POTATO=:POTATO")</code>
 I've forgotten this a million and one times.

@@ Line 1: / Line 1: @@
 =Overview=
-This page probably won't last, the topic is massive. Nonetheless, an area needs to be devoted to discussing development in Infonet (therefore, mostly talk related to WebSmart). That starts here.
+This page probably won't last as the topic is massive. Nonetheless, an area needs to be devoted to discussing development in Infonet (therefore, mostly talk related to WebSmart). That starts here.
 =Bootstrap redesign and new conventions=

@@ Line 15: / Line 15: @@
 ==Code standardization==
 ===Google Analytics - PML include===
-Google Analytics (GA) is a service that allows you to track and analyze web usage. read more about the implementation of GA at uniPHARM [[Information Systems:Google Analytics|here]]. While the tracking code is just a small HTML snippet invoking a javascript function to send data to GA servers, the fact that we have a test and production environment complicates things. Basically, we use one WebSmart source file per program and simply compile it into two different objects residing in different environments. Meanwhile, the GA tracking code must be unique to report different statistics for the dev and production environments (yes, both are tracked separately).
+Google Analytics (GA) is a service that allows you to track and analyze web usage. Read more about the implementation of GA at uniPHARM [[Information Systems:Google Analytics|here]]. While the tracking code is just a small HTML snippet invoking a Javascript function to send data to GA servers, the fact that we have a test and production environment complicates things. Basically, we use just one WebSmart source file for every program and to achieve two copies we simply compile it into two different objects residing in different environments. Meanwhile, the GA tracking code must be unique to report different statistics for the dev and production environments (yes, both are tracked separately).
 Therefore, a PML function should be included in every page as follows:

@@ Line 32: / Line 32: @@
 ===JSON===
-WebSmart is including more and more JSON functionality with every release, and this will allow Infonet development to have more web-service/API-based functionality. The intent will be to make customer names and numbers clickable wherever they exist, and that will in turn call (through AJAX) a central program that will return customer information via JSON.
+WebSmart is including more and more JSON functionality with every release, and this will allow Infonet development to have more web-service/API-based functionality. The intent will be to do stuff like make customer names and numbers clickable wherever they exist, which in turn will call (through AJAX) a central program that will return customer information via JSON.
 The development for that has started in in2_srvapi.pgm.

@@ Line 18: / Line 18: @@
 Therefore, a PML function should be included in every page as follows:
  func z_ga(){
- if (scanstr("WEBDEVP",pgmf_pgmlib) <> 0){
+  if (scanstr("WEBDEVP",pgmf_pgmlib) <> 0){
-  include("/webroot/unipharm/in2/includes/in2_ga_dev.html");
+   include("/webroot/unipharm/in2/includes/in2_ga_dev.html");
-−
+  }
- else if (scanstr("WEBPRDP",pgmf_pgmlib) <> 0){
+  else if (scanstr("WEBPRDP",pgmf_pgmlib) <> 0){
-  include("/webroot/unipharm/in2/includes/in2_ga_prd.html");
+   include("/webroot/unipharm/in2/includes/in2_ga_prd.html");
-−
+  }
- else return;
+  else return;
+ }