General
Kalipso - Developing - Project - Properties - General
Last updated
Was this helpful?
Kalipso - Developing - Project - Properties - General
Last updated
Was this helpful?
In this section you can manage general information regarding your Project basic definitions.
When choosing the option, the screen that appears is as follows:
Project - Area for entering the name of the Project. The name of your Project is the one that will be visible to the user at the terminal. The name of the Project should only contain letters, digits or underscore (_) and must start with a letter.
Description - Area for entering the description of the Project. This description is for your information only, Kalipso does nothing with it.
Project Version - Area for entering the version of the Project. This property is for your information only but it's accessible within your Project in runtime via the “PRJ_VERSION” Keyword. If you intend to generate an APK, the format of this property must comply with Google's rules as follows: <major>.<minor>.<point>.
Database Version - Area for entering the version of the Project's Database. This property is for your information only but it's accessible within your Project in runtime via the “DB_VERSION” Keyword. Its format and content is totally up to you.
Icon - Icon associated with the Project. This icon will be visible to the user on the terminal as the image of your Project. Click the square to select the Icon. You should pick a 32x32 ".ico" file otherwise the generated executable won't show it.
A Kalipso Project must be associated with a Mobile Device, which can be one in the list of devices shipped with Kalipso or one that you create yourself. Nonetheless, you can deploy your Project to almost any kind of Smartphone, Tablet or PDA. Kalipso will use the properties of the Device you’ve defined, to define your Project's Forms size, as well as the physical keyboard information to provide you with its keys as an Event.
Device: Area to choose the device associated with the Project from set of available devices. Form's size will be inherited from the Device's properties. To use keystrokes as an Event to trigger Actions, the keys available to be captured must be defined in the Device. In addition to the available devices, it is possible to configure other dimensions for the device by clicking on the side option. The options for this area are presented below.
Display Width - Width of the Device's screen. This property is not editable; it displays the Width property of the chosen Device. This width will be used by the Forms of the Project so that you know the available working area.
Display Height - Height of the Device's Screen. This property is not editable; it displays the Height property of the chosen Device. This height will be used by the Forms of the Project so that you know the available working area.
When you click the button for more devices, the window that appears is as follows:
Identification
Name - Add a name for the device you are configuring
Group - You can create groups of mobile devices
Description - Add a description for the device you are identifying.
Details
Ratio - You can choose from Pixels (default), auto or Kalipso 3.6 Compatible
Operating System - Add an operating system for the device (information only)
Screen
Width - Define the width in pixels for the device
Height - Define the height in pixels for the device
Bar's Height
Title Bar - Define the height for the title bar in pixels for the device
System Bar - Define the system bar height in pixels for the device
Scroll Bar
Thickness - Define the thickness for the scroll bar in pixels for the device
Each Terminal has a different set of Keys. These Keys can be used as Events. This way, you can define a Key to trigger Actions. To define a Key, insert its Name and Code. Also, you can load the Operative System’s default Keys.
You can delete a relationship between system keys and the key code.
On the right side there is also a button for loading defaults
At the bottom of the window is an area where, after clicking on the field on the right, you can click on a key to know the corresponding code in the table above.
In Kalipso you can associate events by clicking on the terminal keys, but for that you have to indicate here which keys the terminal has and their codes.
You can add an external image to visually identify the device you are inserting.
This image appears on the main screen - General next to the device choice.
Kalipso allows you to develop your Project whether for Portrait view or Landscape. By default, the orientation its defined by the size of the Device. Nonetheless, if you want your application to rotate along with the Device, you must enable it.
Management - Management of the Portrait/Landscape feature. Kalipso allows you to develop your Project whether for Portrait view or Landscape. The options are:
None - No rotation.
Auto - When switching between Portrait and Landscape, based on the Terminal size, Kalipso will resize and reposition the Forms and Controls automatically.
Custom - This option allows you to define the size and position of each Form and Control in both Portrait and Landscape views. On Kalipso Main window, in the Main Toolbar, use the “Rotate” button to switch between the Portrait and Landscape views.
Default View - Default view of the Project. This property lets you define in which view your Project should be: Portrait or Landscape. This property only gets enabled if you choose “Custom” option in the Management property.
Allowed Views - Option to manage the possible views for the project. This option is directly related to the choices made in the previous management option. It allows, as shown in the image, four different types of views.
You can request Kalipso to redefine the size and position of a Form's Controls by right clicking it (the Form) in the Project's Tree. You can convert Portrait to Landscape and vice-versa.
Duplicate - All sizes and positions are duplicated from one orientation to the other. Controls may not fit on the screen and/or not displayed. You may maximize the Form to check if there's any Control outside the screen.
Calculate - All sizes and positions are calculated from one orientation to the other. The final result is the same as it would be in runtime using Management set to Auto. This way, you can get an automatic position and size and then adjust them freely.
In the styles option, styles are managed for the application under development.
When creating the project, it is possible to choose a style for the application. However, in this area, you can change the style, within those available. For that purpose, from the available list, just choose the one you want and click on it for the system to apply to the project. On the other hand, it is also possible to not have a defined style.
