DOCSLIB.ORG

(NDS-32) Coding Standards for Powerbuilder Annex

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
(NDS-32) Coding Standards for Powerbuilder Annex Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 National Database System (NDS-32) Coding Standards for PowerBuilder Annex – 4 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 1/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 Introduction A well-defined system needs to follow standards. The philosophy behind it is consistency, ease of remembrance and maintenance. The following sections state the programming standards for the GUI tool PowerBuilder 6.0 and RDBMS ORACLE. Standards for programming in PowerBuilder Naming Conventions An application consists of various components such as windows, menus, listboxes, commandbuttons, and their associated scripts. The following naming convention will be followed for the above to facilitate quick understanding of the source code. All names will have a two character prefix and an underscore (_), followed by a string of characters that uniquely describes the particular component. The names will be in lower case, with suitable underscore separators between words and without any spaces. (The identifier names in PowerScript are case insensitive). Names will not contain any hyphens (-). To the extent possible, a name must convey the contents of the object. The component name will not be more than 30 characters long, will not have any punctuation marks and will not start with numbers. Application variable names The first character of the prefix will signify the scope of the variable followed by the data type (maximum 3 characters) Scope of variables Scope of variable within an application First character of prefix(in small case) Local L Instance I Shared S Global G Argument A Data types will have the following prefix Data Type Second, third and fourth character of prefix Any A_ 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 2/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 Blob Bbl_ Boolean B_ Character Ch_ Date D_ DateTime Dtm_ Decimal Dc_ Double Dbl_ Integer i_ Long l_ Real r_ String s_ Time Tm_ UnsignedInteger Ui_ UnsignedLong Ul_ Enumerated e_ For constants , the same convention followed by ‘_const’ for constant will be used e.g. a local constant of type integer will be declared as ‘li_const_variablename’. PowerBuilder Object names PowerBuilder Objects will have the following prefix: PowerBuilder Object type Prefix Application app_ Application Function af_ Application Structure astr_ Window w_ Window Function wf_ Window Structure wstr_ Menu Function mf_ Menu Structure mstr_ User Object Function uf_ User Object Structure Ustr_ Function f_ Function Structure Fstr_ Structure str_ Query q_ DataWindow d_ DataPipeline Pipe Project Prj_ Connection cn_ ConnectionInfo Cninfo_ ConnectObject Cno_ DataStore ds_ DynamicDescriptionArea Dda_ DynamicStagingArea Dsa_ Environment Env_ 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 3/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 PowerBuilder Object type Prefix Error Err_ NonVisualObject nv_ WindowObject Wo_ Transaction Tr Proxy prox_ PowerBuilder Control names PowerBuilder Controls will have the following prefix: PowerBuilder Control type Prefix Checkbox cbx_ Commandbutton cb_ Computed Field Cf_ Computed column Co_ DataWindow dw_ DropDownListBox ddlb_ DropDownPictureListBbox ddplb_ DropDownDataWindow dddw_ Graph gr_ Horizontal Scrollbar hsb_ Line ln_ Listbox lb_ ListView lv_ Multi Line Edit mle_ OLE 2.0 ole_ Picture p_ Picturebutton pb_ Picture Listbox plb_ Radiobutton rb_ Rectangle rec_ Rich Text Edit rte_ RoundRectangle rrec_ Single Line Edit sle_ Static Text st_ Tab tab_ Tree View tv_ User Object uo_ Vertical Scrollbar vsb_ DataWindowChild dwc_ DragObject drg_ DrawObject drw_ DatawindowObject dwo_ EditMask em_ ExternalObject ext_ 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 4/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 PowerBuilder Control type Prefix GraphicObject go_ GraphAxis grax_ GraphDisplayAttribute grda_ GroupBox gb_ ListViewItem lvi_ MultipleDocumentInterfaceClient mdi_ Menu m_ MenuCascade mc_ Message msg_ MultiLineEdit mle_ ObjectLinkingEmbeddingControl oc_ ObjectLinkingEmbeddingObject oo_ ObjectLinkingEmbeddingStorage ostg_ Oval oval_ Pipeline Pl PowerObject po_ Rectangle rec_ RichTextEditObject rteo_ TabPage tabpg_ TreeViewItem tvi_ UserEvent ue_ Application level constant names Constants defined at the application level will follow the same conventions, which are defined for the variables. Application level constants will be defined in upper case. 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 5/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 Programming Conventions It is essential to establish a set of basic programming conventions to ensure the use of good and consistent coding techniques across projects. Conventions can greatly enhance the quality of scripts, make them more readable and above all ensure that they are easy to maintain and reuse. Following are the guidelines for programming conventions to be followed in Power Builder code: The source code will be in mixed case and the conventions stated below will be followed for case of code. Names of user-defined functions, events, and variables will be in lower case. • Power Script statement keywords like IF, THEN, FOR, DO, CHOOSE will be in uppercase . • All the PowerBuilder function calls will be in Hungarian Notation. example: integer li_fetched_count = 0 SELECT Count("order_header"."order_id" ) INTO :li_fetched_count FROM "order_header" WHERE "order_cust_id" = :ai_custid USING sqlca; IF gtr_undcp.SQLCode = -1 THEN li_fetched_count = -1 RETURN li_fetched_count I. Local variables will be declared at the beginning of the script. example: decimal ldc_balance, ldc_grandtotal_price string ls_highlight_format, ls_regular_format A. A variable name will indicate the scope, type and purpose of the variable. B. Use of global variables will be limited to the minimum. As far as possible local and instance variables will be used. C. When referring to objects or controls, PowerScript pronouns (such as This, Parent, and ParentWindow) will be used whenever possible instead of using the actual object or control names explicitly. D. For example, for coding the Clicked event script for the cb_close CommandButton in the w_maintaincurrentaccount window 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 6/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 Close (parent) Will be used instead of Close (w_maintaincurrentaccount) This helps in making the script code more reusable because it will not be attached to particular objects and controls. II. All operators in expressions will have at least one preceding and succeeding white space e.g. A + B, A / B - C, A > B III. Use of ‘Any’ data types will be avoided as far as possible, as these variables are slow at runtime and compilation errors are not tracked for them. IV. As calling functions and events dynamically open up the application to potential errors, they will be avoided as much as possible. V. Following standard errors will be tracked at all places in all components: E. Network connection errors F. Database access errors G. Data entry errors VI. Every complex database transaction involving a series of related insert and / or update statements will be processed as a single transaction, i.e. it must be preceded by an explicit begin transaction statement. All transaction operations must be committed on successful completion using the commit transaction statement. All transaction operations will be rolled back, in case of errors, using the rollback statement. VII. Comments will be used wherever required. Inline Documentation Inline documentation increases the ease of maintenance of the application. Suitable comments describing functional aspects of the function will be provided. Event routine / User defined function source code Each event routine, user defined function will have a descriptor header consisting of the following: • Name of the event routine / user defined function • Description of the event routine / user defined function • Arguments list • Return values list • Creation date • Author 02/28/2000 /10:24 AM ver.1.0.0 Doc. Id: RNPBS softcopy : pb page : 7/9 Datamatics Ltd. UNDCP NDS32-Coding Standard forPowerBuilders-Annex-4 NDS-32 • Modification history consisting of modifier, modification date and modification details A sample description header for an event is as follows: ////////////////////////////////////////////////////////////////////////////// // //Event Name : ue_copydata // // Arguments : None // // Returns : None // //Description : Calls the user object function uf_copydata // // Author : userid // // Version : 1.0 Initial version dated : 13 - Dec - 1998 // ////////////////////////////////////////////////////////////////////////////// // //Revision History // // dd-mon-yyyy Author : userid Description : // ////////////////////////////////////////////////////////////////////////////// A sample description header for a function is as follows: ////////////////////////////////////////////////////////////////////////////// // //Function Name : uf_xxxx // // Arguments : None // // Returns : None // //Description : Copies selected rows from the source datawindow to the // destination datawindow // // Author : userid // // Version : 1.0 Initial version dated : 13 - Dec - 1998 // //////////////////////////////////////////////////////////////////////////////
Load more

