CN110083354B - Graphical interface file generation method and device - Google Patents
Graphical interface file generation method and device Download PDFInfo
- Publication number
- CN110083354B CN110083354B CN201910343525.8A CN201910343525A CN110083354B CN 110083354 B CN110083354 B CN 110083354B CN 201910343525 A CN201910343525 A CN 201910343525A CN 110083354 B CN110083354 B CN 110083354B
- Authority
- CN
- China
- Prior art keywords
- primitive
- script
- content
- product software
- graphic
- 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.)
- Active
Links
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
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2107—File encryption
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application provides a method and a device for generating a graphical interface file, wherein the method comprises the following steps: in different product software, aiming at target graphic primitives, respectively adopting the same graphic primitive description specifications to generate graphic primitive contents, and respectively adopting the same script description specifications to generate script contents associated with the graphic primitive contents; and respectively storing the primitive content and the script content generated in different product software to obtain the graphical interface file. In the application, the graphical interface which can mutually identify each other between different product software can be realized in the above mode.
Description
Technical Field
The present disclosure relates to the field of automation technologies, and in particular, to a method and an apparatus for generating a graphical interface file.
Background
The industrial product software generally has the processing function of an industrial automation graphical interface, such as drawing, storing and displaying the graphical interface.
There may be a need for mutually identifying graphical interfaces of each other between different product software, but how to implement mutually identifying graphical interfaces of each other between different product software becomes a problem.
Disclosure of Invention
In order to solve the above technical problems, embodiments of the present application provide a method and an apparatus for generating a graphical interface file, so as to achieve the purpose of implementing a graphical interface that can mutually identify each other between different product software, where the technical scheme is as follows:
a graphical interface file generation method, comprising:
in different product software, aiming at target graphic primitives, respectively adopting the same graphic primitive description specifications to generate graphic primitive contents, and respectively adopting the same script description specifications to generate script contents related to the graphic primitive contents;
and respectively storing the primitive content and the script content generated in different product software to obtain the graphical interface file.
Preferably, the storing, respectively, the primitive content and the script content generated in different product software to obtain the graphical interface file includes:
respectively acquiring a primitive content encryption algorithm and a script content encryption algorithm from different product software;
encrypting the primitive content generated in the corresponding product software by using primitive content encryption algorithms acquired from different product software respectively to obtain encrypted primitive content;
encrypting script contents generated in corresponding product software by using script content encryption algorithms obtained from different product software respectively to obtain encrypted script contents;
generating digital signatures based on the graphic element contents and script contents generated in different product software respectively, and writing the graphic element content encryption algorithm, the script content encryption algorithm and the digital signatures into the graphic interface file information in the corresponding product software respectively, wherein the graphic interface file information in different product software is generated by adopting the same graphic interface file information description specification;
and respectively storing the encrypted primitive content, the encrypted script content and the graphic interface file information containing primitive content encryption algorithm, script content encryption algorithm and digital signature in different product software to obtain the graphic interface file.
Preferably, the same graphic primitive description specification is the same graphic primitive description specification written in JSON language;
the same script description specification is the same script description specification written in BSON language.
Preferably, the same graphic primitive description specification is the same graphic primitive description specification written by using a BSON language;
the same script description specification is the same script description specification written in BSON language.
Preferably, the storing, respectively, the primitive content and the script content generated in different product software to obtain the graphical interface file includes:
generating primitive contents in BSON format based on the primitive contents generated in different product software respectively;
and respectively storing the primitive content and the script content based on the BSON formats generated in different product software to obtain the graphical interface file.
A graphical interface file generation device, comprising:
the generation module is used for respectively adopting the same graphic primitive description specification to generate primitive contents aiming at target primitives in different product software, and respectively adopting the same script description specification to generate script contents related to the primitive contents;
and the storage module is used for respectively storing the primitive content and the script content generated in different product software to obtain the graphical interface file.
Preferably, the storage module includes:
the acquisition sub-module is used for respectively acquiring a primitive content encryption algorithm and a script content encryption algorithm from different product software;
the first encryption sub-module is used for encrypting the primitive content generated in the corresponding product software by using primitive content encryption algorithms acquired from different product software respectively to obtain encrypted primitive content;
the second encryption sub-module is used for encrypting the script content generated in the corresponding product software by utilizing the script content encryption algorithm acquired from different product software respectively to obtain encrypted script content;
the first generation sub-module is used for generating digital signatures based on the primitive content and the script content generated in different product software respectively, writing the primitive content encryption algorithm, the script content encryption algorithm and the digital signatures into the graphical interface file information in the corresponding product software respectively, and generating the graphical interface file information in different product software by adopting the same graphical interface file information description specification;
and the first storage submodule is used for respectively storing the encrypted primitive content, the encrypted script content and the graphical interface file information containing primitive content encryption algorithm, script content encryption algorithm and digital signature in different product software to obtain the graphical interface file.
Preferably, the same graphic primitive description specification is the same graphic primitive description specification written in JSON language;
the same script description specification is the same script description specification written in BSON language.
Preferably, the same graphic primitive description specification is the same graphic primitive description specification written by using a BSON language;
the same script description specification is the same script description specification written in BSON language.
Preferably, the storage module includes:
the second generation sub-module is used for generating primitive contents in a BSON format based on the primitive contents generated in different product software respectively;
and the second storage submodule is used for respectively storing the primitive content and the script content which are based on the BSON formats generated in different product software to obtain the graphical interface file.
Compared with the prior art, the beneficial effects of this application are:
in the application, the primitive content or the script content is generated based on the principle that the primitive content or the script content is described by adopting the same description specification in different product software, so that the primitive content and the script content of the opposite party can be mutually identified in different product software, and on the basis, the graphical interface file generated based on the primitive content and the script content in different product software can be identified in different product software, and the graphical interface of the opposite party can be mutually identified between different product software.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1 is a flowchart of a graphical interface file generation method provided herein;
FIG. 2 is a flow chart of another graphical interface file generation method provided herein;
FIG. 3 is a flow chart of yet another graphical interface file generation method provided herein;
FIG. 4 is a flow chart of yet another graphical interface file generation method provided herein;
FIG. 5 is a flow chart of yet another graphical interface file generation method provided herein;
FIG. 6 is a flow chart of yet another graphical interface file generation method provided herein;
fig. 7 is a schematic logic structure diagram of a graphical interface file generating device provided in the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The embodiment of the application discloses a graphical interface file generation method, which comprises the following steps: in different product software, aiming at target graphic primitives, respectively adopting the same graphic primitive description specifications to generate graphic primitive contents, and respectively adopting the same script description specifications to generate script contents related to the graphic primitive contents; and respectively storing the primitive content and the script content generated in different product software to obtain the graphical interface file. In the application, a graphical interface which can mutually identify each other between different product software can be realized.
Next, a method for generating a graphical interface file disclosed in an embodiment of the present application is described, as shown in fig. 1, and is a flowchart of an embodiment 1 of a method for generating a graphical interface file provided in the present application, where the method is applied to a computer device, and the method includes the following steps:
and S11, respectively adopting the same graphic primitive description specification to generate primitive contents aiming at target primitives in different product software, and respectively adopting the same script description specification to generate script contents related to the primitive contents.
In different product software, the same graphic primitive may be applied as a target primitive, e.g., one or more of a circular primitive and a rectangular primitive
Primitive content may be understood as descriptive information for a target primitive, such as attribute information (e.g., geometric attributes, animation attributes, interaction attributes, and custom attributes) for the target primitive.
Script content associated with the primitive content can be understood as: the contents of the actions and functions of the target primitives are described.
In different product software, the same graphic primitive description specification is adopted to generate primitive contents respectively for target primitives, and the same script description specification is adopted to generate script contents related to the primitive contents respectively, so that the purposes that in different product software, the same graphic primitive description specification is adopted to generate primitive contents and the same script description specification is adopted to generate script contents related to the primitive contents for target primitives are realized.
Preferably, a graphic primitive description specification can be negotiated between different product software as the same graphic primitive description specification, and a script description specification can be negotiated as the same script description specification.
The same graphic primitive description specification can be understood as: the same specification of attribute information describing graphic primitives negotiated between different product software.
It should be noted that, this embodiment is not limited to the language in which the same graphic primitive description specification is written.
The same script description specification can be understood as: the same specification negotiated between different product software describes the actions and functions of the graphics primitives.
The present embodiment is not limited to languages in which the same script description specification is written.
And step S12, respectively storing the primitive content and the script content generated in different product software to obtain a graphical interface file.
In this embodiment, the primitive content and the script content generated in different product software are stored in one file, and the file in which the primitive content and the script content are stored is used as the graphical interface file.
In the application, the primitive content or the script content is generated based on the principle that the primitive content or the script content is described by adopting the same description specification in different product software, so that the primitive content and the script content of the opposite party can be mutually identified in different product software, and on the basis, the graphical interface file generated based on the primitive content and the script content in different product software can be identified in different product software, and the graphical interface of the opposite party can be mutually identified between different product software.
As another optional embodiment of the present application, referring to fig. 2, a schematic flow chart of an embodiment 2 of a graphical interface file generating method provided in the present application is mainly a refinement of the graphical interface file generating method described in the foregoing embodiment 1, and as shown in fig. 2, the method may include, but is not limited to, the following steps:
in step S21, in different product software, the same graphic primitive description specification is adopted to generate primitive contents for target primitives, and the same script description specification is adopted to generate script contents associated with the primitive contents.
The detailed process of step S21 can be referred to the related description of step S11 in embodiment 1, and will not be described herein.
And S22, respectively acquiring a primitive content encryption algorithm and a script content encryption algorithm from different product software.
And step S23, encrypting the primitive content generated in the corresponding product software by using primitive content encryption algorithms acquired from different product software respectively to obtain encrypted primitive content.
In this embodiment, the primitive content is encrypted by using the primitive content encryption algorithm, so that confidentiality of the primitive content can be improved.
For example, the primitive content encryption algorithm obtained from different product software is used for encrypting the primitive content generated in the corresponding product software to obtain encrypted primitive content, for example, the different product software is product software A, B and C respectively, the primitive content encryption algorithm a is obtained from product software A, and the primitive content generated in product software A is encrypted by using the primitive content encryption algorithm a; acquiring a graphic primitive content encryption algorithm B from the product software B, and encrypting graphic primitive content generated in the product software B by utilizing the graphic primitive content encryption algorithm B; and acquiring a graphic primitive content encryption algorithm C from the product software C, and encrypting graphic primitive content generated in the product software C by using the graphic primitive content encryption algorithm C.
And step S24, encrypting the script content generated in the corresponding product software by using the script content encryption algorithm acquired from different product software respectively to obtain the encrypted script content.
In this embodiment, the script content is encrypted by using the script content encryption algorithm, so that confidentiality of the script content can be improved.
The script content generated in the corresponding product software is encrypted by using script content encryption algorithms obtained from different product software, for example, the script content generated in the corresponding product software is described, for example, different product software is product software A, B and product software C respectively, script content encryption algorithm a is obtained from product software A, and script content generated in product software A is encrypted by using script content encryption algorithm a; acquiring a script content encryption algorithm B from the product software B, and encrypting script content generated in the product software B by utilizing the script content encryption algorithm B; and acquiring a script content encryption algorithm C from the product software C, and encrypting the script content generated in the product software C by using the script content encryption algorithm C.
Step S25, respectively generating digital signatures based on the primitive content and the script content generated in different product software, and respectively writing the primitive content encryption algorithm, the script content encryption algorithm and the digital signatures into the graphical interface file information in the corresponding product software, wherein the graphical interface file information in different product software is generated by adopting the same graphical interface file information description specification.
The same graphic interface file information description specification can be understood as: the same specification that describes graphical interface file information is negotiated between different product software.
The graphic element content encryption algorithm and the script content encryption algorithm in the graphic interface file information can be used for decrypting the encrypted content by the display module and displaying the graphic element in the interface.
And generating digital signatures based on the encrypted content and the script content generated in different product software respectively, so that the tamper resistance of the primitive content and the script content can be improved.
The digital signature is generated based on the primitive content and the script content generated in different product software, and the primitive content encryption algorithm, the script content encryption algorithm and the digital signature are written into the graphical interface file information in the corresponding product software respectively, for example, the different product software is the product software A, B and the product software C respectively, the digital signature a1 is generated based on the primitive content and the script content generated by the product software A, and the primitive content encryption algorithm a2, the script content encryption algorithm a3 and the digital signature a1 in the product software A are written into the graphical interface file information in the product software A; based on the primitive content and the script content generated by the product software B, generating a digital signature B1, and writing a primitive content encryption algorithm B2, a script content encryption algorithm B3 and the digital signature B1 in the product software B into graphical interface file information in the product software B; based on the primitive content and the script content generated by the product software C, a digital signature C is generated, and a primitive content encryption algorithm C2, a script content encryption algorithm C3 and a digital signature C1 in the product software C are written into graphical interface file information in the product software C.
And step S26, respectively storing the encrypted primitive content, the encrypted script content and the graphic interface file information containing primitive content encryption algorithm, script content encryption algorithm and digital signature in different product software to obtain the graphic interface file.
In this embodiment, the encrypted primitive content, the encrypted script content, and the graphical interface file information including the primitive content encryption algorithm, the script content encryption algorithm, and the digital signature in the product software are stored in one file, and the file in which the encrypted primitive content, the encrypted script content, and the graphical interface file information including the primitive content encryption algorithm, the script content encryption algorithm, and the digital signature are stored is used as the graphical interface file.
As another optional embodiment of the present application, referring to fig. 3, a flowchart of an embodiment 3 of a graphical interface file generating method provided in the present application is mainly a refinement of the graphical interface file generating method described in the foregoing embodiment 1, and as shown in fig. 3, the method may include, but is not limited to, the following steps:
in step S31, in different product software, for the target primitive, the primitive content is generated by adopting the same graphic primitive description specification written in JSON language, and the script content associated with the primitive content is generated by adopting the same script description specification written in BSON language.
In this embodiment, the graphic primitive description specification written in JSON (JavaScript Object Notation, JS object numbered musical notation) language is used to generate the primitive content, so that the readability, maintainability and expandability of the primitive content can be improved.
Script description specifications written in BSON (Binary Serialized Document Format) language are used for generating script contents associated with the graphic primitive contents, so that the size of the script contents occupying storage space can be reduced.
And step S32, respectively storing the primitive content and the script content generated in different product software to obtain a graphical interface file.
The size of the storage space occupied by the graphical interface file can be reduced on the basis of generating script content associated with the graphic primitive content by using script description specifications written in BSON language and reducing the size of the storage space occupied by the script content.
As another optional embodiment of the present application, referring to fig. 4, a schematic flow chart of an embodiment 4 of a graphical interface file generating method provided in the present application is mainly a refinement of the graphical interface file generating method described in the foregoing embodiment 3, and as shown in fig. 4, the method may include, but is not limited to, the following steps:
in step S41, in different product software, for the target primitive, the primitive content is generated by adopting the same graphic primitive description specification written in JSON language, and the script content associated with the primitive content is generated by adopting the same script description specification written in BSON language.
The detailed process of step S41 can be referred to the related description of step S31 in embodiment 3, and will not be repeated here.
And step S42, respectively generating the primitive contents in the BSON format based on the primitive contents generated in different product software.
And generating the primitive content in the BSON format based on the primitive content generated in different product software respectively, so that the size of the memory space occupied by the primitive content can be reduced.
And step S43, respectively storing the primitive content and the script content based on the BSON formats generated in different product software to obtain a graphical interface file.
The size of the storage space occupied by the graphic interface file can be further reduced on the basis of reducing the size of the storage space occupied by the graphic element content and the size of the storage space occupied by the script content.
As another optional embodiment of the present application, referring to fig. 5, a flowchart of an embodiment 5 of a graphical interface file generating method provided in the present application is mainly a refinement of the graphical interface file generating method described in the foregoing embodiment 1, and as shown in fig. 5, the method may include, but is not limited to, the following steps:
in step S51, in different product software, for the target primitive, the primitive content is generated by adopting the same graphic primitive description specification written in BSON language, and the script content associated with the primitive content is generated by adopting the same script description specification written in BSON language.
In this embodiment, the graphic primitive description specification written in BSON language is used to generate the primitive content, so that the size of the memory space occupied by the primitive content can be reduced.
Script description specifications written by the BSON language are used for generating script contents associated with the graphic primitive contents, so that the size of the memory space occupied by the script contents can be reduced.
And step S52, respectively storing the primitive content and the script content generated in different product software to obtain a graphical interface file.
The graphic element description specification written by the BSON language is used for generating the graphic element content, the size of the memory space occupied by the graphic element content is reduced, the script description specification written by the BSON language is used for generating the script content related to the graphic element content, and the size of the memory space occupied by the script content is reduced, so that the size of the memory space occupied by the graphic interface file is reduced.
As another optional embodiment of the present application, referring to fig. 6, a flowchart of an embodiment 6 of a graphical interface file generating method provided in the present application is mainly a refinement of the graphical interface file generating method described in the foregoing embodiment 1, and as shown in fig. 6, the method may include, but is not limited to, the following steps:
step S61, in different product software, the same graphic primitive description specification is adopted to generate primitive contents for target primitives, the same script description specification is adopted to generate script contents related to the primitive contents, and the same picture description specification is adopted to generate picture contents related to the primitive contents.
In this embodiment, when the graphical interface is drawn, in addition to the target primitive, an external picture other than the target primitive may be used, and if a picture associated with the target primitive is detected, the same picture description specification is used to generate the picture content associated with the primitive content.
The script description specification and the picture description specification may be written in the same language, such as BSON language. The script description specification and the picture description specification are written by adopting BSON language, so that the size of the storage space occupied by script content and picture content can be reduced.
And step S62, respectively storing the primitive content, the script content and the picture content generated in different product software to obtain a graphical interface file.
In this embodiment, the primitive content, the script content, and the picture content generated in the different product software are stored in one file, and the file in which the primitive content, the script content, and the picture content are stored is used as the graphical interface file.
Next, description will be made of a method for generating a graphical interface file provided in an embodiment of the present application, where a graphical interface file generating device described below and a graphical interface file generating device described above may be referred to correspondingly with each other.
Referring to fig. 7, the graphical interface file generating apparatus includes: a generation module 11 and a preservation module 12.
The generation module is used for respectively adopting the same graphic primitive description specification to generate primitive contents aiming at target primitives in different product software, and respectively adopting the same script description specification to generate script contents related to the primitive contents;
and the storage module is used for respectively storing the primitive content and the script content generated in different product software to obtain the graphical interface file.
In this embodiment, the storage module may include:
the acquisition sub-module is used for respectively acquiring a primitive content encryption algorithm and a script content encryption algorithm from different product software;
the first encryption sub-module is used for encrypting the primitive content generated in the corresponding product software by using primitive content encryption algorithms acquired from different product software respectively to obtain encrypted primitive content;
the second encryption sub-module is used for encrypting the script content generated in the corresponding product software by utilizing the script content encryption algorithm acquired from different product software respectively to obtain encrypted script content;
the first generation sub-module is used for generating digital signatures based on the primitive content and the script content generated in different product software respectively, writing the primitive content encryption algorithm, the script content encryption algorithm and the digital signatures into the graphical interface file information in the corresponding product software respectively, and generating the graphical interface file information in different product software by adopting the same graphical interface file information description specification;
and the first storage submodule is used for respectively storing the encrypted primitive content, the encrypted script content and the graphical interface file information containing primitive content encryption algorithm, script content encryption algorithm and digital signature in different product software to obtain the graphical interface file.
In this embodiment, the same graphic primitive description specification may be the same graphic primitive description specification written using JSON language;
the same script description specification may be the same script description specification written using BSON language.
In this embodiment, the same graphic primitive description specification may be the same graphic primitive description specification written using BSON language;
the same script description specification may be the same script description specification written using BSON language.
In this embodiment, in a case where the same graphic primitive description specification is the same graphic primitive description specification written using JSON language, and the same script description specification is the same script description specification written using BSON language, the storing module may include:
the second generation sub-module is used for generating primitive contents in a BSON format based on the primitive contents generated in different product software respectively;
and the second storage submodule is used for respectively storing the primitive content and the script content which are based on the BSON formats generated in different product software to obtain the graphical interface file.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described as different from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other. For the apparatus class embodiments, the description is relatively simple as it is substantially similar to the method embodiments, and reference is made to the description of the method embodiments for relevant points.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.
From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the embodiments or some parts of the embodiments of the present application.
The above describes in detail a method and apparatus for generating a graphical interface file provided in the present application, and specific examples are applied herein to describe the principles and embodiments of the present application, where the description of the above examples is only for helping to understand the method and core ideas of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (8)
1. A graphical interface file generation method, comprising:
in different product software, aiming at target graphic primitives, respectively adopting the same graphic primitive description specifications to generate graphic primitive contents, and respectively adopting the same script description specifications to generate script contents related to the graphic primitive contents; the script description specification is a specification describing actions and functions of graphic primitives; the graphic primitive description specification is a specification for describing attribute information of graphic primitives, wherein the attribute information of the graphic primitives comprises geometric attributes, animation attributes, interaction attributes and custom attributes;
respectively storing the primitive content and script content generated in different product software to obtain a graphical interface file; the step of respectively storing the primitive content and the script content generated in different product software to obtain a graphical interface file comprises the following steps:
respectively acquiring a primitive content encryption algorithm and a script content encryption algorithm from different product software;
encrypting the primitive content generated in the corresponding product software by using primitive content encryption algorithms acquired from different product software respectively to obtain encrypted primitive content;
encrypting script contents generated in corresponding product software by using script content encryption algorithms obtained from different product software respectively to obtain encrypted script contents;
generating digital signatures based on the graphic element contents and script contents generated in different product software respectively, and writing the graphic element content encryption algorithm, the script content encryption algorithm and the digital signatures into the graphic interface file information in the corresponding product software respectively, wherein the graphic interface file information in different product software is generated by adopting the same graphic interface file information description specification;
and respectively storing the encrypted primitive content, the encrypted script content and the graphic interface file information containing primitive content encryption algorithm, script content encryption algorithm and digital signature in different product software to obtain the graphic interface file.
2. The method of claim 1, wherein the same graphic primitive description specification is the same graphic primitive description specification written in JSON language;
the same script description specification is the same script description specification written in BSON language.
3. The method of claim 1, wherein the same graphic primitive description specification is the same graphic primitive description specification written using BSON language;
the same script description specification is the same script description specification written in BSON language.
4. The method according to claim 2, wherein the storing the graphical interface file based on the primitive content and the script content generated in the different product software, respectively, includes:
generating primitive contents in BSON format based on the primitive contents generated in different product software respectively;
and respectively storing the primitive content and the script content based on the BSON formats generated in different product software to obtain the graphical interface file.
5. A graphical interface file generation device, comprising:
the generation module is used for respectively adopting the same graphic primitive description specification to generate primitive contents aiming at target primitives in different product software, and respectively adopting the same script description specification to generate script contents related to the primitive contents; the script description specification is a specification describing actions and functions of graphic primitives; the graphic primitive description specification is a specification for describing attribute information of graphic primitives, wherein the attribute information of the graphic primitives comprises geometric attributes, animation attributes, interaction attributes and custom attributes;
the storage module is used for respectively storing the primitive content and the script content generated in different product software to obtain a graphical interface file; the storage module comprises:
the acquisition sub-module is used for respectively acquiring a graphic element content encryption algorithm and a script content encryption algorithm from different product software, and the graphic interface file information in different product software is generated by adopting the same graphic interface file information description specification;
the first encryption sub-module is used for encrypting the primitive content generated in the corresponding product software by using primitive content encryption algorithms acquired from different product software respectively to obtain encrypted primitive content;
the second encryption sub-module is used for encrypting the script content generated in the corresponding product software by utilizing the script content encryption algorithm acquired from different product software respectively to obtain encrypted script content;
the first generation sub-module is used for generating digital signatures based on the primitive content and the script content generated in different product software respectively, writing the primitive content encryption algorithm, the script content encryption algorithm and the digital signatures into the graphical interface file information in the corresponding product software respectively, and generating the graphical interface file information in different product software by adopting the same graphical interface file information description specification;
and the first storage submodule is used for respectively storing the encrypted primitive content, the encrypted script content and the graphical interface file information containing primitive content encryption algorithm, script content encryption algorithm and digital signature in different product software to obtain the graphical interface file.
6. The apparatus of claim 5, wherein the same graphic primitive description specification is the same graphic primitive description specification written in JSON language;
the same script description specification is the same script description specification written in BSON language.
7. The apparatus of claim 5, wherein the same graphic primitive description specification is the same graphic primitive description specification written using BSON language;
the same script description specification is the same script description specification written in BSON language.
8. The apparatus of claim 6, wherein the preservation module comprises:
the second generation sub-module is used for generating primitive contents in a BSON format based on the primitive contents generated in different product software respectively;
and the second storage submodule is used for respectively storing the primitive content and the script content which are based on the BSON formats generated in different product software to obtain the graphical interface file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910343525.8A CN110083354B (en) | 2019-04-26 | 2019-04-26 | Graphical interface file generation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910343525.8A CN110083354B (en) | 2019-04-26 | 2019-04-26 | Graphical interface file generation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110083354A CN110083354A (en) | 2019-08-02 |
| CN110083354B true CN110083354B (en) | 2023-08-01 |
Family
ID=67416967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910343525.8A Active CN110083354B (en) | 2019-04-26 | 2019-04-26 | Graphical interface file generation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110083354B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309660A (en) * | 2013-05-27 | 2013-09-18 | 北京尚友通达信息技术有限公司 | Mobile application cross-platform development method |
| US9430195B1 (en) * | 2010-04-16 | 2016-08-30 | Emc Corporation | Dynamic server graphics |
| CN109445776A (en) * | 2018-10-25 | 2019-03-08 | 北京科东电力控制系统有限责任公司 | Mixing picture method and device |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6986120B2 (en) * | 2001-07-26 | 2006-01-10 | Tata Consultancy Services Limited | System and apparatus for programming system views in an object oriented environment |
| US20030105778A1 (en) * | 2001-11-30 | 2003-06-05 | Intel Corporation | File generation apparatus and method |
| US7702417B2 (en) * | 2006-01-31 | 2010-04-20 | National Instruments Corporation | Automatically generating code from drawing specifications for use in motion control |
| CN103136768A (en) * | 2011-11-25 | 2013-06-05 | 广东省电力调度中心 | Electric power communication network graph standardized software |
| CN102867021B (en) * | 2012-08-08 | 2016-08-10 | 中国电力科学研究院 | A kind of conversion method of transformer station vector graphics |
| CN103390252B (en) * | 2013-07-30 | 2016-08-10 | 国家电网公司 | A kind of control centre and intelligent substation graphical information exchange method |
| CN104166568B (en) * | 2014-08-13 | 2017-08-29 | 国电南瑞科技股份有限公司 | A kind of method of the picture file of electrical power system loaded in parallel based on CIM/G |
| CN108762731A (en) * | 2018-05-21 | 2018-11-06 | 中国电力科学研究院有限公司 | A kind of general field model panorama visualization method and system |
-
2019
- 2019-04-26 CN CN201910343525.8A patent/CN110083354B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9430195B1 (en) * | 2010-04-16 | 2016-08-30 | Emc Corporation | Dynamic server graphics |
| CN103309660A (en) * | 2013-05-27 | 2013-09-18 | 北京尚友通达信息技术有限公司 | Mobile application cross-platform development method |
| CN109445776A (en) * | 2018-10-25 | 2019-03-08 | 北京科东电力控制系统有限责任公司 | Mixing picture method and device |
Non-Patent Citations (1)
| Title |
|---|
| 基于XML的嵌入式异构域图编程数据的描述方法;李强;黄晨;严义;邬惠峰;;计算机工程与应用(15);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110083354A (en) | 2019-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10650492B2 (en) | Method and apparatus for generating image | |
| US9245182B2 (en) | Enhancing data in a screenshot | |
| CN115997207B (en) | Detecting a sub-image region of interest in an image using a pilot signal | |
| CN109740317A (en) | A kind of digital finger-print based on block chain deposits card method and device | |
| JP6206866B2 (en) | Apparatus and method for holding obfuscated data in server | |
| US20170301115A1 (en) | Method for obfuscating the display of text | |
| CN103493042A (en) | Browsing system, terminal, image server, program, computer-readable recording medium recording said program, and method | |
| WO2022262517A1 (en) | Watermark information display method and apparatus, electronic device, and computer-readable medium | |
| CN110083354B (en) | Graphical interface file generation method and device | |
| CN112991151B (en) | Image processing method, image generation method, apparatus, device, and medium | |
| CN109284487A (en) | The method, apparatus of rendering data, electronic equipment and storage medium in canvas | |
| JP2014212476A (en) | Comic image frame detection device, method and program | |
| CN108985109B (en) | Data storage method and device | |
| EP3491536A1 (en) | Scalable vector graphics bundles | |
| CN109086326B (en) | Method and device for converting interface document into data model file | |
| CN116432606A (en) | Method, device, equipment and storage medium for acquiring explanation steps of equation | |
| CN103377325A (en) | Electronic book content protection | |
| US20190158697A1 (en) | Enhancing graph visualization with supplemental data | |
| JP5718839B2 (en) | Method, system and computer-readable medium for moving labels to avoid overlap in graphic output | |
| CN108073403A (en) | Convert the method and computing device of application | |
| CN110020285B (en) | Histogram processing method and device | |
| CN112583603A (en) | Visual signature method and device, electronic equipment and computer readable storage medium | |
| US20110316878A1 (en) | Computer Implemented Process for Interactive Appreciation of Fine Art | |
| CN113139163B (en) | Method and device for generating watermark information on application program interface | |
| US9064214B2 (en) | Context aware apparatus and method |
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 |