ITRM20100175A1 - MODULAR DYNAMIC WEB APPLICATIONS PERSISTENT WITH COMPLEX INTERFACES - Google Patents

Description

DESCRIPTION of the invention having as TITLE:

"Modular and Persistent Dynamic Web Applications with Complex Interfaces",

Description

The system of Modular and Persistent Dynamic Web Applications with Complex Interfaces is based on a concept of post-rendering of web pages, which are initially written in HTML \ XHTML format and style sheets and subsequently, thanks to a parallel configuration via XML files, the final result is obtained (figures 1 and 2).

The XML file contains a structure divided into 4 logical areas (figure 3)

1. onLoad: This section indicates all the fields that must have a particular behavior, which can range from formatting, to the definition of a mandatory field, to a rendering of a complex object in an indicated area (figure 4). Within complex objects (e.g. grids, repeaters, tree views or others) it is possible to indicate the respective formatting and mandatory fields, as well as validity rules for each group of data within them (fig. 5,6,7 ).

2. JSonComunicationArea: This section defines all the communication areas to and from the server (Listing 2 and Figure 9).

3. Actions: This section defines the various actions that must be taken for the dialogue with the server. The areas to be checked and sent will be indicated, the names of the variables with which these areas will travel to the server, what type of data will transit and what should happen upon return (Listing 2 and Figure 9).

4. UserlnterfaceAction: This section defines the actions that must arise as a result of user interactions, for example enabling / disabling fields.

The ABUCore, is the Client-side framework, written in pure JavaScript, which, when a page loads, analyzes the configuration file, includes and waits for the loading of only the required libraries and generates all the code necessary for rendering. the control and operation of the page (figure 4), transforming a simple HTML / XHTML page into a Rich Dynamic Web Client (figure 5). In practice, ABUCore transforms XML tags and their respective properties into pure JavaScript source. Once a complex Client page has been created, which can contain simultaneous internal managements, just like in a real desktop management application, the data that will pass between the Client and the server have the characteristic of traveling in a compact and modular way. A framework present on the server will take care of sorting the information coming from the Client, and help in the creation of the structures coming from it and to be sent to the Client. In the current version it also deals with the creation of queries, which - written in a special parametric format - are dynamically and automatically created based on the data sent.

To transform a Dynamic Web Application with Rich Graphic Interface into a Dynamic Web Application, on Modular Request, Persistent and with Rich Graphic Interface, it is sufficient to equip the main page of the site with a menu or any type of component that allows navigation between these ( figure 11) and enclose them in a container - keep them as application portions (figures 10 and 11).

The Client framework currently allows for the creation of the following advanced components (which will surely be added, along with specialized print routines): Checklmage, Edit Combo, Dynamic Edit Combo, Dynamic Combo Repeater, MultiCheck, MultiRadio, Grids, Repeater, TreeView, Calendar , Agenda, Windows, XPStartMenu, Tabs, TabMenu, Docking Menu. The objects listed above are almost all provided for data binding and field mapping for the data import / export functions. They are also equipped with a particular technology that allows cross-checking for the validation of the various input fields in editable mode (fig. 5, 6, 7, 8), and access to the various fields is performed indiscriminately by simply indicating the name of the field assigned in the XML configuration file. Another feature of the advanced components is the knowledge of their status (writing / normal mode), of the internal variations of the data (insertion / modification / deletion of a datum) with the possibility of canceling the modifications made. They have an internal validation, which can also be extended with user rules, which allows the ABUCore to execute the validity routines for areas and avoid sending incongruent data. It also contains internal classes that are used to send and receive data, assignment, input formatting on fields through masks, classes for checking required fields, with the possibility of defining mandatory classes, adding functions and prototypes. There are classes for mapping data with JSON Areas fields.

The server framework is much simpler as it is equipped with some classes that deal with the sorting / grouping of information (Listing 5,6), as well as assigning data to the various queries (Listing 6), which being written in a proprietary and parametric format (Listing 7), allow the automatic writing of the same, without any analysis by the user for present or missing data. The data coming from the client travels compactly and in the form of classes in JSON format (Listing 8). The server will take care of the creation of the object coming from the client, which may contain a multitude of other objects, and will dispatch the various information to the various server classes specialized in data processing, which will in turn sort them to other basic classes. to obtain the complete massive processing of the data. In the event that a single processing is not carried out, all the others will be canceled, but this functionality is closely linked to the database. The server framework will take care of the packaging of the data always in a modular way, which will have to travel directly to the client (Listing 5,6).

Simple HTML Page Example (Listing 1)

