Text Editing Apparatus Non-Linear Block Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional text editing tools are limited in handling non-linear document creation and editing processes, lacking features for efficient block swapping, version comparisons, and proper attribution of text from multiple sources.
Innovation Solution
A text editing apparatus and method that utilizes a database memory to store a text database as a linked list of text portions with links, allowing a data processor to edit the text and links in response to user input, enabling non-linear editing, block swapping, version management, and attribution of text contributions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional text editing tools are used, then text can be edited linearly from start to end, but non-linear document creation and editing processes cannot be handled efficiently
Solution Approach 1:
The document is divided into discrete text blocks that can be independently stored and manipulated in a database. Each text block becomes a separate entity that can be accessed, moved, and edited independently, enabling non-linear editing operations such as block swapping and reordering without requiring sequential processing through the entire document.
Solution Approach 2:
The patent transitions from traditional linear text editing to a multi-dimensional editing model using a database structure. Text blocks can be organized hierarchically with parent-child relationships, allowing editors to navigate and manipulate content across multiple levels and dimensions rather than strictly following a linear sequence from start to end.
2Adaptability or versatility
If text is stored as a continuous linear document, then editing is simple, but block swapping and version comparisons become difficult
Solution Approach 1:
The document structure is segmented into discrete text blocks stored as separate database records. Each block has a unique identifier and can be independently manipulated. This segmentation enables efficient block swapping operations where blocks can be moved, copied, or deleted without affecting the entire document structure, while the database management system handles the complexity of maintaining relationships between blocks.
Solution Approach 2:
The database acts as an intermediary layer between the user interface and the actual text storage. It provides standardized operations for manipulating text blocks (insert, delete, move, copy) and automatically manages the underlying data structure complexity, allowing simple user operations to translate into complex database operations without requiring the user to understand the underlying complexity.
3Adaptability or versatility
If multiple text sources are combined, then content richness increases, but proper attribution of text contributions becomes difficult
Solution Approach 1:
Text from different sources is imported as separate text blocks with metadata that preserves attribution information. Each block retains information about its source, author, and origin, allowing the system to track and attribute contributions even as blocks are moved and reorganized within the document structure.
Solution Approach 2:
The database structure is designed to handle multiple types of information universally - text content, attribution metadata, source information, and relationship data all coexist in the same block structure. This universal design allows the system to simultaneously manage content richness from multiple sources while preserving all necessary attribution information through standardized field definitions.
4Adaptability or versatility
If version history is maintained, then collaboration improves, but storage requirements increase
Solution Approach 1:
Instead of storing complete document copies for each version, the system stores only the text blocks that have changed between versions. The database maintains version information by recording modifications to specific blocks rather than duplicating entire documents, significantly reducing storage requirements while preserving version history for collaboration.
Solution Approach 2:
Version control is implemented at the text block level rather than document level. When a document is edited, only the modified blocks are versioned and stored in the version history. This segmented approach to version management allows multiple versions to be maintained with minimal storage overhead, as unchanged blocks are not repeated in subsequent versions.
Data Source
AI summary
Text editing apparatus comprises a database memory configured to store a text database, in which the text database is configured to store a plurality of text portions and a set of links between text portions, the set of links defining a document as a linked list of the text portions; and a data processor configured, in response to user input, to perform an editing operation to edit the text database so as to define an edited document by changing at least one of: (i) text within a text portion and (ii) the set of links between text portions.