add v3 docs workflow

* Update image.go

* Update popupmenu.go

.github/workflows/build-and-test-alpha.yml

@@ -0,0 +1,119 @@
+name: Build + Test v3 alpha
+
+on:
+  push:
+    branches: [v3-alpha]
+  workflow_dispatch:
+
+jobs:
+  test_go:
+    name: Run Go Tests
+    if: github.repository == 'wailsapp/wails'
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        go-version: [1.21]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Install linux dependencies
+        if: matrix.os == 'ubuntu-latest'
+        run: sudo apt-get update -y && sudo apt-get install -y libgtk-3-dev libwebkit2gtk-4.0-dev build-essential pkg-config
+
+      - name: Setup Go
+        uses: actions/setup-go@v3
+        with:
+          go-version: ${{ matrix.go-version }}
+
+      - name: Run tests (mac)
+        if: matrix.os == 'macos-latest'
+        env:
+          CGO_LDFLAGS: -framework UniformTypeIdentifiers -mmacosx-version-min=10.13
+        working-directory: ./v3
+        run: go test -v ./...
+
+      - name: Run tests (!mac)
+        if: matrix.os != 'macos-latest'
+        working-directory: ./v3
+        run: go test -v ./...
+
+  test_js:
+    name: Run JS Tests
+    if: github.repository == 'wailsapp/wails'
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [18.x]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Install dependencies
+        run: npm install
+        working-directory: v2/internal/frontend/runtime
+
+      - name: Run tests
+        run: npm test
+        working-directory: v2/internal/frontend/runtime
+
+  test_templates:
+    name: Test Templates
+    needs: test_go
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: true
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        template:
+          [
+            svelte,
+            svelte-ts,
+            vue,
+            vue-ts,
+            react,
+            react-ts,
+            preact,
+            preact-ts,
+            lit,
+            lit-ts,
+            vanilla,
+            vanilla-ts,
+            plain,
+          ]
+        go-version: [1.21]
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Setup Go
+        uses: actions/setup-go@v3
+        with:
+          go-version: ${{ matrix.go-version }}
+
+      - name: Build Wails3 CLI
+        run: |
+          cd ./v3/cmd/wails3
+          go install
+          wails3 -help
+
+      - name: Install linux dependencies
+        if: matrix.os == 'ubuntu-latest'
+        run: sudo apt-get update -y && sudo apt-get install -y libgtk-3-dev libwebkit2gtk-4.0-dev build-essential pkg-config
+
+      - name: Generate template '${{ matrix.template }}'
+        run: |
+          go install github.com/go-task/task/v3/cmd/task@latest 
+          mkdir -p ./test-${{ matrix.template }}
+          cd ./test-${{ matrix.template }}
+          wails3 init -n ${{ matrix.template }} -t ${{ matrix.template }} -ci
+          cd ${{ matrix.template }}
+          wails3 build

.github/workflows/v3-docs.yml

