CN111008009A - Service componentization method and system based on Flutter - Google Patents
Service componentization method and system based on Flutter Download PDFInfo
- Publication number
- CN111008009A CN111008009A CN201911072354.6A CN201911072354A CN111008009A CN 111008009 A CN111008009 A CN 111008009A CN 201911072354 A CN201911072354 A CN 201911072354A CN 111008009 A CN111008009 A CN 111008009A
- Authority
- CN
- China
- Prior art keywords
- flutter
- project
- engineering
- business
- dependence
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of mobile terminal development, and provides a service componentization method based on Flutter, which comprises the following steps: creating a flutter main project and a flutter business project; the flutter main project is of a flutter application project type, and the flutter business project is of a flutter package project type; increasing the dependence of the flutter main project on the flutter business project; compiling the flute main project after increasing the dependence to obtain a flute product; accessing the flutter product to the existing primary engineering; the native engineering comprises Android system engineering or iOS system engineering. The technical scheme provided by the invention can realize the decoupling between the Flutter functional module and the primary engineering and the decoupling between the service modules in the Flutter functional module, thereby improving the development efficiency of the mobile terminal.
Description
Technical Field
The invention relates to the technical field of mobile terminal development, in particular to a Flutter-based service componentization method and a Flutter-based service componentization system.
Background
Flutter is a mobile UI (User Interface) framework published by google, is an SDK (Software Development Kit) for constructing a cross-platform mobile phone app, and can quickly construct a high-quality User Interface on Android and iOS systems. Flutter is currently completely free, open source.
At present, most developers extend the Flutter function in the existing native Android/iOS to design the user interface and the service componentization, but do not completely Flutter the existing mobile terminal app. That is, most of the current service componentization schemes based on Flutter are hybrid development modes of native engineering and Flutter engineering.
The hybrid development mode is realized by introducing a Flutter function into the existing Android/iOS development, and mainly introducing a Flutter function module in a sub-module mode by taking the original Android/iOS system engineering as a main engineering, so that the existing original engineering has the Flutter function, and various services of the original engineering can be subjected to componentized development and design based on the Flutter.
Fig. 1 is a diagram of a conventional system architecture for introducing a Flutter function module into native engineering. In the prior art, due to the adoption of a source code integration mode, the coupling degree of the native engineering and the Flutter functional module is higher, and all project developers need to install a Flutter environment, so that the native developers who do not develop the Flutter function are greatly influenced. And in the inside of the Flutter functional module, all the service codes are also coupled together, so that the development mode that the current service engineering needs to be separated from each other cannot be met. The above disadvantages all result in low development efficiency of the existing service componentization scheme based on Flutter.
Disclosure of Invention
In view of this, the present invention aims to provide a service componentization method and system based on Flutter, which can achieve decoupling between the Flutter function module and the native engineering, and decoupling between each service module inside the Flutter function module, thereby improving development efficiency of the mobile terminal.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a service componentization method based on Flutter comprises the following steps: creating a flutter main project and a flutter business project; the flutter main project is of a flutter application project type, and the flutter business project is of a flutter package project type; increasing the dependence of the flutter main project on the flutter business project; compiling the flute main project after increasing the dependence to obtain a flute product; accessing the flutter product to the existing primary engineering; the native engineering comprises Android system engineering or iOS system engineering.
Preferably, the dependency on the flutter business project is added in the configuration file yaml of the flutter main project.
Further, before compiling and adding the dependent flutter main project, the method further includes: creating a flutter basic component project; the flutter base component engineering is a flutter plug engineering type or a flutter package engineering type; and increasing the dependence of the flutter main project on the flutter basic component project.
Preferably, the dependency on the flutter base component project is added in the configuration file yaml of the flutter master project.
Preferably, the dependence of the flutter main project on the flutter business project and the dependence of the flutter main project on the flutter basic component project are pub dependence.
Further, when the native engineering is the Android system engineering, accessing the flutter product to the existing native engineering includes: adding a compiling mode which is the same as that of an engine of the flutter main project in the Android system project; and adding the dependence on the flutter product in the configuration file of the Android system project.
Further, when the native engineering is iOS system engineering, accessing the flutter product to the existing native engineering includes: acquiring and storing the flutter product in the iOS system engineering; and adding the dependence on the flutter product in the management file pod of the iOS system engineering.
Another objective of the present invention is to provide a service componentization system based on Flutter, which can achieve decoupling between the Flutter functional module and the native engineering, and decoupling between the service modules inside the Flutter functional module, thereby improving the development efficiency of the mobile terminal.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a Flutter-based business componentization system, the system comprising:
the creating module is used for creating a flutter main project and a flutter business project; the flutter main project is of a flutter application project type, and the flutter business project is of a flutter package project type;
the Flutter dependence adding module is used for adding dependence of the Flutter main project on the Flutter business project;
the compiling module is used for compiling the flute main project after the dependence is added to obtain a flute product;
the access module is used for accessing the flutter product to the existing primary engineering; the native engineering comprises Android system engineering or iOS system engineering.
Further, the creating module is also used for creating a flutter basic component project; the flutter base component engineering is a flutter plug engineering type or a flutter package engineering type; the Flutter dependence adding module is also used for increasing the dependence of the Flutter main project on the Flutter basic component project.
Further, when the native engineering is an Android system engineering, the access module includes:
the compiling mode adding module is used for adding a compiling mode which is the same as that of an engine of the flutter main project in the Android system project;
and the Android maven dependence adding module is used for adding dependence on the flutter product in a configuration file gradle of the Android system engineering.
Further, when the native engineering is iOS system engineering, accessing the flutter product to the existing native engineering includes: acquiring and storing the flutter product in the iOS system engineering; the access module comprises: and the iOSpod dependence adding module is used for adding dependence on the flutter product in the management file pod of the iOS system engineering.
The invention also provides a computer storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the service modularization method based on the Flutter is realized.
The invention also provides terminal equipment which comprises a processor, wherein the processor is used for executing the service componentization method based on the Flutter.
The invention relates to a Flutter-based service componentization method and a Flutter-based service componentization system, which create a Flutter main project of a Flutter application project type and a Flutter service project of a Flutter package project type, compile the Flutter main project to obtain a Flutter product after increasing the dependence on the Flutter service project in the Flutter main project, and directly access the Flutter product into the existing primary project. Due to the adoption of a product integration mode, the Flutter functional module and the native engineering are not coupled, namely the decoupling between the Flutter functional module and the native engineering is realized. And because the Flutter business engineering of the Flutter package engineering type is independently created, each Flutter business engineering can be independently executed, namely the decoupling among all the business modules in the Flutter functional module is realized. The decoupling between the Flutter functional module and the native engineering and the decoupling between the service modules in the Flutter functional module ensure that a native developer not developing the Flutter function is not influenced by the Flutter function and does not sense the existence of the Flutter function; different service developers can conveniently access the flutter function and can independently develop services in respective flutter service projects, and therefore development efficiency of the mobile terminal is greatly improved.
Additional features and advantages of the invention will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an embodiment of the invention and, together with the description, serve to explain the invention and not to limit the invention.
In the drawings:
fig. 1 is a diagram of a conventional system architecture for introducing a Flutter function module in native engineering;
FIG. 2 is a first flowchart of a method according to an embodiment of the present invention;
FIG. 3 is a flowchart of a second method of an embodiment of the present invention;
FIG. 4 is a first block diagram of a system according to an embodiment of the present invention;
FIG. 5 is a second block diagram of the system according to the embodiment of the present invention;
FIG. 6 is a third block diagram of the system according to the embodiment of the present invention;
fig. 7 is an overall system architecture diagram of an embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating embodiments of the invention, are given by way of illustration and explanation only, not limitation.
Fig. 2 is a flowchart of a Flutter-based service componentization method according to an embodiment of the present invention, where the method includes:
step S101, creating a flutter main project and a flutter business project; the flutter main project is of a flutter application project type, and the flutter business project is of a flutter package project type;
the flutter function module itself generally has 4 engineering types, which are respectively a flutter application engineering type, a flutter plug engineering type, a flutter package engineering type and a flutter module engineering type.
The flutter application project type is a standard application type of flutter and is a project type including a complete running flow of the flutter, and the flutter main project created in the embodiment adopts the project type.
The flutter plugin engineering type is a plug-in type of flutter, and mainly functions to package native functions for the flutter to use, for example, when we need to use a log plug-in the flutter environment, the simplest method is to package the log plug-in functions in the native engineering for the flutter to use. Many of our base components use this type to encapsulate many of the engineering components already in the native engineering for use by the flutter layer.
The default of the flutter package engineering type is a base library of a flutter level, the flutter business engineering created in the embodiment uses the engineering type, and the advantage of selecting the type as the business component is that the flutter business only focuses on the flutter code and does not need to focus on any platform-related functions, because the platform-related functions are provided by the flutter plug-in type plug-ins provided by us, and business developers can concentrate more on specific business logic.
The flutter module engineering type is an engineering type used by google officers and introducing flutter functions into native engineering as child modules of the native engineering, and the engineering type is not used in the invention due to the strong coupling of the flutter modules and the native engineering.
In this embodiment, a command "flutter create-template" may be used to create a flutter main project of the flutter application project type, and a native App (native project) may only create a flutter main project. Meanwhile, pub warehouses are added inside and outside the flutter main project, so that dependence of the flutter main project on the flutter business project in subsequent steps is facilitated.
The command of 'flutter create-template' is used to create a flutter business project of the flutter package project type, and multiple business parties need to create their own flutter business projects respectively.
In this embodiment, if the general component function needs to be used in the flutter main project, a flutter base component project needs to be created, where the flutter base component project is a flutter plug project type or a flutter package project type. If general component functionality is not required, this step may be skipped. Specifically, if the existing functions in the native project need to be used, the functions of the native app are encapsulated by a "flutter create-template-plugin-component project name" command to create corresponding plugin components; if it is necessary to use the functions provided in the universal base library of the flutter layer, the universal base library of the flutter layer is created by a "flutter create-template-component engineering name" command.
Step S102, increasing the dependence of the flutter main project on the flutter business project;
in step S101, we create the required project, and in this step, we need to integrate the created projects together, and this integration is mainly implemented by the version dependent tool pub of flutter.
Specifically, the dependency on the created flutter business project is added in the profile yaml of the created flutter master project. The yaml configuration file is similar to a gradle configuration file in an android system or a pod configuration file in an iOS system, and the yaml configuration file exists in a pubspec.yaml file form and is located under a root directory of a flutter item. If the flutter base component project is created in step S101, as shown in fig. 3, in this step, the dependency of the flutter main project on the flutter base component project needs to be added, specifically, the dependency on the flutter base component project is added in the configuration file yaml of the flutter main project. Meanwhile, the versions of the basic components are uniformly managed through the dependency _ overrides file in the version dependent tool pub. In this embodiment, the dependence of the flutter main project on the flutter business project and the dependence of the flutter main project on the flutter basic component project are pub dependence.
The increasing of the dependence of the flutter main project on the flutter business project in this embodiment is to make the flutter main project depend on the flutter business project, that is, the flutter business project can be referred to in the flutter main project. In the compiling process, the flutter business project is compiled before the flutter main project. Similarly, the dependence of the flutter main project on the flutter basic component project is increased, namely the flutter main project is dependent on the flutter basic component project, namely the flutter basic component project can be referred in the flutter main project. During compilation, the flutter base component project is compiled before the flutter master project.
Step S103, compiling the flute main project after the dependence is added to obtain a flute product;
flutter uses Dart as a development language, and the compiling mode of Flutter is related to Dart, but due to the ecological difference between Android and iOS, Flutter derives different compiling modes, and the compiling modes of Flutter are different at different development stages. For example, when developing flutter APP, we need to use hot reload to facilitate quick user interface molding, and also need higher performance to perform view rendering, so flutter uses a KernelSnapshot compiling mode in the debugging process and generates a corresponding flutter product. During the production phase, flutter uses the AOT compilation mode since applications require very fast speed. The embodiment mainly relates to compiling of flutter in the development process.
Step S104, accessing the flutter product to the existing primary engineering; the native engineering comprises Android system engineering or iOS system engineering.
When the native engineering is the Android system engineering, generating a flutter product through a flutter build apk command, and accessing the flutter product to the native engineering comprises the following steps:
(1) adding a compiling mode which is the same as that of an engine of the flutter main project in the Android system project. In this embodiment, since the compiling mode of the engine of the flutter main project is java8, first, java8 compiling mode support needs to be added in the Android system project.
(2) And increasing the dependence on the flutter product in the configuration file of the Android system engineering. Specifically, the dependency is a maven dependency to facilitate our pull and integration of the flutter function.
When the native engineering is the iOS system engineering, generating a flute product through a flute built iOS command, and accessing the flute product to the native engineering comprises the following steps:
(1) acquiring and storing the flutter product in the iOS system engineering;
specifically, a downloading task is executed in a management file pod of the iOS system project, the generated flutter product compression packet is downloaded, and the compression packet is decompressed to the current project directory.
(2) The dependence on the flutter product is increased in the management file pod of the iOS system engineering.
Specifically, traversing the decompressed flutter products, and performing dependency association on the decompressed flutter products in the pod respectively, thereby integrating the flutter functions into the iOS system engineering.
As shown in fig. 7, the Flutter portal project is a Flutter master project, and 3 business projects are created in the Flutter space, which are a second-hand package, a new-room package, and a lease package, respectively. Compiling the flutter project to obtain a flutter product, and introducing the flutter product into the native project in a dependence mode, so that flutter implementation of business logic such as second-hand service, new-house service, lease service and the like contained in the flutter product is integrated into the native project. The flutter base library corresponds to the native base library.
In the embodiment, service modularization can be basically realized through the steps, and each service can be independently developed in the respective flute project; meanwhile, the flute code and the native Android/iOS are decoupled, and the native developer is basically unaffected.
Corresponding to the above embodiment, the present invention further provides a service componentization system based on Flutter, as shown in fig. 4, the system includes:
a creating module 201, configured to create a flutter main project and a flutter business project; wherein, the flutter main project is a flutter application project type, and the flutter business project is a flutter package project type;
a Flutter dependency adding module 202, configured to add dependency of the Flutter main project on the Flutter business project; preferably, the dependency on the flutter business project is added in the configuration file yaml of the flutter main project;
the compiling module 203 is used for compiling the flute main project after the dependence is added to obtain a flute product;
an access module 204, configured to access the flutter product to an existing native project; the native engineering comprises Android system engineering or iOS system engineering.
Further, when the general component function needs to be used in the flutter main project, the creating module 201 is further configured to create a flutter base component project, where the flutter base component project is a flutter plug project type or a flutter package project type. The Flutter dependency adding module 202 is further configured to increase dependency of the Flutter main project on the Flutter base component project; preferably, the dependency on the flutter base component project is added in the configuration file yaml of the flutter master project.
Further, as shown in fig. 5, when the native engineering is the Android system engineering, the access module 204 includes:
a compiling mode adding module 2041, configured to add, in the Android system project, a compiling mode that is the same as a compiling mode of an engine of the flutter main project;
the Android maven dependency adding module 2042 is configured to add a dependency on the flutter product in the configuration file gradle of the Android system project.
Further, as shown in fig. 6, when the native engineering is iOS system engineering, accessing the flutter product to the existing native engineering includes: the iOS system engineering acquires and stores a flutter product; the access module 204 includes:
an iOS pod dependency adding module 2043, configured to add a dependency on the flutter product in the management file pod of the iOS system engineering.
The specific implementation of the working principle, the workflow, and the like of the system can be referred to the specific implementation of the Flutter-based business componentization method provided by the present invention, and the same technical contents will not be described in detail herein.
The present invention also provides a computer storage medium, on which a computer program is stored, which, when executed by a processor, implements the Flutter-based business componentization method according to the present embodiment.
The invention also provides a terminal device, which comprises a processor, wherein the processor is used for executing the service componentization method based on the Flutter according to the embodiment of the invention.
The invention relates to a service componentization method and a system based on a fluter, which create a fluter main project of a fluter application project type and a fluter service project of a fluter package project type, compile the fluter main project to obtain a fluter product after increasing the dependence on the fluter service project in the fluter main project, and directly access the fluter product into a primary project. Due to the adoption of a product integration mode, the Flutter functional module and the native engineering are not coupled, namely the decoupling between the Flutter functional module and the native engineering is realized. And because the Flutter service engineering of the Flutter package engineering type is independently created, each Flutter service engineering can be independently executed, namely, the decoupling among all service modules in the Flutter functional module is realized. The decoupling between the Flutter functional module and the native engineering and the decoupling between the service modules in the Flutter functional module ensure that a native developer not developing the Flutter function is not influenced by the Flutter function and does not sense the existence of the Flutter function; different service developers can conveniently access the flutter function and can independently develop services in respective flutter service projects, and therefore development efficiency of the mobile terminal is greatly improved.
Although the embodiments of the present invention have been described in detail with reference to the accompanying drawings, the embodiments of the present invention are not limited to the details of the above embodiments, and various simple modifications can be made to the technical solutions of the embodiments of the present invention within the technical idea of the embodiments of the present invention, and the simple modifications all belong to the protection scope of the embodiments of the present invention.
It should be noted that the various features described in the above embodiments may be combined in any suitable manner without departing from the scope of the invention. In order to avoid unnecessary repetition, the embodiments of the present invention do not describe every possible combination.
Those skilled in the art will understand that all or part of the steps in the method according to the above embodiments may be implemented by a program, which is stored in a storage medium and includes several instructions to enable a single chip, a chip, or a processor (processor) to execute all or part of the steps in the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
In addition, any combination of various different implementation manners of the embodiments of the present invention is also possible, and the embodiments of the present invention should be considered as disclosed in the embodiments of the present invention as long as the combination does not depart from the spirit of the embodiments of the present invention.
Claims (10)
1. A service componentization method based on Flutter is characterized by comprising the following steps:
creating a flutter main project and a flutter business project; the flutter main project is of a flutter application project type, and the flutter business project is of a flutter package project type;
increasing the dependence of the flutter main project on the flutter business project;
compiling the flute main project after increasing the dependence to obtain a flute product;
accessing the flutter product to the existing primary engineering; the native engineering comprises Android system engineering or iOS system engineering.
2. The Flutter-based business componentization method according to claim 1, wherein the increasing the dependency of the Flutter master project on the Flutter business project comprises:
and adding the dependence on the flutter business project in the configuration file yaml of the flutter main project.
3. The Flutter-based business componentization method according to claim 1, wherein before the compiling adds the depended Flutter master project, the method further comprises:
creating a flutter basic component project; the flutter base component engineering is a flutter plug engineering type or a flutter package engineering type;
and increasing the dependence of the flutter main project on the flutter basic component project.
4. The Flutter-based business componentization method according to claim 3, wherein the increasing the dependency of the Flutter master project on the Flutter base component project comprises:
adding the dependency on the flutter base component project in the configuration file yaml of the flutter master project.
5. The Flutter-based business componentization method according to claim 3, wherein the dependence of the Flutter master project on the Flutter business project and the dependence of the Flutter master project on the Flutter base component project are pub dependencies.
6. The Flutter-based business componentization method according to claim 1 or 3, wherein when the native engineering is Android system engineering, accessing the Flutter product to an existing native engineering comprises:
adding a compiling mode which is the same as that of an engine of the flutter main project in the Android system project;
and adding the dependence on the flutter product in the configuration file of the Android system project.
7. The Flutter-based business componentization method according to claim 1 or 3, wherein when the native engineering is iOS system engineering, accessing the Flutter product into an existing native engineering comprises:
acquiring and storing the flutter product in the iOS system engineering;
and adding the dependence on the flutter product in the management file pod of the iOS system engineering.
8. A Flutter-based business componentization system, the system comprising:
the creating module is used for creating a flutter main project and a flutter business project; the flutter main project is of a flutter application project type, and the flutter business project is of a flutter package project type;
the Flutter dependence adding module is used for adding dependence of the Flutter main project on the Flutter business project;
the compiling module is used for compiling the flute main project after the dependence is added to obtain a flute product;
the access module is used for accessing the flutter product to the existing primary engineering; the native engineering comprises Android system engineering or iOS system engineering.
9. A computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the Flutter-based business componentization method of any of claims 1 to 7.
10. A terminal device, characterized in that it comprises a processor for executing the Flutter-based service componentization method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911072354.6A CN111008009B (en) | 2019-11-05 | 2019-11-05 | Service componentization method and system based on Flutter |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911072354.6A CN111008009B (en) | 2019-11-05 | 2019-11-05 | Service componentization method and system based on Flutter |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008009A true CN111008009A (en) | 2020-04-14 |
| CN111008009B CN111008009B (en) | 2023-02-24 |
Family
ID=70110954
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911072354.6A Active CN111008009B (en) | 2019-11-05 | 2019-11-05 | Service componentization method and system based on Flutter |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008009B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111694564A (en) * | 2020-06-05 | 2020-09-22 | 百度在线网络技术（北京）有限公司 | Compiling method, device, equipment and medium for Flutter mixed mode |
| CN111796817A (en) * | 2020-07-22 | 2020-10-20 | 睿智合创(北京)科技有限公司 | High-cohesion low-coupling processing method and system for iOS and electronic equipment |
| CN112416468A (en) * | 2020-12-11 | 2021-02-26 | 四川长虹电器股份有限公司 | Flutter privatization plug-in management system and method and computer storage medium |
| CN112559928A (en) * | 2020-12-24 | 2021-03-26 | 成都新希望金融信息有限公司 | Page processing method and device based on hybrid development, electronic equipment and storage medium |
| CN112631600A (en) * | 2020-12-24 | 2021-04-09 | 上海哔哩哔哩科技有限公司 | Software construction method and system based on Flutter |
| CN112966278A (en) * | 2021-02-04 | 2021-06-15 | 北京高因科技有限公司 | Method for Flutter to safely access SQLite in environment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060253441A1 (en) * | 2005-05-06 | 2006-11-09 | Nelson John M | Database and index organization for enhanced document retrieval |
| US20180089337A1 (en) * | 2016-09-23 | 2018-03-29 | Prashanth Uppunda | Creating an engineering project in an industrial automation environment |
| CN107908403A (en) * | 2017-11-10 | 2018-04-13 | 北京搜狐新动力信息技术有限公司 | A kind of collocation method and system of the modularization of mobile terminal business module |
| WO2019072110A1 (en) * | 2017-10-11 | 2019-04-18 | 阿里巴巴集团控股有限公司 | Method for generating application program, apparatus, system, device, and medium |
| CN109947426A (en) * | 2019-03-12 | 2019-06-28 | 天津字节跳动科技有限公司 | Generation method, device and the electronic equipment of application program |
| CN110083360A (en) * | 2019-04-26 | 2019-08-02 | 深圳乐信软件技术有限公司 | A kind of Compilation Method of application code, device, equipment and storage medium |
| CN110286927A (en) * | 2019-06-24 | 2019-09-27 | 北京字节跳动网络技术有限公司 | Hot update method, device and the equipment of Flutter application |
| CN110399119A (en) * | 2019-06-18 | 2019-11-01 | 五八有限公司 | A kind of modularization construction method, device, electronic equipment and storage medium |
-
2019
- 2019-11-05 CN CN201911072354.6A patent/CN111008009B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060253441A1 (en) * | 2005-05-06 | 2006-11-09 | Nelson John M | Database and index organization for enhanced document retrieval |
| US20180089337A1 (en) * | 2016-09-23 | 2018-03-29 | Prashanth Uppunda | Creating an engineering project in an industrial automation environment |
| WO2019072110A1 (en) * | 2017-10-11 | 2019-04-18 | 阿里巴巴集团控股有限公司 | Method for generating application program, apparatus, system, device, and medium |
| CN107908403A (en) * | 2017-11-10 | 2018-04-13 | 北京搜狐新动力信息技术有限公司 | A kind of collocation method and system of the modularization of mobile terminal business module |
| CN109947426A (en) * | 2019-03-12 | 2019-06-28 | 天津字节跳动科技有限公司 | Generation method, device and the electronic equipment of application program |
| CN110083360A (en) * | 2019-04-26 | 2019-08-02 | 深圳乐信软件技术有限公司 | A kind of Compilation Method of application code, device, equipment and storage medium |
| CN110399119A (en) * | 2019-06-18 | 2019-11-01 | 五八有限公司 | A kind of modularization construction method, device, electronic equipment and storage medium |
| CN110286927A (en) * | 2019-06-24 | 2019-09-27 | 北京字节跳动网络技术有限公司 | Hot update method, device and the equipment of Flutter application |
Non-Patent Citations (1)
| Title |
|---|
| 周勇，程子清: "Flutter的原理深度剖析", 《电脑编程技巧与维护》 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111694564A (en) * | 2020-06-05 | 2020-09-22 | 百度在线网络技术（北京）有限公司 | Compiling method, device, equipment and medium for Flutter mixed mode |
| CN111694564B (en) * | 2020-06-05 | 2023-08-04 | 百度在线网络技术（北京）有限公司 | Method, device, equipment and medium for compiling Flutter mixed mode |
| CN111796817A (en) * | 2020-07-22 | 2020-10-20 | 睿智合创(北京)科技有限公司 | High-cohesion low-coupling processing method and system for iOS and electronic equipment |
| CN112416468A (en) * | 2020-12-11 | 2021-02-26 | 四川长虹电器股份有限公司 | Flutter privatization plug-in management system and method and computer storage medium |
| CN112559928A (en) * | 2020-12-24 | 2021-03-26 | 成都新希望金融信息有限公司 | Page processing method and device based on hybrid development, electronic equipment and storage medium |
| CN112631600A (en) * | 2020-12-24 | 2021-04-09 | 上海哔哩哔哩科技有限公司 | Software construction method and system based on Flutter |
| CN112559928B (en) * | 2020-12-24 | 2023-09-26 | 成都新希望金融信息有限公司 | Page processing method and device based on hybrid development, electronic equipment and storage medium |
| CN112966278A (en) * | 2021-02-04 | 2021-06-15 | 北京高因科技有限公司 | Method for Flutter to safely access SQLite in environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008009B (en) | 2023-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111008009B (en) | Service componentization method and system based on Flutter | |
| CN106605212B (en) | Modular common version management in dynamically linked runtime environments | |
| CN111008007B (en) | Component development method, system, storage medium and processor | |
| CN102053836B (en) | Implementation method of version management tool for Android application development | |
| WO2017185606A1 (en) | Overlay mechanism-based apk development method and system | |
| US20130159981A1 (en) | Extension mechanism for scripting language compiler | |
| CN110321131B (en) | Service component packaging method, system and server | |
| TWI528288B (en) | Method for transforming application codes in cross-platform and apparatus thereof | |
| CN102402427A (en) | Method and device for updating Java application program | |
| CN106569880B (en) | Method and system for dynamically sharing resources between Android applications | |
| CN105573734A (en) | Method and device for providing SDK file | |
| CN111443939A (en) | Configuration method and device of software development kit and storage medium | |
| EP3866443A1 (en) | Opc ua server, system operating using opc ua, and method of executing opc ua system | |
| CN105094878A (en) | System library file integration method and apparatus | |
| CN111966357A (en) | Operating system application compiling method and device and electronic equipment | |
| US20130185626A1 (en) | METHOD, TERMINAL AND COMPUTER-READABLE RECORDING MEDIUM FOR COMPILING JAVASCRIPT INCLUDED IN WEB APPLICATION USING Ahead-Of-Time (AOT) | |
| CN110457013B (en) | Program component configuration device and method | |
| CN112416612B (en) | Service calling method and device, computer equipment and readable storage medium | |
| CN110941443B (en) | Method and device for modifying file name in SDK (software development kit) and electronic equipment | |
| CN111596970A (en) | Dynamic library delay loading method, device, equipment and storage medium | |
| CN111552480A (en) | Cross-platform compiling method, device, equipment and readable storage medium | |
| CN113641389B (en) | Software upgrading method, device and equipment based on OpenCPU | |
| KR101308404B1 (en) | A method for generating a resource file package available in different platform and a method for using a resource in a different platform | |
| CN114201174A (en) | Construction method and device of hybrid mobile application, electronic equipment and storage medium | |
| CN110377367B (en) | Component configuration method and device, electronic terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |