|
|
|
|
|
- Overview
- Creating a project for Android with WINDEV Mobile
- Creating an Android project with WINDEV Mobile
- Fonts used in an Android project
- Analysis of an Android project
- Testing an Android project
- Project test (Go) in the simulator directly
- Project test (Go) in the Android emulator directly
- Project test (Go) on the device directly
Developing applications for Android
WINDEV Mobile allows you to develop Android applications. The method for developing applications for Android with WINDEV Mobile is very simple. You can test Android applications directly from WINDEV Mobile. Once created, the applications can be deployed. For more details, see Deploying Android applications. This help page presents: Creating a project for Android with WINDEV Mobile Creating an Android project with WINDEV Mobile To create an Android project with WINDEV Mobile: - Click
in the quick access buttons. - In the window that appears, click "Project".
- The project creation wizard opens.
- Choose the type of project to create: "Android or iOS application".. Proceed to the next step of the wizard.
- Select the platform of the project you want to create. It is possible to create:
- a cross-platform Android and iOS project: this project already contains the 2 platforms Android and iOS and can be run on either of these platforms.
- an Android-only project: this project will contain only the Android platform.
- an iOS-only project: this project will contain only the iOS platform.
To create an Android project, select "Android only".. Proceed to the next step of the wizard. - The wizard asks you to select the type of device involved in the project: phone and/or tablet..
Note: If the application is intended to run on several Android devices (phones of different sizes or resolutions, for example), WINDEV Mobile defaults to the smallest resolution for creating application windows.. You can use anchors to adapt the application to any device. - Select the desired style book. This style book will be available by default when creating a window or report, and will be applied to all new controls. This option can be modified in the project description window ("Style" tab). Go to the next step.
- Specify the project name and location. These options cannot be modified. The project corresponds to a ".WPP" file for WINDEV Mobile. This file can be opened by WEBDEV and WINDEV. For more details, see Common project.
All the objects associated with the project will be created in the specified directory. - Finish the wizard. The new project is opened in the editor. This project has a specific "Android application" configuration. You can edit this configuration or create a new one at any time. For more details, see Project configuration.
Una vez creado el proyecto, puede: - cambiar las opciones de configuración del proyecto. Para obtener más información, consulte Configuración del proyecto.
- asociar uno o varios documentos al proyecto. Estos documentos pueden ser archivos de texto, imágenes, documentos escaneados, etc. Para obtener más información, consulte Asociar documentos al proyecto.
- asociar uno o varios análisis al proyecto. Para obtener más información, consulte Análisis del proyecto.
- integrar el proyecto en el Administrador de Código Fuente (SCM). El Administrador de Código Fuente simplifica el trabajo en equipo y también puede ser útil para el trabajo individual.
- definir un estilo de código. El estilo de código corresponde a un estándar de programación que puede aplicarse a toda la aplicación. Este estándar permite añadir prefijos a los diferentes elementos del proyecto, las variables, etc. Para obtener más información, consulte Estilo de código.
- especificar los idiomas que admite el proyecto. Estos idiomas estarán disponibles de forma predeterminada al traducir el texto de un elemento (control, ventana, página, reporte, etc.). Para obtener más información, consulte Proyecto multilingüe.
Remarks: - All the available skin templates can be used with an Android application.
- All the skin templates apply the holographic theme from Android 5.
Note: To use the "Material Design" theme, in the "General" tab of the Android configuration description, check the "Apply Material Design theme to native fields and Info/Error/Dialog windows (requires Android 5.0 or higher)" option.
Fonts used in an Android project By default, Android projects use Droid (Droid Sans, Droid Sans Mono and Droid Serif) and Roboto fonts in the editor. These fonts are automatically installed along with WINDEV Mobile on the development computer. Using native Android/iOS fonts at runtime The following fonts can be used: - Droid Sans -> all Android versions
- Droid Sans Mono-> all Android versions
- Droid Serif -> all Android versions
- Roboto -> from Android 4.0 (Ice Cream Sandwich, api level 14)
- Roboto Condensed -> from Android 4.1 (Jelly Bean, api level 16)
- Roboto Light -> from Android 4.1 (Jelly Bean, api level 16)
- Roboto Thin -> from Android 4.2 (Jelly Bean MR1, api level 17)
You can choose other fonts installed on the development computer when defining the style of a control. If the device does not support the specified font at runtime, a substitution font will be used (Droid Sans or Roboto from Android 4.0). This can lead to display problems. Note: If a custom font is used in the project without having been integrated into the project, a UI error is displayed.. Analysis of an Android project When creating an analysis for an Android project, you have the ability to use: - an HFSQL Classic or Client/Server database.
- an "SQLite" database. It is the default database found on the Android operating system. The Native Connector to this database is included in WINDEV Mobile.
When using an SQLite database, WINDEV Mobile helps you describe a connection to an SQLite database by specifying: - A name and a description for the connection (the name is used in programming with functions such as HOpenConnection).
- The advanced parameters of the connection:
- The name of the file containing the database (in SQLite, the entire database is contained in a single file whose extension is .db in most cases).
- The directory containing the database.
Remarks: - In an SQLite database, each data file should contain an automatic identifier (strongly recommended).
- The Native Connector for SQLite is available for WINDEV, WEBDEV and WINDEV Mobile applications.
- For more details, see Android application: Using and sharing data.
Testing an Android project Several test modes are available for Android applications: Project test (Go) in the simulator directly This test starts a WINDEV Mobile test window in which the application for Android is run. This test allows you to use the debugger. However, several differences can be noticed compared to a real execution. Indeed, the simulation uses the PC and not the Android device. Note: When GOing a project, a first project window must be defined.. If the application is available for phones and tablets, a first window can be defined for the phones and another one can be defined for the tablets. Project test (Go) in the Android emulator directly The Android emulator is supplied with the Android SDK. To use an emulator, you must first create it in Android Studio (refer to the Android Studio documentation for more details). If the emulator has been created, it will automatically appear in the list of available devices for testing via the "GO" option. Remarks: - The emulator may take a long time to start. It is recommended not to close the emulator between 2 project tests.
- The debugger is not attached to the application. The breakpoints are ignored.
- This type of test does not take the speed of the phone into account. The test takes the speed of the development computer into account.
- Some WLanguage functions are not available in the emulator. The documentation of the different functions indicates whether the function can be used in the emulator. The functions fail when they are not available.
Project test (Go) on the device directly Then, the Android executable is copied onto the phone connected to the PC and run. Remark: The debugger is not attached to the application. The breakpoints are ignored.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|