Mobile

Labels
AJAX(112) App Studio(6) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(8) OAuth Scopes(1) OAuth2(11) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(10) PKCE(2) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(178) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(80) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Mobile
Wednesday, May 29, 2019PrintSubscribe
Multi File Upload
Code On Time release 8.7.11.0 introduces Multi-File Upload. End users can select multiple files and submit them for upload at once to create multiple database records. Application framework automatically inserts a table row for each file, uploads the file, and persists the data either to the database or to an external storage system.

Here is how it works:

1) Start upload.



2. Select multiple files.


3. Preview the selection and tap Submit.


4. Multiple database records are created for each file and associated with a parent if needed.



The feature is activated when the Upload action is executed by the data controller. A built-in form is displayed to allow selecting multiple files for upload.  User submits the form and the framework starts processing files one by one. For each file an Insert action is executed through the same data controller. By default, the view createForm1 is used to figure a list of data fields for Insert. An alternative view can be specified in Command Argument of Insert action.  Special fields are detected to store File Name, Content Type, and Length of the file. For child data views, the master field values are also included. If insert is successful, then the physical file is uploaded to the server and stored in the first on-demand field of Byte[] type. Failure to insert a record or to upload a file will interrupt the processing. The data view is refreshed when processing of all files has been completed.

Consider the following database schema that allows associating documents with the supplier records.



Table Docs defines three explicit fields to maintain information about the files: FileName, ContentType, and Length. The physical data will be stored outside of the database and processed with File System Blob adapter.

Start Code On Time and create an app with two data models - Suppliers and Docs. Next, start Project Designer and begin defining the new field with the name Data and type Byte[] in Docs controller. Mark the field as On Demand. Enter DocID in Source Fields and DocsData in On Demand Handler. Choose Thumbnail in On Demand Style drop down to have a file preview in the app. Save the new field and drag it to createForm1, editForm1, and grid1 in the Docs controller.



Select Docs data controller and enter the following in the Blob Adapter Config property:

Field: Data
Storage-System: File 
Path-Template: C:\app\DocsFileData\{DocID}-{FileName}
File-Name-Field: FileName
Content-Type-Field: ContentType
Length-Field: Length

Make sure that the specified folder C:\app\DocsFileData does exist on your device. Application will use the primary key of the Docs record and the file name to create physical copies of the files submitted to the virtual on-demand Data field.

Add a new action with command name set to Upload to action group Docs / Actions / ag3 .



Proceed to drag Docs controller onto Suppliers controller or copy Docs and paste onto Suppliers. This will create a new field with type DataView and name Docs in the fields of Suppliers controller. Drag the new field to editForm1 view in the same controller.




Run the application and select a supplier.



Select Upload action and choose multiple files to upload.



Tap submit and see the corresponding records appear in the app.


The entire process take a few seconds. User can choose individual records to add comment. There is also an alternative it to create one record at a time if a more deliberative data input mode is desired.



Multi-file upload significantly improves ease-of-use for document management applications.


Monday, May 27, 2019PrintSubscribe
Code On Time With Command Line
Code On Time release 8.7.11.0 makes possible creating mobile and web apps directly from command line. New command line parameters allow configuring, generating, and refreshing apps without requiring developer to go through Project Wizard and Model Builder. Now the app generator can be integrated in automated scripts to produce custom apps.



For example, the following command line will instantly produce a basic app:

codeontime -generate "c:\apps\app1" -theme "Citrus" -run -appname "Hello World"

The app will be displayed in the default web browser when the code generation is completed.


This application is not connected to a database and displays no data. Next command will connect it to a database and produce data models, data controllers, and pages for Products, Suppliers, and Categories. The app will have a built-in membership manager and content management system.

codeontime -generate "c:\apps\app1" -dbconnection "Data Source=;Initial Catalog=northwind-cmd;Integrated Security=True;" -objects products,suppliers,categories -dbmembership -dbcms



This command will remove CMS (Content Management System), enable reporting, change the theme to "Petal", and make the app display Shippers and Customers tables.

codeontime -generate c:\apps\app1 -dbcms false -reports -theme Petal -objects Shippers,Customers


Notice that previously specified project options are persisted in the project file and do not need to be re-entered. Use double quotes to surround property values with spaces. Value "true" for Boolean properties can be omitted.

The app generator folder is not included in the Path variable of the machine during installation. Make sure to add C:\Program Files (x86)\Code OnTime LLC\Code OnTime Generator path to the Path environment variable. Otherwise use a full path to the app generator executable codeontime.exe when using the app generator in command line mode.

The three core commands controlling the app generator from command line require a path to the project folder. If the specified folder does not exist, then it will be created. If there is no file DataAquarium.Project.xml in the specified location, then the file will be created with the default settings. All three commands will change the project file if the configuration options are also specified in the command line. 

-Config

Use -config command to create a project, change its options, or view the current option values. For example, this command will create a project configured for Microsoft SQL Server database, implemented in Visual Basic with MyBiz namepace, and build-in user and role management.

codeontime -Config "c:\apps\myapp1" -DbConnection "Data Source=;Initial Catalog=northwind-cmd;Integrated Security=True;" -Language VisualBasic -Namespace MyApp1 -DbMembership

This command will alter the project to have it presented in Berry theme. The app will start in a default web browser after the code generation.

codeontime -Config "c:\apps\myapp1" -Run -Theme Berry

