Skip to content

Document initial modules to work on. #4

@BeyondMagic

Description

@BeyondMagic
Petalize (web client)

Purpose: is the front-end for the server, displays content, let user manage this module settings and other modules entirely, let user update modules through UI (although the server handles the request to update/add/remove modules, etc), etc.

  • Subscribe to receive Request from the server (not sure how to do this yet in a very generalizing way, or even if receiving Request is the answer, because the purpose of the server is back-end entirely, to parse the Request into a manageable thing for modules who are going to parse it into web resources);

Model Editor

2D model editor with different sized layers.

Capabilities:

  • a single web component (custom element) through a static JS file named <model-editor>.

The reason it's a module is that it can be remotely updated without having to interfere with the server running.

Usage:

  • At a domain/route, e.j: https://game.beyondmagic.space/editor, the user can simply select this capability (let's call it resource in the UI for comprehensiveness) in a list, and the file will be automatically loaded when the user enters that page, which then he can import in the content editor.

Progress-it

Tracks the progress you've made in life, whether it's a project, a personal goal, or a hobby.

Capabilities:

  • a web component

Database Visualizer

Visualize database structure and relationships.


Command Navigator

Commands can set commands in the navigator.

Recommended for:

  • quickly setup flashcard;
  • quickly setup page/content;
  • quickly set bookmarks;

Visualizer

Visualize all domains in different modes, like graph.

Expose a widget map.


Flashcard

Receives: no event.
Exposes:

[
	{
		"label": "decks":
		"interface": [
			{
				"type": "GET",
				"description": "List all available decks."
			}
		]
	},
	{
		"label": "flashcard@add":
		"data": {
		}
	},
]
  • Have a field be randomized based on a condition.

Startpage
  • Can access something random of the server (quotes data).

Storyboard
  • Divide story in hierarchy types:
    1. parenthicals:
    2. lines:
    3. dialogue:
    4. slugline:
    5. scene:
    6. chapter:
    7. arc:
    8. ...
    9. story:
    10. series:

Metadata

Metadata

Assignees

Labels

docsChanges to Continuous Integration files and scripts.researchFurther information is requested

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions