Restructur and start dedicated pages for user tutorials #7
36
docs/01-overview.md
Normal file
36
docs/01-overview.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
|
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Overview
|
||||
|
||||
Stardust XR _(formerly known as Stardust)_ is an XR [display server](https://itsfoss.com/display-server) designed for Linux-based systems<!-- (possibly most unix-based too, but untested)-->.<br/>
|
||||
Unlike traditional display servers that focus on 2D screens, Stardust XR introduces new conventions to utilize unbounded 3D space in virtual or real environments.
|
||||
|
||||
## Priorities
|
||||
|
@technobaboo please check if i narrowd it down @technobaboo please check if i narrowd it down
seems pretty good, yea!! seems pretty good, yea!!
|
||||
|
||||
- **3D Environment Focus**: While supporting 2D clients through the Wayland protocol, Stardust XR primarily aims to create and manage 3D environments.
|
||||
|
||||
- **Standard Interfaces**: Utilizes Wayland and OpenXR for 2D and XR app integration.
|
||||
|
||||
- **Stardust Protocol**: Implements a special protocol for:
|
||||
- Creating virtual objects
|
||||
- Developing 3D UIs around 2D apps (Panel Shells)
|
||||
- Handling data as Items that can represent files, Wayland surfaces, etc.
|
||||
|
||||
- **Personal Device Interaction**: Focuses on individual user interactions rather than collaborative 3D spaces.
|
||||
|
||||
- **Flexible Object Interaction**: Users can choose objects that best suit their current scenario, with easy setup for default configurations.
|
||||
|
||||
## Architecture
|
||||
|
||||
TODO: add some diagram of the core components needed and how they interface
|
||||
<!-- example: https://woodpecker-ci.org/docs/next/usage/terminology#woodpecker-architecture -->
|
||||
|
||||
## Projects & Components
|
||||
|
||||
|
that is the part where I'm most lacking ... I would say merge this pull and discust this list in a new pull that is the part where I'm most lacking ... I would say merge this pull and discust this list in a new pull
sure thing sure thing
|
||||
- [**telescope**](https://github.com/StardustXR/telescope): bundle most used components to have a demo environment set up
|
||||
- ...
|
||||
|
||||
<!-- TODO: add more core components and projects! -->
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Overview
|
||||
|
||||
## Description
|
||||
Stardust XR (informally known as Stardust) is an XR display server for Linux-based distros (possibly most unix-based too, but untested). Unlike display servers of the past that were run on bounded 2D screens, Stardust has to break convention in order to account for unbounded 3D space in any potential virtual or real environment.
|
||||
|
||||
Unlike many display servers, Stardust is not trying to reinvent how applications interface with the system. Stardust uses Wayland and will use OpenXR for 2D/XR app integration. Stardust however has a special protocol for creation of virtual objects such as 3D UIs around 2D apps (called Panel Shells) and handling of data as objects (called Items, can represent files or Wayland surfaces or such). Stardust is not a collaborative 3D space, instead focusing on your own personal device and interactions with it.
|
||||
|
||||
Put simply, Stardust is a system UI base where multiple different clients (programs that connect to Stardust directly) can create objects for the user to interact with their apps and device. The user can choose to use the objects that work best for their current scenario, and default setups can easily be created so users start out with all the essentials.
|
||||
86
docs/02-getting-started/01-tutorial.md
Normal file
86
docs/02-getting-started/01-tutorial.md
Normal file
@@ -0,0 +1,86 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Tutorial
|
||||
|
||||
## Setup OpenXR
|
||||
|
||||
:::note
|
||||
if you have no headset or other OpenXR device, you can skip this step and start with [installing nix](#install-nix).
|
||||
:::
|
||||
|
||||
### SteamVR
|
||||
|
||||
#### Archlinux
|
||||
|
||||
TODO
|
||||
|
||||
#### NixOS
|
||||
|
||||
TODO
|
||||
|
||||
#### Others
|
||||
|
||||
TODO: collect links for setup on different distrons
|
||||
|
||||
### [Monado](https://monado.dev/)
|
||||
|
||||
#### Archlinux
|
||||
|
||||
TODO
|
||||
|
||||
#### NixOS
|
||||
|
||||
TODO
|
||||
|
||||
#### Others
|
||||
|
||||
TODO: collect links for setup on different distrons
|
||||
|
||||
## Install nix
|
||||
|
||||
For easy development and distribution this project uses the [nix package manager](https://nix.dev/).<br/>
|
||||
This allows to ensure all dependency requirements are met.
|
||||
|
||||
:::info
|
||||
Make sure to have [flakes enabled](https://nixos.wiki/wiki/flakes).
|
||||
:::
|
||||
|
||||
You can install nix on all common linux systems:
|
||||
|
||||
#### Archlinux
|
||||
|
||||
```shell
|
||||
# install git and nix
|
||||
sudo pacman -Sy git nix
|
||||
# enable flakes
|
||||
echo 'experimental-features = nix-command flakes' | sudo tee -a /etc/nix/nix.conf
|
||||
# enable nix daemon service
|
||||
sudo systemctl enable nix-daemon.service
|
||||
# add the current user to nix-users group
|
||||
sudo usermod -aG nix-users $(id -un)
|
||||
# reboot to apply user and service changes
|
||||
sudo systemctl reboot
|
||||
```
|
||||
|
||||
#### NixOS
|
||||
|
||||
TODO
|
||||
|
||||
#### Others
|
||||
|
||||
TODO: collect links for setup on different distrons
|
||||
|
||||
## Run Demo
|
||||
|
||||
1. clone https://github.com/StardustXR/telescope
|
||||
2. make sure your OpenXR device works (if 2D mode is not used)
|
||||
3. run `nix run .`
|
||||
|
||||
## Run wayland client
|
||||
|
||||
```shell
|
||||
# run demo.mp4 video in a loop within Stardust
|
||||
WAYLAND_DISPLAY=wayland-0 DISPLAY= mpv Downloads/demo.mp4 --loop
|
||||
```
|
||||
@@ -36,4 +36,4 @@ The Stardust XR IPC uses Unix domain sockets for communication and a protocol ba
|
||||
The Stardust XR protocol is object-oriented, depending on a scenegraph on the server end and scenegraph or functionally equivalent structure on the client end. This allows easier implementation of the protocol while still remaining fast, reliable, and extensible.
|
||||
|
||||
## Clients
|
||||
The clients tell the server what models to draw, where they would like to accept input in, etc. Stardust clients are much more suited to widgets or user interfaces to 2D/XR apps.
|
||||
The clients tell the server what models to draw, where they would like to accept input in, etc. Stardust clients are much more suited to widgets or user interfaces to 2D/XR apps.
|
||||
@@ -14,4 +14,4 @@ Non-exhaustive list of clients:
|
||||

|
||||
- [Gravity](https://github.com/StardustXR/gravity): Command line tool to launch programs inside of stardust at a particular offset in space. This is nestable so you can run a script using gravity, and then gravity inside that script to make a whole composed setup out of thin air! It also ensures that everything launched through it will properly connect to the stardust server, such as wayland clients.
|
||||
- [Protostar](https://github.com/StardustXR/protostar): Prototype app launcher library/examples. Grab app icons and drop them in space to launch apps where they're dropped.
|
||||
- [Magnetar](https://github.com/StardustXR/magnetar): Workspaces in 3D. Any object inside the rings will move with them, so you can move a bunch of stuff out of the way temporarily when you don't need it.
|
||||
- [Magnetar](https://github.com/StardustXR/magnetar): Workspaces in 3D. Any object inside the rings will move with them, so you can move a bunch of stuff out of the way temporarily when you don't need it.
|
||||
@@ -26,4 +26,4 @@ and include the `stardust-xr-fusion` dependency in your `cargo.toml`. Documentat
|
||||
|
||||
## Molecules
|
||||
|
||||
`stardust-xr-molecules` is an even higher level widget library built on Fusion similar to [MRTK](https://github.com/microsoft/MixedRealityToolkit-Unity) to get your clients up and running faster. Documentation will be available at https://docs.rs/crate/stardust-xr-molecules/latest.
|
||||
`stardust-xr-molecules` is an even higher level widget library built on Fusion similar to [MRTK](https://github.com/microsoft/MixedRealityToolkit-Unity) to get your clients up and running faster. Documentation will be available at https://docs.rs/crate/stardust-xr-molecules/latest.
|
||||
@@ -1,4 +1,4 @@
|
||||
{
|
||||
"label": "Getting Started",
|
||||
"position": 1
|
||||
"position": 2
|
||||
}
|
||||
4
docs/09-terminology.md
Normal file
4
docs/09-terminology.md
Normal file
@@ -0,0 +1,4 @@
|
||||
# Glossary
|
||||
|
||||
- **Item**:
|
||||
- **Panel Shells**: 3D UIs around 2D apps
|
||||
|
this allso needs input from the @technobaboo this allso needs input from the @technobaboo
uhhh yeah for now that's probably the only glossary item that's unknown by XR devs, will need to revisit it though uhhh yeah for now that's probably the only glossary item that's unknown by XR devs, will need to revisit it though
well If you know a good source where the OpenXR glossary is documented I'll just refference it and we can only document stardust specific terms here ... else if such thing does not exist, we can be the list for others ... not everybody is an XR dev >D well If you know a good source where the OpenXR glossary is documented I'll just refference it and we can only document stardust specific terms here ... else if such thing does not exist, we can be the list for others ...
_not everybody is an XR dev >D_
|
||||
@@ -76,7 +76,7 @@ module.exports = {
|
||||
},
|
||||
{
|
||||
label: 'Getting Started',
|
||||
to: '/docs/getting-started/overview',
|
||||
to: '/docs/getting-started/tutorial',
|
||||
},
|
||||
],
|
||||
},
|
||||
|
||||
@@ -19,7 +19,7 @@ function HomepageHeader() {
|
||||
<div className={styles.buttons}>
|
||||
<Link
|
||||
className="button button--secondary button--lg"
|
||||
to="/docs/getting-started/overview">
|
||||
to="/docs/getting-started/tutorial">
|
||||
Get Started
|
||||
</Link>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user
I have no idea but @technobaboo if you provide me with an scetch I'll create an mermaidjs out of it
sorry it took me so long but i got it!
it doesn't cover everything but the basic architecture
depends on #9I just used your image for now ...