In this section you can manage general information regarding your Project basic definitions.
General
Project
Name of the Project
The name of your Project is the one that will be visible to the user at the PDA. The name of the Project should only contain letters, digits or underscore (_) and must start with a letter.
Description
Description of the Project
This description is for your information only, Kalipso does nothing with it.
Icon
Icon associated with the Project
This icon will be visible to the user on Windows Mobile/CE devices and Desktop 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.
Style
Visual style collection associated with the Project
A copy of the selected style will be created in the Project. Any created Control will inherit it's default properties from the default style in the Theme.
Project Version
Version of your 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
Version of your 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.
Mobile Device
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 (Check Terminals for more information).
Nonetheless, you can deploy your Project to almost any kind of PDA or
Smartphone. 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
Device associated with the Project
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.
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.
Screen Orientation
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.
- <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 “Switch” 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.
Remarks
|
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. |