The summary of the project configuration is display after successful -config command.




There will be a single file in the project folder.




-Generate 

Use -generate command to produce application source code. The app will be displayed in default web browser if -run option is specified for the project.

codeontime -generate "c:\apps\myapp1" 

Here is an example of application generated for the previously configured project. It includes every database object from the northwind database.




The project will look like this:



Please note that you can build this app with a single -generate command if you specify the same set of options in the command line. Command -generate first creates a project file or modifies the file according to the specified options. Code generation is performed only if every single configuration option has been successfully processed.

You can customize the generated app in the Project Wizard and Project Designer if you start the app generator without command line parameters and choose "Add an existing application" option. The new application will be displayed on start page.

-Refresh

Command -refresh deletes cached database metadata (information about tables, views, columns, etc) and rebuilds all data models, data controller, and corresponding pages from scratch. Use this command to generate the app if database schema has changed. 

It behaves just as -generate command in every other aspect.

-DbProvider

App generators supports many database engines. Option -DbProvider allows specifying the data provider for the app. By default, the assumption is that Microsoft SQL Server is the database engine of application. The equivalent command line option would be:

-dbprovider sqlclient

The supported data providers are the same ones available in the Project Wizard:


The command line processor will match the text specified by -dbprovider option in case insensitive fashion to one of the options in Supported Data Providers list.

Use mariadb or mysql for MySql or Maria DB server.

Use oracle for Oracle database.

Use ibm or db2 for DB2 databases.

Use sqlanywhere, postgres, or firebird for the corresponding database engines.

Automated App Building

The new command line support enables automated production of mobile and web applications with Code On Time app generator. Consider using Code On Time if you are a database administrator, application architect, or project manager. Just a few keystrokes will help to validate a database schema, provide high qualify data input screens, and eliminate tremendous amount of man hours.

Applications produced with Code On Time are metadata driven. Data modes and controllers are defined in XML files stored in ~/app/controllers folder of generated application. This makes possible to use the app generator to build apps from custom metadata. For example, a set of custom labels for table columns can be maintained in Excel spreadsheet or incorporated directly in the command line text manipulation commands. 

If your apply customization to data models then make sure to delete the corresponding data controllers. The app generator will build the dropped data controllers if you issue a -generate command. If you choose to modify the data controllers directly then the app will reflect the changes right away.

Code On Time v9

The upcoming new development environment incorporates the Project Designer and Object Inspector directly in the app. The development environment is activated at runtime from the app user interface. All project configuration options are arranged in a single hierarchy. The hierarchy will synchronize with the contents visible at the moment when developer activates "design" mode in the live app. Object Inspector presents properties of the selected hierarchy element in a unified presentation similar to the one found in Visual Studio. Developer will be able to perform live app inspection and drag hierarchy elements onto live pages.

New development environment is integrated into each app as add-on DLL. It will execute the app generator in command line mode when project configuration is changed. The add-on is removed from the code base when application is published.

The project creation and management will also change in v9. The app generator started without parameters will generate a management app displaying a list of projects. The management app will display in the default web browser.  A new project created from the management app will include a start page similar to the first app screenshot above. Developer will activate Project Designer from the live app to connect databases, create data models, pages, etc. 


Wednesday, May 22, 2019PrintSubscribe
Removing Header Text from Views
The responsive user interface of apps created with Code On Time is intuitive.  Nevertheless the grids and forms do display generic text to provide basic user instructions.

This is an example of a grid view with the header text displayed above the data.


This is how the data form may look.


Each description can be changed individually in the Project Designer.

If you prefer a minimalist user interface then the descriptions may appear to be excessive. The unique architecture of apps created with Code On Time makes possible altering various aspects of an app with a just few lines of code.

For example, enable shared business rules in your app by selecting the corresponding option in Settings | Database Model & Business Logic | Shared Business Rules section of the project configuration. Re-generate the app. If you have existing custom "code" business rules, then open each rule and change the base class from BusinessRules to SharedBusinessRules.

Application framework will create an instance of SharedBusinessRules class or a custom version of it whenever a client request is processed through the server-side code. The framework retrieves the XML description of the corresponding data controller to handle the request.Then it provides the app with a chance to perform changes to the in-memory copy of the data controller. If the matching business rules class indicates that it supports data controller virtualization (customization at runtime), then the customization code is invoked. By default, no customization is performed. Developer can override virtualization code to make changes to the controller.

The header text definitions in views of data controllers are as shown in this sample:



Changed the file ~/app/App_Code/custom/Rules/SharedBusinessRules.cs as follows:

namespace MyCompany.Rules
{
    public partial class SharedBusinessRules : MyCompany.Data.BusinessRules
    {

        public override bool SupportsVirtualization(string controllerName)
        {
            return true;
        }

        protected override void VirtualizeController(string controllerName)
        {
            NodeSet().SelectViews().SetHeaderText(string.Empty);
        }
    }
}

Save the code file and observe that all views in the app are displayed without descriptions:



You can customize your data controllers selectively by inspecting the name of the data controller specified in the argument of VirtualizeController method.

Take you minimalist presentation even further by removing category descriptions in form views with this code.

protected override void VirtualizeController(string controllerName)
{
    NodeSet().SelectViews().SetHeaderText(string.Empty)
        .SelectCategory("c1").SetHeaderText(string.Empty).SetDescription(string.Empty);
}

Your forms will now have an even more streamlined data-only presentation: