You can simplify and speed up development of digital applications by using a variety of existing components as building blocks, allowing you to create sophisticated digital applications without having to write all the code yourself. You can download a variety of components from Kony Marketplace and import them into your projects, or import reusable components that you create yourself.
For example, you can download the following free components developed by the Kony Marketplace Assets team, and drag and drop them into your applications:
You can also import masters created in an earlier version of Kony Visualizer into a Free Form JavaScript project. You can continue to use the masters in your applications, or make them available as reusable components that can be published to Kony Marketplace by converting them to components. A master is similar to a component without a contract, except that a component includes a controller module.
For information about creating components, see Creating a Component. For information on the types of projects, you can create, see Types of Projects.
The following topics provide additional information about using components:
Kony Marketplace gives you access to a rich assortment of components. You can download a component, and then import it into your project.
Check the Video to learn more about Kony Marketplace and how to download one to use it in your application.
To download a component from Kony Marketplace:
From Asset Version, select the version of the component to download.
Once you are done selecting the asset version, scroll down.
You can import components to your Kony Visualizer project and reuse them at necessary places in the application. Components can be imported from the following sources:
To import a component to your project, follow these steps:
Once you have imported a component to your project, you can easily add the component to a form. For more information, refer Add a Component to a Form.
You can also save the component to a collection. For more information, refer Add a Component to a Collection.
To help you organize your components, you can group them in a collection within the Library Explorer. You can organize related components, or organize them however you like, in multiple collections within a library. You can then easily drag and drop the component from the Collections pane of Library Explorer onto a form in any of your digital application projects.
To add a component to a collection, follow these steps:
If the component uses any Kony Fabric services, Kony Visualizer Classic prompts you to select the services that you want to include with the component. Kony Visualizer creates a trial Kony Fabric account and includes any required services.
You can also add a master created in earlier versions of Kony Visualizer to a collection.
Starting with Kony Visualizer V 8.1, you can add skins, media assets, and images to components. In previous releases, when you create a component and export the component to the marketplace, associated dynamic skins, and media assets were not added to the collection automatically. These skins and media assets used to be accessed through the code that you customized within the component.
Important: When you are importing a component into a project, ensure that the component assets do not have the same name as any of the assets in the project you are importing the component. Visualizer does not warn you of any duplication, and you may lose some functionality.
To add skins to a component, do the following:
When you add a skin to a component, a live two-way dependency map is maintained to track skins associated to a component. If you delete a skin from a project, the skin is removed from associated components.
To add media assets to a component, do the following:
If you delete an asset from a project, the asset is removed from associated components.
From Kony Visualizer V8 SP4 Fixpack 28 onwards, you can directly import an image from your local computer and add it to the widget in a component. Previously, to change the asscoiated image of a Login component, you had to first import the image to the Assets tab and only then you could add it to the component.
To directly import an image and add it to a component, follow these steps:
The Select Image dialog box appears, containing the list of available imported images.
Components downloaded from Kony Marketplace often include documentation supplied by the component creator. For example, the Rating Prompt component developed by the Kony team includes a summary of key details about the component, along with a more complete description of the component and how to use it.
You can view this documentation, if it exists, from within Library Explorer in the collection where you saved the component.
To view details and documentation about a component:
To switch between details and documentation view, click Details or Documentation.
You can add a component to a form in a project in virtually any form scenario, including using components within another component. You can then drag and drop the component into your application to create sophisticated, full-featured digital applications without writing all of the code.
For example, rather than creating a log-in form from scratch for each of your digital applications, you can download the Login component from Kony Marketplace. You can add the Login component to a collection of components, and then add it to a form.
To add a component to a form:
Note: From Kony Visualizer V8 SP4 Fixpack 28 onwards, the Default Library filter has been enhanced to segregate components according to their respective channels. As a result, mobile-only components are displayed in the Default Library when a Mobile form or a Tablet form is open at that time on the Project Canvas. Similarly, web-only components are displayed Default Library when a Web form is open on the Project Canvas. However, when there is no form open on the Project Canvas, all the available components are displayed in the Default Library.
If the component is added to the project and appears on the Templates tab, you can also do one of the following:
The instance appears in the Project Explorer as blue text with a different icon, making it easy to identify as a component instance.
You can also use a master created in an earlier version of Kony Visualizer in your digital application by importing the master into a Free Form JavaScript project. For information on the types of projects you can create, see Types of Projects.
To import a master:
You can then drag and drop the master onto a form just as you would drag and drop a component.
Just as you can import a component into your project, you can export a component to your computer, network, or the cloud. You can then import the component into another project or share it with others.
To prevent your component from being modified by users, you may want to lock the component. This prevents users from viewing or modifying the component's source code. For more information about locking a component, see Creating a Component.
Note: Locales are not exported with a component. For more information about locales, see Appendix A • Internationalizing (i18n) Application Content.
To export a component, follow these steps:
If the component has been added to the project and appears on the Templates tab, select the component there.
Note: While exporting a component, if any project-level properties have been enabled, these properties are automatically applied to the exported component. To avoid this issue, you must first disable the required NFIs for either iOS or Android from Edit > Manage Native Function APIs > iOS/Android and then export the component.
If the component uses any Kony Fabric dependencies, including .jar files, service definitions, connectors, or node.js files, a pop-up is displayed with the list services used in the component.
Select the required services by clicking the checkbox and click Package to export (or) to add it to the library.
If you create a component that requires configuration of Kony Fabric service parameters, follow these steps:
The JSON file includes the information about all the configurable parameters for the services included in the component.
Here is a sample JSON file with the default parameters.
[{ "name": database_url, "displayName": < Display name of the parameter to show in Properties Window > , "defaultValue": < Mandatory if property is readOnly, Optional otherwise > , "type": < Type of the parameter.Can be one of String / Integer / Double > , "serviceName": < Name of the MF service > , "serviceType": < Type of the MF service.Can be one of identity / integration / object / orchestration > , "readOnly": true / false }, { < configurable param 2 > }]
<? xml version = "1.0" encoding = "UTF-8" standalone = "yes" ?> < endpoint dataAdapterId = "1" encryptSecureInfo = "false" name = "default" type = "CustomDataAdapter" > < apiThrottling / > < config > < entry > < entry > < key > jdbcUrl < /key> <value>${database_url }</value > < /entry> <key>jdbcClass</key > < value > com.mysql.jdbc.Driver < /value> </entry > < /config> </endpoint >
To publish a component to Kony Marketplace, first add it to a collection in your project. For more information on adding a component to a collection, see Add a Component to a Collection.
Click the video to learn about how to submit Kony Visualizer components to Kony public Marketplace or to your private Marketplace.
Note: You can only publish a component with a contract to Kony Marketplace. For more information about components with a contract, see Components Overview and Creating a Component.
To publish a component to Kony Marketplace:
Note: While uploading a component again, you must change the asset version.
If you are an enterprise customer whose organization uses a private section of Kony Marketplace, you can download a component from that private section or upload a component to that private section using your organization's cloud account. First, configure Kony Visualizer or Kony Visualizer Classic to use the cloud account.
Click the video to learn about the various features of Private section of Kony Marketplace..
To work with a private section of Kony Marketplace in Kony Visualizer:
mp:{privateMPAccountId: <MyAccountId>}
<MyAccountId> is the account identifier of your cloud account. The account identifyer is displayed in the top-right corner of your cloud console on manage.kony.com.
To work with a private section of Kony Marketplace in Kony Visualizer Classic:
To download a component, see Download a Component from Kony Marketplace. To upload a component, see Publish a Component to Kony Marketplace.
Kony Marketplace offers a private section where you can upload your own components, distribute them among your teams, download them, and use them.
Moderators manage the private section. As a moderator, you can review a component, approves them, or delete them.
If you want to be a moderator, you must have a Kony cloud account, and your cloud administrator must provide access to the private marketplace as a moderator.
To Manage components as a moderator, follow these steps.
When a user wants to create a component, if the user wants to select an option to switch between the default value for Drag and drop experience for a component, he can do that by the snap to drag position or snap to the layout.
In Kony Visualizer V8 SP1, Kony introduced Snap Mode feature which enables a user to snap all components and collections to the layout. A user can configure this in the preferences section of Kony Visualizer.
If Snap is OFF, all components and collections are placed where the user drags them. When a user selects Alt + Drag, the function will work opposite to what is configured.
To turn on the Snap Mode, do the following:
With V8 SP3 GA, a new feature is provided to help you to get the UI elements of a component on to a form without affecting the parent component and reuse the component’s UI elements. You can use Component Flattening to:
You can further bundle your modified form to a new component.
The feature, Flatten Component is applicable for components with contracts and components without contracts. It is also applicable to pre-built components.
To flatten a component, perform these steps:
Important: All associated controllers and module files in component are lost after flattening. This might result in loss of functionality of your component.
Any actions associated with the source model widgets present in the form are copied to the newly created flexContainer. All actions also are moved to a channel specific directory.
Limitations:
Rev | Author | Edits |
V8 SP1 | PG | PG |
V8 | SHS | SHS |
Copyright © 2013 Kony, Inc. All rights reserved. |