WYSIWYG Editor Using External Rendering Engine and Input Overlay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wysiwyg editors require their own rendering means, which can be underpowered and introduce errors, and necessitate rendering visual content twice before publication, increasing complexity and processing requirements.
Innovation Solution
A wysiwyg editor configured to work with an external rendering engine, where the rendering engine generates the visible portion of a document, and an overlay is used to intercept user inputs for editing the schema, eliminating the need for the editor to generate visual content and reducing rendering iterations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the wysiwyg editor uses its own rendering means to generate visible content, then the editor can independently display and edit visual content, but the rendering quality may be underpowered and introduce errors
Solution Approach 1:
The rendering function is extracted from the wysiwyg editor and delegated to a separate, dedicated rendering engine. This allows the editor to focus on editing operations while the rendering engine handles visual content generation with higher reliability and quality, eliminating the need for the editor to maintain its own rendering capabilities.
Solution Approach 2:
A schema document serves as an intermediary between the wysiwyg editor and the rendering engine. The editor edits the schema, which then serves as input to the rendering engine that generates the visible content. This intermediary structure enables reliable rendering while keeping the editor simple.
2Productivity
If the editor generates visual content separately and then passes it to the rendering engine, then the editor maintains independence, but the visual content must be rendered twice before publication
Solution Approach 1:
The intermediate rendering step performed by the editor is eliminated. The schema document directly serves as input to the final rendering engine, removing the redundant rendering process and enabling direct publication of rendering-ready content.
Solution Approach 2:
The schema document is prepared in advance with all necessary structural and content information that the rendering engine needs. This preliminary preparation of the schema ensures that the final rendering produces publication-ready content without requiring additional rendering iterations.
3Ease of operation
If the editor uses an overlay to intercept user inputs, then user interactions are directed to the editor for schema editing, but the overlay must be placed on top of the rendered visible content
Solution Approach 1:
The overlay acts as an intermediary layer between the user and the rendered content. It captures user inputs and translates them into schema editing operations, while the rendered content remains visible underneath. This enables intuitive WYSIWYG editing without requiring the editor to generate separate visual representations.
Data Source
AI summary
Systems and methods of editing a user experience by a what you see is what you get (wysiwyg) editor are disclosed. A system obtains a visible portion of a document object model for a document, with the visible portion including one or more visible objects to be presented to a user during a user experience. Instead of the visible portion being generated by the wysiwyg editor (thus requiring the visible portion to be rendered again at a later time by a rendering engine), the visible portion to be used is generated by the rendering engine based on a schema of the document. To allow such, the system generates and outputs an overlay to be placed on the visible portion during display of the visible portion, with the overlay to receive user inputs to the visible portion and thus prevent user interaction with the visible portion.