Operation Stenen is a contemporary action plan (ACTPLAN) to refactor Vercengen 0.5b to 1.0b. Because this necessarily requires a top-down, rather than bottom-up static to dynamic refactor, it is complex enough to warrant its own operation, the details of which will be outlined below. In addition, there are numerous maintenance tasks that need to be handled, as well as consistency guarantees between different Vercengen Components. Vercengen also requires redocumentation after the completion of Operation Stenen.
The following is a chronological notice of what has been done and what remains to be done.
20 July 2025:
Note: This phase is only meant to get Vercengen to a point where elements are created dynamically instead of statically. See Phase 2. Class-based restructuring for details on splitting up Components into separate Classes.
Top-down refactoring should be done via element insertion, where elements are created dynamically in a shadow/non-actual DOM before insertion into the actual context menu/interface at hand. This would require element handling in .vercengen.js's ve.Component class within the main constructor for objects first.
Afterwards, individual components would need non-comprehensive refactors through the following functions, starting with createInput()'s shift to a dynamic return list:
Split up global.ve into FP/OOP bindings. Top-level classes (Window, PageMenu, Interface, etc) should be placed in their own files (beginning with numbers to maintain alphabetical order) and DOM-level Vercengen bindings should be placed in a separate vercengen_dom.js framework. Additionally, context menus should be folded in, and Vercengen JSON5 parsers will be placed in a logic/ as well as localisation/ folder for resolution.
Each Class should then receive JSDoc inline documentation for both their OOP functionality and their DOM bindings.