With the release of yeet version 2.2, our low-code platform is being expanded with important and powerful functions and components. We also provide information about bug fixes and changes.
Innovations
Media Manager
With this new tool, as part of the development environment, it is possible to upload and download media content (images and videos) and documents.
The Media Manager consists of a directory tree and a display area. Folders for content can be created in the directory tree on the left-hand side in order to group them or organize them thematically. The existing content of the selected folder is displayed in the display area. Content can be found and filtered by file type using the search function in the display area.
In the tile options, the images can be downloaded, deleted or the relative link for the image can be copied. The content can be used via the link, e.g. in the Picture component for display in the application.
In addition, files can also be selected directly from the Media Manager for certain components using the file picker.
The Media Manager can be accessed via the yeet burger menu.
New UI components
A lot has also happened in the area of components. The range of available UI elements has been expanded to include the following components:
QR code
This makes it easy to place and display your own QR codes in the application.
The displayed QR code can be defined in the Code__value property. In addition, a small logo can be placed in the QR code and the color can be selected. The Code__level determines how much of the QR code can be covered without restricting its readability.
Video
This can be used to play small videos (max. 5MB) directly from the Media Manager or to display external streams, e.g. YouTube.
In addition, properties are offered to add audio tracks / text tracks or to adapt the color of the surface to the branding.
Scanner
This allows a connected camera to be used as a scanner for a wide range of 1D and 2D codes. Alternatively, the barcodes can also be recognized via an image.
In the properties, you can specify which barcode type is to be scanned and which camera is to be used for scanning. You can also set whether the scanned value is displayed directly in the camera image. The scanned value can then be read out via an event and used further.
Using the Scanner__mode property, the UI switches to a different display in which an image upload can be started.
Map
This new component allows the display of a geographical map based on OpenStreetMaps.
The following groups can be found in the properties:
- Map
You can select the language and the map section here using the center coordinate. You can also set the standard and search zoom and set the standard marker. - Search
In this group, a search bar can be switched on and its position in the map component can be defined. The “Auto-Search” property is used to determine whether the search should handle the results list independently or whether the search result should be handled via an external event. - Zoom
Display of the zoom control - Routing
Display of a simple routing control - Marker
The properties displayed here determine whether a user may add/delete their own markers on the map or which markers from a self-defined list should be displayed.
Template List
With the template list, content can be built up dynamically using entities.
The component behaves like a normal container in the Designer. Therefore, all other components can be included in the template list. In contrast to a normal container, an entity can also be selected here as with a table.
If the template list is then in app mode, a clone is created for each record instance of the entity and displayed as a list.
The list contains infinite scrolling. Therefore, further instances are only created when scrolling. The alignment of the list can be determined via the list properties in the template list.
In order to use the data of the record instance in the components of the template list, all component properties that are a child element of a template instance receive an additional option (DataMaper) in their properties. Here, the record values can be assigned to a component property so that each Template List instance can react individually to its record. The record values are assigned to each event via the “EventData” and can therefore also be read out via event snippets.
Signature
The signature component provides a field for signatures. A signature can be created here by touch or mouse and further processed as an image (EvtSave). There are also options for uploading or downloading images that contain a signature or for clearing the input field.
The properties can be determined:
- the format in which the signature is saved (PNG, SVG, JSON)
- which brush color and line width should be used
- which options (Upload, Download, Save, Clear, Undo) should be displayed to the end user
Unique Keys
Properties can now be classified as “Unique” in the Entity Manager. This specifies that the value of the property (e.g. an invoice number) may only be contained once in the entity set.
The unique property can be assigned via a toggle button for the entity property as long as no records exist for the entity.
Links
In yeet version 2.1, links were introduced when using concept 16 operation. With the current version, the principle has been extended to standalone operation. Links (so-called navigation properties) can be created here in the entity manager and used in the usual way via the table component.
To create a new link, there is a new entry “BasicLink” in the list of available properties
A source property of the selected entity must be selected in the link, which is then linked to the target property of the target entity. It must always be possible to select a unique property. The following links are possible:
- 1 : 1
- 1: N
- N: 1
* 1 = Eine Unique-Property
Once the link has been created, it appears in the property overview
Deprecations & Breaking changes
- For the event functions (e.g. EvtMouse or EvtMouseDown), the HTML events for some events were included under Data in EventData. For standardization, the HTML events, if available, are now included under Events in EventData.
- The API functions runRpc and execute have been replaced by runRpcSimplified and executeSimplified. The deprecation was announced in the yeet Version 2.1 blog post.
Troubleshooting
In addition, further enhancements and bug fixes have been implemented. A complete description can be found in the change log in the installation package. The current release 5.9.05 of conzept 16 is required to use the new version in conzept 16 mode.
Further information
Would you like to try yeet? We would be happy to provide you with the installation package for yeet 2.2.0 on request.