- engine canvas is passed to editor as a DOM reference
- camera view canvas is passed to editor as a DOM reference
- scene container is passed to editor as a DOM reference
- amended all the editor code that wants to do a DOM query using DOM ID
to use the variable that stores the reference
- added guard functions to query the DOM-ID just incase the reference is
lost due to a re-render
- the above change guarantees the reference to the DOM, fixes the bug
where the editor cannot read the size of DOM elements, and increases
stability of the app in general.
Co-authored-by: wil <wil@storyteller.ai>
- All components to should talk to the editor via the Queue
- useQueueHandler itself now resides in the page level collection of
hooks
Co-authored-by: wil <wil@storyteller.ai>
make it so that new devs cant just run the code without deliberately
moved the env variables, this makes sure they are aware of the proxy
server for CORS and what the env variables are
Co-authored-by: wil <wil@storyteller.ai>
supress error for process env, added vscode setting to gitignore
segrgate enums (#369)
Co-authored-by: Christopher Oliphant
<RALifeCoach@users.noreply.github.com>
Refactor storybook (#370)
Co-authored-by: Christopher Oliphant
<RALifeCoach@users.noreply.github.com>
button dropdown docs (#372)
storybook doc for button dropdown component
refactor side panel tabs (#371)
Co-authored-by: Christopher Oliphant
<RALifeCoach@users.noreply.github.com>
fix enums (#373)
Co-authored-by: Christopher Oliphant
<RALifeCoach@users.noreply.github.com>
Refactoring Auth Context to Signals (#374)
- file restructure, store -> signals
- rewrite AuthContext to signals, and get rid of AuthContext
- modify all files that need to use AuthContext to use the
authentication Signal
- the complex login persistency logic is now just a persistLogin
function ran at root!
- fetchers uses the auth signal directly to get the sessionToken
- components no longer useSignals for these fetchers, hence decoupled
from the auth signals
!! components and fetchers that are definitely subjected to refactor
does not receive the useSignal decoupling treatment
Co-authored-by: wil <wil@storyteller.ai>
Refactoring Toaster Context to a Toaster Component + Signal (#378)
- Created the Toaster Component
- Created the Toasts Signal
- Now no useContext is needed for Toast Poping, nor passing AddToast
around
- Simply import addToast from the Signals and you can pop a toast from
anywhere in the codebase
Co-authored-by: wil <wil@storyteller.ai>
Refactoring AppUi Context (partial: delete unused, editorLoader becomes
signal) (#379)
- dialogueTTS is unused, hence deleted
- view side-by-side mode is unused, hence deleted
- timeline height in this context was already made into signal, hence
deleted
- editorLoader in this context is now made into a page level signal,
hence deleted
- components and dispatcher of the editorLoader are modified to use
signal instead
- app level reducer is no longer used, tugged into context folder to
avoid confusion, will be deleted when all attributes in AppUi context is
refactored into signals
Co-authored-by: wil <wil@storyteller.ai>
Refactor control panel (#391)
- control panel - simplified and improved
- Please also test it. It operates slightly differently. For example, if
the user types an invalid character, the character is ignored.
---------
Co-authored-by: Christopher Oliphant
<RALifeCoach@users.noreply.github.com>
Refactoring App Level Components
- Components that are in the /app/component folder are split into
reusable and signaled
- reusable are in theory signal independent
- signaled are dependent on signals (and maybe a use-once component)
- some app level components has page level enums or signals, those are
bumped to app level now
- all components in the module directory are moved into the component
directories depending on whether it's reusable or signaled
- code changes in are mostly just import changes to get re-target to get
the correct files
- discovered a small bug in FilterButtons and is fixed
- whether a component need more work, it is commented on the index file
that import them into the grand collection of components
Refactor - Signals Part 2
- store is renamed to signals in PageEditor for clarity
- ObjectControlPanel now uses a Signal instead of the AppUiContext
- Moved EditorContext to Page Level, all context are page level only now
- editor is modified to read and use signals directly (for now), this
includes: -- the ObjectPanel signal
-- the Scene signal
-- the Authentication signal
- and hence, editor now has a constructor doesn't require any arguments
- editor also has a simple initialization
- AppUiContext is retired completely and deleted
---------
Co-authored-by: wil <wil@storyteller.ai>
Co-authored-by: Christopher Oliphant <RALifeCoach@users.noreply.github.com>
**Basic Usage** (just wrap it over any feature you want to premium
lock):
`<PremiumLock requiredPlan="any">
<div>Content for premium users</div>
</PremiumLock>`
This component still needs to be linked with the API.
- fixed by giving a proper filename.
- not fixed: filename exists, but is untitled, need to wait for backend
update to get a proper title
Co-authored-by: wil <wil@storyteller.ai>
FromTheLOLAshesandChristopher Oliphant
BFlat
wilandwil
ArEnSc
Brandon Thomas
Miles Ryan
Victor OandVictor