# US 2013/0174135 A1 · Creating a shockwave flash file

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0174135 A1
- Document ID: US20130174135A1
- Status: Published application
- Kind: A1
- Application number: 12/549,838
- Filed: 2009-08-28
- Published: 2013-07-04
- Earliest claimed: 2009-08-28
- Inventors: Krishna G. Kiran; Ravi Kishore Reddy
- Web page: https://patentgrep.com/patent/US20130174135A1

## CPC

- G06F 8/447: {Target code generation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system identifies a first portion of a project as static code. The system compiles the static code to create compiled static code. The system identifies a second portion of the project as dynamic code that requires a plurality of compilations for a plurality of sub portions of the dynamic code to create compiled dynamic code. The system converts a subset of the dynamic code into dynamic byte code. The dynamic byte code reduces the plurality of dynamic code compilations necessary to create a SWF file. The system then merges the compiled static code and the dynamic byte code to create the SWF file.

## Claims

### Claim 1

A computer readable medium having computer readable code thereon, the medium comprising instructions for:
identifying a first portion of a project as static code;
compiling the static code to create compiled static code;
identifying a second portion of the project as dynamic code where the dynamic code requires a plurality of compilations for a plurality of sub portions of the dynamic code to create compiled dynamic code;
converting a subset of the dynamic code into dynamic byte code, the dynamic byte code reducing the plurality of dynamic code compilations necessary to create a file; and
merging the compiled static code and the dynamic byte code to create the file.

### Claim 2 (depends on 1)

The computer readable medium of claim 1 comprising:
during execution of the file, for each component and each sub-component rendered during execution, executing a respective component class and sub-component class, each referencing eXtensible Markup Language code generated during the conversion of the subset of the second portion of the project.

### Claim 3 (depends on 2)

The computer readable medium of claim 2 wherein executing a respective compiled component class and compiled sub-component class comprises:
for each component property associated with a component, obtaining the component property by referencing the component property contained within eXtensible Markup Language code generated during the conversion of the subset of the second portion of the project, the component property referenced via the component class; and
for each sub-component property associated with a sub-component, obtaining the subcomponent property by referencing the sub-component property contained within eXtensible Markup Language code generated during the conversion of the subset of the second portion of the project, the sub-component property referenced via the sub-component class.

### Claim 4 (depends on 1)

The computer readable medium of claim 1 wherein converting a subset of the dynamic code into dynamic byte code comprises:
converting a subset of the dynamic code into dynamic byte code capable of compilation prior to the receiving notification to compile the project to create the file, the prior compilation reducing the plurality of compilations necessary to create the file.

### Claim 5 (depends on 1)

The computer readable medium of claim 1 wherein converting a subset of the dynamic code into dynamic byte code comprises:
traversing the project to identify components to be rendered during execution of the file; and
for each component identified, traversing the component to identify sub-components to be rendered during execution of the file, the sub-components rendered during the rendering of the respective component.

### Claim 6 (depends on 5)

The computer readable medium of claim 5 comprising:
identifying eXtensible Markup Language code generated as a result of identification of components and sub-components to be rendered during the execution of the file; and
inserting the eXtensible Markup Language code into an initialization class associated with the converted dynamic code, the eXtensible Markup Language code inserted as a member of the initialization class, the initialization class comprising initializing values for the components and sub-components in the file.

### Claim 7 (depends on 5)

The computer readable medium of claim 5 wherein traversing the project to identify components to be rendered during execution of the file comprises:
for each component identified, associating the component to a component class; and
generating eXtensible Markup Language code associated with the component.

### Claim 8 (depends on 7)

The computer readable medium of claim 7 wherein generating eXtensible Markup Language code associated with the component comprises:
creating a component node to represent the component; and
writing at least one component property, associated with the component, in the component node.

### Claim 9 (depends on 5)

The computer readable medium of claim 5 wherein traversing the component to identify subcomponents to be rendered during execution of the file comprises:
for each sub-component identified, associating the sub-component to a sub-component class; and
generating eXtensible Markup Language code associated with the sub-component.

### Claim 10 (depends on 9)

The computer readable medium of claim 9 wherein generating eXtensible Markup Language code associated with the sub-component comprises:
creating a sub-component node to represent the sub-component, the sub-component node created as a child node of the component node; and
writing at least one sub-component property, associated with the sub-component, in the sub-component node.

### Claim 11 (depends on 1)

The computer readable medium of claim 1 wherein merging compiled static code and the dynamic byte code to create the file comprises:
for each component type and sub-component type that exists within the project, defining a respective component class and sub-component class; and
compiling each of the respective component class and sub-component class wherein the compilation of the component classes and sub-component classes is capable of being performed prior to the converting a subset of the dynamic code into dynamic byte code.

### Claim 12 (depends on 1)

The computer readable medium of claim 1 wherein merging compiled static code and the dynamic byte code to create the file comprises:
compiling a initialization class comprising eXtensible Markup Language code identifying components and sub-components to be rendered during the execution of the file.

### Claim 13

In a computer system, a method comprising:
identifying a first portion of a project as static code;
compiling the static code to create compiled static code;
identifying a second portion of the project as dynamic code where the dynamic code requires a plurality of compilations for a plurality of sub portions of the dynamic code to create compiled dynamic code;
converting a subset of the dynamic code into dynamic byte code, the dynamic byte code reducing the plurality of dynamic code compilations necessary to create a file; and
merging compiled static code and the dynamic byte code to create the file.

### Claim 14 (depends on 13)

The method of claim 13 comprising:
during execution of the file, for each component and each sub-component rendered during execution, executing a respective component class and sub-component class, each referencing eXtensible Markup Language code generated during the conversion of the subset of the second portion of the project.

### Claim 15 (depends on 14)

The method of claim 14 wherein executing a respective compiled component class and compiled sub-component class comprises:
for each component property associated with a component, obtaining the component property by referencing the component property contained within eXtensible Markup Language code generated during the conversion of the subset of the second portion of the project, the component property referenced via the component class; and
for each sub-component property associated with a sub-component, obtaining the subcomponent property by referencing the sub-component property contained within eXtensible Markup Language code generated during the conversion of the subset of the second portion of the project, the sub-component property referenced via the sub-component class.

### Claim 16 (depends on 13)

The method of claim 13 wherein converting a subset of the dynamic code into dynamic byte code comprises:
converting a subset of the dynamic code into dynamic byte code capable of compilation prior to the receiving notification to compile the project to create the file, the prior compilation reducing the plurality of compilations necessary to create the file.

### Claim 17 (depends on 13)

The method of claim 13 wherein converting a subset of the dynamic code into dynamic byte code comprises:
traversing the project to identify components to be rendered during execution of the file; and
for each component identified, traversing the component to identify sub-components to be rendered during execution of the file, the sub-components rendered during the rendering of the respective component.

### Claim 18 (depends on 13)

The method of claim 13 wherein merging compiled static code and the dynamic byte code to create the file comprises:
for each component type and sub-component type that exists within the project, defining a respective component class and sub-component class; and
compiling each of the respective component class and sub-component class wherein the compilation of the component classes and sub-component classes is capable of being performed prior to the converting a subset of the dynamic code into dynamic byte code.

### Claim 19 (depends on 13)

The method of claim 13 wherein merging compiled static code and the dynamic byte code to create the file comprises:
compiling a initialization class comprising eXtensible Markup Language code identifying components and sub-components to be rendered during the execution of the file.

### Claim 20

A computerized device comprising:
a memory;
a processor;
a communications interface;
an interconnection mechanism coupling the memory, the processor and the communications interface;
wherein the memory is encoded with a compiling and executing application that when executed on the processor is capable of compiling and executing applications on the computerized device by performing the operations of:
identifying a first portion of a project as static code;
compiling the static code to create compiled static code;
identifying a second portion of the project as dynamic code where the dynamic code requires a plurality of compilations for a plurality of sub portions of the dynamic code to create compiled dynamic code;
converting a subset of the dynamic code into dynamic byte code, the dynamic byte code reducing the plurality of dynamic code compilations necessary to create a file; and
merging compiled static code and the dynamic byte code to create the file.

### Claim 21 (depends on 1)

The computer readable medium of claim 1, wherein the dynamic byte code represents a component class and/or a component sub class of the project.