Recommended publications
  • Semantic Navigation of Large Code Bases in Higher-Order, Dynamically Typed Languages
    Semantic Navigation of Large Code Bases in Higher-Order, Dynamically Typed Languages S. Alexander Spoon and Olin Shivers College of Computing Georgia Institute of Technology Atlanta, GA 30032 Abstract— Chuck is a new code browser that allows navigation formed by deeper semantic connections between elements of of a code base along semantic structures, such as data-flow and the code, such as the data- and control-flow induced by the higher-order control-flow relationships. Employing the fast DDP dynamic semantics of the language. (In particular, note that type inferencer, it is effective on dynamically typed code bases an order of magnitude larger than the code bases supported by control flow in a higher-order functional or object-oriented previous browsers. Chuck supports the full Smalltalk language, language is no longer directly encoded in the syntax of the lan- and is now shipped as a standard component of the Squeak guage.) For example, semantic navigation allows programmers open-source Smalltalk system, where it routinely works with code to navigate from a new expression to the expressions that use bases exceeding 300,000 lines of code. Chuck’s implementation is objects created by that expression. It allows programmers to tuned for interactive use, and is transparently integrated with the Squeak system’s existing code-browsing tools. Thus, it provides navigate from a message-send expression to the narrow set of semantic navigation of a live code base that is still being edited methods that might respond to that specific invocation. These without requiring long pauses for reanalysis due to edits of the links, whose increased precision and tighter bounds help guide code.
    [Show full text]
  • 1 Lesson 2 VARIABLES Aim Understanding How Computer
    Lesson 2 VARIABLES Aim Understanding how computer programs store values, and how they are accessed and used in computer programs. WHAT ARE VARIABLES? When you input data (i.e. information) into a computer the data is stored in the computer’s memory. To visualise this, you might think of the computer’s memory as millions of little boxes, each holding a single value. Normally, each box is numbered starting at zero. As a computer uses binary numbers (made up of 0s and 1s), the boxes may be numbered something like this: 10100010, which is 162 in decimal. The actual number of boxes depends on the amount of memory in the specific computer. When data is put into the computer, the computer stores the data in the boxes that are part of the computer’s Random Access Memory (RAM), and the number of those boxes is referred to as the memory address. Obviously, for humans to refer to memory addresses by their binary index would be very difficult, so programming languages use a device called a variable. A variable is a word label that the programmer assigns to a piece of data, so they don’t need to worry about where it is stored in memory or how to tell the computer where to find it. Variables are simple memory boxes with names. You, the programmer, supply these names. For example, the following lines first declare a variable called myAge of data type Integer (it will store whole numbers), and then assigns the integer value 25 to myAge : Dim myAge As Integer myAge = 25 When you declare a variable, you must give it a name (and then compiler will claim some memory space and associate the name with the binary address), and specify the type of data that will be stored in that variable.
    [Show full text]
  • On the Naming of Methods: a Survey of Professional Developers
    On the Naming of Methods: A Survey of Professional Developers Reem S. Alsuhaibani Christian D. Newman Michael J. Decker Michael L. Collard Jonathan I. Maletic Computer Science Software Engineering Computer Science Computer Science Computer Science Kent State University Rochester Institute of Bowling Green State The University of Akron Kent State University Prince Sultan University Technology University Ohio, USA Ohio, USA Riyadh, Saudi Arabia New York, USA Ohio, USA [email protected] [email protected] [email protected] [email protected] [email protected] Abstract—This paper describes the results of a large (+1100 Here, we focus specifically on the names given to methods responses) survey of professional software developers concerning in object-oriented software systems. However, much of this also standards for naming source code methods. The various applies to (free) functions in non-object-oriented systems (or standards for source code method names are derived from and parts). We focus on methods for several reasons. First, we are supported in the software engineering literature. The goal of the interested in method naming in the context of automatic method survey is to determine if there is a general consensus among summarization and documentation. Furthermore, different developers that the standards are accepted and used in practice. programming language constructs have their own naming Additionally, the paper examines factors such as years of guidelines. That is, local variables are named differently than experience and programming language knowledge in the context methods, which are named differently than classes [10,11]. Of of survey responses. The survey results show that participants these, prior work has found that function names have the largest very much agree about the importance of various standards and how they apply to names and that years of experience and the number of unique name variants when analyzed at the level of programming language has almost no effect on their responses.
    [Show full text]
  • Jquery Fundamentals Rebecca Murphey [ Jquery Fundamentals Rebecca Murphey [ Copyright © 2010
    jQuery Fundamentals Rebecca Murphey [http://www.rebeccamurphey.com] jQuery Fundamentals Rebecca Murphey [http://www.rebeccamurphey.com] Copyright © 2010 Licensed by Rebecca Murphey under the Creative Commons Attribution-Share Alike 3.0 United States license [http://creativecommons.org/licenses/ by-sa/3.0/us/]. You are free to copy, distribute, transmit, and remix this work, provided you attribute the work to Rebecca Murphey as the original author and reference the GitHub repository for the work [http://github.com/rmurphey/jqfundamentals]. If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license. Any of the above conditions can be waived if you get permission from the copyright holder. For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to the license [http://creativecommons.org/licenses/by-sa/3.0/us/]. Table of Contents 1. Welcome ....................................................................................................................... 1 Getting the Code ........................................................................................................ 1 Software ................................................................................................................... 1 Adding JavaScript to Your Page ................................................................................... 1 JavaScript Debugging .................................................................................................
    [Show full text]
  • Function Declaration Vs Function Definition Javascript
    Function Declaration Vs Function Definition Javascript Haemolytic and Cenozoic Oliver harmonise so schematically that Mylo democratising his pipestones. Morly glad-hands her mess indecently, valerianaceous and leaden. Awed Son still partialised: meticulous and rakehell Maynord lip quite apogamously but brooms her fragments suicidally. For earth, you register forward grasp a function or class however often do want, but you hold only half have one definition for it. And definition apply only declared inside the declarations load before everything is vs function declarations are like statements, and that concerns me a lookup to. Use inline comments sparingly. You well always dark the assignments that destructuring would generate yourself. There are leaving different ways that function expressions become more gas than function declarations. Wrapped lines are not indented. There can javascript function definition contains styles that we can write less work around docker is vs expression vs declarations are some different. Ecma RF patent policy. Function Definition, on than other hand, refers to the actual function that specifies the function name, return types and parameters with the function body. Made a banana cake! Functions that create values are easier to man in new ways than functions that directly perform side effects. Introduction to the old function simply want name may want the javascript function declaration vs definition. In javascript ad click help request that sort of declaring global is definitely a constant variable called a duplicate variable? Being declared inside multiple functions vs declaration declares that specifies how to declare it appears in. Read to Stay Baffled. But simply calling functions vs definition indicates the javascript function definitions: there is definitely on a react.
    [Show full text]
  • 11. Metadata, Metamodelling, and Metaprogramming
    11. Metadata, Metamodelling, and Metaprogramming 1. Searching and finding components 2. Metalevels and the metapyramid 3. Metalevel architectures 4. Metaobject protocols (MOP) Prof. Dr. Uwe Aßmann 5. Metaobject facilities (MOF) Technische Universität Dresden 6. Metadata as component markup Institut für Software- und Multimediatechnik http://st.inf.tu-dresden.de 14-1.0, 23-Apr-14 CBSE, © Prof. Uwe Aßmann 1 Mandatory Literature ► ISC, 2.2.5 Metamodelling ► OMG MOF 2.0 Specification http://www.omg.org/spec/MOF/2.0/ ► Rony G. Flatscher. Metamodeling in EIA/CDIF — Meta-Metamodel and Metamodels. ACM Transactions on Modeling and Computer Simulation, Vol. 12, No. 4, October 2002, Pages 322–342. http://doi.acm.org/10.1145/643120.643124 Prof. U. Aßmann, CBSE 2 Other Literature ► Ira R. Forman and Scott H. Danforth. Metaclasses in SOM-C++ (Addision- Wesley) ► Squeak – a reflective modern Smalltalk dialect http://www.squeak.org ► Scheme dialect Racket ► Hauptseminar on Metamodelling held in SS 2005 ► MDA Guide http://www.omg.org/cgi-bin/doc?omg/03-06-01 ► J. Frankel. Model-driven Architecture. Wiley, 2002. Important book on MDA. ► G. Kizcales, Jim des Rivieres, and Daniel G. Bobrow. The Art of the Metaobject Protocol. MIT Press, Cambridge, MA, 1991 ► Gregor Kiczales and Andreas Paepcke. Open implementations and metaobject protocols. Technical report, Xerox PARC, 1997 Prof. U. Aßmann, CBSE 3 Literature on Open Languages ► Shigeru Chiba and Takashi Masuda. Designing an extensible distributed language with a meta-level architecture. In O. Nierstrasz, editor, European Conference on Object-oriented Programming (ECOOP '93), number 707 in Lecture Notes in Computer Science, pages 483-502.
    [Show full text]
  • Software Development and Coding Standards
    Software Development and Coding Standards Falko Kuester and David Wiley Visualization and Interactive Systems Group Department of Electrical and Computer Engineering University of California, Irvine 537 Engineering Tower Irvine, California 92697-2625 Visualization and Graphics Research Group Center for Image Processing and Integrated Computing Department of Computer Science University of California, Davis, CA 95616-8562 December 10, 2001 1 Preface Every programmer inherently learns and practices a custom programming style. The reason for this is no doubt rooted in how programmers learn to program: a snippet from this book, a line from that, an algorithm from this magazine, an array class from that. Every programmer is essentially a melting pot for the many different styles that exist. It is left to the statistically inclined reader to determine just how many combinations are possible and at which frequency. Having a custom style is generally suitable as long as the programmer abstains from interacting with other programmers and decides to be a prisoner to that particular style. Aside from the usual social discontinuities, problems surface when programmers begin to mingle. A random sample of C++ source code from the Internet will yield a variety of C++ dialects. Either you will learn some new things or your eyes will tire from poorly written code. The one constant is that you will never find two programmers that do things exactly the same way. Even more problems occur when teams of programmers must work together. In this environment source code can make round trips through programmers, changing ever so slightly in each iteration. Small scale battles can occur in these code bytes in the form of moving curly braces and parenthesis around, adding or removing spaces, tabbing this, carriage- returning that, commenting this, not commenting at all, renaming variables, or using for loops instead of while loops.
    [Show full text]
  • CSCI 431-001 Java Language Programming
    CS5000: Foundations of Programming Mingon Kang, PhD Computer Science, Kennesaw State University Overview of Source Code Components Comments Library declaration Classes Functions Variables Comments Can be anywhere in the source code A compiler ignores the block Three kinds of comments: /* text */ The compiler ignores everything from /* to */ /** documentation */ This indicates a documentation comment // text The compiler ignores everything from // to the end of the line Javadoc Generate Java code documentation in HTML format from Java source code /** * The HelloWorld program implements an application that * simply displays "Hello World!" to the standard output. * * @author Mingon Kang * @version 1.0 * @since 2015-08-01 */ public class HelloWorld { public static void main(String[] args) { System.out.println("Hello World!"); } } http://www.tutorialspoint.com/java/java_documentation.htm Library declaration Declare libraries that need to load in the program Set of dynamically loadable libraries User-defined library import package_name e.g. import java.io.*; import com.sun.*; http://docs.oracle.com/javase/7/docs/api/ Identifiers The name of a variable or other items such as class, method, object defined in a program. Unlimited-length sequence of letters and digits Begin with a letter, the dollar sign "$", or the underscore character "_“. No digit Subsequent characters may be letters and digits, dollar signs, or underscore characters Neither commas nor blanks are not permitted. No special symbols other than underscore
    [Show full text]
  • NET Framework Guidelines and Best Practices
    DBHDS Business Solution Development Jefferson Building, 5rd Floor [email protected] .NET Framework Guidelines and Best Practices Application Architect: Mario Epps DBHDS Business Solution Development Jefferson Building, 5rd Floor [email protected] Department of Behavioral Health and Developmental Services - Abstract Abstract This document describes the coding style guidelines for native .NET (C# and VB.NET) programming used by the Business Solutions Development team. Application Architect: Mario Epps .NET Framework Guidelines and Best Practices Contents Department of Behavioral Health and Developmental Services - Abstract ......................................................... 2 Overview .............................................................................................................................................................. 3 1.1 Principles & Themes 3 General Coding Standards................................................................................................................................... 5 2.1 Clarity and Consistency 5 2.2 Formatting and Style 5 2.3 Using Libraries 7 2.4 Global Variables 7 2.5 Variable Declarations and Initializations 7 2.6 Function Declarations and Calls 8 2.7 Statements 10 2.8 Enums 11 2.8.1 Flag Enums 14 .NET Coding Standards ..................................................................................................................................... 18 3.1 Design Guidelines for Developing Class Libraries 18 3.2 Files and Structure 18 3.3 Assembly
    [Show full text]
  • Naming Conventions in Win32 and MFC
    Naming Conventions in Win32 and MFC Dr. Patrick Young, Stanford University CS193W Summer 2003 Hungarian Notation Win32 follows a notation convention called Hungarian Notation. In Hungarian Notation the first character or first several characters of a variable or parameter name identifies that variable or parameters type. Here are some of the most common Hungarian Notation prefixes: b or f—used as a prefix for booleans (f stands for flag). c—used as a prefix to chars.1 n—used as a prefix to shorts. h—used as a prefix for a handle. Handles in Win32 are numbers used to identify resources or windows. They are not pointers or pointers to pointers. Think of them as ID numbers. l—used as a prefix to a long. w—used as a prefix to a word. dw—used as a prefix to a double word. s—used as a prefix to a string. sz—used as a prefix to a null-terminated string.2 p—used as a prefix to a pointer. lp—used as a prefix to a long pointer (this is the same as a pointer in Win32 and is a relic from Win16). fn—used as a prefix to function parameters. 1 The combination cb is also used for parameters which represent the number of bytes of something. In this case cb is short for count in bytes. 2 sz can also be used for size. I do recommend double checking the documentation to make sure that the string is indeed null terminated, as an error here can be very difficult to track down.
    [Show full text]
  • Coding Conventions: the Hungarian Notation
    Coding Conventions: The Hungarian Notation The Hungarian notation is a language-independent programming naming convention wherein the name of an object designates its type and usage. The Hungarian notation has primarily been popularised by Microsoft and their corresponding usage of it in their APIs, articles, code samples and reference documentation sets. It works by adding a prefix to the identifier name; this prefix indicates the identifier’s type. Hungarian notation was the brainchild of Charles Simonyi while at Xerox. The notation was commonly used at Xerox PARC (Palo Alto Research Centre) and later widely implemented at Microsoft, the company Simonyi joined after leaving Xerox. There are many advantages to using Hungarian notation, one of them is that you can, for instance, look at a variable name and instantly know its type, without having to look it up – thus easing the process of reading code written by someone else. Hungarian notation is also very useful where large development teams are involved since it offers a well structured naming convention, forcing everyone involved to program in a unified manner. The notation applies to variable names, types, constants, parameters, functions and classes. Using Hungarian Notation Table A.1 lists some of the prefix codes used in Hungarian notation. Table A.1 – Hungarian Notation Prefix Coes Prefix Code Description ch Character. s String. w Word. l Long. n Number type (either int or short). i Integer. fn Function pointer. b BYTE. st Pointer to a string. sz Pointer to a 0 byte terminated string lp Long pointer. p Pointer. d Difference between instances. c Count of instances.
    [Show full text]
  • Invenio Mobile App
    Invenio Mobile App August 2014 Author: Harry Cutts Supervisor: Jiří Kunčar CERN openlab Summer Student Report 2014 CERN openlab Summer Student Report 2014 Project Specification The aim of this openlab summer student project is to enhance mobile user experience for Invenio digital library services. The project will use the Apache Cordova platform to build native Android and iOS applications. The application itself will be built using HTML5 and JavaScript technologies. An initial prototype of the application, targeting mostly search functionality, is available. The selected student will enrich existing functionality as well as address personal features related to tagging of resources or notifications about new publications of interest. The project will include server-side programming in Python to enrich REST API of the digital library platform. CERN openlab Summer Student Report 2014 Abstract In this project, a mobile application is developed for the Invenio digital library system, using HTML5 with Apache Cordova. Alternative HTML5 technologies are compared and decisions justified. The features of a prototype are reimplemented with a view to improving performance, usability, and maintainability. OAuth2 authentication is implemented, and further work proposed. CERN openlab Summer Student Report 2014 Table of Contents 1 Introduction..........................................................................................................6 2 Project Goals........................................................................................................6
    [Show full text]