Danny McGee 03f87b2544 "Add to Scene" menu and Media Library dialog (#78)
This PR adds a new "Add to Scene" dropdown menu for adding elements to
the current scene, and a new Media Library dialog for importing and/or
adding Storyteller Engine assets (characters, scenes, animations, etc.)
associated with the user's Storyteller.ai account.

The scope of this PR is limited to the UI — actual asset importing
behavior, and adding elements other than primitive shapes to the current
scene, will be implemented in follow-up PRs.

### Technical Details

In order to facilitate these changes, a new "overlay" abstraction has
been added to `@storyteller/studio-ui` (loosely modeled after
[`@angular/cdk/overlay`](https://material.angular.io/cdk/overlay/overview))
for managing DOM elements which should render in a self-contained
stacking context "above" the rest of the application.

Two new base UI components &mdash; `<sts-menu>` and `<sts-dialog>`
&mdash; have also been added to make use of this overlay system, but
it's worth noting that these new components have not yet been
exhaustively tested or thoroughly fleshed out, so they may require
significant changes in order to accommodate future use cases or address
unforeseen bugs.

### Testing

The Media Library makes some API calls which will run into CORS errors
in a normal browser. This can be bypassed by running Chrome with the
following command-line flags:
```
--disable-web-security --ignore-certificate-errors --user-data-dir=path/to/some/temporary/directory
```
Verify all of the following:

* The "Add to Scene" menu opens and closes as expected
* The primitive-shape menu items (Cube, Sphere, etc.) add the
  corresponding elements to the scene
* The "Media Library..." menu item correctly opens the Media Library
  dialog
* The Media Library's search bar and category filters work as expected
* A single asset can be selected by clicking on it
* Multiple assets can be selected by holding the "Ctrl" or "Cmd" key
* The selection can be cleared by clicking in an empty space in the
  results grid
* An "Add to Scene" button appears if (and only if) one or more assets
  are selected
* The Media Library dialog can be closed by:
  - Clicking the "X" in the upper right-hand corner
  - Pressing the "Esc" key
  - Clicking anywhere outside of the dialog boundaries

Additionally, ensure that the Media Library dialog handles all of the
following situations gracefully:
* User is not logged in to fakeyou.com
* User is logged in but does not have any engine-compatible assets
  uploaded (this can be tested by selecting any of the categories from the
  sidebar, since the database has not yet been migrated to use the new
  `media_file_class` field, so all of those categories should currently
  yield an empty list)
* User is logged in and there are engine-compatible assets to list (this
  can be tested by pressing the "Save" button in the main application
  toolbar to save the current scene to your account, and selecting the
  "Home" entry from the Media Library sidebar)
2024-03-15 13:30:06 -04:00
2023-11-10 21:07:39 -05:00
2024-02-28 15:52:01 -05:00
2023-12-27 17:45:07 -05:00
2024-02-19 16:00:30 -07:00
2023-09-27 10:44:40 -04:00
2024-02-19 16:00:30 -07:00
2023-11-10 15:51:17 -05:00
2023-09-28 23:33:08 -04:00
2024-02-27 10:22:00 -07:00
2023-12-07 15:46:32 -05:00
2024-03-09 02:34:55 -05:00
2023-09-27 10:48:41 -04:00

Storyteller Studio

Installing dependencies

Building / Running / Testing stuff

This repo is managed by Nx, a polyglot build system and monorepo framework written in TypeScript. After installing dependencies, dev tasks can be run through the Nx CLI:

npx nx <command> <project> [options]
# OR
npx nx run <project>:<command> [options]

For example, to compile the Bevy app to WebAssembly and serve it via the web frontend project, run:

npx nx serve studio-frontend

You'll need to install the wasm compiler for Rust:

rustup target add wasm32-unknown-unknown

Projects are located in directories at the workspace root. The list of commands supported by a given project can be found under the target property of its project.json file, which defines the Nx configuration for that project.

The full list of options for a given command can be discovered by passing the --help flag:

npx nx <command> <project> --help
S
Description
Danny's Bevy exploration
Readme 316 MiB
Languages
Rust 59.2%
TypeScript 34.9%
SCSS 4.1%
JavaScript 1%
HTML 0.3%
Other 0.5%