Patent Application
20150113513
Many software developers use interactive development environments (IDEs) in order to develop software. The developers use an IDE in order to develop models of types within a computer system, and in order to customize those models.
An exemplary integrated development environment is illustratively a development tool or development environment that includes a plurality of different tools so that developers can develop and test the code that needs to be developed and in order to customize a computer system as desired. By way of example, an IDE may include a source code editor, one or more build automation tools and a debugger that allow computer programmers to develop software. Some IDEs illustratively include a compiler, an interpreter, or both. They may include a version control system and various tools to simplify the construction of graphical user interfaces. They can also include a class browser, an object browser, and a class hierarchy diagram for use with object oriented software development. Thus, developers can use IDEs to generate the code and metadata, along with customizations to code and metadata, that may be utilized in developing a system for use in a given organization.
In generating or customizing software using an IDE, the application developer models specific concepts (also referred to as types) within an application and, where necessary, writes code. Large applications, for which developers often use IDEs, can include thousands of different types. Thus, developing and customizing these types is a relatively large task.
By way of example, some computer systems include business systems, such as enterprise resource planning (ERP) systems, customer relations management (CRM) systems, line-of-business (LOB) systems, among others. These types of computer systems often have many thousands of different types that are modeled and customized. By way of example, some such business systems often have thousands of different forms, alone, not to mention many other types.
Business systems are not the only types of computer systems that have a large number of types. For instance, gaming systems, or a wide variety of other types of systems, often also have many thousands of different types that are modeled in the software system.
Such computer systems can be represented by interpreted code or compiled code. As a developer is developing or customizing compiled code, the developer often wishes to work on the development or customizations, and then run the code to make sure that it is working as the developer desires. In a compiled code environment, this has required the compiler to recompile the entire system, in order to run the system with the newly developed or customized code. The reason is that, currently, a compiler is largely just an executable that runs when compilation is needed. When compilation is finished, the compiler loses its memory and any cache it has built. In the development environment, this can be very time consuming and can add time and cost to the development phase of a project, and it can also lead to frustration in the developer experience.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
An interactive development environment receives developer inputs to develop or customize modeled types. A compilation agent receives a request from the IDE to compile the modeled types that the developer is developing or customizing. The compilation agent hosts a compiler as a long running service that maintains a cache of previously compiled types and determines which of the individually loadable types are to be re-compiled based upon the changes made by the developer, and compiles only those identified types. The re-compiled types are also stored in cache.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
In addition,
Compilation agent 104 illustratively performs compilation operations requested in compilation requests 122 sent by IDE 102. Compilation agent 104 illustratively includes cache 124, management component 126 and processor 128. After the compilation operations are performed, agent 104 can illustratively provide responses 130 back to IDE 102. All of these operations are discussed in greater detail below with respect to
Compilation agent 104 also illustratively provides the compiled types 132 to runtime environment 108 where they can be stored in a data store 134 for execution during runtime. Runtime environment 108 illustratively includes application server 136 and runtime translator/locator 138. Runtime translator/locator 138 illustratively locates the types for the application elements that are needed to run the computer system, and loads them on demand. They are illustratively loaded from data store 134 into application server 136 where they can be executed during runtime.
Metadata and code store 106 illustratively stores the metadata and code corresponding to various different types of application elements (e.g., types). It is accessible, for instance, by IDE 102 and compilation agent 104.
IDE 102 first illustratively receives developer inputs identifying application elements (such as compilable types) that the developer wishes to either model or customize. This is indicated by block 150 in
Optionally, compilation agent 104 can also illustratively accesses the metadata and code from store 106 to pre-loaded all needed application elements (e.g., compilable types) that will be loaded in order for developer 110 to run the developed or customized code, after the development or customization operations are performed. Agent 104 illustratively compiles them into individually loadable types and caches them in cache 124. This is indicated by block 154 in
At some point, after developer 110 has made a desired number of customizations to existing models, or has developed a number of models from scratch, developer 110 may wish to have the code compiled by compilation agent 104. This will enable developer 110 to run the newly developed or customized code to see whether it performs as desired. Recall that compilation agent 104 may have already accessed a number of modeled types from data store 106 and pre-loaded them into cache 124. Also, compilation agent 104 may have already compiled a number of compilable types that have been received from IDE 102, based upon changes that were previously made, or development that was previously performed, by developer 110. Those compiled types may also already be in cache 124. Thus, compilation agent 104 receives a compilation request 122 from IDE 102. In one embodiment, compilation agent 104 receives the compilation parameters in compilation request 122 through a service contract method call. By way of example, the exposed service contract may be one similar to that shown in table 1 below.
It will be appreciated that compilation agent 104 can receive compilation request 122 in other ways as well. Having compilation agent 104 receive compilation requests identifying changes or developments made at IDE 102 by developer 110 is indicated by block 158 in
Compilation agent 104 then accesses cache 124 to identify elements (e.g., the modeled types) that need to be compiled so that the development and customizations made by developer 110 can be run and inspected by developer 110. In one embodiment, compilation agent 104 does this by identifying which particular modeled types have been changed by developer 110, or which have been added, and compiles only those modeled types, and any other modeled types that must be compiled in order for the developed or customized code to be run.
Compilation agent 104 examines cache 124 to determine whether any of the modeled types that are to be compiled have already been compiled and stored in cache 124. If they are, they need not be re-compiled. This is because the modeled types are modeled and compiled as independently loadable assemblies. Thus, only the modeled types that have currently been customized or developed need to be compiled, and any other modeled types need not be re-compiled, so long as they have already been compiled and the compiled version is stored in cache 124. Identifying the elements to be compiled is indicated by block 160 in
Compilation agent 104 then loads the metadata and code for only the identified elements that need to be compiled from data store 106. This is indicated by block 162 in
Once compilation agent 104 has all of the metadata and code needed to perform the compilation, it compiles the identified elements (e.g., the modeled types) into individually loadable types and makes the compiled types 132 available to the runtime environment 108. This is indicated by block 164 in
Compilation agent 104 then stores the newly compiled elements in cache 124, and sends a response 130 to IDE 102 indicating that the compilation is complete. This is indicated by block 166 in
Throughout the entire process, management component 126 illustratively performs self-management of agent 104. This is described in greater detail below with respect to
If, at block 170, it is determined that management component 126 should shut down agent 104, it is shut down. This is indicated by block 172 in
As discussed above with respect to
Management component 126 intermittently queries the operating system in which it is running (or with which it is running) to determine whether the memory consumption of compilation agent 104 exceeds a given threshold value. This is indicated by block 184 in
If, at block 184, it is determined that the memory consumption does not exceed the threshold value, or after the cache is invalidated at block 186, management component 126 determines whether there are any instances of IDE 102 still running. This is indicated by block 188 in
However, if at block 188 it is determined that there are instances of IDE 102 still running, then management component 126 determines whether compilation agent 104 has been idle for a threshold amount of time. This is indicated by block 192 in
It can thus be seen that compilation agent 104, whenever it receives a compilation request 122, compiles or re-compiles only those compilable types that need to be, based upon the changes made by developer 110, and based upon which types are already compiled and stored in cache 124. This significantly reduces the compile time during which developer 110 has to wait to see whether the code runs properly. This enhances the developer experience, and it can reduce time and effort required in developing, customizing, or debugging code.
It should also be noted that the above discussion has shown a number of data stores, including data store 120, data store 106 and data store 134. While these are shown as three independent data stores, they could also be formed within a single data store. In addition, the data in those data stores can be stored in multiple additional data stores as well. Also, the data stores can be local to the environments or agents or components that access them, or they can be remote therefrom and accessible by those environment, components or agents. Similarly, some can be local while others are remote.
Processors 118 and 128, and server 136 illustratively include computer processors with associated memory and timing circuitry (not separately shown). They are a functional part of the agent or environment to which they belong, and are illustratively activated by, and facilitate the functionality of, other items in that environment or agent.
It will also be noted that
Also, the user interface displays that developer 110 interacts with to manipulate and control IDE 102 illustratively have user actuatable input mechanisms that can take a wide variety of different forms, such as icons, text boxes, check boxes, tiles, drop down menus, etc. They can illustratively be actuated using a point and click device (such as a trackball or mouse), buttons, joysticks, thumbpads, thumb switches, virtual or hardware keyboards or keypads. Also, where the user interface displays are displayed on a touch sensitive screen, the user input mechanisms can be activated by touch gestures, with a users finger, a stylus, etc. Where the device displaying the displays has speech recognition components, then the user input mechanisms can be actuated using speech commands.
The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
In the embodiment shown in
It will also be noted that architecture 100, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.
Under other embodiments, applications or systems are received on a removable Secure Digital (SD) card that is connected to a SD card interface 15. SD card interface 15 and communication links 13 communicate with a processor 17 (which can also embody processors 118 or 128 or server 136 from
I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.
Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.
Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. Similarly, device 16 can have a client business system 24 which can run various business applications. Processor 17 can be activated by other components to facilitate their functionality as well.
Examples of the network settings 31 include things such as proxy information, Internet connection information, and mappings. Application configuration settings 35 include settings that tailor the application for a specific enterprise or user. Communication configuration settings 41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
Applications 33 can be applications that have previously been stored on the device 16 or applications that are installed during use, although these can be part of operating system 29, or hosted external to device 16, as well.
The mobile device of
Note that other forms of the devices 16 are possible.
Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation,
The computer 810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 820 through a user input interface 860 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, computers may also include other peripheral output devices such as speakers 897 and printer 896, which may be connected through an output peripheral interface 895.
The computer 810 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 810. The logical connections depicted in
When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
