Application GUI Block Locking for Consistent Co-Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Concurrent application development by multiple users leads to issues such as overwriting and inconsistency due to multiple versions of the same block of code being edited across different pages, with existing tools failing to address these challenges effectively.
Innovation Solution
A system and method that manages co-development by using a global store lock service to lock blocks for editing by a single user, ensuring that only one user can edit a block at a time, and synchronizing changes across all instances, while considering user privileges and block activity through a centralized server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple users edit blocks concurrently across different pages, then development collaboration is enabled, but code overwriting and inconsistency occur
Solution Approach 1:
The patent divides the application into discrete blocks that can be independently locked and edited. Each block is a separate unit that can be locked for a specific user, allowing concurrent editing of different blocks while preventing overwriting within the same block. This segmentation enables multiple users to work simultaneously without causing code inconsistency.
Solution Approach 2:
The patent introduces a lock management system as an intermediary between users and the code blocks. This intermediary mechanism (the lock system) mediates access to blocks by assigning locks to specific users, controlling who can edit which blocks, and preventing direct conflicts between concurrent users. The lock system acts as a mediator that enables collaboration while maintaining code consistency.
2Reliability
If blocks are locked for single-user editing, then overwriting is prevented, but user access control complexity increases
Solution Approach 1:
The patent implements dynamic lock management where locks are assigned and revoked based on real-time user actions. The system dynamically determines which user should have access to a block based on current editing activity, and dynamically updates the lock status accordingly. This dynamic approach prevents overwriting while managing access control complexity through automated, real-time decisions rather than static rules.
Solution Approach 2:
The patent incorporates feedback mechanisms where the system monitors which user is actively editing a block and uses this feedback to automatically assign or revoke locks. When a user stops editing or navigates away, the system receives feedback about their inactivity and accordingly removes the lock, making it available for the next user. This feedback-driven approach simplifies access control by automating the lock assignment process based on actual usage patterns.
Data Source
AI summary
This disclosure relates to method and system for managing co-development of applications. The method includes receiving a request corresponding to a first user to edit a Graphical User Interface (GUI) of a development environment for an application. The application includes a plurality of pages, which includes a plurality of blocks. The method includes retrieving lock data of each of the plurality of blocks and a first set of user privileges associated with the first user. The lock data of each block includes a lock status. The method includes determining editability of the first user to each of the plurality of blocks based on the lock data of each of the plurality of blocks and the first set of user privileges. The method includes rendering the GUI on a first user device associated with the first user based on the determined editability.