<IDOCTYPE HTML PUBLIC "- // W3C // DTD HTML 4.01 // EN" "http://www.w3.org/TR/html4/strict.dtd"> <HTML> <HEADxlink rel = "stylesheet" type = "text / css" href = "../ styles / style.css" xscript type = "text / javascript" src = "ABUCore.js" x / scriptxscript type = "text / javascript" language = "javascript"> var oABUCore = new ABUCoreTest.xml "," oABUCore "); function AnagraficalnsUpd () {if (document.getElementByld (" id_anagrafica "). value.trim (). length == 0) {anagraficalnsert ();} else {anagraficalUpdate () ;}} function confìrmDelete () {var bRes = false; if (ìsDefined (<,> registry_id'.toObj (). value, ")) {var agree = confirm (" Do you want to delete the current record? "); if (agree) {bRes = true; }} return bRes; } </ scriptx / HEAD> <BODY> <form name = "frmAnagrafica" id = "frmAnagrafica" method = "post" action = ""> <div id = "XPTabAnagrafica"> <div dass = "ABUTab"> <div id = "anagrafìcaBase"> <div id = 'divABUToolBar' style = "text-align: center; widht: 100%; height: Opx; border: 0px solid;" x / div> <INPUT name = "id_anagrafica" id = "id_anagrafìca" class = "hide"> <INPUT name = "id_user" id = "id_user" class = "hide"> <INPUT name = "id_tipologia_anagrafìca" id = "id_tipologia_anagrafica" class = "hide" value = ""> <fieldset class = "in" title = "General Data Individual"> <legend id = divFisGiur> General Data </legend> <label for = "surname"> <strong> * </strong> Surname : <input id = "surname_rag_soc" name = "surname_rag_soc" class = "medium" x / label> <label for = "name"> <strong> * </strong> Name: <input id = "name" name = " name "class =" medium "> </label> <br/xlabel for="radSex"> Male <INPUT id = gender name = gender type = radio class- 'small" value =' M'x / label> <label for = "radSesso"> Female: <INPUT id = sex name = sex type = radio class = "small" value = 'F'x / label> <label for = "date_birth"> Date of Birth <input type = "text" id = â € date_birth "class =" normal "value =" "x / label> <label for =" VAT number "> VAT number <input type = "text" id = "VAT number" class = "normal" value = "" x / label> <label for = "Codice_fiscale"> Codice Fiscale <input type = "text" -id = "Codice_fiscale" class = "normal" style = "disabled" value = "" x / label> _ </fieldset> <fieldset class = "in" title = "Telephone numbers"> <legend> Telephone numbers </legend> <table id = "tblTelefoni "> </table> </fieldset> <fìeldset class =" in "title- 'Main Address"> <legend> Main Address </legend> <label for = "address" class = "req" xstrong> * </strong> address: <input id = "address" name = "address" class = "medium" x / label> <label for = "localita"> LocalitÃ: <input id = "localita" name = "localita" class = "mediumnormal" x / label> <label for = "cap"> Cap: <input id = "cap" name = "cap" class = "small" x / label> <br/> <label for = "id_nazioni" > id_nation: <SELECT id = id_nation name = id_nation class = "mediumnormal"> <OPTION if lectedx / OPTION> </SELECT> </label> <label for = "id_provincia"> id_provincia: <SELECT id = id_provincia name = id_provincia class = "mediumnormal"> <OPTION selectedx / OPTION> </SELECT> </label> <label for = "id_comuni"> id_comuni: <SELECT id = id_comunl · name = id_comuni class = "mediumnormal"> <OPTION selectedx / OPTION> </SELECT> </label> </ fìeldset> </div> < / div> <div class = "ABUTab"> <div id = "divRicerca"> <table id = "tblRicerca"> </table> </div> </div> </div> </form> </ BODYx / HTML>

