status-desktop/storybook
Alex Jbanca 00fb1ff60a
fix(WC): Refactor dapps service to work with multiple SDKs
This PR is refactoring the dapps service to avoid code duplication between SDKs and also to avoid overlapping requests/responses.
It brings Browser Connect inline with Wallet Connect in terms of session management and sign transactions.

New architecture:

WalletConnectService becomes DAppsService. Its responsibility is to provide dapp access to the app. This is the component currently used by the UI
What does it do:
1. Provide dapp APIs line connect, disconnect, session requests etc
2. Spawn app notifications on dapp events
3. Timeout requests if the dapp does not respons

DAppsRequestHandler becomes DAppsModule. This component is consumed by the DAppService. Its responsibility is to aggregate all the building blocks for the dapps, but does not control any of the dapp features or consume the SDKs requests.
What does it do:
1. Aggregate all the building blocks for dapps (currently known as plugins)

DAppConnectionsPlugin - This component provides the session management features line connect, disconnect and provide a model with the connected dapps.
SignRequestPlugin - This component provides the sign request management. It receives the sign request from the dapp, translates it to what Status understands and manages the lifecycle of the request.
2024-11-09 00:38:52 +02:00
..
pages fix(WC): Refactor dapps service to work with multiple SDKs 2024-11-09 00:38:52 +02:00
qmlTests fix(WC): Refactor dapps service to work with multiple SDKs 2024-11-09 00:38:52 +02:00
src Storybook: added ability to mark pages with their status 2024-10-30 18:23:11 +01:00
stubs fix(WC): Refactor dapps service to work with multiple SDKs 2024-11-09 00:38:52 +02:00
tests chore(Storybook): Exclude DirectoryFilesWatcher from PagesModel, add tests 2023-10-16 13:37:08 +02:00
CMakeLists.txt Storybook: switch to determine how to resolve stores' paths in QtCreator 2024-10-24 09:30:19 +02:00
README.md chore(Storybook): Update Readme to point CMakeLists.txt as the main way to build instead of WebAssembly 2023-03-01 13:48:31 +01:00
StoryBook.pro move qzxing and SortFilterProxyModel to vendor folder 2023-03-23 12:09:19 +01:00
cachecleaner.cpp
cachecleaner.h
directorieswatcher.cpp
directorieswatcher.h
directoryfileswatcher.cpp chore(Storybook): Exclude DirectoryFilesWatcher from PagesModel, add tests 2023-10-16 13:37:08 +02:00
directoryfileswatcher.h chore(Storybook): Exclude DirectoryFilesWatcher from PagesModel, add tests 2023-10-16 13:37:08 +02:00
figmaio.cpp
figmaio.h
figmalinks.cpp
figmalinks.h
figmalinksmodel.cpp
figmalinksmodel.h
main.cpp Introduce ability of calling StatusQ methods from nim 2024-10-11 23:37:50 +02:00
main.qml Storybook: added ability to mark pages with their status 2024-10-30 18:23:11 +01:00
modelutils.cpp
modelutils.h
pagesmodel.cpp Storybook: added ability to mark pages with their status 2024-10-30 18:23:11 +01:00
pagesmodel.h Storybook: added ability to mark pages with their status 2024-10-30 18:23:11 +01:00
sectionsdecoratormodel.cpp feat(Storybook): reflect pages model changes in sections decorator model 2023-10-02 11:17:56 +02:00
sectionsdecoratormodel.h feat(Storybook): reflect pages model changes in sections decorator model 2023-10-02 11:17:56 +02:00
storybook-resources.qrc chore(storybook) load WalletConnect SDK in storybook by QRC for now 2024-05-20 15:09:57 +02:00
systemutils.cpp feat(wallet) Wallet Connect integration prototype 2023-10-30 09:29:33 +01:00
systemutils.h feat(wallet) Wallet Connect integration prototype 2023-10-30 09:29:33 +01:00
testsrunner.cpp feat(Storybook): Open tests dir from the app 2023-10-16 13:37:08 +02:00
testsrunner.h feat(Storybook): Open tests dir from the app 2023-10-16 13:37:08 +02:00
validator_main.cpp Introduce ability of calling StatusQ methods from nim 2024-10-11 23:37:50 +02:00

