-
Notifications
You must be signed in to change notification settings - Fork 11
App Architecture
Electron + Bulma.io + SASS + jQuery
- Electron : https://electron.atom.io/
- Bulma.io : CSS Frameworks http://bulma.io/
- SASS : http://sass-lang.com/
- jQuery : https://jquery.com/
I use the folder structure follows this one on electron/electron-api-demos:
The following paragraph is directly copy and paste from electron-api-demos' documentation
This directory contains assets for the app itself: CSS, fonts, images and shared JavaScript libraries or helpers.
This directory contains sub folders for each demo section that requires JavaScript in the main process. This structure is mirrored in the renderer-process
directory.
The main.js
file, located in the root, takes each .js
file in these directories and executes them.
This directory contains sub folders for each demo section that requires JavaScript in the renderer process. This structure is mirrored in the main-process
directory.
Each of the HTML page views requires the corresponding renderer-process .js
files that it needs for its demo.
Each page view reads the content of its relevant main and renderer process files and adds them to the page for the snippets.
This directory contains sub folders for each demo section. These subfolders contain the HTML files for each of the demo pages. Each of these files is appended to index.html
, located at the root.
This is the main view in the app. It contains the sidebar with navigation and uses HTML imports to append each section HTML page to the body
.
This file contains the lifecycle instructions for the app like how to start and quit, it is the app's main process. It grabs every .js
file in the main-process
directory and executes.
The package.json
sets this file as the main
file.
This file is required when using npm
and Electron.js. It contains details on the app: the author, dependencies, repository and points to main.js
as the application's main process file.