Example configuration file above page (Listing 2) <ABUConfiguration> <JSonComunicationArea> <JSonArea tagld = "AreaAnagraficaBase" form = "frmAnagrafica"> <tag tagld = "id_anagrafica" fieldld = "" x / tagxtag tagld = "user_id" fieldld = "" x / tag> <tag tagld = "id_type_anagrafica" fieldld = "" x / tagxtag tagld = "surname_rag_soc" fieldld = "" x / tag> <tag tagld = "name" fieldld = "" x / tagxtag tagld = "sex" fieldld = "" x / tag> <tag tagld = "date_birth" fieldld = "" x / tag> <tag tagld = "code_fiscale" fieldld = "" x / tag> <tag tagld = "batch" fieldld = "" x / tagxtag tagld = "address" fieldld = "" x / tag> <tag tagld = "location" fieldld = "" x / tagxtag tagld = "cap" fieldld = "" x / tag> <tag tagld = " id_nazioni "fieldld =" "x / tagxtag tagld =" id_provincia "fieldld =" "x / tag> <tag tagld =" id_comuni "fieldld =" "x / tagxgrid tagld =" tblTelefoni "fieldld =" telephones "x / grid> </JSonArea> <JSonArea tagld = "AreaAnagraficaSearch" xgrid tagld = "tblRicerca" fieldld = "search" x / gridx / JSonArea> </JSonComunicationArea> <onLoad> <tag tagld = "surname_rag_soc" fieldld = " "x / tagxtag tagld =" name "fieldld = <,,>" x / tagxtag ~ tagld = "sex" fieldld = <,> '"x / tagxtag tagld =" sex "fieldld =" "x / tag> <tag tagld = "birth_date" fieldld = "" x / tagxtag tagld = "game_iva" fieldld = "" x / tag> <tag tagld = "code_fiscal" fieldld = "" x / tagxtag tagld = "address" fieldld = "" x / tag> <tag tagìd = "localita" fieldld = "" x / tagxtag tagld = "{cap" fieldld = "" x / tag> <tag tagld = "id_nation" fieldld = "" - onchange = "if (this .selectedlndex! = - 1) {changeNazione (this.options [this.selectedlndex] .value)} "initialize =" 112 "x / tagxtag tagld =" id_provincia "fieldld =" "onchange =" if (this.selectedlndex! = -l) {changeProvincia (this.options [this.selectedlndex] .value)} "initialize =" 58 "x / tag> <tag tagld =" id_comuni "fieldld =" "x / tag> <tabs tagld =" XPTabAnagrafica " varObjName = "tabAnagrafica" width = "790" height = "550" activetab = "0"> <field tagld = "detail" objHtmlld = "" title = "Detail" canclose = "false" x / field> <field tagld = "search" objHtmlld = "" title = "Search" canclose = "false" x / field> </ tabsxgrid tagld = "tblPhone" fieldld = "" varObjName = "grdTelefoni" objHtmlld = "" width = "765" height = "100"; editable = "true" created = "true" deleted = "true" paging = "false"> <field tagld = "phone_id" fieldld = "" visible = "false" sort = "" x / field> <field tagld = ⠀ description "fieldld =" "visible =" true "sort =" S "mask =" A (25) "leaveMask- 'false" req = "true" x / field> <field tagld-' phone "visible =" true "mask =" (+ 99) 999/999999 "leaveMask =" false "req =" true "x / field> </grid> <grid tagld =" tblRicerca "fieldld =" "varObjName =" grdTelefoni "tableld =" tblSearch "width =" 765 "'height =" 550 "> <field tagld =" identity_id "fieldld =" "objHtmlld =" "visible =" false "sort =" "x / field> <field tagld =" subject "fieldld = "" objHtmlld = "" visible = "true" sort = "S" format = "" label style = 'cursor: pointer; color: # 0000FF;' onclick = <,> anagraficaRead (% id_anagrafica%) <,> "% subject%" / label "" x / field> <field tagld = "address" fieldld = "" objHtmlld = "" visible = "true" sort = " S "x / field> <field tagld =" delivery "fieldld =" "objHtmlld =" "visible =" true "sort =" "x / field> </ gridxtoolbar tagld =" divABUToolBar "varObjName =" toolBar "left =" 240 "top =" 0 "> <field_ tagld =" butNuovo "image =" new.ico "hint =" New "event- oABUCore.clearJSonArea (" AreaAnagraficaBase "); ' enabled = "true" enabledMask = "lllll" x / field> <field tagld = "butSearch" ìmage = "search.ico" hint = "Search" event = "anagraficaSearch" enabled = "true" enabledMask = "00100" x / field> <field tagld = "butElimina" - image = "Delete.ico" hint = "Delete" event = "anagraficaDelete" enabled = "true" - enabledMask = "00010"> </field> <field tagld = "butArmulla" image- 'Cancel.ico "hint =" Cancel "events" "enabled =" true "enabledMask =" llill "x / field> </toolbar> </onLoad> <Actions> <action tagld =" anagrafjcalnsert "url =" Motori / anagraficalns.php "ctrlValidation =" AreaAnagraficaBase "'refreshWhenDone =" "onAjaxResponse =" "- onAfterAction =" anagraficalnsUpd_onAfterAction () "> <send name =" frmAnagrafica "value =" x AreaAnagraficaB / action> <action, tagld = "anagraficaUpdate" url = "Motori / anagraficaUpd.php" ctrlValidation = "AreaAnagraficaBase" refreshWhenDone = "" onAjaxResponse = "" onAfterAction = "anagraficalnsUpd_onAfterAction value =" name frank = "sendfica name =" "AreaAnagraficaBase" x / send> </aetion> <action tagld = "changeNazione (id_n actions) "ctrlValidation =" id_nation = ((isDefined (id_nation, <,,>)) \ x26 \ x26 (id_nation> = 0)? id_nation: -l) "onBeforeAction =" 'id_provincia'.toObj (). innerHTML = "; <,> common_id <,>. toObj (). innerHTML ="; " url = "Motori / getComuni.php" _ refreshWhenDone = "id_provincia" resultTransform = "" onAjaxResponse = "result = result.split ('\ n');" onAfterAction = ""> <send name = "id_nazioni" value = "id_nazioni" x / send> </action> </Actions> <UserlnterfaceActionxaction tagld = "radFisGiur"> <when ctrlValidation = "F"> <tag tagld = " Dt_Gen_PF "visible =" true "v =" l "x / tag> <tag tagld =" Dt_Gen_PG "visible =" false "v =" 2 "x / tag> </when> <when ctrlValidation =" G "> < tag tagld = "Dt_Gen_PF" visible = "false" v = "3" x / tag> <tag tagld = "Dt_Gen_PG" visible = "true" v = "4" x / tag> </when> </action> < / UserlnterfaceActionx / ABUConfiguration>

Menu Page Script Example (Listing 3)

ciDOCTYPE HTML PUBLIC "- // W3C // DTD HTML 4.01 // EN" "http://www.w3.org/TR/html4/strict.dtd"xHTMLxHEADxscript type =" text / javascript "src =" ../ javascript / ABUCore.js "x / scriptxscript type =" text / javascript "language =" javascript "> var oABUCore = new ABUCore (" index.xml "," oABUCore "); oABUCore.path = '../javascript/';</scriptx/HEADxBODYxDIV id = pageContentx / DIVx / BODYx / HTML>

Menu Page Configuration Script Example (Listing 4)

<? xml version = "1.0" encoding = "ISO-8859-l"? xABUConfiguration> <onLoad> <window tagld = "wAnagBanca" varObjName = "wAnagBanca" title = "Anagrafìca Credit Institutions", ... x / window> <window tagld = "wAnagMutuatari" varObjName = "wAnagMutuatari" title = "Borrowers' registry" x / window> <window tagld = "wAnagClienti" -varObjName = "wAnagClienti" title = "Customer registry" ... x / window> <window tagld = "wAnaglmmobili" varObjName = "wAnaglmmobili" title- 'Real Estate Registry "... x / window> <startMenu tagld =" startMenu "varObjName =" startMenu "container ='" '...> <field tagld = "ml0" idMenu = "10" idParentMenu = "0" caption = "Personal data" image- 'globe.ico "... x / field> <field tagld =" ml0 "idMenu =" 20 "idPar.entMenu = "10" caption = "Customers" image = "handl.ico" ... x / field> <field tagld = "ml0" idMenu = "21" idParentMenu = "10" caption = "Lenders" ... x / field> <field tagld = "ml0" idMenu = "22" idParentMenu = "10" caption = "Borrowers" ... x / field> <field tagld = "mlO" idMenu = "23" idParentMenu = "10" caption = "furniture" ... x / field> </ startMe nu> <dockMenu tagld = "dockMenu" varObjName = "dockMenu" container = "" position = "center" ... x / dockMenu> </ onLoadx / ABUConfìguration> ⠀ "

