Brovin Yaroslav

Администраторы
  • Публикаций

    1 974
  • Зарегистрирован

  • Посещение

  • Победитель дней

    313

Весь контент Brovin Yaroslav

  1. Первые пробы портирования существующего приложения с FMX на FGX. За основу был выбран классный проект Станислава Ихнатовича из Беларуссии с мобильным расписанием, отличающийся от других продуманным интерфейсом и детальной шлифовкой UI. Станислав любезно предоставил исходные коды своего проекта. Предлагаю вам ознакомиться с первым наброском его приложения на базе FGX. Обратите внимание, на сколько удобно идет создание стиля расписания пары, сделанного на базе компонента TfgCollectionView. В дизайн тайме созданы три варианта стилей без единой строчки кода для отображения расписания одной пары в разных исполнениях. Используя всю мощь FlexBox, удается достигнуть разнообразных вариантов "резинового" выравнивания контролов. А связь с данными не размазывается по коду, а сосредоточена вся в одном месте. Меню навигации сделано на базе нового компонента TfgListMenu без единой строчки кода, за исключением обработчиков нажатия на пункты меню и открытия отдельных форм, которым отведена роль отображения экранных страниц. Отдельно стоит указать, что специально для данного мобильного приложения была расширена возможность задавать задний фон контролов на базе картинки. А также были расширены возможности отображения и выравнивания форм относительно других. Так например форму можно встроить в любой контрол контейнерного типа, как фрейм. Или же просто отобразить форму, как всплывающее окно. P.S. Портирование приложения на FGX Native находится на стадии разработки. Screenrecorder-2018-05-28-00-54-39-998.mp4
  2. Скачать пакет можно здесь: Скачать 1. Удалить старый пакет библиотеки FGX Открываем среду IDE RAD Studio XE7 с административными правами. В меню открываем менеджер пакетов: "Component -> Install Packages..." Среди списка компонентов находим "FMX Extension Components". Выделяем и нажимаем кнопку "Remove" 2. Установка пакета библиотеки FGX Открываем в среде группу проектов. "File -> Open Project -> FGXGroup.groupproj" Собираем пакет fgx210 для всех требуемых платформ. Выделяем в менеджере проектов нужную платформу "Target Platforms" и в контекстном меню пакета fgx210 выбираем "Build" Далее повторяем сборку для всех целевых платформ. 3. Устанавливаем Design-Time пакет Выбираем в группе проектов dclfgx210 пакет и в контекстном меню выбираем "Install" Если пакет успешно установлен, то появится сообщение со списком зарегистрированных компонентов следующего вида: Все! Установка окончена.
  3. Brovin Yaroslav

    RAD Studio August 2018 Roadmap

    With this article the RAD Studio PM team is introducing an updated roadmap for Delphi, C++Builder and RAD Studio. This August 2018 roadmap includes plans for the second part of this year and the key focus areas for next year. Alongside, we have also published an August 2018 Roadmap PM Commentary blog post, with more details and information. Просмотр полной статьи
  4. Приветствую, Отвечая на вопрос насколько хороша подача материала в курсе "FireMonkey cтили" и подойдёт ли она именно Вам, предлагаю ознакомиться с парой уроков непосредственно из курса. Уроки достаточно большие, около 25 минут каждый. Но тем не менее имеет смысл их внимательно просмотреть, даже если вы не собираетесь вписываться в коучинг группу на льготных условиях, запись в которую приоткрыто сейчас всего на 2 дня, в честь дня знаний, на 1 и 2 сентября. Урок 1. Введение в концепцию стилей. В этом уроке мы начинаем изучение стилей в FireMonkey с аспектов создания кроссплатформенной библиотеки с точки зрения внешнего вида. Разбираемся, какими способами можно реализовать отображение внешнего вида компонентов. Выявляем отличия концепций скинов и стилей. Учимся применять стили к компонентам. Урок 11-1. Обзор структуры стилей компонентов FireMonkey. Первая часть дополнительного урока, записанного по просьбе обучающихся. В данном уроке рассматриваем структуру стилей половины компонентов FireMonkey. Изучаем из каких объектов и каких классов может состоять стили компонентов. С уважением, Ярослав Бровин.
  5. через всплывающее окно не получится это сделать. Потому что сам андроид не дает такой возможности. А если использовать инплейс редактирование через клавиатуру, то просто задайти кастомный формат времени, в котором добавьте секунды.
  6. The RAD Server Field Service Template provides an end to end field service application template for routing appointments, managing parts, and user administration. It is made up of a REST server module, a desktop client, and a cross platform mobile client. The template can give you a head start in building your own field service solutions. You can download the template from within the RAD Studio IDE using Embarcadero GetIt. Introduction The RAD Server Field Service Template utilizes a RAD Server based REST server module for the server side. On the admin side there is a FireMonkey based desktop client for adding, viewing, and managing appointments. Additionally, the admin client allows you to manage parts inventory and do user administration. The offline capable cross platform client app is built in FireMonkey and it can be deployed to Android, iOS, macOS, and Windows. There is a single codebase and single UI. It allows you to view pending and completed appointments, map their locations, and mark them as completed. You can also view parts inventory and receive local notifications when new appointments are synced from the server. Both LiveBindings and FireDAC are used extensively through the Field Service Template to provide a low code solution. The Field Service Template consists of a RAD Server backend connected to an InterBase database. RAD Service provides REST endpoints which both the Field Service Admin and the Field Service App connect to for performing CRUD operations. Additionally, there is a Field Service Setup app which you will run on the same machine as RAD Server to setup the Field Service Template database and sample data. Field Service Admin Field Service App Field Service Server (RAD Server) Field Service Setup You should deploy and run the projects in the following order: RAD Server Dev Server needs to be running for the Field Service Setup app to connect to and create the user accounts. Field Service Setup app will help you set up your database, the tables and data, and your EMS user accounts. Field Service Server is a RAD Server side REST resource which both the Admin client and the App client interface with. It should be deployable on Windows and Linux through IIS, Apache, or the stand alone RAD Server (EMS) server. Field Service App is a RAD Studio FireMonkey based client application for Android, iOS, macOS and Windows. The client application should allow you to select a tenant from your RAD Server and then log in as a user. Once logged in it will download the sample appointment and parts data for your current tenant and allow appointments to be completed. Once an appointment is complete it can be submitted back to the server if there is internet access. If the Field Service App is offline it will save the changed data until it is online again. Field Service Admin is a RAD Studio FireMonkey based client application designed for desktops on Windows and macOS. The Admin app can be used to create and edit appointments, view completed appointments, create and edit parts, and create and edit users. Field Service Setup [YoutubeButton url='https://www.youtube.com/watch?v=cT5tiPDPh3c&list=PLwUPJvR9mZHiMb6KBD-zb6uRvi6BS0HKN&index=1'] Start: Your RAD Server Dev Server should already be setup and running. Step 1: Set a path for your field service database. Set the path to the EMSServer database. The Field Service database is created, used, and populated with data in Step 3. The EMSServer database link is used to populate the drop down of Tenant ID in Step 2. Step 2: Setup the demo users on the RAD Server using the EMS API. You will need your EMSServer Host, Port, and Tenant ID in this step. The Setup will connect to your EMSServer and create groups and users for the template. There is a Managers group which can log into the Field Service Admin app and a Technicians group for logging into the Field Service App. You can create Tenant IDs using this tutorial: http://docwiki.embarcadero.com/RADStudio/Tokyo/en/RAD_Server_Multi-Tenancy_Support#EMS_Multi-Tenant_Console Step 3: Create the tables and insert the data into your field service database with the Initialize All button. This step contains the SQL setup queries for the Field Service database. There are three tables which will be set up which are: APPOINTMENTS, PARTS, TECHNICIANS Each table will be dropped and re-created when the queries are run (any existing data in the tables will be lost). There are also TFDMemTables containing the default data and these are copied into the InterBase tables once they have been created. Pressing the Initialize All button will execute the SQL queries against your defined Field Service database from Step 1. Step 4: Optional. View or reset the default data in the Field Service database. You can view the default sample data that is inserted into the database on this step. Additionally, you could come back later and reset the data in your database with the Reset button to the default data. Step 5: Setup the IBLite license file for the Field Service App client. IBLite requires a license file to use. Download it from the Product Registration Portal. You can find out more about doing that here: http://docwiki.embarcadero.com/RADStudio/Tokyo/en/IBLite_and_IBToGo_Test_Deployment_Licensing Locate the IBLite registration file that you download from the Product Registration Portal. It may be in your Downloads directory by default. The filename will be similar to regXXXX_XXXXXXXX.txt where the X's are numbers. The file will ultimately need to be named reg_iblite.txt. Complete: After step 5 the databases and users should be setup and ready for you to use the client and admin areas. Your EMS database and users should be setup at this point. You should be able to connect the Field Service package to your new field service database and compile the package. Once your Field Service Server EMS package is running in the RAD Server Development Server you should be able to open and compile the Field Service App client. After you complete some of the appointments via the Field Service App client you should be able to log into the Field Service Admin and see the completed appointments in the Service History. Field Service Server [YoutubeButton url='https://www.youtube.com/watch?v=paw3nCwd_qs&list=PLwUPJvR9mZHiMb6KBD-zb6uRvi6BS0HKN&index=2'] The Field Service Server is the RAD Server module for the Field Service App and the Field Service Admin to interface with. The end points mainly return the FireDAC JSON format which can be easily loaded in to a RAD Studio client or access via standard JSON in a non-RAD Studio environment. FireDAC JSON can be loaded into various FireDAC components like TFDQuery and TFDMemTable using LoadFromStream and LoadFromFile. Endpoints: GET fieldservice/appts/:PageId - Returns FireDAC JSON containing the appointments list. For Managers it is all appointments. For Technicians it is only their current day appointments for their user account. GET fieldservice/parts/:PageId - Returns FireDAC JSON containing the parts list. GET fieldservice/technicians/:PageId - Returns FireDAC JSON containing the users list. For Managers it is all users. For Technicians it is only their own account. POST fieldservice/update/appt - Receives FireDAC JSON containing an appointment ID and NOTES for an existing appointment, stores the data, and sets the appointment to completed. POST fieldservice/appts/0 - Receives FireDAC JSON for creating or editing appointments. Returns FireDAC JSON with the IDs. Only users in the Managers group can use this endpoint. Passing an ID of 0 will create a new record while using an existing ID will edit the existing record. POST fieldservice/parts/0 - Receives FireDAC JSON for creating or editing parts. Returns FireDAC JSON with the IDs. Only users in the Managers group can use this endpoint. Passing an ID of 0 will create a new record while using an existing ID will edit the existing record. POST fieldservice/technicians/0 - Receives FireDAC JSON for creating or editing users. Returns FireDAC JSON with the IDs. Only users in the Managers group can use this endpoint. Passing an ID of 0 will create a new record while using an existing ID will edit the existing record. DELETE fieldservice/appts/:Id - Takes the Id to be deleted as the last segment parameter in the URL and deletes the appointment record. Returns JSON. Only users in the Managers group can use this endpoint. DELETE fieldservice/parts/:Id - Takes the Id to be deleted as the last segment parameter in the URL and deletes the appointment record. Returns JSON. Only users in the Managers group can use this endpoint. DELETE fieldservice/technicians/:Id - Takes the Id to be deleted as the last segment parameter in the URL and deletes the appointment record. Returns JSON. Only users in the Managers group can use this endpoint. User Permissions: User permissions are governed by the {$DEFINE GROUPPERMISSIONS}. You can comment or uncomment this line for dev and live deployments. User permissions are ignored when {$DEFINE GROUPPERMISSIONS} is commented out. By default there are two Groups setup which are Managers and Technicians. Different data is returned depending on if the user is in the Managers or Technicians group. Some operations are only allowed by users in the Managers group. Database Schema: The FireDAC JSON format is used to pass data back and forth between the server, the Admin client, and the App client. The database schema for the Appointments, the Parts, and the Technicians tables are the same across all four applications. You can save the data from each of the application’s TFDMemTables out to file and load it into each of the other applications. Field Service Admin [YoutubeButton url='https://www.youtube.com/watch?v=Y5Dex1miXj0&list=PLwUPJvR9mZHiMb6KBD-zb6uRvi6BS0HKN&index=3'] The Field Service Admin project is built in RAD Studio Delphi using FireMonkey (FMX). The Admin app connects to RAD Server on the backend via a REST API. You should be able to log into the Admin area by selecting a Branch ID (Tenant ID) plus entering the login and password for a user in the Managers Group. For this template the default user is manager1. Be sure to configure the EMS_SERVER and EMS_PORT const in uMainForm.pas to point at your development server. The default is localhost 8080. The Branch ID is stored with each data table so each branch will only see its own set of appointments, parts, and users. Each branch has its own users and groups as well. The Branch system is built on top of the Tenant functionality in RAD Server. Appointments Appointments are records that can be created, viewed, and edited in the Admin client. They can also be assigned to a Technician. Appointments can be viewed and completed in the Field Service App. Appointments have various fields like Appointment date and time, customer title, description, address information, phone number, location, photo, status, and notes. The photo field supports PNGs and JPGs. Addresses can be converted to longitude and latitude using the Locate button utilizing the Google Geocoding API. History The Service History list is a view into the Appointments and only shows Appointments that have been their status set to Complete. Technicians using the Field Service App submit completed appointments and include notes. The History view utilizes TFDLocalSQL to show only the completed appointments. Parts Parts are records that can be created, viewed, and edited in the Admin client. They can also be viewed by Technicians. Parts have various fields like title, description, location, quantity, and photo. The photo field supports PNGs and JPGs. Users Users are records that can be be created, viewed, and edited in the Admin client. They also show up as an individual profile to logged in Technicians. When a user is created in the Field Service database it also creates a shadow user in the RAD Server Users API where their username and password are stored. By default users can be in the Managers Group or the Technicians Group. The Group information is also stored in the RAD Server Groups API and the server accesses the RAD Server User and Group data for the permissions. Data Sync The Data Sync tab in the Admin client is where JSON data is downloaded from the Field Service Server REST endpoint and loaded up into the various in memory TFDMemTable components. Data for the Appointments, Parts, Users, and Groups is all downloaded on this tab. You can also request to Refresh the data at any time to get new updates from the server. Additionally, there is a background TTimer which will refresh the data from the server automatically on an interval. Architecture The architecture of the app is built in a low code rapid application development style using TTabControls for handling pages and individual frames for each page. TActionList is used to consolidate much of the code in the MainForm. There are two TTabControls on the MainForm. The first one contains the Login frame and the second TTabControl. The second TTabControl contains the rest of the frames. Within the ApptsFrame, HistoryFrame, PartsFrame, and TechsFrame there are additional Master/Detail TTabControls. If you want to make changes to the design time frames be sure to edit the frame itself and not the version of it that is embedded in the MainForm. This will keep your changes consolidated in one place. If your changes don't update in the MainForm you can delete the Frame from the MainForm and re-add it. Be sure to add it to the correct Tab and set to Align Client after you add the frame. The frames are built to be as modular as possible with TBindSourceDB components used as endpoints for the LiveBindings. This allows you to easily re-use the frames in your own projects by connecting the TBindSourceDBs to your own datasets. A TFDLocalSQL component is used to provide SQL access to the various TFDMemTables via TFDQuery components. This allows the App to provide query results for filtering some of the datasets. uDataModule in 'uDataModule.pas' {MainDM: TDataModule},Contains the RAD Server (EMS) Provider client components, the in memory table components, and the various FireDAC connecting components. uMainForm in 'uMainForm.pas' {MainForm},Contains the main form of the application with the various TTabControls and inline embedded TFrames. uLoginFrame in 'uLoginFrame.pas' {LoginFrame: TFrame},Contains the UI and code for the Login screen. uApptsFrame in 'uApptsFrame.pas' {ApptsFrame: TFrame},Contains the UI and code for the Appointments screen. uHistoryFrame in 'uHistoryFrame.pas' {HistoryFrame: TFrame},Contains the UI and code for the History screen. uPartsFrame in 'uPartsFrame.pas' {PartsFrame: TFrame},Contains the UI and code for the Parts screen. uTechsFrame in 'uTechsFrame.pas' {TechsFrame: TFrame},Contains the UI and code for the Users screen. uProgressFrame in 'uProgressFrame.pas' {ProgressFrame: TFrame},Contains the activity progress TFrame which is displayed when the app is busy. uTenantsDM in 'uTenantsDM.pas' {TenantsDM: TDataModule},Contains the RAD Server (EMS) Provider connector components for accessing the Branch (Tenants) list. uTenantListForm in 'uTenantListForm.pas' {TenantForm},Contains the UI and code for selecting a Branch/Tenant. uQueueFrame in 'uQueueFrame.pas' {QueueFrame: TFrame},Contains the UI and code for syncing data from the server. uGroupsListForm in 'uGroupsListForm.pas' {GroupsForm},Contains the UI and code for selecting a Group. uTechsListForm in 'uTechsListForm.pas' {TechsForm};Contains the UI and code for selecting a Technician to assign to an appointment. Permissions The Field Server Admin app will make an additional call after it logs in to download the list of Groups that the current user account is in. It will check to see that the user is in the Managers Group. If the user is not in the Managers Group it will log you back out. There are additional permissions in the Field Server Server which govern what data is sent down to which users as well. Only users in the Managers Group will receive the full data and be able to make changes to it. Customize The UI You can quickly and easily customize most of the look and feel of the app with three easy changes. In TMainForm there is a BackgroundRect, a BackgroundImageRect, and a EmeraldDarkStyleBook control. You can change the background color of the app by changing the BackgroundRect.Fill.Gradient property. You can change the image that is overlayed over the entire app by changing the BackgroundImageRect.Fill.Bitmap.Bitmap property. The background image works by being above all of the other controls, having a low Opacity, having a HitTest of False and a Locked property of True. Finally, you can change most of the rest of the theme by loading different Premium Styles into the EmeraldDarkStyleBook control. You can customize the header logo of the Login screen on the LoginFrame. There are a few other places where the custom green color is used on some elements in the TListView controls and some the search icons using a TFillRGBEffect. You will need to update the BackgroundRect and BackgroundImageRect in the GroupsListForm, the TechsListForm, and the TenantForm as well. There is a BackgroundImage control in the LoginFrame if want to customize the background of the Login page. Remember that you will need to load one style for each of the four deployment platforms. You can access the Premium Styles here: https://www.embarcadero.com/products/rad-studio/fireui/premium-styles https://cc.embarcadero.com/item/30491 Field Service App [YoutubeButton url='https://www.youtube.com/watch?v=SnIMq-s3EHc&list=PLwUPJvR9mZHiMb6KBD-zb6uRvi6BS0HKN&index=4'] The Field Service App client project which is built in RAD Studio Delphi using FireMonkey (FMX). The client is targeted for deployment to Android, iOS, macOS, and Windows. The Field Service App client connects to RAD Server on the backend via a REST API. You should be able to log into the App client by selecting a Branch ID (Tenant ID) plus entering the login and password for a user in the Technicians Group. For this template the default users are technician1 and technician2. Be sure to configure the EMS_SERVER and EMS_PORT const in uMainForm.pas to point at your development server. The default is localhost 8080. The Branch ID is stored with each data table so each branch will only see its own set of appointments, parts, and users. Each branch has its own users and groups as well. The Branch system is built on top of the Tenant functionality in RAD Server. Appointments Appointments are records that can be viewed in the Field Service App client. When you are logged in as a Technician you will only see appointments assigned to you, marked as pending, and with a date of today. Appointments have various fields like Appointment date and time, customer title, description, address information, phone number, location, photo, status, and notes. You can view a static map of the address of the appointment plus you can press a Locate button to bring up an interactive map of the address. You can also click on the phone number on a mobile device and it will launch the call functionality of the device. Technicians can enter notes about an appointment and mark it as complete. The notes and status change are sent to the server. History The Service History list is a view into the Appointments and only shows Appointments that have been their status set to Complete for this technician for today. Newly completed records show up in the History tab even if they have not yet been synced with the server yet. Parts Parts are records that can be viewed in the Field Service App client. Parts have various fields like title, description, location, quantity, and photo. Parts are not editable in the Field Service App but the data does get updated when synced from the server. Profile The profile section shows the current Technician that is logged into the Field Service App and their various information. You can also choose to disable the local notifications here. Profile information also shows up in the TMultiView menu. Notify The notify section shows new appointments that have been downloaded from the server that have not yet been viewed by the current technician. Choosing a notification here will take you to the appointment for that notification. Local notifications are also implemented and when new appointments are received local notifications will be sent to the device. The notification functionality is built so that you can implement your own remote notifications using the same system if needed. Data Sync The Data Sync tab in the Field Service App client is where JSON data is downloaded from the Field Service Server REST endpoint and loaded up into the local IBLite database. Data for the Appointments, Parts, and Technician is all downloaded on this tab. You can also request to Refresh the data at any time to get new updates from the server. Additionally, there is a background TTimer which will upload and sync the completed data from the Field Service App automatically on an interval. A cloud icon will appear in the upper left of the Field Service App when there is data to be synced in the queue. Architecture The architecture of the app is built in a low code rapid application development style using TTabControls for handling pages and individual frames for each page. TActionList is used to consolidate much of the code in the MainForm. There are two TTabControls on the MainForm. The first one contains the Login frame and the second TTabControl. The second TTabControl contains the rest of the frames. Within the ApptsFrame and the HistoryFrame there are additional Master/Detail TTabControls. If you want to make changes to the design time frames be sure to edit the frame itself and not the version of it that is embedded in the MainForm. This will keep your changes consolidated in one place. If your changes don't update in the MainForm you can delete the Frame from the MainForm and re-add it. Be sure to add it to the correct Tab and set to Align Client after you add the frame. The frames are built to be as modular as possible with TBindSourceDB components used as endpoints for the LiveBindings. This allows you to easily re-use the frames in your own projects by connecting the TBindSourceDBs to your own datasets. uDataModule in 'uDataModule.pas' {MainDM: TDataModule},Contains the RAD Server (EMS) Provider client components, the in memory table components, the IBLite tables, and the various FireDAC connecting components. uMainForm in 'uMainForm.pas' {MainForm},Contains the main form of the application with the various TTabControls and inline embedded TFrames. Additionally, it includes the TNotificationCenter. uLoginFrame in 'uLoginFrame.pas' {LoginFrame: TFrame},Contains the UI and code for the Login screen. uApptsFrame in 'uApptsFrame.pas' {ApptsFrame: TFrame},Contains the UI and code for the Appointments screen. uHistoryFrame in 'uHistoryFrame.pas' {HistoryFrame: TFrame},Contains the UI and code for the Service History screen. uPartsFrame in 'uPartsFrame.pas' {PartsFrame: TFrame},Contains the UI and code for the Parts screen. uProfileFrame in 'uProfileFrame.pas' {ProfileFrame: TFrame},Contains the UI and code for the Profile screen. uNotifyFrame in 'uNotifyFrame.pas' {NotifyFrame: TFrame},Contains the UI and code for the Notification screen. uProgressFrame in 'uProgressFrame.pas' {ProgressFrame: TFrame},Contains the activity progress TFrame which is displayed when the app is busy. uTenantsDM in 'uTenantsDM.pas' {TenantsDM: TDataModule},Contains the RAD Server (EMS) Provider connector components for accessing the Branch (Tenants) list. uTenantListForm in 'uTenantListForm.pas' {TenantForm},Contains the UI and code for selecting a Branch/Tenant. uQueueFrame in 'uQueueFrame.pas' {QueueFrame: TFrame},Contains the UI and code for syncing data from the server. uWebBrowserForm in 'uWebBrowserForm.pas' {WebBrowserForm};Contains the UI and code for viewing real time map data in a TWebBrowser. Offline Caching The Field Service App is able to work offline once you have logged into your account at least once. The next time you log into the app it will use your previous RAD Server Session ID for any new connections it tries to make to the server. The data from the server is cached as JSON files and stored in the IBLite database. The Appointments are saved as appts.json, the Parts as parts.json, the Techs as technicians.json, and the Tenants as tenants.json. If no connection to the server is available the data will be loaded from those files instead. Additionally, if there is no internet connection it will save the appointments and notes that you have marked completed in the History table of the IBLite database. When the next time an internet connection is detected it will upload those changes. The Field Service App has a local History table where is stores the local changed state of the Appointments. Even if you re-sync the data from the server and your changes have not been uploaded yet it will apply your existing local changes to this new data until which time it is able to upload the changes to the server. If you log out of the existing account the local database is deleted until you log in again. If you log out before uploading your changes then you changes would be lost. Notifications The local notification functionality built into the Field Service App relies on the cross platform TNotificationCenter component that is built into RAD Studio. There is a local IBLite Notify table in the Field Server App where it stores the current state of notifications (whether the user has viewed them already and whether they have been sent to the user’s platform). When a new Appointment is downloaded from the server during a data sync a new record is added to the IBLite Notify table. A notification is sent to the platform through the TNotificationCenter when this happens. The user can view the notification by clicking on the record on the Notify tab. Once a notification is viewed it will no longer be displayed on the Notify tab. Each platform handles notifications differently. You should be able to hook up remote notifications as well through this existing local notification system. Customize The UI You can quickly and easily customize most of the look and feel of the app with three easy changes. In TMainForm there is a BackgroundRect, a BackgroundImageRect, and a EmeraldDarkStyleBook control. You can change the background color of the app by changing the BackgroundRect.Fill.Gradient property. You can change the image that is overlayed over the entire app by changing the BackgroundImageRect.Fill.Bitmap.Bitmap property. The background image works by being above all of the other controls, having a low Opacity, having a HitTest of False and a Locked property of True. Finally, you can change most of the rest of the theme by loading different Premium Styles into the EmeraldDarkStyleBook control. You can customize the header logo of the Login screen on the LoginFrame. There are a few other places where the custom green color is used on some elements in the TListView controls and some the search icons using a TFillRGBEffect. The Profile screen for the technician has a background image in the ProfileFrame called HeaderBackgroundRect plus a BackgroundRect control. The Profile is also displayed in the TMultiView control on the MainForm with another control named HeaderBackgroundRect as well. Change the Fill.Bitmap.Bitmap property on both controls. You will need to update the BackgroundRect and BackgroundImageRect in the WebBrowserForm and the TenantForm as well. Remember that you will need to load one style for each of the four deployment platforms. You can access the Premium Styles here: https://www.embarcadero.com/products/rad-studio/fireui/premium-styles https://cc.embarcadero.com/item/30491 [YoutubeButton url='https://www.youtube.com/watch?v=GrHdj_4ACxg&list=PLwUPJvR9mZHiMb6KBD-zb6uRvi6BS0HKN&index=5'] Просмотр полной статьи
  7. Years ago I worked at a company that maintained a Point of Sale (POS) system written in Delphi. I wasn’t involved in that project (I was developing a medication management system for an assisted living facility), but talking with some of the developers that were working on it I learned that Delphi is very popular in many different vertical markets, specifically Point of Sale systems. So I’m not surprised to see MalyKangurek POS by SoftSystem as the cool app winner for June 2018. What makes MalyKangurek POS cool is that it is designed specifically around a children's playground with features designed for that specific business niche. It has all the standard POS features including the ability to work with hardware devices like barcode readers, cash drawers, and receipt printers. Additionally it is designed to work great on a touch screen with nice big buttons and on screen input. Originally it was created in Delphi 2009 with VCL components, and now it is transferred to the latest Delphi and the FireMonkey platform. It started out targeted the Windows desktop, but now that it is migrated to FireMonkey there are plans to make it available on Android in the future. Beyond FireMonkey it also makes use of FireDAC for database access, Devart SDAC, TMS Software Components, AlphaSkin, FastReport, EurekaLog, CPort. When I asked Osmański Przemysław of SoftSystem, the developer of MalyKangurek POS to tell me more about his use of Delphi he said the following: Delphi is a great environment for creating applications. I started to play with Delphi in the days of Delphi 2. Later Delphi became my work environment and all the applications I created were created in Delphi. For many years Delphi was the only real visual tool for creating applications. Its advantages are the speed of compilation and the ability to compile to different platforms. In addition, the Delphi community in Poland is very large and helpful to other programmers. In developing MałyKangurek I learned about external devices such as barcode readers, receipt printers, fiscal printers, time meters etc.The application was written for my wife and her business, but with time it has become an application used in many places. As users made suggestions Delphi made it very quick and easy to make changes and features. For a while I started developing some of my new software in Visual Studio. Then Delphi 10 (Seattle, Berlin and Tokyo) brought new quality when compared to earlier versions. Now I do not have to worry about changing development tools, and I can devote myself to the pleasure of writing a new cross-platform version of the application in an environment that i know well and like. Now all my software is developed with Delphi. There are so many new solutions for Delphi, such as UniGUI which allows for seamless development of web applications. I look forward to the future of development with Delphi that will allow me to continue to work with the pleasure that I’ve had so far. Watch MalyKangurek POS video in action here: [YoutubeButton url='https://www.youtube.com/watch?v=SWjekG5ECCc&t=12s'] Просмотр полной статьи
  8. Brovin Yaroslav

    THTTPClient авторизация

    http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Using_an_HTTP_Client#Handling_Authentication_and_Certificates
  9. Anyone who loves playing with deck of cards knows solitaire. And no matter how advanced the technology is, it will always be played. That is why I’m thrilled to see BVS Solitaire Collection by BVS Development as our May 2018 cool app winner. It is an award-winning multi-featured collection of solitaire card games that includes over 510 variations. It features both old-time favorites (like Spider Solitaire, FreeCell and Pyramid) and original variations not found elsewhere. You can modify rules of any game, thus easily creating your own unique variations. Attractive smoothly scalable playing cards, completely customizable game appearance and comprehensive set of statistics to measure your performance. Its Windows version gained popularity and was even featured in a movie "The Girl with the Dragon Tattoo" (2011). BVS Solitaire Collection is built with Delphi along with Firemonkey. It runs on iOS, MacOS and Windows. Boris of BVS Development Corporation shared his experience on Delphi, he said: "Delphi was chosen due to the flexibility of Object Pascal and both powerful and convenient development environment. I like the aesthetics of the Object Pascal code and its high readability. When I'm in an edit-compile- debug cycle I want it to be as fast as possible. Delphi compiler is extremely quick. That accelerates my development efforts and greatly improve my productivity. Besides, Object Pascal is much simpler and safer than C++ which further improves productivity and code maintainability. Embarcadero keeps adding new features continuously. Actually Delphi is one of the best IDEs on the market, that can be used to create cross platform applications." Watch BVS Solitaire Collections video in action here: Interested in submitting for the Embarcadero’s Cool App contest? It’s open to any business or consumer application built with RAD Studio, Delphi or C++Builder. Embarcadero awards Cool App contest winners a $500 Amazon gift card and winning submissions are also highlighted on the company’s YouTube channel. For more information on the contest and a link to the submission form, click here. Просмотр полной статьи
  10. Brovin Yaroslav

    FGActionSheet

    Why do you decide, that problem with it relates TfgActionSheet?
  11. Brovin Yaroslav

    FGActionSheet

    I have just checked this demo sample on Tokyo and it works fine for me. How do you use this component?
  12. Brovin Yaroslav

    FGActionSheet

    Hello, Does ActionSheetDemo working for you in Tokyo? Thank you
  13. There is an interesting post on Medium aiming to inspire students why to learn C++. Its main point is that learning C++ teaches fundamental computer science concepts: memory management, compile-time vs run-time, polymorphism implementation, iterators and containers, and more. Unfortunately, it phrases itself in an exclusionary manner. While C++ is not the only language where you can learn these fundamentals, it is one of the most popular. However, with dozens of coding "boot camps" popping up and charging thousands of dollars for the promise of a quick path to a software development career, why should you consider learning a complex language like C++? Here are three key reasons to learn and use C++ today: Technical Foundation It's Widely Used Support and Future Let’s look at these in order. Technical Foundation C++ is one of the most common languages used to teach strong foundational knowledge that is applicable to all other languages. There are many core concepts you can learn with C++: Memory management: Allocating and freeing; use of pointers, and very quickly why you should not manually manage memory Different memory management models: reference-counted in the form of shared_ptr; strict ownership in the form of unique_ptr Ownership and deterministic behaviour, illustrated by RAII (see C++ specifics) Polymorphism behaviours: this one is in fact illustrated by some odd behaviours of C++, such as that the type identity of an object changes throughout its construction - hint, what happens when you call a virtual method in a constructor? Fundamental containers and algorithms Optimizations: what causes fast or slow code? Functional programming: while not a pure functional language, functional style is a direction the language has been heading and is very powerful in C++ If you learn C++, you will have a solid background that will allow you to understand other languages’ designs and implementations. It’s Widely Used C++ is the most widely used language for software today, especially in areas requiring performance. The following applications are written totally or mostly in C++: Windows Explorer Photoshop Word Clang compiler Windows (key area, including the new wrappers for XAML and desktop in C++17) Amazon’s key services Large parts of Apple’s macOS Bloomberg’s financial software And many more. Why is it widely used? Because C++ is powerful, expressive, concise, and performant. When you need to write solid, fast, applications and need powerful concepts in your code, you use C++. Support and the Future Finally, one key item in learning a language is the direction it’s going in the future. C++ is an ISO standard, and is evolving rapidly. You can read an overview of the various standard versions here. It’s a language that is being kept up-to-date and extended as developers need it. That’s a language to rely on. Ready to Get Started learning or expanding your C++ knowledge? Start with our free tools and C++ Bootcamp replays. Просмотр полной статьи
  14. Спасибо. Приложение обязательно будет доступно на пощупать чуть позже, когда я завершу его. Более того, можно будет поставить себе с плей маркета это оригинальное приложение, написанное на FMX и сравнить его же, сделанного на FGX.
  15. Практически любое мобильное приложение сложно представить без стандартной навигации. В FMX меню обычно делается на базе TListBox. Однако, при всей гибкости данного компонента зачастую создать меню, которое будет следовать гайдлайнам ОС довольно сложная задача, поскольку она требует хороших навыков работы со стилями. Именно с этой целью разработан новый компонент TfgListMenu для FGX Native, который значительно упрощает создание меню навигации в вашем приложении. Компонент полностью построен с использованием концепций материал дизайна для андроида и следует всем его рекомендациям. Данный компонент использует заранее разработанные стили пунктов меню, которые позволяют быстро и гибко создать навигацию по примерам, изображенным ниже. Помимо этого компонент поддерживает несколько режимов выделения итемов. Начиная от работы без выделения и заканчивая множественным выделением элементов. На уровне каждого пункта меню в отдельности можно настроить реакцию пукнта меню на выделение и нажатие. Screenrecorder-2018-05-23-03-34-12-146.mp4
  16. Brovin Yaroslav

    Download FGX Nativo

    Hello, Currently FGX Native is under development. There are no possibility to download it yet.
  17. I was really excited to see BriskBard by Salvador Díaz Fau as the April 2018 winner of the Cool App Contest. BriskBard is a browser, and a whole lot more. All the other browsers out there are just browsers, while BriskBards is a web browser for Windows that includes an email client, a media player, a news aggregator, a contact manager, an FTP client, a usenet newsreader, an IRC client, and several web developer tools. Did I mention it is also free? Think of it as your one stop shop for all your internet related tools. BriskBard is built with Delphi 10.2 Tokyo along with Indy, Hunspell, OpenSSL, SQLite, and three HTML rendering engines. It includes both Blink (used by Chromium), Trident (used by Internet Explorer) and it’s own custom rendering engine. To take advantage of Blink/Chromium Salvador created the CEF4Delphi open source project which makes it easy for Delphi developers to use DCEF3 (made by Henri Gourvest). When talking to Salvador about his use of Delphi in BriskBard he said: Pascal was one of the first computer languages I learned as a kid and I was happy to see that Delphi was one of the IDEs used in my university. Delphi made my student life much easier because it uses a strongly typed language that allowed me to detect mistakes even before I built my programs. Many other features also helped me a lot, like the form designer, templates and automatic block completion but what I like most about Delphi is its speed. Simply put, Delphi is a Formula 1 car in the IDE race. It’s not unusual to find open source projects written in other languages that take several hours to build using a high end computer. The worst case I’ve seen is a project that takes more than 6 hours using an Intel I7 with more than 16Gb of RAM. I can’t imagine how much time it would take to build that project in my 10 year old computer. In contrast, I’ve seen large Delphi projects built in less than 2 minutes on my old computer. People often neglect this but in my opinion it’s one of the most important features in Delphi. Delphi 10.2 can also be used to create cross-platform applications and includes countless new features that makes it one of the best IDEs in the market. Delphi is easy to learn, can create applications quickly and anyone can start using it thanks to the 100% discount in Delphi Starter Edition. You can see a video overview of BriskBard on YouTube: [YoutubeButton url='https://www.youtube.com/watch?v=KPwvaMlJE3A’] Interested in submitting for the Embarcadero’s Cool App contest? It’s open to any business or consumer application built with RAD Studio, Delphi or C++Builder. Embarcadero awards Cool App contest winners a $500 Amazon gift card and winning submissions are also highlighted on the company’s YouTube channel. For more information on the contest and a link to the submission form, click here. Просмотр полной статьи
  18. Тема: FGX Native. Новейшая кроссплатформенная платформа для мобильной разработки на Delphi Дата и время: 27 марта 2018 года в 12:00 Участники: @Brovin Yaroslav, Андрей Совцов Регистрация: ссылка Ссылка на официальный телеграмм канал: https://t.me/fgx_native Участие бесплатное На вебинаре познакомимся с текущей разработкой новой кроссплатформенной платформы, позволяющей создавать нативные приложения с быстрым откликом, плавной анимацией, продвинутой системой выраванивания, поддержкой RTL языков, оптимизированной работой с изображениями, быстрой канвой и многим другим. RAD Studio, Android/iOS В вебинаре принимает участие автор разработки Ярослав Бровин
  19. TfgImage - компонент отображения изображений: Реализован режим отображения 9-patch изображений для дизайнера и Android. Этот режим полезен для формирования тени разного размера на базе одного растрового изображений. На первом скриншоте отображена загрузка единственного изображений тени размером 60x60. Для компонента TfgImage указаны отступы со всех четырех сторон CapInsets, задающие правила растягивания изображений. Эти отступы делят изображение на 9 виртуальных областей. В итоге на втором скриншоте получаем три варианта отображения тени любых размеров.
  20. Будут свои мысли, что вы хотите, пишите. Функционал, компоненты. Предложения.
  21. Brovin Yaroslav

    Обрезается размер у Form

    В токио 10.2.3 была пофикшена проблема с неверным вычислением скейла при использовании системного увеличения приложений.
  22. Brovin Yaroslav

    Собственный TListBoxItem на C++

    При применении стиль всегда растягивается по размеру контрола, а не наоборот. Если вы хотите, чтобы у вас всегда был фиксированный размер, то в стиле используйте FixedWidth, FixedHeight. Если вы не хотите фиксировать размер итема, а лишь задать дефолтный размер, то переопределите в классе итема метод GetDefaultSize, в котором верните желаемый размер.
  23. Если я правильно понял, то у меня есть такой режим и он называется Aspect Fill. Вписывание изображения с сохранением пропорций таким образом, чтобы изображение полностью заполняло контрол. Речь об этом?
  24. Физически, при старте приложения с дебагом, среда посылает на ваше устройство интент на запуск приложения. В интенте передается порт для отладчика, по которому среда будет взаимодействовать с дебаггером. Система, получив интент: Стартует приложение Приложение при старте получает порт и пытается поднять gdb сервис отладки на указанном порту. Соответственно, если порт уже занят, то вы получите эту ошибку. Он может быть занят в результате предыдущей отладки делфи приложения, которое не было завершено, что заставляет Андроид удерживать нужный среде порт. Помогает обычно: Полный ребут девайса, который гарантирует, что никакой ваш процесс у вас не повис. Удаление из процессов винды android_gdb. Который так же может удерживать нужный вам порт.