JAVASCRIPTTM PROGRAMMING EXTENSION

• US 20090049423A1
• Filed: 07/18/2008
• Published: 02/19/2009
• Est. Priority Date: 07/23/2007
• Status: Abandoned Application

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Early, Justin Christopher, Yao, Yitao, Choi, Gregory, Palaima, Mark P.
• Application Number:
  US12/176,244
• Publication Number:
  US 20090049423A1
• Time in Patent Office: Days
• US Class Current: 717/108
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/51 Source to source

Abstract

A JavaScript™ programming extension is provided. An example JavaScript™ programming extension comprises a code generator and a JavaScript™ reference converter. The code generator may be configured to access an existing JavaScript™ file, validate JavaScript™ definitions in the existing JavaScript™ file, and generate a Java™ representation of the existing JavaScript™ file. The JavaScript™ reference converter may be configured to generate a validated JavaScript™ file corresponding to the existing JavaScript™ file.

Claims

1. A system comprising:

a code generator to;

access an existing JavaScript™

file;

validate JavaScript™

definitions in the existing JavaScript™

file, and

generate a Java™

representation of the existing JavaScript™

file; and

a JavaScript™

reference converter to generate a validated JavaScript™

corresponding to the existing JavaScript™

.

2. The system of claim 1, including a JavaScript™

authoring module to facilitate authoring of JavaScript™

files.

3. The system of claim 2, wherein the JavaScript™

authoring module comprises a JavaScript™

runtime framework to support object-oriented component programming style with JavaScript™

.

4. The system of claim 2, wherein the JavaScript™

authoring module supports JsDoc annotation to declare data types.

5. The system of claim 1, wherein the Java™

representation of the existing JavaScript™

file comprises a typed referencing class in Java™

for each JavaScript™

component in the existing JavaScript™

file.

6. The system of claim 4, wherein the code generator is to provide value-binding support.

7. The system of claim 1, wherein the JavaScript™

reference converter comprises one or more converters to convert Java™

data type into JS-compatible data type.

8. The system of claim 7, wherein the one or more converters include a date converter to convert a Java™

Date type into a JavaScript™

compatible type.

9. The system of claim 1, further comprising a dependencies manager to maintain one or more dependencies among one or more JavaScript™

components in the validated JavaScript™

file.

10. The system of claim 1, wherein the system is integrated with an Integrated Development Environment (IDE).

11. A method comprising:

accessing an existing JavaScript™

file;

validating JavaScript™

definitions in the existing JavaScript™

file; and

generating a Java™

representation of the existing JavaScript™

file.

12. The method of claim 11, wherein the Java™

representation of the existing JavaScript™

file is a Java™

class.

13. The method of claim 11, further comprising generating a validated JavaScript™

file corresponding to the existing JavaScript™

.

17. The method of claim 11, wherein the Java™

representation of the existing JavaScript™

file includes a Java™

function that can take typed-value-binding as an argument and return a value that is also a typed-value binding.

18. The method of claim 11, further comprising:

determining dependencies between JavaScript™

components in the existing JavaScript™

file; and

maintaining the determined dependencies to enable JavaScript™

aggregation and externalization.

19. The method of claim 11, further comprising facilitating authoring of the existing JavaScript™

file including building dependencies for the existing JavaScript™

file.

14. The method of claim 14, further comprising obfuscating the contents of the validated JavaScript™

file module to impede readability of the validated JavaScript™

file.

15. The method of claim 14, wherein the generating of the validated JavaScript™

file comprises converting a Java™

data type into a JavaScript™

data type.

16. The method of claim 15, wherein the a Java™

data type is a Java™

date type and the JavaScript™

data type is one of “

string”

, “

long”

, and JSDate.

20. A machine-readable medium having instruction data to cause a machine to:

access an existing JavaScript™

file;

validate JavaScript™

definitions in the existing JavaScript™

file;

generate a Java™

representation of the existing JavaScript™

file; and

generate a validated JavaScript™

corresponding to the existing JavaScript™

.