Selective application view

• US 20130198715A1
• Filed: 10/09/2006
• Published: 08/01/2013
• Est. Priority Date: 10/09/2006
• Status: Abandoned Application

• Current Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Zuckerman, David, Hyatt, Rebecca
• Application Number:
  US11/545,708
• Publication Number:
  US 20130198715A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/33 Intelligent editors
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

A selective outline view is described in an application development environment that allows viewing an outline of an application in either a procedural code outline view or a declarative tree-view. The application is written, at least in part, in a tag-based declarative language. The declarative language has a representational relationship to a procedural language that defines the logic of application. The choice of views is presented in a selection indicator. On selection of the procedural code outline view, the application is processed to obtain a procedural code representation of the application using the relationship between the declarative and procedural languages. The procedural code outline view is generated from the procedural code representation. On selection of the declarative tree-view of the application, the ADE parses the application to obtain a declarative object model of the application. The declarative tree-view of the application is created using the declarative object model.

Claims

1-27. -27. (canceled)

28. A method comprising:

receiving, by at least one processor, an application file comprising tag-based code and procedural components, the procedural components corresponding to a procedural language;

identifying the procedural components, by at least one processor; and

generating a procedural outline view, by at least one processor, based on the identified procedural components, the procedural outline view at least substantially comprising procedural components.

29. The method of claim 28 wherein identifying the procedural components comprises:

parsing the tag-based code; and

determining the procedural components based at least in part on the parsed tag-based code.

30. The method of claim 29 wherein parsing the tag-based code comprises:

creating an object model for the tag-based code.

31. The method of claim 28 wherein identifying the procedural components comprises:

at least partially compiling the application file; and

determining the procedural components based at least in part on the at least partially compiled application file.

32. The method of claim 28 wherein identifying the procedural components comprises:

identifying potential procedural components in the application file; and

for each potential procedural component;

comparing the potential procedural component to a list of previously determined procedural components for the procedural language to determine whether the potential procedural component is a procedural component.

33. The method of claim 32 wherein the list of previously determined procedural components is stored in at least one database.

34. The method of claim 28 wherein identifying the procedural components comprises:

referencing a data store to determine the procedural components.

35. The method of claim 28 further comprising:

displaying a visual indicator associated with at least one of the procedural components in the procedural outline view.

36. The method of claim 35 wherein the visual indicator identifies a type of procedural component.

37. The method of claim 28 wherein at least one of the procedural components identifies at least one of a class, a variable, or a function in the application file.

38. The method of claim 28 wherein at least one of the procedural components comprises an element corresponding to a function.

39. The method of claim 28 wherein the procedural outline view does not comprise tag-based code.

40. The method of claim 28 wherein the procedural outline view comprises only procedural components.

41. The method of claim 28 further comprising:

identifying declarative components in the application file; and

generating a declarative outline view based on the identified declarative components, the declarative outline view at least substantially comprising declarative components.

42. A system comprising:

a memory; and

a processor in communication with the memory, the processor configured for;

analyzing an application file comprising tag-based code and procedural components, the procedural components corresponding to a procedural language;

identifying the procedural components; and

generating a procedural outline view based on the identified procedural components, the procedural outline view at least substantially comprising procedural components.

43. The system of claim 42 wherein identifying the procedural components comprises:

parsing the tag-based code; and

determining the procedural components based at least in part on the parsed tag-based code.

44. The system of claim 42 wherein identifying the procedural components comprises:

at least partially compiling the application file; and

determining the procedural components based at least in part on the at least partially compiled application file.

45. The system of claim 42 wherein identifying the procedural components comprises:

identifying potential procedural components in the application file; and

for each potential procedural component;

comparing the potential procedural component to a list of previously determined procedural components for the procedural language to determine whether the potential procedural component is a procedural component.

46. The system of claim 42 wherein identifying the procedural components comprises:

referencing a data store to determine the procedural components.

47. The system of claim 42 wherein the processor is further configured for:

displaying a visual indicator associated with at least one of the procedural components in the procedural outline view.

48. The system of claim 42 wherein the processor is further configured for:

identifying declarative components in the application file; and

generating a declarative outline view based on the identified declarative components, the declarative outline view at least substantially comprising declarative components.

49. A non-transitory computer-readable medium comprising program code, the program code configured for:

receiving an application file comprising tag-based code and procedural components, the procedural components corresponding to a procedural language;

identifying the procedural components; and

generating a procedural outline view based on the identified procedural components, the procedural outline view at least substantially comprising procedural components.

50. The non-transitory computer-readable medium of claim 49 wherein identifying the procedural components comprises program code configured for:

parsing the tag-based code; and

determining the procedural components based at least in part on the parsed tag-based code.

51. The non-transitory computer-readable medium of claim 49 wherein identifying the procedural components comprises program code configured for:

at least partially compiling the application file; and

determining the procedural components based at least in part on the at least partially compiled application file.

52. The non-transitory computer-readable medium of claim 49 wherein identifying the procedural components comprises program code configured for:

identifying potential procedural components in the application file; and

for each potential procedural component;

comparing the potential procedural component to a list of previously determined procedural components for the procedural language to determine whether the potential procedural component is a procedural component.

53. The non-transitory computer-readable medium of claim 49 wherein identifying the procedural components comprises program code configured for:

referencing a data store to determine the procedural components.

54. The non-transitory computer-readable medium of claim 49 further comprising program code configured for:

displaying a visual indicator associated with at least one of the procedural components in the procedural outline view.

55. The non-transitory computer-readable medium of claim 49 further comprising program code configured for:

identifying declarative components in the application file; and

generating a declarative outline view based on the identified declarative components, the declarative outline view at least substantially comprising declarative components.