README.md

Building Storybook

For regular usage of Storybook it's enough to open status-desktop/storybook/CMakeLists.txt in QtCreator. Please do not use StoryBook.pro which is intended for WebAssembly builds. Please make sure that selected run target is Storybook.

Building Storybook with Webassembly and Qt 5.14

Configuring the environment

Install Emscripten v1.38.27

# Get the emsdk repo
git clone https://github.com/emscripten-core/emsdk.git

#go to emsdk folder
cd emsdk

#install Emscripten v1.38.27
./emsdk install emscripten-1.38.27

#activate emscripten-1.38.27
./emsdk activate emscripten-1.38.27

#install Fastcomp backend
./emsdk install fastcomp-clang-tag-e1.38.27-64bit

#activate Fastcomp backend
./emsdk activate fastcomp-clang-tag-e1.38.27-64bit

#add emsdk tools to env variables
#this can be done by following instructions received from previous activate command
#there are two options:

#1. Configure the env variables for the current shell only:
source emsdk_env.sh

#2. Configure the env variables using the shell startup script:
echo 'source "[path to emsdk folder]/emsdk_env.sh"' >> $HOME/.zprofile

#WARNING: this will configure the environment to use the emsdk compiler
#Ex:"which clang" command will now point to the emscripten clang instead of the system clang
#to disable the env configuration comment the source command added earlier in ~/.zprofile

#check environment
#python needs to be installed. The emsdk scripts state that it should work with pyton 2 and 3
#make sure python command can be resolved
which python
em++ --version
emcc --version
#clang should point to fastcomp-clang-tag-e1.38.27-64bit
which clang
which clang++

More documentation: https://emscripten.org/docs/getting_started/downloads.html

Configure QtCreator (optional)

Newer versions of QtCreator won't support Qt5.14 with Webassembly. Latest version found to support Qt5.14 with WebAssembly is 4.14.2 Download: https://download.qt.io/archive/qtcreator/4.14/

Adding the Emscripten compilers (emcc and em++) Details here: https://doc.qt.io/qtcreator/creator-tool-chains.html

Adding Qt version 5.14: https://doc.qt.io/qtcreator/creator-project-qmake.html

Adding Qt5.14 for Webassembly kit: https://doc.qt.io/qtcreator/creator-targets.html

Open StoryBook.pro in Qt Creator and configure it using the new kit.

Qt creator might not set the env paths correctly. In this case manually set build environment variables (Projects -> 5.14.2 kit -> Build -> Build Environment -> Batch edit). Ex:

EMSCRIPTEN=~/Repos/emsdk/emscripten/1.38.27
EMSDK=~/Repos/emsdk
EMSDK_NODE=~/Repos/emsdk/node/14.18.2_64bit/bin/node
EMSDK_PYTHON=~/Repos/emsdk/python/3.9.2_64bit/bin/python3
EM_CONFIG=~/Repos/emsdk/.emscripten
LLVM_ROOT=~/Repos/emsdk/fastcomp-clang/tag-e1.38.27/build_tag-e1.38.27_64/bin
PATH=[check echo $PATH]

Running qmake (without qt Creator)

#create build folder
mkdir buildStoryBook

#go to folder
cd buildStoryBook

#run qmake (add CONFIG+=debug CONFIG+=qml_debug to qmake command for debug build)
~/Qt/5.14.2/wasm_32/bin/qmake [path to StoryBook.pro] -spec wasm-emscripten && /usr/bin/make qmake_all

#build (add -j[nb of cores] for parallel execution)
make

#run
emrun StoryBook.html