@@ -0,0 +1,28 @@
+name: v3 docs
+on:
+  push:
+    branches:
+      - v3-alpha
+permissions:
+  contents: write
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: ./mkdocs-website
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-python@v4
+        with:
+          python-version: 3.x
+      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
+      - uses: actions/cache@v3
+        with:
+          key: mkdocs-material-${{ env.cache_id }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+      - run: pip install -r requirements.insiders.txt
+      - run: pip install git+https://${GH_TOKEN}@github.com/squidfunk/mkdocs-material-insiders.git
+      - run: mkdocs gh-deploy --force

Taskfile.yaml

@@ -16,6 +16,11 @@ includes:
     dir: v3
     optional: true
 
+  docs:
+    taskfile: mkdocs-website
+    dir: mkdocs-website
+    optional: true
+
 tasks:
   contributors:check:
     cmds:

mkdocs-website/README.md

@@ -0,0 +1,41 @@
+# v3 Docs
+
+This is the documentation for Wails v3. It is currently a work in progress.
+
+## Recommended Setup Steps
+
+Install the wails3 CLI if you haven't already:
+
+```shell
+go install github.com/wailsapp/wails/v3/cmd/wails3@latest
+```
+
+The documentation uses mkdocs, so you will need to install [Python](https://www.python.org/). Once installed, 
+you can setup the documentation by running the following command:
+
+```bash
+wails3 task docs:setup
+```
+
+This will install the required dependencies for you. 
+
+If you have installed the wails3 CLI, you can run the following command to build the documentation and serve it locally:
+
+```bash
+wails3 task docs:serve
+```
+
+### Manual Setup
+
+To install manually, you will need to do the following:
+
+  - Install [Python](https://www.python.org/)
+  - Run `pip install -r requirements.txt` to install the required dependencies
+  - Run `mkdocs serve` to serve the documentation locally
+  - Run `mkdocs build` to build the documentation
+
+
+## Contributing
+
+If you would like to contribute to the documentation, please feel free to open a PR!
+

mkdocs-website/Taskfile.yml

@@ -0,0 +1,53 @@
+# https://taskfile.dev
+
+version: '3'
+
+tasks:
+
+  setup:
+    summary: Setup the project
+    preconditions:
+      - sh: python{{exeExt}} --version
+        msg: "Looks like Python isn't installed. Python is required to build the documentation: https://www.python.org/downloads/"
+    cmds:
+      - python -m pip install -r requirements.txt --user
+
+  setup:insiders:
+    summary: Setup the project (insiders)
+    preconditions:
+      - sh: python{{exeExt}} --version
+        msg: "Looks like Python isn't installed. Python is required to build the documentation: https://www.python.org/downloads/"
+    cmds:
+      - python -m pip install -r requirements.insiders.txt --user
+
+  upgrade:insiders:
+    summary: Upgrade the project (insiders)
+    preconditions:
+      - sh: python{{exeExt}} --version
+        msg: "Looks like Python isn't installed. Python is required to build the documentation: https://www.python.org/downloads/"
+    cmds:
+      - python -m pip install -r requirements.insiders.txt --upgrade --user
+
+  build:
+    summary: Builds the documentation
+    preconditions:
+      - sh: mkdocs --version
+        msg: "Looks like mkdocs isn't installed. Run `wails3 task setup` or `task setup` in the documentation directory to install it."
+    cmds:
+      - mkdocs build
+
+  serve:
+    summary: Builds the documentation and serves it locally
+    preconditions:
+      - sh: mkdocs --version
+        msg: "Looks like mkdocs isn't installed. Run `wails3 task setup` or `task setup` in the documentation directory to install it."
+    cmds:
+      - mkdocs serve
+
+  serve:insiders:
+    summary: Builds the documentation and serves it locally
+    preconditions:
+      - sh: mkdocs --version
+        msg: "Looks like mkdocs isn't installed. Run `wails3 task setup` or `task setup` in the documentation directory to install it."
+    cmds:
+      - mkdocs serve --config-file mkdocs.insiders.yml

mkdocs-website/docs/appendix/_category_.json

@@ -1,4 +0,0 @@
-{
-  "label": "Appendix",
-  "position": 70
-}

mkdocs-website/docs/changelog.md

@@ -0,0 +1,36 @@
+# Changelog
+
+<!--
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+- `Added` for new features.
+- `Changed` for changes in existing functionality.
+- `Deprecated` for soon-to-be removed features.
+- `Removed` for now removed features.
+- `Fixed` for any bug fixes.
+- `Security` in case of vulnerabilities.
+
+-->
+
+## [Unreleased]
+
+
+### Added
+* [darwin] add getPrimaryScreen/getScreens to impl by @tmclane in https://github.com/wailsapp/wails/pull/2618
+
+### Fixed
+
+- Fixed background colours of examples on Windows by [mmgvh](https://github.com/mmghv) in [#2750](https://github.com/wailsapp/wails/pull/2750).
+- Fixed default context menus by [mmgvh](https://github.com/mmghv) in [#2753](https://github.com/wailsapp/wails/pull/2753).
+
+### Changed
+
+### Removed
+
+### Deprecated
+
+### Security
+

mkdocs-website/docs/community/_category_.json

@@ -1,4 +0,0 @@
-{
-  "label": "Community",
-  "position": 50
-}

mkdocs-website/docs/community/community.md

@@ -1,177 +0,0 @@
-# Community Guide
-
-The number of Wails users is growing at an incredible rate, and if you're reading this, chances are you're ready to join. So... welcome!
-
-## Resources
-
-### Code of Conduct
-
-This [Code of Conduct](./coc) is an easy guide to develop the technical communities in which we participate.
-
-### Stay in the Know
-
-- Follow our [official Twitter account](https://twitter.com/wailsapp).
-
-### Get Support
-
-- [GitHub](https://github.com/wailsapp/wails) - If you have a bug to report or feature to request, that's what the GitHub issues are for. Please respect the rules specified in each repository's issue template.
-- [Discord](https://discord.gg/JDdSxwjhGf) - A place for Wails devs to meet and chat in real time.
-- [QQ Group(中文)](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - A Wails group for Chinese developers to communicate, where you can get help from other developers.
-
-### Explore the Ecosystem
-
-- [The Awesome Wails Page](https://github.com/wailsapp/awesome-wails) - See what other awesome resources have been published by other awesome people.
-
-## Ways of contributing
-
-Wails is an open source, community driven project. We welcome anyone to join us in
-contributing to the project. This documentation is aimed at anyone wishing to get
-familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-
-Guides for these have been created in their own sections. Before getting started,
-please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520)
-discussion.
-
-### Developing New Features
-
-We are always keen to add features to Wails and expand on what the project can do.
-The process for adding new features are as follows:
-
-- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current
-  [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
-- Before developing, check that the ticket includes the following information:
-  - The purpose of the enhancement
-  - What is out of scope for the enhancement
-  - What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
-- If the ticket does not include this information, feel free to request the information from the
-  person who opened the ticket. Sometimes placeholder tickets are created and require more details
-- Comment on the ticket stating if you wish to develop the feature
-- Clone the repository and create a branch with the format `feature/<ticket_number>_<ticket_title>`
-- New features often require documentation so please ensure you have also added or updated the documentation as part of
-  the changes
-- Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and
-  test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-enhancement requests are reviewed for good fit. Not all ideas will be selected, so it's best to have discussion
-about the enhancement first.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-:::
-
-### Fixing Bugs
-
-The process for fixing bugs are as follows:
-
-- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
-- Before developing, check that the ticket includes the following information:
-- The scope of the issue including platforms affected
-- The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to
-  prove that it is a Wails issue with a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example)
-- The output of `wails doctor`
-- A test that can reproduce the bug
-- If the ticket does not include this information, feel free to request the information from the
-  person who opened the ticket.
-- Comment on the ticket stating you wish to develop a fix
-- Clone the repository and create a branch with the format `bugfix/<ticket_number>_<ticket_title>`
-- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and
-  test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-bugfixes should be discussed as the approach may have unintended side effects.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-:::
-
-### Testing
-
-Testing is vitally important to ensure quality in the project. There are a couple of
-scenarios where testing can really help the project:
-
-- Testing if a bug is reproducible on your local system
-- Testing PRs to ensure that they work correctly
-
-If you chose to test if someone's bug report is reproducible on your local system, then
-feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
-
-To test PRs, choose a PR to test and check if the PR description has the testing scenarios
-listed. If not, please ask the person who opened the PR to provide that list. Once you have
-determined a valid test scenario, please report your findings on the PR.
-
-If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520)
-discussion or on slack.
-
-### Documenting
-
-This website is also the main documentation site for the project. Sometimes this gets
-out of date and needs some slight adjustments. Some of the documentation isn't written
-to the best standards either. Developing documentation is hard and so any contribution
-to this is greatly appreciated. Features without documentation are unfinished so to the
-project, it's _as important_ as the code.
-
-We generally do not create tickets for updating documentation so if there is text you
-think should be updated or rephrased then feel free to submit a PR for that. This site
-is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create
-the site so there is plenty of existing documentation and tutorials around to get started.
-
-To set up a local documentation development environment, do the following:
-
-- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
-- `cd website`
-- `npm install`
-- `npm run start`
-
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000).
-Any changes made to the site text will be immediately reflected in the browser.
-
-#### Versioning
-
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which
-has all the changes that have occurred since the last release. We also keep the last release
-documentation as well as the version before that.
-
-There isn't usually a reason to update released documentation so we don't generally update
-the documents in the `versioned_docs` or `versioned_sidebars` directories.
-
-The "next version" docs are mainly in `website/docs` with some "version independent" documents
-in `src/pages`. Any updates should be made in the `website/docs` directory.
-
-#### Languages
-
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
-
-##### Add new language
-
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
-
-### Helping Others
-
-A great way to contribute to the project is to help others who are experiencing difficulty.
-This is normally reported as a ticket or a message on the Wails discord server. Even just
-clarifying the issue can really help out. Sometimes, when an issue is discussed and gets
-resolved, we create a guide out of it to help others who face the same issues.
-
-To join the Wails discord server, click [here](https://discord.gg/JDdSxwjhGf).
-
-:::note
-
-Work In Progress
-
-:::

mkdocs-website/docs/community/contributing.md

@@ -1,29 +0,0 @@
-# Contributing
-
-## Introduction
-
-Wails is a community project, and we welcome contributions from anyone. This document outlines the process for contributing to Wails.
-
-## Ways of contributing
-
-We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get
-familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-- Improving the documentation
-
-### Getting started
-
-To get started, clone the project repository:
-    
-```shell
-wails3 contribute
-```
-

mkdocs-website/docs/community/links.md

@@ -1,23 +0,0 @@
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom)
-to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Wails Discord Server](https://discord.gg/JDdSxwjhGf)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
-
-## Other Tutorials and Articles
-
-- [Building of Bulletin Board](https://blog.customct.com/building-bulletin-board)

mkdocs-website/docs/community/showcase/_category_.json

@@ -1,4 +0,0 @@
-{
-  "label": "Showcase",
-  "position": 1
-}

mkdocs-website/docs/community/showcase/bulletinboard.mdx

@@ -1,10 +0,0 @@
-# BulletinBoard
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img src={require("@site/static/img/showcase/bboard.webp").default} />
-  <br />
-</p>
-```
-
-The [BulletinBoard](https://github.com/raguay/BulletinBoard) application is a versital message board for static messages or dialogs to get information from the user for a script. It has a TUI for creating new dialogs that can latter be used to get information from the user. It's design is to stay running on your system and show the information as needed and then hide away. I have a process for watching a file on my system and sending the contents to BulletinBoard when changed. It works great with my workflows. There is also an [Alfred workflow](https://github.com/raguay/MyAlfred/blob/master/Alfred%205/EmailIt.alfredworkflow) for sending information to the program. The workflow is also for working with [EmailIt](https://github.com/raguay/EmailIt).

mkdocs-website/docs/community/showcase/emailit.md

@@ -1,10 +0,0 @@
-# EmailIt
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img src={require("@site/static/img/showcase/emailit.webp").default} />
-  <br />
-</p>
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a scripts terminal to run scripts in EmailIt on files in your system. The scripts and templates can be used from the commandline itself or with the Alfred, Keyboard Maestro, Dropzone, or PopClip extensions. It also supports scripts and themes downloaded form GitHub. Documentation is not complete, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.

mkdocs-website/docs/community/showcase/encrypteasy.mdx

@@ -1,12 +0,0 @@
-# EncryptEasy
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img src={require("@site/static/img/showcase/encrypteasy.webp").default} />
-  <br />
-</p>
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.

mkdocs-website/docs/community/showcase/filehound.mdx

@@ -1,24 +0,0 @@
-# FileHound Export Utility
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img src={require("@site/static/img/showcase/filehound.webp").default} />
-  <br />
-</p>
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with:
-Go 1.15
-Wails 1.11.0
-go-sqlite3 1.14.6
-go-linq 3.2
-
-Frontend with:
-Vue 2.6.11
-Vuex 3.4.0
-TypeScript
-Tailwind 1.9.6

mkdocs-website/docs/community/showcase/hiposter.mdx

@@ -1,10 +0,0 @@
-# hiposter
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img src={require("@site/static/img/showcase/hiposter.webp").default} />
-  <br />
-</p>
-```
-
-[hiposter](https://github.com/obity/hiposter) is a simple and efficient http API testing client tool. Based on Wails, Go and sveltejs.

mkdocs-website/docs/community/showcase/minecraftupdater.mdx

@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img
-    src={
-      require("@site/static/img/showcase/minecraft-mod-updater.webp").default
-    }
-  />
-  <br />
-</p>
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.

mkdocs-website/docs/community/showcase/modalfilemanager.mdx

@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img
-    src={require("@site/static/img/showcase/modalfilemanager.webp").default}
-  />
-  <br />
-</p>
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands, but a git install has to be on the system to download themes and extensions. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers. There are themes and extensions available to download from GitHub.

mkdocs-website/docs/community/showcase/mollywallet.mdx

@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-<p style={{ "text-align": "center" }}>
-  <img src={require("@site/static/img/showcase/mollywallet.webp").default} />
-  <br />
-</p>
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.