Server-side script example (Listing 5)

<?

if (! isset ($ _ POST ["id_anagrafìca"])) {return false; }

require_once ('includeAll.php');

require_once 'openConnection.php';

$ Result =

$ idAnagrafica = $ _POST ["id_anagrafica"];

$ json = new Services_JSON ();

$ arr_rsMututatari = cABUADO :: ReadLine (Borrowers :: GetFromlD ($ idAnagrafica), MYSQL_ASSOC);

Sjson-> addFields ($ arr_rsMutatari);

$ arr_rsAnagBaseMututatari = cABUADO :: ReadLine (Anagrafìca :: GetFromlD ($ idAnagrafica), MYSQL_ASSOC);

Sjson-> addFields ($ arr_rsAnagBaseMututatari, "anagrafìcaBaseMutuatario");

$ rsTelAnagBaseMututatari = cABUADO :: RecordsetToArray (Anagrafìca :: getTelefoni ($ idAnagrafìca), SResult);

$ json-> addSubSectionFields ($ rsTelAnagBaseMututatari, "phones", "anagrafìcaBaseMutuatario");

$ rsConiuge = cABUADO :: ReadLine (Borrowers :: GetConiugeFromlDMutuatario ($ idAnagrafìca), MYSQL_ASSOC); $ json-> addFields ($ rsCospouse, "anagraficaConsugeMutuatario");

$ rsTelColugeMututatari. . = cABUADO :: RecordsetToArray (Borrowers :: GetTelefonÌConiugeFromlDMutuatario ($ idAnagrafìca), $ Result);

$ json-> addSubSectionFields ($ rsTelConiugeMututatari, "telephones", "anagraficaConiugeMutuatario");

$ rsProfessioni = cABUADO :: RecordsetToArray (Borrowers :: GetProfessioni ($ idAnagrafìca), SResult);

$ json-> addFields ($ rsProfessioni, "professioni"); <»> SrsAltriRedditi = cABUADO :: RecordsetToArray (Borrowers :: GetAltriRedditi ($ idAnagrafica), SResult); - -Sjson-> addFields ($ rsAltriRedditi, "otherRedits");

SrsSpese = cABUADO :: RecordsetToArray (Borrowers :: GetSpese ($ idAnagrafìca), SResult);

Sjson-> addFields ($ rsSpese, "expenses");

SrsAltrilmpegniFinanziari = cABUADO :: RecordsetToArray (Borrowers :: GetAltrilmpegniFinanziari ($ idAnagrafica), SResult); - - â € "

$ json-> addFields ($ rsOtherFinancial Commitments, "otherFinancial Commitments");

SrsSoluzioniAssicurativeComplementari = cABUADO :: RecordsetToArray (Borrowers :: GetSoluzioniAssicurativeComplementari ($ idAnagrafìca), SResult);

Sjson-> addFields ($ rsSoluzioniAssicurativeComplementari, "solutionsAssicurativeComplementari");

SJSonAnag = $ json-> finalize ();

echo (SJSonAnag);

require_once 'closeConnection.php';?>

Data Processing Server-Side Class Example (Listing 6)

