Overview
Icon is a visual element used to represent specific actions, objects, or status indicators within the user interface. Icons in noKodr are integrated into various components and serve as intuitive symbols that help users quickly understand and navigate the application.
Here's how icons are typically used in noKodr:
Component Representation: Icons may be used to represent different UI components, making it easier for users to identify and select them when designing a layout.
Action Triggers: Icons can be linked to specific actions, such as saving a form, opening a modal (referred to as "screens" in noKodr), or deleting an entry. These icons are usually placed on buttons or within interactive elements.
Status Indicators: Icons might indicate the status of a process or item, such as showing whether a workflow is active, pending, or completed.
Enhancing Visual Appeal: Icons add a visual layer to the interface, making it more engaging and user-friendly by providing quick, recognizable cues.
Icons in noKodr are designed to be intuitive and functional, helping users efficiently interact with the application and streamline their workflow.
Basic Attributes:
Attributes are the options available for each component, allowing you to customize its appearance and functionality. They help you tailor the look and behavior of your components to fit your needs.
Attribute Name | Description |
---|---|
Icon |
|
UI Attributes:
Attribute Group | Attribute Name | Description |
---|---|---|
UI | Component Size |
Note: Currently, we support Component Size |
Margin Location | "Margin Location" refers to the spacing around the outside edge of an element | |
Margin Size | "Margin Size" refers to the amount of space around the outside edges of an element, | |
Style |
| |
Classes |
|
Visibility and Component:
Attribute Name | Description |
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Component Label | It simply shows the name of the component. |
Note: This field displays the name of the component along with the count of its usage. For example, if you add the section for the third time in a layout, it will be labeled "Section 3."
Events:
Events available for any component is of onload type.
Onload Events:
onload event occurs when the component has been loaded.
Here, only onload event actions are available for components.
Actions are basically workflow actions, which you can explore in Workflow here.
Add Comment