Merge pull request #300 from open-edge-platform/update-branch

Update Edge AI Studio (#806)

Author: gooishin

usecases/ai/edge-ai-studio/.gitignore

@@ -36,3 +36,5 @@ tmp
 !/out/README.md
 !/out/run_web.sh
 !/out/setup.sh
+!/out/run_web.ps1
+!/out/setup.ps1

usecases/ai/edge-ai-studio/.vscode/extensions.json

@@ -11,7 +11,14 @@ Edge AI Studio is a modern toolkit for deploying, managing, and serving AI model
 - **Easy Model Deployment:** Download, convert, and serve Hugging Face models with minimal setup.
 - **Web-Based Management:** Manage devices, workloads, and users through a modern web interface.
 - **Edge Optimized:** Built for Intel hardware and edge environments.
-
+- **AI Services:** AI Services that users can use for their applications
+  - Text Generation (LLM)
+  - Text to Speech (TTS)
+  - Speech to Text (STT)
+  - Embedding 
+  - Lipsync
+- **Samples:** Samples use cases that implements the ai services
+  - Digital Avatar
 
 ## Software Requirements
 

usecases/ai/edge-ai-studio/.vscode/launch.json

@@ -1,2 +1,5 @@
-/node_modules
-/out
+node_modules/
+dist/
+logs/
+*.log
+.DS_Store

usecases/ai/edge-ai-studio/.vscode/settings.json

@@ -1,73 +1,134 @@
-# Edge AI Studio - Electron App
+# Edge AI Studio - Electron Builder Version
 
-This directory contains the Electron application for Edge AI Studio.
+This directory contains the Electron Builder implementation of Edge AI Studio, running in parallel with the Electron Forge version for comparison and testing.
 
-## Development
+## Differences from Electron Forge
 
-### Prerequisites
+| Feature | Electron Forge | Electron Builder |
+|---------|---------------|------------------|
+| Configuration | `forge.config.js` | `build` in `package.json` |
+| Package Command | `electron-forge package` | `electron-builder --dir` |
+| Make Command | `electron-forge make` | `electron-builder` |
+| Dependencies | Multiple `@electron-forge/*` packages | Single `electron-builder` package |
 
-Before starting, ensure you have the following installed:
+## Setup
 
-- **Node.js** and **npm**
+From the project root, run:
 
-If you're behind a proxy, export the following environment variable before installing dependencies:
+```bash
+# Linux/macOS
+./setup.sh
 
-For Linux/macOS:
+# Windows PowerShell
+./setup.ps1
+```
+
+Or setup just this directory:
 
 ```bash
-export ELECTRON_GET_USE_PROXY=http://proxy:port
+# Linux/macOS
+cd electron-builder
+./setup.sh
+
+# Windows PowerShell
+cd electron-builder
+./setup.ps1
 ```
 
-For Windows (PowerShell):
+## Development
+
+### Start in Development Mode
 
-```powershell
-$env:ELECTRON_GET_USE_PROXY="http://proxy:port"
+```bash
+cd electron-builder
+npm start
 ```
 
+This will launch the Electron app pointing to your local frontend server.
 
-### Starting the Electron App
+## Building
 
-To start the Electron app in development mode:
+### Build Package Directory (No Installer)
 
 ```bash
-npm run start
+cd electron-builder
+npm run build:dir
 ```
 
-### Packaging the Electron App
+This creates an unpacked directory at `../out/linux-unpacked/` (or `win-unpacked` on Windows).
 
-To package the Electron app for distribution:
+### Build Distributable
 
 ```bash
-npm run make
-```
+# Linux
+npm run build:linux
 
-**Note:** Before running `npm run make`, ensure that all dependencies are set up properly by running the package script:
+# Windows
+npm run build:win
 
-```bash
-../scripts/package.sh
+# Both
+npm run build
 ```
 
-This script will help ensure all dependencies are installed and configured correctly before packaging.
+This creates distributable installers:
+- **Linux**: ZIP and DEB files
+- **Windows**: Squirrel installer
+
+Output is in `../out/`.
+
+## Configuration
+
+The build configuration is in `package.json` under the `build` key. Key settings:
+
+- **appId**: `com.intel.edge-ai-studio`
+- **productName**: `EdgeAIStudio`
+- **extraResources**: Copies `frontend`, `workers`, and `scripts` from `../build/`
+- **electronFuses**: Same security settings as Forge version
+- **Linux targets**: ZIP and DEB
+- **Windows targets**: Squirrel
 
-## Running on Ubuntu 24.04
+## Package Script
 
-If you're running the packaged Electron app on Ubuntu 24.04, you may need to adjust AppArmor settings to allow the application to run properly:
+To use the automated package script (similar to Forge):
 
 ```bash
-sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
+cd ../scripts
+./package-builder.sh
 ```
 
-This command disables AppArmor restrictions on unprivileged user namespaces, which is required for Electron apps to function correctly on Ubuntu 24.04.
+This will:
+1. Create `../build/` directory
+2. Copy workers (excluding `.venv`, `__pycache__`, etc.)
+3. Copy scripts
+4. Build frontend
+5. Run `electron-builder`
+6. Create final ZIP package
+
+## Comparing with Forge
+
+Both versions are functionally identical. You can test both to compare:
+
+1. **Build time**: Which is faster?
+2. **Package size**: Any difference in final output?
+3. **Ease of use**: Which configuration is clearer?
+4. **Features**: Any missing capabilities?
+
+## Migration Status
 
-## Project Structure
+✅ **Completed**:
+- Package.json with build configuration
+- All source files (main.js, preload.js, splash files)
+- Setup scripts (Linux & Windows)
+- Electron Fuses configuration
+- Extra resources configuration
 
-- `main.js` - Main Electron process
-- `preload.js` - Preload script for renderer process
-- `splash.html` - Splash screen HTML
-- `splash.js` - Splash screen JavaScript
-- `forge.config.js` - Electron Forge configuration
-- `logs/` - Application log files
+📋 **To Do**:
+- Create package script for automated builds
+- Test on Windows
+- Compare output with Forge version
 
-## Prerequisites
+## Notes
 
-Make sure you have Node.js and npm installed before running the commands above.
+- The `main.js` file is identical to the Forge version
+- Output directory is shared (`../out/`) but different subdirectories
+- Both versions can coexist without conflicts

usecases/ai/edge-ai-studio/README.md

@@ -0,0 +1,45 @@
+// Copyright (C) 2025 Intel Corporation
+// SPDX-License-Identifier: Apache-2.0
+
+const { flipFuses, FuseVersion, FuseV1Options } = require('@electron/fuses');
+const path = require('path');
+
+exports.default = async function (context) {
+  const { electronPlatformName, appOutDir } = context;
+  
+  let electronBinaryPath;
+  
+  if (electronPlatformName === 'darwin') {
+    electronBinaryPath = path.join(
+      appOutDir,
+      `${context.packager.appInfo.productFilename}.app`,
+      'Contents',
+      'MacOS',
+      context.packager.appInfo.productFilename
+    );
+  } else if (electronPlatformName === 'win32') {
+    electronBinaryPath = path.join(
+      appOutDir,
+      `${context.packager.appInfo.productFilename}.exe`
+    );
+  } else {
+    electronBinaryPath = path.join(
+      appOutDir,
+      context.packager.appInfo.productFilename
+    );
+  }
+
+  console.log('Flipping Electron fuses...');
+  
+  await flipFuses(electronBinaryPath, {
+    version: FuseVersion.V1,
+    [FuseV1Options.RunAsNode]: false,
+    [FuseV1Options.EnableCookieEncryption]: true,
+    [FuseV1Options.EnableNodeOptionsEnvironmentVariable]: false,
+    [FuseV1Options.EnableNodeCliInspectArguments]: false,
+    [FuseV1Options.EnableEmbeddedAsarIntegrityValidation]: true,
+    [FuseV1Options.OnlyLoadAppFromAsar]: true,
+  });
+
+  console.log('Fuses flipped successfully!');
+};