class Financial Products {

function _SetProductsFinancialParam (& $ JSon, & $ SQL, $ Finalize = true) {

cABUPrepareSQL :: SetSQL ($ SQL, $ Finalize); cABUPrepareSQL :: AddParam ('@ ID_FINANCIAL_PRODUCTS @', $ JSon-> id _financial_products, cABUPrepareSQL :: AddParam ('@ PRODUCT_NAME @', $ JSon-> product_name,

cABUPrepareSQL-AddParam ('@ MUTUAL_TYPE_ID @', $ 'JSon-> mortgage_type, .cABUPrepareSQL :: AddParam (<,> @ INDEX_ID @', SJSon-> index_id, -cABUPrepareSQL '$ :: AddParam @' -> tan,

cABUPrepareSQL :: AddParam ('@ TAEG @', $ JSon-> taeg, cABUPrepareSQL :: AddParam (<,> @ PERC_SPESE_ISTRUTTORIA @ ', $ JSon-> perc_spese_istruttorìa, "0"); cABUPrepareSQL :: AddParam (' @ MAX_SPESEJSTRUTTORIA @ <,>, $ JSon-> max_spese_istruttoria, "0"); cABUPrepareSQL :: AddParam ('@ PERC_FINANZIABILE @', $ JSon-> payable_perc, "0"); cABUPrepareSQL :: AddParam {'(S <> MIN_FINANCIABLE @ ', SJSon-> min_financeable, "0"); cABUPrepareSQL :: AddParam ('@ MAX_FINANCIABLE (5 <)>', $ JSon-> max_financeable, "0"); cABUPrepareSQL :: AddParam ('@ MIN_DURATION @', $ JSon-> min_time, "0"); cABUPrepareSQL :: AddParam ('@ MAX_DURATION @', $ JSon-> max_time, "0"); cABUPrepareSQL :: AddParam ('(S <)> EXPERT_EXPENSES @ <l>, $ JSon- >pà ̈rizia_expenses, "0"); cABUPrepareSQL :: AddParam ('@ START_EXPENSES (S <)>', $ JSon-> initial_expenses, "0"); cABUPrepareSQL :: AddParam ('@ PENALE_RIMBORSO_ANTICIPATO @', $ JSon-> penalty_reimborso_anticipato, "0â €); cABUPrepareSQL-AddParaml ^ DESCRIPTION ^ ALCOHOL ^ RATElffl '^ JSon ^ description ^ alcUPoloJERTA $ JSon-> Insurance_RequestsJcABUPrepareSQL :: AddParam ('@ GUARANTEES_RICHIESTE @', $ JSon-> Guarantees_Requests, cABUPrepareSQL :: AddParam ('@ INSTANT_DISPENSION @', $ JSon-> instant_delivery, cABUPrepare ($ AddPrepareSQL JSon-> note, cABUPrepareSQL :: AddParam ('@ DATAJNIZIO_VALIDITA @ <,>, $ JSon-> start_valid_date, cABUPrepareSQL :: AddParam (' @ END_DATE_VALIDITA @ ', $ JSon-> valid_date_fine,

cABUPrepareSQL :: AddParam ('@ DELETED @', @ $ JSon-> deleted,

$ SQL = cABUPrepareSQL :: Finalize (); }

function lnsert (& $ JSon) {

global $ FinancialProductsilns, $ ObjUser;

$ SQL = $ FinancialProductsilns;

SetSessionParam ($ SQL, false);

FinancialProducts :: _ SetFinancialProductsParam ($ JSon, $ SQL, true);

return $ SQL; }

} - Server-side query example (Listing 7)

$ProdottiFinanziarilns = "INSERT INTO tb_prodotti_finanziari (id_societa, id_prodotti_finanziari, id_anagrafica, nome_prodotto, id_tipologia_mutuo, idjndicizzazione, tan, taeg, perc_spese_istruttoria, max_speseJstruttoria, perc_finanziabile, min_finanziabile, max_finanziabile, durata_min, durata_max, spese_perizia, spesejniziali, penale_rimborso_anticipato, descrizione_calcolo_tasso, coperture_assicurative, garanziejrichieste, instante_erogazione, notes, validity_start_date, validity_date_date) VALUES ('@ ID_SOCIETA @', @ ID_PRODOTTI_FINANZIARI @, <5> ID_ANAGRAFICA @, '@ NOME_PRODOTTO @', @ ID_TIPOLOGIA_MUTUO_, @DISTIPOLOGIA_MUTUO_ @, @ ID_TIPOLOGIA_MUTUO_, @CUTTANTIPOLOGIA_MUTUO @, @ ID_TIPOLOGY_MUTUO_, @JU @, @ MAX_SPESE_ISTRUTTORIA @, @ PERC_FINANZIABILE @, @ MIN_FINANZIABILE @, @ MAX_FINANZIABILE @, @ DURATA_MIN @, @DURATA_MAX <'> @, @ EXPENSES <5>, @ EXPENSESJ ^ INZIALI @ ^' @ PENALTY @DESCRIPTION_RATE_CALCULATION @ <,>, '@ INSURANCE_COVER @', '@REQUIRED_GARANZIE <5>', '@ INSTANT_DRAWING @', '@ ΠΟΤΠ• @', STR_TO_DATE ('@ DATA JNIZIO_VALIDITA @ ','% d /% m /% Y '), STR_TO_DATE (' @ DATA_FINE_VALIDITA @ ','% d /% m /% Y ')) ";

$ SearchProdottiFinanziari4Finanziamenti = "SELECT DISTINCT PF.id_company, PF.id_financial_products, PF.id_anagrafica, PF.name _product, PF.id_typology_mutual, PF.idJindication, /*PFA.financial_id_id, PF.Financial_id_id, PF. / PF.tan, PF.taeg, PF.perc_spese_istruttoria, PF.max_spese_istruttoria, PF.perc_financabile, PF.max_financabile, PF.expese_expertizia, PF.speseJnitiali, PF.penale_rimborso_anticipato, PF.description_Finance.Furchable .time_delivery, PF.note, NULLIF (DATE_FORMAT (PF.data_begin_validita, '% d /% m /% Y'), '00/00/0000') date_begin_valid, NULLIF (DATE_FORMAT (PF.data_fine_validita, '% d / % m /% Y '),' 00/00/0000 ') validity_date

FROM TBL_PRODOTTI_FINANZIARI AS PF INNER JOIN TBL_PRODOTTI_FINANZIARI_ATTIVITA AS PFA ON ((PF.id_societa = PFA.id_societa) AND (PF.id_prodotti_finanziari = PFA.id_Prodotti_FINANZIARI_ATTIVITA AS PFA ON ((PF.id_societa = PFA. (PF. PfP ON ((PF.id_societa = PFP.id_societa) AND (PF.id_prodotti_finanziari = PFP.id_prodotti_finanziarì)) WHERE PF.id_societa = '@ ID_SOCIETA @'

/ * [AND (PF.max_financeable 3⁄4 = @ AMOUNT_REQUIRED @) AND (PF.min_financeable <= @ AMOUNT_REQUIRED @)] * // * [AND (PF.perc_financable> = @PERC_FINANZIABILE @)] * /

/ * [AND (PFA. (PF.id_tipolpgia_mutuo = @ID_TIPOLOGIA_FINANZIAMENTO @)] * // * [AND (PFF.id_finalita = @ID_FINALITA @)] * / / * [AND (PFP.id jaeriodicita = @ID_PERIODICITA @)] * / ";

Example of data transit between client and server (Listing 8)

{

"intestera_mutuo": false, "id_civile_stato": "1", "quota_proprieta": "50", "anni_in_italia": "36",

"Other Income": [

{"sts": "new", "datajnizio": "01V01V1995", "income": "500", "end_date": "01V01V2009", "period_type_id": "the <!>," description ":" Rent House "," id_other_; income ":

"Professions": [{

"socio_cariche_societarie_presso": "Sociol", "sts": "new", "monthly_numberâ € œ:" 14 "," annual_income ":" 25000 "," da_anni ":" 8 "," company ":" Theorematica "," id_tipologia_attivita ":" 2 "," id_professioni ":" undefined ",

"juridical_formation_company": "3", "last_date_assunz_iscriz_albo": "", "company_iva_game": "pivaSocl",.

"id_contratto_type": "2", "first_date_assunz_iscriz_albo": "01 \ / 01 \ / 2000", "id_anagrafica": "undefined", "monthly_income": "1300", "company_fiscal_code": "cfìscsocl", "professional_type_id ":" 1 "," description ":" IT Services Company "

}, {"socio_cariche_societarie_presso": "Socio2", "sts": "new", "num_mensilita": "13",

"annual_income": "23000000", "da_anni": "3", "company": "ISIS", "id_typology_activity": "2", "id_professioni": "undefined", "juridical_formation": "2", "last_date_assunz_iscriz_albo ":" 01VÃ'ÃŒV2000 "," lotto_iva_societa ":" PIVASoc2 "," id_type_contratto ":" 3 "," data_prima_assunz_iscriz_albo ":" 01V01V1997 "," id_anagrafìca ":" undefined "," income_m00ensile "," "Codice_fiscale_societÃ": "CfiscSoc2", "id_tipologia_professione": "1", "description": "IT Services Company"

}, {

"socio_cariche_societarie_presso": "Socio3" T "sts": "new", "number_mensilitaâ €:" 12 ",

"annual_income": "14000000", "da_annì": "2", "company": "Hermes Multimedia", "ìd_tipologia_attivita": "3", "ìd_professioni": "undefmed", "juridical_formation": "1", "last_date_assunz_iscriz_albo": "01V01V1997", "company_vehicle_game": "PlvaSoc3", "id_contract_type": "1", "first_assunz_date_write_albo": "01V01V1997", "unfinished_date": " "," code_fìscale_societa ":" CFisc3 "," id_typology_profession ":" 9 ",

"description": "Multimedia IT Services Company"

1, - "marriage_year": "2004", "pensions_rendite": "7", "provenance": "Ro", "fìgli_a_load": "2", "id_comuni_res": "4448", "id_comuni_dom": "4422", "occupera_": true, "id _provincia_res": "58", "id_provincia_dom": "58",

"Expenses": [{"sts": "new", "dataJnizio": "01V01V2002", "id_spese": "data_fine": "01V01V2012", "id_tipologia_periodicita": "5", "description": "Auto Insurance" , "cost": "600"}],

"intestatariojmmobile": "Mastinu Rita", "id_nazioni_res": "112", "id_nazioni_dom": "112" / cap _ :. res ":" 00040 "," cap_dom ":" 00183 "," intestera_ ": true}

Claims (16)

CLAIMS: 1. Procedure for the realization of a technology that, starting from the use of a browser and without the aid of additional components, allows the creation of dynamic, multi-management, modular and persistent web applications, equipped with complex interfaces and characterized by a drastic reduction of quantity of data and web pages exchanged between a remote server and a Client, consisting of the following elements: â € ¢ Multi-management Web page (written or generated in any format and / or language, the final result of which is an HTML page) built in a very elementary way and containing the definition of multiple managements within it relating to a complete procedural flow complex; â € ¢ Complex / advanced / intelligent dynamic components; â € ¢ Data Binding Techniques; â € ¢ Complex data structures with JSON, XML or whatever formats; â € ¢ Parallel configuration associated with the Web page, written or generated in any format that can be interpreted by an appropriate Core Client (XML, JSON etc); â € ¢ Core Client, which interprets the configuration file associated with the web page to generate the multifunctional dynamic web page with complex interfaces from the application skeleton; â € ¢ Client-side techniques for post-generation and post-rendering of web pages not only in the initialization phase, but both during the interaction with the user and following requests for a calling object (e.g. during import some data); â € ¢ Synchronous and asynchronous AJAX calls; â € ¢ Dialogue with the server for heterogeneous amounts of data; â € ¢ Core Server for the dialogue with the multi-management web pages and the sorting / grouping of the same from / to the relative specific specialized classes; Characterized by the fact that: â € ¢ The page is created, in terms of graphics, programming and calls to the server, directly locally on the client through the XML file and the post-generation, post-rendering and post-execution techniques by the Core Client; â € ¢ Once prepared for use, the user operates in full autonomy and freedom upon completion of the input process; â € ¢ During this process, various partial validation and congruity checks are performed (also through synchronous / asynchronous AJAX calls to additional services or web pages) on the data entered; â € ¢ During the input process and directly on the Client itself, following user actions or requests for data coming from outside, the automatic generation techniques can be further recalled, for the dynamic creation of missing web application parts; â € ¢ At the end of the acquisition process, global validation is performed (also through synchronous / asynchronous AJAX calls to additional services or web pages) and the entire data entered is sent to the server; The dialogue takes place in the form of a heterogeneous amount of data; â € ¢ The server for sorting, handling and processing the heterogeneous amount of data; · The page is set up for subsequent use by means of local initialization on the client of both visible and invisible objects, both simple and complex / advanced / intelligent; â € ¢ The main page is equipped with a component that incorporates and stores the various web pages, acting as a container (like a small browser eg: iframe), which connected to display / disappearance of elements / components / actions or other it allows to obtain the creation of Dynamic Web Applications with Rich Graphic Interfaces and Persistence of Data and Pages which can be recalled upon request by the user; The pages recalled from time to time during the use of the web application, will have a single loading for the entire life cycle of the entire session of the main web page, will always be immediately available and operational directly on the client, without any passage of activation from the server; With the method, according to the invention, it is possible to obtain: â € ¢ A reduction in the weight of the web pages that can reach well over 50% of current pages; â € ¢ Reduced network traffic, thanks to the dialogue with the server for heterogeneous amounts of data, with a reduction ratio of exchanged data from 1:60 to over 1: 200; â € ¢ Server processing reduced to a minimum and comparable to 10% compared to current techniques; â € ¢ Very low network traffic for the request of the various portions of the application that will be loaded only once for the entire life cycle of the entire web application; â € ¢ Implementation, development and analysis techniques for web applications that are considerably reduced and similar to those for creating desktop or client-server solutions; â € ¢ It is possible to pass real-time and without any loss of information from one portion of the web application to another, with considerable advantages for the end user. 2. Process according to claim 1, characterized by the fact that the Multi-Functional Web Page must be written and designed with the principle of containing several simultaneous managements within it, relating to the acquisition of a complete complex procedural flow and which is normally divided into several web pages with separate management; To achieve this, it is necessary to perform a: · Subdivision of the page into management / functional areas marked by an identifier; Within the same will be inserted: i. elementary tags distinguished by an identifier and the related class of styles; ii. elementary tags marked with an identifier which, following declarations in the XML file, will have the characteristics of "Complex / Advanced / Intelligent Objects / Components"; iii. Empty areas (identified with container tags) marked by an identifier with the following functions: 1. Areas for creating the "Complex / Advanced / Intelligent Objects / Components"; 2. Functional Logic Areas (with logic aggregation functions), therefore containing the elements of points i, ii, iii; iv. Full areas (identified with container tags) identified by an identifier and containing the elements of points i, ii, iii used by "Objects / Components Complex / Advanced / Intelligent "; â € ¢ Given the editable mode of numerous complex, advanced, intelligent controls / objects, it is necessary to define the input source objects (both elements and areas full of elements) outside the container tags of complex / advanced / intelligent objects (eg : pre-loaded combos external to the grids); â € ¢ Portions of code may be present: i. client (javascript or other) necessary and specific for a given development or controls; 11 on the server side, to immediately generate preloaded elements (for example data source combo boxes or other) in order to avoid the immediate forwarding of calls to the server for their loading; â € ¢ A configuration file, preferably external and in XML standard (or in other data formats) associated with it, must be indicated; â € ¢ You will need to include the Core Client (ABUCore) interpreter. 3. Process according to claim 1 characterized in that the invention is characterized by the use of advanced / complex / intelligent dynamic components. â € ¢ these are components: the. existing, but with limited functionality; ii. do not normally exist and are the result of client programming (javascript) and which can be: 1. visuals; 2. not visual; these must have some common features that can be configured and recalled by the Core Client; â € ¢ Know their type, and their identification; â € ¢ Be aware of the Core Client identification for subsequent interactions; â € ¢ Expose properties, methods, -â € ¢ Expose events to give the possibility to write code to be executed following user actions on the object, such as a confirmation of the data entered, -â € ¢ Expose their status (normal or editable); â € ¢ Expose their change; â € ¢ Knowing how to import and export data according to established formats (data binding client); â € ¢ Knowing how to perform a data mapping, ie the names of the data to be imported / exported may be different from those to be used (data binding client); â € ¢ Be aware of the changes that have occurred on the data assigned to them (new / modified / deleted); â € ¢ Knowing how to apply validation techniques; â € ¢ Specific features characteristic of each object. 4. Process according to claim 1 characterized in that the invention uses a parallel configuration associated with each multi-functional web page, written or generated in any format that can be interpreted by a suitable Core Client (XML, JSON etc); said configuration contains within it a structure divided into at least 4 logical areas: â € ¢ Interview areas: This section defines all the interview areas that will be used to communicate with the server; each area has its own identifier and the fields and objects that are indicated in it with their name or with an alias map the respective objects on the page; These areas represent the heterogeneous amount of data that will be exchanged with the server; â € ¢ Initialization areas: This section defines: the. the fields: which will have a particular behavior, which can range from an input mask, to an initialization of values, to the definition of a mandatory field, to the specialization of a field (eg: date field, tax code, VAT number, etc. .), with related controls that can be expanded by users; ii. the areas: in which both visual and non-visual complex / advanced / intelligent objects will be rendered; in this case, in addition to the specific definitions and behavior of the object itself (different from object to object), the fields or areas contained therein and their behavior as specified in the above point (i) will be indicated; â € ¢ Actions: This section schematically defines all the characteristics of the synchronous / asynchronous calls for dialogue with the server, the areas to be controlled and sent and those to be updated (through direct references to the sections of the "Area of Conversation "), the names of the variables with which said areas travel to and from the server, and the actions to be taken before and at the end of data reception and of the call; â € ¢ Actions on User Interface: This section defines the visual actions that arise as a result of user actions, such as enabling, showing, hiding, etc. certain fields or areas of section a). 5. Process according to claim 1, characterized by the use of dynamic post-generation and post-rendering techniques; it involves automatic generation of: â € ¢ HTML tags; â € ¢ Styles and style classes; â € ¢ Client Code (JavaScript); â € ¢ Synchronous / asynchronous AJAX calls; â € ¢ Everything you need (validation, formatting, advanced controls etc.); for the dynamic realization on Client of portions of pages with functionalities of portions of application, or with all the expected features, -These techniques are applied directly on the Client by the Core Client and can occur: â € ¢ at the end of the loading of the page, when the onLoad event of the page occurs; â € ¢ while using a page, following user actions (editable mode activation); â € ¢ following data import and therefore upon request of advanced / complex / intelligent objects. 6. Process according to claim 1, characterized by the fact that the Core Client, or ABUcore, is an XML file analyzer that generates all the code necessary for the creation of the web application; the code generation will be performed within the browser, directly on the client at the end of the loading of the basic page (post-generation), and will be performed in real time, obtaining a complete redesign of the same (post-rendering of the page); The Core Client, which is not an application container, performs at least the following operations: to. Loading basic, generic and advanced functionality libraries, including functionality extensions of standard objects and classes for controlling data (eg: validation, masks, control of data area changes) and more; b. Reading of the configuration file associated with the page and its storage; c. Analysis of the configuration file and automatic inclusion of all the libraries necessary for the generation of the web application (avoiding loading libraries that are not required) and waiting and checking that the upload has been completed; d. Reading of the "Initialization Area" section with: the. Generation of the initialization, formatting and validation code etc. relative to standard objects, excluding all those that are included within repeating objects; ii. Generation of the source code for the compilation checks of the required and mandatory fields relating to areas, objects and the entire application according to particular methods: a field marked as required belongs to a group of fields that are marked as such and must all be filled in by the user; the mandatory ones, if filled in one must be filled in in groups; iii. Generation of source code for the creation of complex, advanced and intelligent objects / components, excluding all those included within repeating objects; iv. for each object contained in other objects, the respective code will be generated as in points i.ii.iii .; And. Reading of the "Interview Area" section and generation of the source code for the creation of the dialogue structures from / to the outside (creation of the complex data structure that will constitute the heterogeneous amount of data); f. Reading of the "Actions" section and generation of the source code relating to synchronous / asynchronous AJAX calls, to the data to be sent and received, to the areas that will be interested in an update, as well as to preventive checks on the data to be sent, transforming the data from the format text to an object format and vice versa: serialization and deserialization, -g. Reading of the "User Interface Actions Area" section and generation of the relative source code; h. Generation of source code for repetitive objects: in a preventive manner or upon request of the calling object (following user actions, data import, etc.), the repetitive objects will query the Core Client again to proceed with the generation of the above points c), d), e), f), g). 7. Process according to claim 4, characterized by the fact that the Core Client provides the possibility of simply defining an HTML area with an identifier and indicating in the configuration file the structure of the complex object to be created inside it; in the definition of complex objects such as grids, repeaters, tree views, etc., it being possible to indicate the input objects that must be used during the data entry / modification / display phases, as well as the respective formatting, mandatory fields and rules validity, initialization and more. 8. Process according to claim 7, characterized by the fact that it provides for the possibility of inserting not only advanced objects, but also areas which in turn must be rendered with advanced objects, formatting, calls to the server etc., and always in a dynamic and on the Client. 9. Process according to claim 1 characterized by the use of synchronous / asynchronous AJAX calls; By applying this technology it is possible (in a totally transparent way for the user) to forward dialogues with the server, and to apply the techniques of claim 5. 10. Method according to claim 1 characterized by the dialogue with the server for heterogeneous data volumes; by mass of heterogeneous data we mean the union of a set of simple information ("pairs": "values") whose result is complex structures; It is possible to make them: â € ¢ Through the areas declared and defined in the "Interview Areas" section; â € ¢ By exporting the structures defined within the advanced / complex / intelligent objects / components. 11. Process according to claim 1, characterized in that starting from a pure page written in trivial HTML, which can also be generated with a php, asp, .net, java, etc. and from a preferably external configuration file - written in XML connected to the Core, the latter takes care of the analysis and generation of the code necessary to create the web application. 12. Process according to claim 1, characterized in that it provides for the provision of a Core Server for: â € ¢ provide for the serialization / deserialization of the exchanged data, or the transformation from the format sent as text to the object format and vice versa; â € ¢ arrange for the sorting and grouping of the heterogeneous amount of data to and from the various specific classes, applying the actions impressed on the data by the Client; · Also provide for the automatic generation of queries and their fusion with data to have actions on the data base only following user actions; as an alternative to the generation of queries, it is also possible to sort the data by interfacing with other systems based on the various RDBMS technologies. 13. Process according to claim 12, characterized by the fact that said Core Server carries out the sorting of the information coming from the client, their assignment to suitable structures for the processing to be handled, and the re-compaction of the structures coming back to the client. 14. Process according to claim 1, characterized by the fact that said Core Client is written in pure JavaScript and that when a web page is loaded it analyzes the configuration file, including and waiting for the loading of only the requested libraries, then generating all the code necessary for the rendering of complex objects, the control and operation of the page, as well as all the synchronous and asynchronous calls with the relative structures, transforming a simple HTML / XHTML page into a Rich Dynamic Web Client. 15. Process according to claim 1, characterized by the fact that in order to transform a Dynamic Web Application with a Rich Graphic Interface of a known type into a Dynamic Web Application with Modular, Persistent Request and with a Rich Graphic Interface, provides for providing the main page of a site web of a component that incorporates and stores the various web pages, behaving like a small browser, for example an iframe; the persistence of the desired portions of the application is obtained by connecting their display or disappearance to any object / web action of the main page. 16. Process according to claim 12, characterized by the fact that said Core Server is much simpler than the Core Client as it is equipped with some classes that deal with the sorting / grouping of data, as well as the assignment of these to the various queries, which being written in a proprietary and parametric format, allow the automatic writing of the same, without any analysis by the user for the data present or missing.