From 6f6f33573bdad44d3c367961bcd81393ba7bc3bf Mon Sep 17 00:00:00 2001 From: Robin Davies Date: Fri, 19 Aug 2022 08:30:09 -0400 Subject: [PATCH] Build break. --- docs/Architecture.md | 7 ++----- src/CMakeLists.txt | 2 +- 2 files changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/Architecture.md b/docs/Architecture.md index 180e4ba..3e48adc 100644 --- a/docs/Architecture.md +++ b/docs/Architecture.md @@ -1,12 +1,9 @@ ### PiPedal Architecture The PiPedal client is a web application written in React Framework, using Typescript. The bulk of the application is static content -compiled from TypeScript sources, using React Fraework tools. The static content is fetched from a web server hosted by the `pipedald` service. Once loaded, the web application +compiled from TypeScript sources, using React Framework tools. The static content is fetched from a web server hosted by the `pipedald` service. Once loaded, the web application opens a web socket connection to the `pipedald` server. Dynamic content is fetched over the web socket. The web client controls the server application using asynchronous json messages that are exchanged over the web socket. Changes to the state of the server application are propagated to all connected web clients via events that are fired by the server application over the web socket. Changes to the UI are (for the most part) implemented by binding state in the client-side PiPedalModel with state data in the React Framework view model. -The PiPedal client is generated by compiling Typescript source to a static web application consisting of HTML and Javascript -using React Framework tools. - The PiPedal server is written in C++. The server relies on an additional service, `pipedaladmind`, which provides privileged operations (e.g. shutdown, reboot, and configuration changes) for use by the main `pipedald` service which runs on a service account without privileges. @@ -27,7 +24,7 @@ Figure 2 shows the architecture of PiPedal when running with the React debug ser Fig 2. PiPedal architecture when using the React development server. -To debug React code, connect to the development server, on port 3000, with Chrome. To access the Chrome debugger, press F12. You should be able to browse the react source files from within the Chrome debugger. Load the typescript source file in the Chrome debugger. Once you have done that, you should be able to debug the Typescript code directly. Chrome will automaticallyt detect that it is connected to a React debug server, and will automatically download symbol and map files from the React development server. +To debug React code, connect to the development server, on port 3000, with Chrome. To access the Chrome debugger, press F12. You should be able to browse the React source files from within the Chrome debugger. Load the typescript source file in the Chrome debugger. Once you have done that, you should be able to debug the Typescript code directly. Chrome will automaticallyt detect that it is connected to a React debug server, and will automatically download symbol and map files from the React development server. When using the React development server, the web client can be configured to make web socket connections to either a debug version of the server, with a web server at port 8080, or a production server, with a web server at port 80. When running with the React development server, edit diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt index 0d1ecc5..46461d3 100644 --- a/src/CMakeLists.txt +++ b/src/CMakeLists.txt @@ -14,7 +14,7 @@ include(FindPkgConfig) # SDK. ################################################################# -set (ENABLE_VST3 1) +set (ENABLE_VST3 0) if (ENABLE_VST3)