UI Text String Management via Database File Structure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex software applications face challenges in efficiently organizing and maintaining user interface (UI) text strings due to a lack of contextual information, leading to redundancy, inconsistency, and difficulties in updating or revising these strings across multiple features and components.

Innovation Solution

The implementation of a methodology that associates UI text strings with contextual information using suitably configured database structures and file structures, allowing for unique identification and management of each string within a component-based file structure, thereby providing context for their appearance, behavior, and purpose.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If UI text strings are embedded directly in software code, then implementation is straightforward, but organization and maintenance become difficult and time-consuming

Engineering Contradiction:
ImproveEase of implementing UI text managementVSAvoidComplexity of organizing and maintaining UI text strings
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent extracts UI text strings from the software code and stores them in an external database structure. This separation allows the code to reference text strings by unique identifiers rather than containing the actual text, thereby improving organization and maintenance while reducing the complexity of managing UI text throughout the codebase.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a database structure as an intermediary between the software code and UI text strings. This database acts as a mediator that stores text strings with contextual information and allows code to reference them through identifiers, resolving the contradiction between easy implementation and ease of maintenance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If UI text strings are stored externally with contextual information, then maintenance and updating become efficient, but the system structure becomes more complex

Engineering Contradiction:
ImproveEfficiency of updating and maintaining UI text stringsVSAvoidComplexity of database and file structure configurations
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the UI text management system into distinct components: a database structure for storing text strings with contextual information, a file structure for organization, and code references using unique identifiers. This segmentation improves maintenance efficiency by allowing targeted updates while managing complexity through structured organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension to UI text management by introducing a database layer between the code and text strings. This dimensional change enables efficient maintenance through centralized storage and contextual information while managing complexity through structured data organization and identifier-based references.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If contextual information is associated with each UI text string, then consistency and reliability improve, but the data structure becomes more complex

Engineering Contradiction:
ImproveReliability of UI text string managementVSAvoidComplexity of database structure for storing contextual information
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal database structure that stores multiple types of contextual information (component context, feature context, translation status, etc.) in a standardized format. This multi-functional structure improves reliability by ensuring consistent information availability while managing complexity through a unified data model that can be applied across all UI text strings.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent changes the parameters of text string storage by adding contextual information fields to the database structure. This includes parameters such as component identifiers, feature identifiers, translation status, and other metadata. These parameter changes improve reliability by providing comprehensive context while managing complexity through structured data organization.

Inventive Principle:
Principle #35Parameter changes

4Loss of time

If text strings are updated without contextual context, then changes are quick to make, but errors and inconsistencies increase

Engineering Contradiction:
ImproveTime required to update UI text stringsVSAvoidConsistency of UI text strings across features
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent performs preliminary action by storing all contextual information (component context, feature context, relationships) in the database structure before updates are needed. This pre-established context allows for quick updates through identifier references while maintaining reliability, as the contextual framework is already in place to ensure consistent changes across the system.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11604765B2Database and file structure configurations for managing text strings to be provided by a graphical user interface
Publication Date: 2023.03.14 SALESFORCE INC
  • US11604765B2 patent drawing
  • US11604765B2 patent drawing
  • US11604765B2 patent drawing

AI summary

A computer-implemented database system as described herein includes a memory device and one or more processors coupled with the memory device. The one or more processors are configurable to create and maintain a folder structure for a user interface (UI) environment, wherein the folder structure includes: a feature folder that defines an application feature supported by the UI environment, the application feature having a UI component associated therewith, and the UI component having a UI text string associated therewith; a component folder located in the feature folder, the component folder having computer readable files that define the UI component; and a text string file located in the component folder, wherein the text string file defines content of the UI text string.