REAL-TIME COLLABORATIVE DEVELOPMENT IN A LIVE PROGRAMMING SYSTEM

• US 20180107455A1
• Filed: 12/29/2015
• Published: 04/19/2018
• Est. Priority Date: 12/29/2015
• Status: Abandoned Application

• Current Assignee: Eyelead Software SA
• Original Assignee: Eyelead Software SA
• Inventors: PSISTAKIS, IOSIF
• Application Number:
  US14/981,982
• Publication Number:
  US 20180107455A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Improved techniques for real-time collaborative development in an authoring system, especially suited for the production of multimedia applications and games, are described. In an exemplary embodiment, collaborative live development involves: (i) loading digital resources of a structured binary format in a host device that manages synchronization and versioning, (ii) establishing a communication session between the host device and a client device, (iii) synchronizing digital files of a structured binary format between the client device and the host device using devices similar to Source Control Management systems, and (iv) incorporating any resource changes in the Live Programming execution environment in a non-intrusive manner on the basis of predefined criteria.

Claims

1. In a client computing device, a method of live editing the source code and content of a software application or digital medium by a first user while a second user s live editing the source code and content of the same software application or digital medium on a second remote device, comprising the client computing device implemented method of:

loading resources as structured in-memory representations where the representations are shared between edit and play modes of operation;

associating corresponding content files as part of the software application or digital medium being editing via a Project grouping data structure;

further associating team members, roles and permissions as part of a Project grouping data structure; and

executing the application defined by the structured in-memory representations while the contents of the representations are being edited by a first user, then, once the editing operations are finished, loading the edits into the executed application to reflect those edits while preserving the state of the application to avoid unnecessary reloads.

2. The method of claim 1, further comprising a mechanism for synchronizing data via a Shared Network Resource that also stores Project Information.

3. The method of claim 2, further comprising locking a structured in-memory resource representation in response to the request to alter that resource.

4. The method of claim 3, where the alteration of a first structured in-memory resource representation includes altering a property of that representation and automatically triggers the capture of Editing Metadata, including the time of alteration, the altering user and the segments of the in-memory representation affected.

5. The method of claim 4, where the altering of a property of a first structure in-memory resource representation is transmitted to the Shared Network Resource along with its Editing Metadata.

6. The method of claim 5, where additional users including the Second User are attached to the Shared Network Resource for data exchange and synchronization.

7. The method of claim 6, where the Shared Network Resource, upon receiving an update message regarding the alteration of a first structured in-memory resource representation along with its editing metadata, it stores that alteration, transmitting the alteration along with its editing Metadata to all attached client devices except the originating client device.

8. The method of claim 5, where a client device senses a change in a source code element of the application from the user controlling the client device and immediately loads and executes that modified source code resource ensuring that:

the state of the running application is preserved, thereby minimized reload times;

any changes in the code are properly displayed, including changes to initial values of variables; and

any required actions, including a reset in the executed application state happen immediately upon loading.

9. The method of claim 5, where a client device senses a change in a source code element of the application, originated from the Shared Network Resource and compares the current execution state with the modified element'"'"'s state set requirements, then decides, based on that comparison immediately loading that source code resource so, deeming that it is safe to do so, or refrain from loading.

10. The method of claim 5, where whenever a structured in-memory resource representation is locked, the lock instruction is also automatically transmitted to the Share Network Resource and from there propagated to all attached client devices to the Shared Network Resource, as dictated by the Project definition.

11. The method of claim 5, where a client device is attached to a Shared Network Resource after a loss of connectivity, thereby

receiving all updates to structured in-memory resource representations from the Shared Network Resource since the time of loss of connectivity;

applying all updates to structured in-memory resource representations; and

transmitting all the catalogued edits (including Editing Metadata) that it has not transmitted since loss of connectivity.

12. A non-transient computer readable medium containing program instructions for live editing code and content on a client device of a software application or digital medium by a first user while a second user s live editing code and content on the same software application or digital medium on a second remote device, the instructions including:

loading resources as structured in-memory resource representations in a memory where the structured in-memory resource representations are shared between edit and play modes of operation;

associating corresponding content files as part of the software application or digital medium being editing via a Project grouping data structure;

further associating team members, roles and permissions as part of a Project grouping data structure; and

executing the application defined by the structured in-memory resource representations while the contents of those representations are being edited by a first user, then, once the editing operations are finished, loading the edits into the executed application to reflect those edits while preserving the state of the application to avoid unnecessary reloads.

13. The non-transient computer readable medium of claim 12, further comprising an instruction to synchronize data via a Shared Network Resource that also stores Project information

14. The non-transient computer readable medium of claim 13, further comprising an instruction to lock a structured in-memory resource representation in response to the request to alter that structured in-memory resource representation.

15. The non-transient computer readable medium of claim 14, further comprising an instruction to automatically capture Editing Metadata for a structured in-memory resource representations (including the time of alteration, the altering user and the segments of the representation affected), whenever the system detects a change in the representation being edited.

16. The non-transient computer readable medium of claim 15, further comprising an instruction to automatically transmit an update message to the Shared Network Resource along with pertinent Editing Metadata whenever the altering of a property of a first structured in-memory resource representation.

17. The non-transient computer readable medium of claim 16, further comprising an instruction for the Shared Network Resource, to store an alteration and retransmit it along with pertinent Editing Metadata to all attached client devices except the originating client device, whenever it receives an alteration update message.

18. The non-transient computer readable medium of claim 17, further comprising an instruction to a client device, that whenever it senses a change in a source code element of the application from the user controlling the client device it will immediately load and executes that modified source code resource ensuring that:

the state of the running application is preserved, thereby minimized reload times;

any changes in the code are properly displayed, including changes to initial values of variables;

any required actions, including a reset in the executed application state happen immediately upon loading.

19. The non-transient computer readable medium of claim 18, further comprising an instruction to a client device, that whenever t senses a change in a source code element of the application, originated from the Shared Network Resource, to compare the current execution state with the modified element'"'"'s set requirements and then decide, based on that comparison immediately loading that source code resource so, deeming that it is safe to do so, or refrain from loading until the local user explicitly commands it, so as to avoid a possible execution state reset.

20. The non-transient computer readable medium of claim 18, further comprising an instruction to disable local editing capabilities but present the software application being developed as an independent software application.