Overview

How to build something:

[Mostly from POV of a Linux user:]

• Before you start building:
  
  
  • Ask for advice about how to solve the problem your app would solve. Maybe a solution exists already.
    
    
  • Ask about the standard name for the kind of thing you want to do; often that's the key to finding existing things.
    
    
  • Search for existing similar apps, ask on forums if anyone knows of a similar app.
    
    
  • Search for apps on a variety of platforms and styles: scripts, phone apps, desktop CLI apps, desktop GUI apps, GitHub projects, desktop widgets/extensions, docks/launchers, macroes, bookmarklets, add-ons, web pages, CLI shells.
    
    
• Can you do what you need with existing CLI apps ? Make a shell script.
  To add char-graphical touches, you can use a dialog package, or tput.
  Linux Shell Script
  
  
• Is what you need best done inside an existing GUI app (browser or editor or IDE or image-editor or system file-explorer app) ?
  
  
  • Search the Help and menus and buttons of the app; often they have buried features you don't know about.
    
    
  • Can you use an existing extension/add-on for the existing app ? If your usual app for that kind of processing doesn't support add-ons, maybe switch to an alternative app that does.
    
    
  • Can you use CLI to drive the existing GUI app ? Go to CLI and run the GUI app from there to see options, such as "firefox --help". If the necessary options exist, make a shell script.
    Linux Shell Script
    
    
  • Can you use a macro/script engine to drive the existing GUI app ?
    Kantu, iMacro, Greasemonkey, FireMonkey.
    
    
  • Can you build a new extension/add-on for the existing app ? If your usual app for that kind of processing doesn't support add-ons, maybe switch to an alternative app that does.
    Building a Firefox Extension
    Building a Thunderbird Extension
    Building a VSCode Extension
    Nemo file-explorer actions/scripts
    Dolphin file-explorer actions/scripts
    
    
• Can you do what you need by adding a small feature to an existing app ? Find out where that app's source project lives, what language it's built in. File a feature request, or build the new feature yourself.
  
  
• Do you need a fairly simple app, a step or two up from a shell script ? Maybe make a single-file Python or PHP app.
  PHP program
  
  
• Does your app not need access to the filesystem ? Maybe make a web page, with HTML and CSS and JavaScript. Or a Jupyter Notebook document: Jack Wallen article. Or a spreadsheet. Or a web site/app embedded in an Electron app: Ayush Sharma's "Turn any website into a Linux desktop app" (Nativefier).
  
  
• If you want to make a text-processing app, and maybe pipe it with other apps, make a CLI app.
  Probably write it in Rust or Go.
  Prasad, Firshman, Tashian, and Parish's "Command Line Interface Guidelines"
  Manuel Odendahl's "14 great tips to make amazing CLI applications"
  
  
• If you want to make a GUI app:
  
  
  • If you want the app to be very cross-platform, maybe use: Electron, Flutter, Java, C# with Uno. Qt runs on a lot of platforms too.
    
    
  • If you want the app to be very Linux-native, maybe use GTK or Qt for the GUI framework/toolkit.
    
    Then you can use one of many languages for the app logic. With GTK, you can use C, C++, Python, Rust, Vala, Java, or even JavaScript ? With Qt, same ?
    PyQt or pyside2 or similar
    Java
    
    With GTK, maybe use GNOME Builder ?
    With Qt, maybe use Qt Creator (article) ?
    
    Make a Linux App
    
    Don't make your own theme and icons and decorations etc in the app; use the system-wide settings.
    
    If you do want to take it cross-platform, follow the convention for each OS, for things such as where to put config files, name and location of Settings/Preference menu item, etc.
    
    From people on reddit 12/2021:
    
    ... Qt, it's simple yet very powerful. Qt's C++ is basically a whole different language compared to "standard" C++ due to historical (imho bad in hindsight) choices, but you can write entire apps without touching it using a JS-like language called QML which is quite powerful. It also has lots of neat frameworks like Bluetooth, serial, ... which are very nice and abstract a lot of stuff away from you. The KDE frameworks are the cherry on top though, lots of functionality can be plugged in for free in your app thanks to them ...
    
    ...
    
    Nothing's preventing you from using C++17 or 20 tools and idioms in Qt, except for signals and slots (and therefore QThread), which need to be able to cross thread boundaries as needed. You don't need to use QFile if you want to use std::filesystem. The only things that really need to be Qt are widget (or data model) related stuff that plugs right into widget rendering.
    
    For that matter, QML can get you really far by itself with a lot less code. I still do the classic Qt thing most of the time, but QML has a lot of appeal, especially if you want to be mobile-portable.
    
    ...
    
    You can write your backend in regular old C/C++ and just use Qt's weirdness in the UI parts of your code where you're actually using Qt. That's what I do in my app. If I wanted I could build a CLI version without any Qt dependencies that way.
    
    ...
    
    [Isn't GTK an equally well-supported platform?] On Linux, yes. On Windows and MacOS, not much at all, and not natively (requires MingW/Cygwin).
    
    GTK and Qt aren't much alike, really. GTK's functionality is very much a subset of Qt's.
    
    ...
    
    Qt is more programmer-friendly too in the way it handles elements. GTK is a moshpit of code. Qt is more organized.
    
    If you're not already used to GTK and are a beginner about to learn, Qt is the way to go.
    
    
    

Linux GUI toolkits/frameworks:

[Not sure all of this is accurate.]

Higher-level toolkits:

• GTK: Use via C language, or something that binds through C.
  Used in the GNOME, Cinnamon, LXDE, Xfce desktop environments.
  Nitesh Kumar's "How to Create a Simple Application in Python and GTK3"
  GeeksforGeeks' "How to create GUI in C programming using GTK Toolkit"
  GNOME's "Getting Started"
  
  
• Qt: Use via C++, Python languages.
  Used in the KDE, Unity, LXQt, Lumina desktop environments.
  Qt5 Cadaques - A Book about Qt5
  Mike Royal's "Qt Guide"
  
  
• Electron: write in HTML / CSS / JS on top of Node, in browser engine.
  
  
• Chromium Embedded Framework (CEF): many languages.
  
  
• Swing: Use via Java language.
  
  
• Clutter: Use via C language.
  
  
• SDL:
  
  
• Tk:
  
  
• Enlightenment Foundation Libraries (EFL):
  
  
• Flutter:
  
  
• Kivy: Python.
  
  
• Dear PyGui: Python.
  
  
• Dear ImGui: C++.
  
  
• Nuklear:
  
  

Wikipedia's "List of widget toolkits"
Wikipedia's "List of platform-independent GUI libraries"
Joshua Strobl's "Building an Alternative Ecosystem"

Some apps use a lower level: drawing libraries instead of toolkits:

• Cairo: Connects to X Windowing. Used by Firefox browser.
  
  
• OpenGL: Connects to Mesa.
  
  
• Direct3D:
  
  
• Vulkan:
  
  

Next level down:

• Xlib or XCB, libraries that connect to X Windowing System.
  X does both window management and rendering.
  Clean Rinse's "The Linux Graphics Stack"
  
  
• Mesa.
  Does rendering only ?
  Wikipedia's "Mesa (computer graphics)"
  
  
• Wayland.
  Does window management only, uses Mesa for rendering ?
  Wikipedia's "Wayland (display server protocol)"
  
  
• Mir.
  Does window management only, can use X, Wayland and/or Mesa.
  Wikipedia's "Mir (software)"
  
  

GUI app types/architectures:

[Still trying to get my head around these.]


Architectures:

• Web app:
  
  State is kept in a database server. UI is provided by web pages from web server. App-logic may be in an app-server in the middle, with a RESTful API. Scales up to many users. Works for sharing/syncing data among multiple devices. State at any time is sane and persistent.
  
  Data can change out from under the web page at any time. Data could be saved in one big form-submit, or small field-by-field operations to the database. Data could be read from database once at page load, or constantly in the background via AJAX ?
  
  Only local client is a browser. Fits well with MVC model. May have to duplicate some logic at multiple levels.
  
  Less control by the app developer: User could refresh a page or click Back or close the page at any time. Attacker could submit any kind of get/post to the server to try to break in.
  
  Progressive web-app (PWA): has a disputed definition. Web app that runs in a browser but has features/feel/UI of a desktop/mobile app. Probably should be able to run from an icon on the desktop, maybe run without browser's menus/toolbars showing, be cached in the browser and have a manifest and run offline and use local storage, have service workers and TLS in the background that handle the data connection, maybe do push notifications. On mobile, not being an app means not having to pay a percentage to the Store.
  Sam Richard's "What are Progressive Web Apps?"
  Anand Mahajan's "What are Progressive Web Apps?"
  
  Reactive: you write an HTML page, linking fields/buttons to database items and operations. Then things happen sort of automatically, from bottom up: as data in UI or database changes, framework reacts by sending data between UI and database, without you having to write code to do it.
  Honestly Undefined's "Reactive solution" (cartoon)
  
  Single-page web app (SPA): Browser loads the page once, then code on the page rewrites pieces of the DOM again and again as the user does things, fetching data and HTML fragments from the server or reacting to data pushed from the server. Looks to the user somewhat like a traditional desktop app, because the big "page-and-all-resources fetch-and-parse" only happens once, at the start. Frameworks such as React, Vue, AngularJS support this style. Back-end connection can be via AJAX, WebSockets, Server-Sent Events (SSE), more. The data may be sent in XML, JSON, serialized, HTML formats. There can be various designs where most business logic is done on the client, on server, or both. SPAs create problems in some areas: search engines, portability across browsers, security, server code may track or replicate state of DOM, duplicate code on client and server, user actions can interfere.
  
  
• Desktop app:
  
  State, UI, app-logic are kept locally and may be mixed together. Single-user, and the app can make lots of assumptions about state. State at any time is sane but may be transient (not saved yet) or persistent.
  
  Thick client: Local client is a custom application (which may include a browser engine).
  
  Usually CPU-architecture-specific, OS-specific, maybe DE-specific.
  
  More control by the app developer: User can be forced to follow a certain path, warned about unsaved data, etc. Attacker has fewer APIs or attack surfaces to work with.
  
  
• Some mixture of the two.
  
  Maybe the desktop app is custom and complex and has much of the app-logic, but then there is a database server storing the state and having some app-logic, and multiple users of the database.
  
  Thin-client: Maybe the desktop runs only a browser or remote-desktop app (Citrix, VNC, etc), but the web/app-server is running a large custom, complex app that provides UI and app-logic and has the notion of "sessions" and stores some state. And there is a database server storing the state and having some app-logic, and multiple users of the database.
  
  
• Phone app:
  
  Have to follow conventions of the device and OS. Often authentication/login is done implicitly, using the ID of the phone. Varying, limited, intermittent, and maybe metered network connection. If applicable, expected to use shared facilities / messages to other apps to do things such as calendar and contacts and notifications. May have to adapt to features being disabled by user, or not available in older OS versions or older API versions, or not available on some devices.
  
  Android development
  Flutter / Dart
  
  
  

UIs:

• Web pages (HTML, CSS, JS):
  
  Portable across many environments, but less detailed control of the UI. Each view is transient. Each operation is atomic.
  
  Easy to let the user tweak some UI things simply by editing CSS or changing browser settings.
  
  Responsive: adapt reasonably to varying screen sizes and touch screens and varying device abilities. Some key ideas here seem to be: design for mobile first, and learn CSS grid and flexbox.
  
  
• Desktop UI (Java, C++, Qt, GTK, etc):
  
  Often OS-specific or DE-specific, but more detailed control of the UI. Often large, complex pages.
  
  
• Phone app:
  
  Have to follow conventions of the device and OS. Limited and varying screen size. May have to adapt to features being disabled by user, or not available in older OS versions or older API versions, or not available on some devices.
  
  

Cross-platform GUI stacks:

[Still trying to get my head around these.]

Java etc:

Java Beans	Swing
Java		Kotlin	Scala	many more
Java bytecode
JVM (Java Virtual Machine)

.NET:

C#	F#	Visual Basic	Iron Python	PowerShell	C++ (Windows only)	many more
IR ? CLI ?
CLR (Common Language Runtime)

C# probably is the main language on .NET.
.NET 5 fully supports Windows, Mac, Linux, iOS, Android.
.NET 5 is the newest version; .NET Framework (Windows-only) and .NET Core (old name) are older.
.NET Standard 2.0 is a library/specification/abstraction layer that works on top of any of them (.NET 5, .NET Framework, .NET Core).
.NET doesn't have a strong cross-platform desktop GUI toolkit; that's being worked on (as of 12/2020). It's very strong for back-end or web apps.
Wikipedia's ".NET Core"
Tim Anderson's "20 years of .NET: Reflecting on Microsoft's not-Java"
Wikipedia's "Universal Windows Platform"
Wikipedia's "LLVM"
Will Fuqua's ".NET and Linux" (video)
Federico Antuna's "Set up a .NET development environment" (on Fedora)
Charles Chen's "6 .NET Myths Dispelled"

Programming styles:

[Still trying to get my head around these.]

"State" is values that can be changed in place; written and rewritten; mutable state.

• Procedural:
  
  State is kept in global variables, database, files, devices (UI), etc.
  
  
• Object-oriented:
  
  State is kept in objects, database, files, devices (UI), etc.
  
  IMO this can work well if the problem naturally is modeled as a network of objects, or if inheritance and polymorphism are minimized. But it's easy to get into a trap where state is spread all over the place, and code locality is poor (you have to look in many places up and down the hierarchy to figure out what a particular method is doing and what the state is).
  
  Well-suited languages: C++, C#, Java.
  
  
• Functional:
  
  State is kept in a database, files, and devices (UI).
  
  The data flows through sort of a pipeline of functions, with everything (data, configuration, rules, etc) needed by a function passed into it as arguments, and all results come out of the function. Also you can pass functions as arguments to other functions.
  
  This style is a good fit with VMs and micro-services and cloud, where computing/processing engines are transient, and state is kept in a database.
  
  It works best if you minimize the state (so you don't have tons of database accesses), concentrate the state (keep it in one place), and defer changes (one commit at the end of processing).
  
  Well-suited languages: F#.
  
  

Using Git and GitHub

Resources:

git:
Aaron Kili's "How to Use Git Version Control System in Linux"
Dolamu Asipa's "A Git Workflow Guide for Code Newbies"
Git Immersion
Rapid7's "Git cheatsheet"
giteveryday(7) Manual Page
Scott Chacon and Ben Straub's "Pro Git" book
gittutorial(7) Manual Page
Matt Neuburg's "Picturing Git: Conceptions and Misconceptions"
Git - Documentation
Oh Shit, Git!?!

git and GitHub:
GitHub Guides' "Hello World"
GitHub Guides' "Git Handbook"
Meghan Nelson's "An Intro to Git and GitHub for Beginners (Tutorial)"
Adam Dachis' "How the Heck Do I Use GitHub?"
Lauren Orsini's "GitHub For Beginners: Don't Get Scared, Get Started"
Aayushi Johari's "How To Use GitHub - Developers Collaboration Using GitHub"
Bobby Iliev's "Introduction to Git and GitHub"
Matthew Setter's "A Beginner's Git and GitHub Tutorial"
GitHub's "Set up Git"
GitHub Help's "Fork a repo"

Santosh Yadav's "How GitHub is Improving Developer Experience"

GUIs:
James Quick's "How to use Git Integration in Visual Studio Code"
GitHub Extension for Visual Studio
codeSTACKr's "Learn Git in 30 Minutes" (video) (git and VSCode)
Aaron Kili's "11 Best Graphical Git Clients and Git Repository Viewers for Linux"

reddit's /r/git
reddit's /r/github
Chris Coyier's "The GitHub Profile Trick"

Patricia Johnson's "Top 5 Git Security Mistakes"
William Le's "Taking a Look at the GitHub CLI Tool" (GitHub-specific CLI to manage issues/PRs/repos on GitHub)

Drew DeVault's "Tips for a disciplined git workflow"
Mikkel Paulson's "Effective Git as a solo developer"

Rajeev Bera's "Don't ignore .gitignore"

Vladimir Kaplarevic's "How to Install and Use Git on Windows"

Humor: "Handmade Hero Day 523 - Introduction to Git" (video)

Basics to get started:

sudo apt install git
git config --global user.name "Your Name Here"
git config --global user.email "your_email@youremail.com"
git config --list

Clone existing repo to disk:

# In browser, log in to GitHub, go to a project you want to copy.
# copy the URL ending in ".git"

git clone URL

Create new project from scratch:

1. On GitHub web page, create new repository P in my account.
2. Set description.
3. Turned off Wiki and Projects. Turned on "Restrict editing to collaborators only", but I think it only applies to the Wiki ?

mkdir P
cd P
git init
# edit README.md file
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/BillDietrich/P.git
git push -u origin main
# Had to turn off 2FA for login to work.

Enable SSH access to GitHub/GitLab/etc:

1. "ssh-keygen -t ed25519 -C 'for GitHub'"
2. Set no passphrase.
3. Save to file named "/home/USER/.ssh/id_ed25519GitHub".
4. "ssh-add $HOME/.ssh/id_ed25519GitHub"
5. "cat /home/USER/.ssh/id_ed25519GitHub.pub"
6. Copy public key (except trailing "for GitHub") from screen into clipboard.
   
   
7. On GitHub/GitLab/etc web page, go to settings or profile, and create new SSH key.
8. Paste public key from clipboard.
   
   
9. "cd PROJECT"
10. "git remote rm origin"
11. Get SSH link from web page of repo in browser.
12. "git remote add origin 'git@github.com:YOURNAME/PROJECT.git'"

Making changes in my personal project:

# Edit source files.

git add filename (for each file edited)
git commit -m "message"
git push -u origin main

When you operate this way, there is only one branch ("main").

To see status at any time, do "git status".

If you stage (git add) a file, then decide that was a mistake, do "git rm --cached filename".

If you do a commit, then decide you forgot some changes or the message was wrong, stage more changes and then do "git commit --amend". This doesn't remove the commit, it modifies it, using the (new) contents of the staging area and the new message. Only do this before you do any push to a remote repo.

To delete a file completely, do "git rm filename", then commit and push.

If you edit a file locally and then want to discard the edits and get the last-committed version of the file again, do "git checkout -- filename".

In a bigger, multi-person project:

From a project-owner on GitHub:

"Forking" is just Github's name for making your own clone of someone else's repo on Github. It is a weird name and completely different from forking an open source project (into a new project).

[After pushing changes to a branch on your repo on GitHub] it doesn't matter, you can open a pull request between the original repo's main and your issue branch in your Github repo, or between original repo's main and your repo's main branch.

If you fork an original repo on GitHub to make your own repo on GitHub, then clone your repo on GitHub to your local disk, you now have three repo's. Your files on disk are a repo.

There are two cases for project management:

• Shared repository, you have write access to the original project repo:
  
  [This mixes GUI and CLI operations, probably not best style:]
  
  

  1. Clone the original main branch files on GitHub to disk: login to GitHub web site, go to repo, click big green "Clone or download" button near upper-right. Easiest to click on "Download ZIP".
  2. Build the project on disk, test.
  3. Create a branch (on project's main page in GitHub, click "Branch: Main" pull-down, and type new branch's name; or "git branch issue857").
  4. Have to "checkout" to the branch on disk. Do "git status" to see that you're on branch, not main.
  5. Edit files on disk, test, repeat.
  6. Commit changed files to the branch as you go along, and push them to the GitHub repo, or after it's all working ("git add FILENAMES" and "git commit -a -m 'whatever'" and "git push -u origin issue857").
  7. Get whole thing into a finished state.
  8. When all changes are done and committed and pushed to the branch on GitHub, open a pull request for the branch.
  9. Get approval of the pull request (the changes).
  10. On disk, go back to main branch.
  11. Merge branch into main branch.
  
  
  
• Fork and pull, you don't have write access to the original project repo:
  
  [This mixes GUI and CLI operations, probably not best style:]
  
  

  1. Fork the whole original repo on GitHub to make your own repo on GitHub: login to GitHub web site, go to repo, click "fork" button near upper-right.
  2. From your repo on GitHub, clone the (main branch) files to disk: login to GitHub web site, go to repo, click big green "Clone or download" button near upper-right. Easiest to click on "Download ZIP".
  3. Build the project on disk, test.
  4. Create a branch (on project's main page in GitHub, click "Branch: Main" pull-down, and type new branch's name; or "git branch issue857").
  5. Have to "checkout" to the branch on disk. Do "git status" to see that you're on branch, not main.
  6. Edit files on disk, test, repeat.
  7. Commit changed files to the branch as you go along, and push them to the GitHub repo, or after it's all working ("git add FILENAMES" and "git commit -a -m 'whatever'" and "git push -u origin issue857").
  8. Get whole thing into a finished state.
  9. When all changes are done and committed to the branch, open a pull request for the branch but to the original GitHub repo.
  10. Owner will approve and merge the pull request (the changes).
  
  
  

Picking a package to use from GitHub:

• What language(s) does it use ?
• Look at how recently parts were updated. If it hasn't been updated in several years, maybe find something fresher.
• Look at open issues.
• Look at forks. Maybe one of them is newer/better.

2FA in GitHub:

When I turned on 2FA (TOTP) on my GitHub account, I could no longer log in through the CLI.

Found out later: log in to GitHub web page, go to Settings / Security and enable 2FA. Back to Settings, go to Developer settings, then Personal access tokens. Click on Generate new token button. Check only the "repo" item, to do just that stuff through the CLI; do all other stuff through the web UI. Click Generate new token button. Copy the token value and save it.

Then when you do operations through the CLI, use the value of your personal access token instead of your account password.

Also, if you have a "secret service" storing your GitHub password (on a keyring or in a password manager), you could edit ~/.gitconfig to contain "[credential] helper = libsecret" (two lines).

Count lines in files in git project on disk:

# cd into project directory
git ls-files | xargs wc -l
# or:
git ls-files | grep -P ".*(js|html)$" | xargs wc -l
# or:
git ls-files | grep -vE ".*(png|jpg|ico)$" | xargs wc -l
# or:
sudo apt install cloc
cloc $(git ls-files)
#or:
cloc --vcs git

Count lines in files from git repository:

# clone latest commit of project to disk, count, then remove it from disk
git clone --depth 1 https://github.com/OWNERNAME/PROJECTNAME.git
cd PROJECTNAME
cloc --vcs git
cd ..
rm -fr PROJECTNAME

Or use Chrome extension "GLOC" ? Shows only files in current directory, no recursion ?

Diff files on disk with committed files in main branch in repo:

# Diff a single file on disk with same file in main branch:
git diff main -- FILENAME

# Diff all files on disk with same files in main branch:
git diff main --

If you ever wipe out the .git tree, and then want to commit source changes:

# make a good backup

# in the overall projects directory:
git clone https://github.com/BillDietrich/linkcheckerhtml.git

git init
git remote add origin https://github.com/BillDietrich/linkcheckerhtml.git
git remote -v   # see repos linked to local repo

# maybe:
git config --global user.name "Your Name Here"
git config --global user.email "your_email@youremail.com"

# copy backed-up files to working dir

# do add, commit, push

Build Systems

• Shell scripts:
  
  
  
  
• Make:
  
  
  
  
• Autotools:
  
  Wikipedia's "GNU Autotools"
  Thomas Petazzoni's "GNU Autotools: a tutorial" (PDF)
  
  
  
• CMake:
  
  Seth Kenlon's "CMake"
  
  
  
• pip:
  
  
  
  
• Java:
  
  Open Source Build Systems in Java
  
  
  

App GUI Prototyping

• Glade:
  
  Available in Mint's Software Manager.
  Too complicated, couldn't figure out how to use it.
  Also: Chris Davis's "Glade Not Recommended"
  
  
  
• Pencil:
  
  Pencil Project
  No grid/table tool.
  
  
  
• Google Web Designer:
  
  Google Web Designer
  If you don't want Google's repository added to your system, do "sudo touch /etc/default/google-webdesigner" before installing the package.
  It's really just for building ads for mobile.
  
  
  
• Akira:
  
  akiraux / Akira
  SkySilk's "Akira: A Native Linux App for UI & UX Design"
  
  
  

Mobile

Electron (Simple App)

An Electron application is (basically) a web app packaged with a (slightly old) version of the Chrome browser ...

The Electron application has a copy of the Node.js runtime, which allows you to do many of the things that a native desktop application can do, but which the security model of a web browser doesn't allow you to do, including accessing local files, integrating at a lower level with the Operating System.

Tricky: "main process" versus "render process":

JavaScript in the "main" JS file (as specified in package.json) is running in the "main process", and JavaScript in the HTML file is running in the "render process". The syntax for connecting to modules is a bit different between the two.

"The DevTools in an Electron browser window can only debug JavaScript that's executed in that window (i.e. the web pages). To debug JavaScript that's executed in the main process you will need to use an external debugger and launch Electron with the --inspect or --inspect-brk switch."
from Electron's "Debugging the Main Process"

Using console.log() in Electron app

Electron's "remote"
Carlos Delgado's "How to execute a function of the main process inside the renderer process in Electron Framework"

Making a tree-display application:

Carlos Delgado's "Best tree view jQuery and JavaScript plugins"
npm's "electron tree view"
js-treeview"

npm --version
electron --version
sudo npm install -g electron --unsafe-perm=true --allow-root

cd ~/projects
mkdir installproto2
cd installproto2

npm init

npm install js-treeview
npm install load-json-file
npm install systeminformation

Create app.js file:

const {app, BrowserWindow} = require('electron')
const path = require('path')
const url = require('url')

let window = null

// Wait until the app is ready
app.once('ready', () => {
  // Create a new window
  // https://www.electronjs.org/docs/api/browser-window
  window = new BrowserWindow({
    // Set the initial width to 800px
    width: 800,
    // Set the initial height to 600px
    height: 600,
    // Set the default background color of the window to match the CSS
    // background color of the page, this prevents any white flickering
    backgroundColor: "#D6D8DC",
    // Don't show the window until it's ready, this prevents any white flickering
    show: false,
    webPreferences: { devTools: true, nodeIntegration: true }
  })

  // Load a URL in the window to the local index.html path
  window.loadURL(url.format({
    pathname: path.join(__dirname, 'index.html'),
    protocol: 'file:',
    slashes: true
  }))

  // Show window when page is ready
  window.once('ready-to-show', () => {
    window.show()
  })
})

Create index.html file:

<!DOCTYPE html>
<html lang="en-US">
<head>
<title>My app name</title>
<meta charset="UTF-8">

<link rel="stylesheet" href="index.css" />
<link rel="stylesheet" href="./node_modules/js-treeview/dist/treeview.min.css" />

<script>
delete module.exports
</script>

<script src="https://code.jquery.com/jquery-3.2.1.js"></script>
<script src="./window.js" charset="utf-8"></script>

</head>

<body>

<label id="t1filename"></label>
<button id="t1expandAll">Expand All</button>
<button id="t1collapseAll">Collapse All</button>
<br /><br />
<div id="t1tree"></div>

</body>

</html>

Create window.js file:

// "document ready" function:

$(() => {

  const jstreeview = require('js-treeview')
  const loadJsonFile = require('load-json-file')

// https://www.npmjs.com/package/js-treeview
// https://github.com/justinchmura/js-treeview
// https://www.npmjs.com/package/load-json-file


  //
  // Tree Structure
  //

  var t1dataX = [{
    name: 'Vegetables',
    children: []
  }, {
    name: 'Fruits',
    children: [{
      name: 'Apple',
      children: []
    }, {
      name: 'Orange',
      children: []
    }, {
      name: 'Lemon',
      children: []
    }]
  }, {
    name: 'Candy',
    children: [{
      name: 'Gummies',
      children: []
    }, {
      name: 'Chocolate',
      children: [{
        name: 'M & M\'s',
        children: []
      }, {
        name: 'Hershey Bar',
        children: []
      }]
    }, ]
  }, {
    name: 'Bread',
    children: []
  }];

let t1filename = "System-Existing.json";
var t1data = loadJsonFile.sync(t1filename);
$('#t1filename').text(t1filename);

  //
  // Grab expand/collapse buttons
  //
  var t1expandAll = document.getElementById('t1expandAll');
  var t1collapseAll = document.getElementById('t1collapseAll');

  //
  // Create tree
  //

  var t1 = new jstreeview(t1data, 't1tree');
  //$('#t1tree').text("hello");
  //alert("JSON.stringify(t1): " + JSON.stringify(t1));

  //
  // Attach events
  //

  $('#t1expandAll').bind('click', function() {
    //alert("t1expandAll click");
    t1.expandAll();
  });
  $('#t1collapseAll').bind('click', function() {
    //alert("t1collapseAll click");
    t1.collapseAll();
  });


  t1.on('select', function (e) {
    //const text = this.text;
	  //alert('select "' + this.name + '"');
    //alert("select");
    //alert("select: JSON.stringify(e.data): " + JSON.stringify(e.data));
	});
  t1.on('expand', function (e) {
	  // alert('expand');
    //alert("expand: JSON.stringify(e.leaves): " + JSON.stringify(e.leaves));
	  });
  t1.on('collapse', function (e) {
	  // alert('collapse');
    //alert("collapse: JSON.stringify(e.leaves): " + JSON.stringify(e.leaves));
	  });
  t1.on('expandAll', function () {
	  //alert('expand all');
	  });
  t1.on('collapseAll', function () {
	  // alert('collapse all');
	  });

})

Create index.css file:

td.mytree1 {
	border-style: solid;
	border-width: 1px;
	border-collapse: collapse;
	display:table;
	margin:0 auto;
	min-height: 500px;
	min-width: 300px;
	background-color:lightgreen;
}

Edit package.json file:

  "main": "app.js",
  "scripts": {
    "start": "/usr/local/lib/nodejs/node-v10.15.3-linux-x64/lib/node_modules/electron/dist/electron app.js"
  },

Run electron desktop-app:

npm start
# see desktop app window appear !

Updating after not running for a while ?

npm --version
electron --version
npm install
npm start
# see desktop app window appear !

Making an installer:

There can be two steps: packaging, and then making an installer.

There are four ways to do packaging and/or making installer: electron-packager, electron-builder, electron-forge, or manually (bad).

So far, I haven't tried electron-forge or manually, and I've found electron-builder is better than electron-packager.

Manually: Electron's "Application Distribution"

Electron-forge might be best ?
Electron's "Boilerplates and CLIs"
Electron Forge
electron-userland / electron-forge


Packaging the app (if you want to do packaging and making installer separately):

Using electron-packager:

Christian Engvall's "Electron packager tutorial"
electron / electron-packager

npm install electron-packager --save-dev
sudo npm install electron-packager -g
# edit package.json to add a "productName" line

#-------------------------
# build for MacOS:
./node_modules/.bin/electron-packager . --overwrite --platform=darwin --arch=x64 --icon=./icon.icns --prune=true --out=release-builds

#-------------------------
# build for Windows:
./node_modules/.bin/electron-packager . YOURPROJECTNAME --overwrite --asar --platform=win32 --arch=ia32 --icon=./icon.ico --prune=true --out=release-builds --version-string.ProductName="YOURPRODUCTNAME"
# requires WINE !!!

#-------------------------
# build for Linux:
./node_modules/.bin/electron-packager . YOURPROJECTNAME --overwrite --asar --platform=linux --arch=x64 --icon=./icon.png --prune=true --out=release-builds

Making an installer for the app:

If you used electron-packager:

Christian Engvall's "DMG installer for electron app"
Christian Engvall's "Electron Windows installer tutorial"
Christian Engvall's "Electron installer debian package"

# build for MacOS:

npm install electron-installer-dmg --save-dev
sudo npm install electron-installer-dmg -g

./node_modules/.bin/electron-installer-dmg ./release-builds/YOURPRODUCTNAME-darwin-x64/YOURPRODUCTNAME.app YOURPROJECTNAME
# FAILS !!!:    Error: Must be run on OSX
# creates a file called YOURPROJECTNAME.dmg in the root folder of the application

# build for Windows:

npm install --save-dev electron-winstaller
mkdir installers
cd installers
mkdir windows
cd windows
# make file createinstaller.js as described in
# https://www.christianengvall.se/electron-windows-installer/
cd ../..

node installers/windows/createinstaller.js

# build for Linux:

npm install --save-dev electron-installer-debian
sudo npm install -g electron-installer-debian
# create file debian.json as described in
# https://www.christianengvall.se/electron-installer-debian-package/

./node_modules/.bin/electron-installer-debian --src release-builds/YOURPROJECTNAME-linux-x64/ --arch amd64 --config debian.json

Using electron-builder:

electron-builder
electron-userland / electron-builder
Akash Nimare's "A complete guide to packaging your Electron app"

mkdir build
# copy a background.png and icon files into build directory

npm install electron-builder --save-dev

# had to tweak package.json file a lot
# https://www.electron.build/configuration/configuration
# add following to package.json file:
# "build": {
#  "appId": "YOURAPPID",
#  "mac": {
#    "category": "YOURAPPCATEGORY"
#  },
# "win": {
#   "target": "NSIS"
#  }
# },

#-------------------------
# build for MacOS:
./node_modules/.bin/electron-builder --macos default
# failed because it couldn't spawn hdiutil, which apparently runs only on MacOS

#-------------------------
# build for Windows:
# requires WINE !!!

# If you don't want to install wine through Software Manager:
apt install wine
sudo dpkg --add-architecture i386 && apt update && apt install wine32

# https://www.linuxbabe.com/linux-mint/install-wine-linux-mint-19-1
# Best to install wine-stable from Software Manager (535 MB)
# add /opt/wine-stable/bin to PATH in .profile, log out and in
winecfg
# gave:  0009:err:file:init_redirects cannot open L"C:\\windows" (c000000f)
# but kept going
# wanted to install wine-mono and gecko, but I said cancel to each
# Settings dialog came up, and I chose Windows 10
# Finished, and I ran it again, and Settings dialog came right up, no problems.

./node_modules/.bin/electron-builder --windows nsis
# insisted on an icon at least 256x256

#-------------------------
# build for Linux:
./node_modules/.bin/electron-builder --x64 --linux deb
# insisted on an icon at least 256x256

Electron (Complicated App)

The technology stack I'm looking at is:

HTML/CSS:	Bootstrap or Materialize or Tailwind CSS or Foundation
Library everything else uses:	jQuery
UI library or framework:	Library: React or Vue. Framework: Angular (AKA "ng")
	Electron
	electron-builder (packager)
Modules:	Node
Database access:	SQL.js or Electron-store
Database format:	SQLite or MongoDB
OS:	Linux.

Bootstrap / Angular / Electron

The technology stack I've chosen is:

HTML/CSS:	Bootstrap (CSS and JS), ng-bootstrap (JS)
Library:	jQuery from ng-bootstrap (JS)
UI framework:	Angular (AKA "ng")
	Electron
	electron-builder (packager)
Modules:	Node
Database access:	SQL.js
Database format:	SQLite
OS:	Linux.

1. Install stuff:
   
   

   
   
   # if you don't have Node.js, install that
   
   sudo npm install -g @angular/cli@latest
   # got "skipping optional dependency fsevents"
   # apparently fsevents is for running on OSX
   ng --version
   # 3/2019: I got "Angular CLI: 7.3.5"
   
   sudo npm install -g typescript
   # 3/2019: got "typescript@3.3.3333"
   
   sudo npm install -g electron --unsafe-perm=true --allow-root
   # 3/2019: got "electron@4.0.8"
   
   # Name of new app can not have any uppercase letters in it !
   # cd to place where you want app dir to be created, and:
   ng new matrix-dashboard
   # Asked "Would you like to add Angular routing ?"
   #		This allows user to follow URL links to different parts
   #		of the one page of your single-page application
   #		I answered "no"
   # Asked "Which stylesheet format ?"
   #		I picked the default, CSS.
   
   cd matrix-dashboard
   
   # (I didn't realize that ng-bootstrap and ngx-bootstrap
   # are different things.  Having installed ng-bootstrap,
   # I'll stick with it.)
   ng add @ng-bootstrap/schematics
   # see warnings about peers of jquery and popper not found
   #	ignore the warnings
   #	You don't need jQuery / popper to use ng-bootstrap and
   #	you shouldn't install those manually
   # I also saw warnings about peers of angular/common and
   # /core and /forms not found.  Sounds fatal.  But online,
   # someone says as long as the installed version of Angular
   # is higher than the version in the warning, no problem.
   
   # start development server
   ng serve
   # saw messages that server is up and compile succeeded
   # now app is accessible on http://localhost:4200/
   # go there in browser, see default Angular app
   # back to CLI window, ctrl-C to kill server
   
   # add electron as a dev dependency
   npm i -D electron
   # 3/2019: got electron 4.0.8
   
   npm i -D @types/electron
   
   mkdir dist
   mkdir dist/matrix-dashboard
   
   # edit tsconfig.json file to add first line:
   #		/* angular tsconfig.json */
   
   # edit package.json file to add first component:
   #		"comment": "angular package.json file",
   
   mkdir electron
   cd electron
   mkdir dist
   mkdir dist/matrix-dashboard
   

   Directory structure that resulted:

   
   matrix-dashboard/
   	angular json files
   	do "ng build" when in this dir
   	dist/
   		matrix-dashboard/
   			app's angular HTML, JS files
   	e2e/
   		end-to-end tests
   	node-modules/
   		bootstrap
   			CSS, JS files
   		@ng-bootstrap/
   			JS files
   	src/
   		angular CSS, TS, HTML, JSON files
   		app/
   			app's CSS, TS, HTML files
   	electron/
   		TS, JSON files
   		dist/
   

   So, some trickiness going on here:
   
   

   • The "top-level" app is an Angular web-app, which uses a local server if you run it.
     
     
   • The Angular web-app is using CSS and JS from bootstrap, and JS from @ng-bootstrap.
     
     
   • Inside the electron directory is stuff which grabs the Angular code and node_modules, compiles it, and runs it as a desktop app in the electron framework.
     
     

   Mosh Hamedani's "Angular 4 Tutorial: Angular 4 in 20 minutes"
   Angular's "Workspace and project file structure"
   
   
   
   
   
2. Build and run Angular web-app:

   
   
   # cd to main matrix-dashboard/ dir
   ng serve
   ng generate service file  # one-time thing to add a service
   ng build
   # go to http://localhost:4200/ to see Angular web app running
   # page HTML source is src/app/app.component.html
   
   # ctrl-C to kill Angular server
   

   Structure of the Angular application:
   
   

   • Really all that should be in the body of src/index.html is

     
       <app-root>
         <app-yourappsname></app-yourappsname>
       </app-root>"
     

     
     
     
   • In app.component.ts should be the line:

     
       selector: 'app-yourappsname'
     

     
     
     
   • The main page of your app will be in app.component.html.
     
     
   • You can't use deprecated HTML in the pages. That means no "center" tags: use CSS "text-align:center" or "margin:0 auto;". Probably also no "font" or "u" tags, and a bunch of deprecated attributes.
     CodeHelp.co.uk's "What's a deprecated tag / attribute?"
     
     
   
   Places errors could be flagged/shown:
   
   

   • In your source-code editor as you type.
     
     
   • In the "ng serve" window when it recompiles.
     
     
   • In the page displayed in the browser.
     
     
   • In browser's debug-console for the page displayed in the browser.
     
     

   Edward Jackson's "Debugging Angular CLI Applications in Visual Studio Code"
   
   
   
   
   
3. Get electron desktop-app going:
   
   Create electron/index.html file:

   
   
   <html>
   <head>
   <title>Matrix Dashboard</title>
   </head>
   <body>
   Hello
   </body>
   </html>
   

   Create electron/tsconfig.json file:

   
   
   /* electron tsconfig.json */
   {
     "compileOnSave": false,
     "compilerOptions": {
       "baseUrl": "./",
       "outDir": "./dist",
       "sourceMap": true,
       "declaration": false,
       "module": "commonjs",
       "moduleResolution": "node",
       "emitDecoratorMetadata": true,
       "experimentalDecorators": true,
       "target": "es5",
       "typeRoots": ["../node_modules/@types"],
       "lib": ["es2018", "dom"]
     }
   }
   

   Create electron/main.ts file:

   
   
   import { app, BrowserWindow } from "electron";
   //import { Injectable } from "@angular/core";
   //import { ipcMain, IpcRenderer } from "electron";
   import * as path from "path";
   import * as url from "url";
   
   let win: BrowserWindow;
   
   app.on("ready", createWindow);
   
   app.on("activate", () => {
     if (win === null) {
       createWindow();
     }
   });
   
   /*
   ipcMain.on("getFiles", (event, arg) => {
     const files = fs.readdirSync(__dirname);
     win.webContents.send("getFilesResponse", files);
   });
   */
   
   function createWindow() {
     win = new BrowserWindow({ width: 800, height: 600 });
   
     win.loadURL(
       url.format({
         pathname: path.join(__dirname, `/../../dist/matrix-dashboard/index.html`),
         protocol: "file:",
         slashes: true
       })
     );
   
     //win.webContents.openDevTools();
   
     win.on("closed", () => {
       win = null;
     });
   }
   

   Create electron/package.json file (I added the comment):

   
   
   {
     "comment": "electron package.json file",
     "name": "matrix-dashboard",
     "version": "0.0.0",
     "main": "electron/dist/main.js",
     "scripts": {
       "ng": "ng",
       "start": "ng serve",
       "build": "ng build",
       "test": "ng test",
       "lint": "ng lint",
       "e2e": "ng e2e",
       "electron": "ng build --base-href ./ && tsc --p . && electron ."
     }
   }
   

   Build and run electron desktop-app:

   
   
   cd electron/
   npm run electron
   # see desktop app window appear !
   

   
   
   
4. Now to use Bootstrap:
   
   Edit Angular's src/styles.css file to add line:

   
   @import "../node_modules/bootstrap/dist/css/bootstrap.css"
   

   Edit src/app/app.component.html file to add:

   
   
   a bootstrap thing:<br />
   <select multiple data-role="tagsinput">
     <option value="Amsterdam">Amsterdam</option>
     <option value="Washington">Washington</option>
     <option value="Sydney">Sydney</option>
     <option value="Beijing">Beijing</option>
     <option value="Cairo">Cairo</option>
   </select>
   

   Build and run Angular web-app:

   
   
   # cd to main matrix-dashboard/ dir
   ng serve
   # go to http://localhost:4200/
   # see Angular web app running with bootstrap-CSS-influenced "select" in page
   

   
   Build and run electron desktop-app:

   
   
   cd electron/
   npm run electron
   # see new "select" appear in desktop app window
   

   
   
   
5. Now to use ng-bootstrap:
   
   Let's try a simple example widget: Rating.
   
   Edit src/app/app.component.html file to add:

   
   
   an ng-bootstrap thing:<br />
   <ngb-rating rate="2"></ngb-rating>
   

   Edit src/app/app.module.ts file to add lines:

   
   
   import { NgbModule } from '@ng-bootstrap/ng-bootstrap';
   
   // in imports, after BrowserModule:
       NgbModule.forRoot()
   

   Build and run Angular web-app:

   
   
   # cd to main matrix-dashboard/ dir
   ng serve
   # go to http://localhost:4200/
   # see Angular web app running with new widget in page
   
   # ctrl-C to kill Angular server
   

   Edward Jackson's "Debugging Angular CLI Applications in Visual Studio Code"
   
   Build and run electron desktop-app:

   
   
   cd electron/
   npm run electron
   # see new widget appear in desktop app window
   

   
   
   
6. Add a new app component that uses ng-bootstrap:
   
   Create src/app/rating-basic.html file containing:

   
   
   <ngb-rating [(rate)]="currentRate"></ngb-rating>
   <br />
   <pre>Rate: <b>{{currentRate}}</b></pre>
   

   Create src/app/rating-basic.ts file containing:

   
   
   import {Component} from '@angular/core';
   
   @Component({
     selector: 'ngbd-rating-basic',
     templateUrl: './rating-basic.html'
   })
   export class NgbdRatingBasic {
     currentRate = 8;
   }
   

   Edit src/app/app.component.html file to add:

   
   
   app component that references an ng-bootstrap thing:<br />
   <ngbd-rating-basic></ngbd-rating-basic>
   

   Edit src/app/app.module.ts file to add lines:

   
   
   import { NgbdRatingBasic } from './rating-basic';
   
   // in declarations:
       NgbdRatingBasic
   

   Build and run Angular web-app:

   
   
   # cd to main matrix-dashboard/ dir
   ng serve
   # go to http://localhost:4200/
   # see Angular web app running with new widget in page
   
   # ctrl-C to kill Angular server
   

   Edward Jackson's "Debugging Angular CLI Applications in Visual Studio Code"
   
   Build and run electron desktop-app:

   
   
   cd electron/
   npm run electron
   # see new widget appear in desktop app window
   

   
   
   

• vscode-angular-html
  
  
• vscode-typescript-angular-plugin
  
  
• People report problems with vscode-ng-language-service, say it causes a huge performance hit.
  
  

7. Add a new app component that is the main window of my application:
   
   Bootstrap - Layout - Overview
   
   
   
   Ran into a nasty problem involving tables and Angular. I had one big table, with a header row generated in one page/component (mdmainwindow), then next rows generated by N calls to a sub-component (mdrow). But Angular passes the tags <sub-component-name> ... </sub-component-name> through to the browser, and since they are encapsulating each row, they made the browser place the whole row (for rows 2-N) into the first column in the bigger table, not what I wanted. Ended up with an L-shaped table ! I'll have to generate the whole table structure in one page, and then call sub-components to fill the contents of each cell in the table.
   
   HTML looked like:

   
   <table>
     <tr><td>colheader1</td><td>colheader2</td></tr>
     <mdrow>
       <tr><td>data</td><td>data</td></tr>
     </mdrow>
     <mdrow>
       <tr><td>data</td><td>data</td></tr>
     </mdrow>
     <mdrow>
       <tr><td>data</td><td>data</td></tr>
     </mdrow>
   </table>
   

   
   Fixed it by making mdrow into a TypeScript class, not an Angular class, and never putting <mdrow> in HTML.
   
   Later, someone told me I could have fixed it by invoking ("selecting") MDRow via an attribute on another tag (e.g. <tr mdrow>), instead of via an <mdrow> tag:
   "In @Component you've a 'selector' property. It's pretty much a CSS selector. Normally it's like 'mdrow', but it can be also a class selector ".mdrow" or attribute '[mdrow]'."
   
   Got the code working.
   
   Code is too big to show here. But src/app/mdmainwindow.html file contains:

   
   
   <table class="table-striped table-bordered table-hover table-sm">
   
   <thead class="thead-light">
   <tr>
   <td> </td>
   <td *ngFor="let colname of appareas[ncurrentapparea].columnnames; index as ncolumn" id="{{colname}}">
     {{colname}}
   </td>
   </tr>
   </thead>
   
   <tr *ngFor="let row of rows; index as nrow" id="{{row.name}}">
     <td>{{row.name}}</td>
     <td *ngFor="let colname of appareas[ncurrentapparea].columnnames; index as ncolumn"
           id="cell{{nrow}}-{{ncolumn}}">
       <mdcell [nrow]="nrow" [ncolumn]="ncolumn"></mdcell>
     </td>
   </tr>
   
   </table>
   

   And src/app/mdmainwindow.ts file contains:

   
   
   export class MDMainWindow implements OnInit {
     @Input() nrows = 0;
     @Input() ncolumns = 0;
   
     rows: Array<MDRow>;
   
     appareas: Array<MDAppArea>;
     ncurrentapparea = 0;
   
     constructor() {
     }
     ngOnInit() {
       this.rows = new Array();
       for (let r = 0; r < this.nrows; r++) {
         var newrow = new MDRow(r,this.ncolumns);
         this.rows.push(newrow);
       }
   
       this.appareas = new Array();
       var aa = new MDAppArea("Standard",this.ncolumns);
       this.appareas.push(aa);
       aa = new MDAppArea("Custom1",this.ncolumns);
       this.appareas.push(aa);
       aa = new MDAppArea("Custom2",this.ncolumns);
       this.appareas.push(aa);
     }
   }
   

   
   
   

• {{name}} is an "interpolation" to fetch the value of "name".
  
  
• [name]=value is a "property binding" to send "value" from parent object to "name" property of the child object.
  
  
• (name)=method(value) is an "event binding" that calls the component's "method" when the "name" event occurs.
  
  
• [(name1)]=name2 is a "two-way binding" where first value of name2 is copied to name1, then any changes to name1 are copied back to name2.
  
  

8. Add database connection:
   
   Angular can do HTTP requests, and SQL databases can provide RESTful APIs, where they accept HTTP requests to do operations.
   
   I wanted to use Node's sql.js module and a local SQLite database, following patrickmoffitt / local-sqlite-example. But Angular is in a browser client with no access to filesystem. And the sql.js module throws errors when added to a TypeScript project.
   
   There used to be an Angular "http" module, but it's been replaced by an "HttpClient" module.
   
   Started looking into client/server components:
   
   Sunny Sun's "How to map REST API data using Decorator pattern in Angular 6"
   
   GraphQL seems easier than a RESTful connection ?
   
   Client:
   Apollo Angular
   Alexandr Selyanov's "How To Use GraphQL with Angular 2"
   Uri Goldshtein's "GraphQL as a best practice for modern Angular apps?"
   Nikolas Burk's "How to GraphQL - Introduction"
   prisma-labs / graphql-request
   apollographql / apollo-client
   grafoojs / grafoo
   chentsulin / awesome-graphql
   
   Server:
   Mikhail Novikov's "Building a GraphQL Server with Node.js and SQL"
   Sam Hogarth's "Connecting SQLite to GraphQL"
   rexxars / sql-to-graphql
   Jonas Helfer's "Tutorial: How to build a GraphQL server"
   Chimezie Enyinnaya's "How To Set Up a GraphQL Server in Node.js with Apollo Server and Sequelize"
   
   
   Then someone said just use IndexedDB, a database inside the browser.
   
   A complication for me: often there will be two browser profiles, one for daily use and one for web-app testing use. Probably this app will have to "live" in the testing profile.
   MDN's "IndexedDB API
   MDN's "Browser storage limits and eviction criteria
   Wikipedia's "Web storage"
   Works on Firefox, Chrome, Opera.
   Data-size limits not a problem for my app.
   How to backup or copy to another machine ? On Firefox, the DB is under "<profile>/storage/permanent". Or I could create export and import features into my app.
   
   But I see some statements:
   "IndexedDB is a document-oriented database while SQL is relational database ... Avoid using multiple tables in IndexedDB and trying to create joins."
   "SQL is relational database. IndexedDB is an indexed key/value store similar to a document-oriented database."
   
   Wrapper libraries, or DB engines that use IndexdDB for storage:
   SQL-like interface:
   AlaSQL (SQL-like interface)
   Object interface:
   JsStore
   Dexie.js
   NanoSQL
   Lovefield
   
   Firefox uses SQLite to store IndexedDB data, and there's an API directly to SQLite ? Confusing.
   Mozilla's "Performance/Avoid SQLite In Your Next Firefox Feature"
   
   
   Decided to use AlaSQL.
   The AlaSQL Wiki
   
   
   Whoops, better design my database schema first:
   
   

   Table Name	Row Fields	Example
   projects:	project_id, project_name	Project1
   appareas:	apparea_id, project_id, apparea_name	Standard
   appfunctions:	appfunction_id, project_id, apparea_id, appfunction_name	Login
   activities:	activity_id, project_id, activity_name, role_id, client_id	Learn app
   cells:	cell_id, project_id, appfunction_id, activity_id	Learn app / Login
   tools:	tool_id, tool_name, tool_path_type, tool_path	Burp Suite
   cellpaths:	cellpath_id, cell_id, cellpath_type, path_name, path_type, path, toolid, args	app.com/login.html or docs/doc1.md
   roles:	role_id, role_name	Admin
   clients:	client_id, client_name, devicetype_id, browsertype_id, ostype_id	PFL
   devicetypes:	devicetype_id, devicetype_name	PC
   browsertypes:	browsertype_id, browsertype_name	Firefox
   ostypes:	ostype_id, ostype_name	Windows

   
   Before I changed to AlaSQL, I started to do:
   
   SQLite Home Page
   Create a new file mdschema.sql:

   
   CREATE TABLE "projects" (
   	 "project_id" INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
   	 "project_name" TEXT(255,0) NOT NULL
   );
   CREATE INDEX "project_name_index" ON projects ("project_name" COLLATE NOCASE ASC);
   INSERT INTO `projects` VALUES
   	(NULL, "Default");
   
   CREATE TABLE "appareas" (
   	 "apparea_id" INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
   	 "project_id" INTEGER NOT NULL,
   	FOREIGN KEY(project_id) REFERENCES projects(project_id),
   	 "apparea_name" TEXT(255,0) NOT NULL
   );
   CREATE INDEX "apparea_name_index" ON appareas ("apparea_name" COLLATE NOCASE ASC);
   INSERT INTO `appareas` VALUES
   	(NULL, (SELECT project_id FROM projects WHERE project_name = "Default"), "Standard");
   

   
   

   
   npm install alasql
   # gave "3 vulnerabilities found"
   

   Create a new file mdsql.ts (only partial code shown):

   
   import alasql from 'alasql';
   
   ...
   
     alasql("SET AUTOCOMMIT ON");
     alasql("DROP localStorage DATABASE matrixdashboard");
     alasql("CREATE localStorage DATABASE matrixdashboard");
     alasql("ATTACH localStorage DATABASE matrixdashboard AS matrixdashboard");
     alasql("USE matrixdashboard");
   
   ...
   
     var res = alasql('CREATE TABLE projects ( \
                     project_id INT NOT NULL PRIMARY KEY AUTOINCREMENT, \
                     project_name  TEXT(255,0) NOT NULL \
                     )');
   
   ...
   
     var res = alasql('INSERT INTO projects (?,?)',[0,new_project_name]);
   
   ...
   
     var res = alasql("SELECT * FROM projects WHERE project_id=" + project_id);
   
   ...
   
     var res = alasql('CREATE TABLE appareas ( \
                     apparea_id INT NOT NULL PRIMARY KEY AUTOINCREMENT, \
                     project_id INT REFERENCES projects(project_id), \
                     apparea_name  TEXT(255,0) NOT NULL \
                     )');
   

   Every time I start up "ng serve", the very first compile fails with "alasql no default export". Change the source in some tiny way, recompiles, the compile sucseeds, while STILL saying "alasql no default export".
   
   Got things working, creating a database, using it, closing it, opening it. But when I quit out of Firefox and launched it again, the database was gone.
   
   Messed around in FF's storage settings, ended up clearing all storage, and that destroyed everything ! Anything I do in alasql gives "There is no any AlaSQL databases in localStorage" error message. Restarted "ng serve" and FF, tried loads of code combinations, always get that error. Gave up and filed a bug report on GitHub.
   
   An hour later, situation on my machine is fixed. Maybe I forgot to try just starting with a CREATE after it got into this state ? I quit everything, did "npm remove alasql", then "npm install alasql", DROP still gave the error if it was the first operation, but CREATE as first operation worked. And now the database is persistent across quit/relaunch of Firefox, too. I must have gotten the storage into some weird state or something.
   
   Tried building in Electron, and that "alasql no default export" error made the build fail every time. Back to Angular, and tried to eliminate it. Tried all kinds of variations of the import statement in mdsql.ts and the declare/export statements in node_modules/alasql/dist/alasql.d.ts, but no luck.
   
   Then started looking at compiler options, and found something. Added

   
   "allowSyntheticDefaultImports": true
   

   to src/tsconfig.app.json, and that killed the error, but caused uses of "alasql.databases.*" to fail (can import using either "import alasql from 'alasql';" or "import * as alaSQLSpace from 'alasql';", same behavior with either). I can do without "alasql.databases.*", I think. Holding my breath to see if anything else breaks. Build and run in Electron works.
   
   Started wiring the database further into my app. Reached a point where I was beating my head against a problem for half an hour, finally noticed compile-time errors from "ng serve", and realized it was using an old copy of one of the source files. Restarted it and app worked. Also, if you change a JSON config file, best to kill "ng serve" and restart it.
   
   Built in electron, and app fails with "alasql.min.js: It looks like you are using the browser version of AlaSQL. Please use the alasql.fs.js file instead.".
   
   Tried adding following to electron/package.json file, later (without "../") in angular.json file, but no change:

   
     "fileReplacements": [
       {
         "replace": "../node_modules/alasql/dist/alasql.min.js",
         "with": "../node_modules/alasql/dist/alasql.fs.js"
       }
     ],
   

   In the app under electron, select View/ToggleDeveloperTools menu item (or ctrl-shift-I) to see console log and errors.
   
   Got the app to run, despite the "alasql.fs.js" error message. And got another message in the console: "This window has node integration enabled by default. In Electron 5.0.0, node integration will be disabled by default. To prepare for this change, set {nodeIntegration: true} in the webPreferences for this window ...". Fixed it; in electron/main.ts, change:

   
     win = new BrowserWindow({ width: 800, height: 600 });
   

   to:

   
     win = new BrowserWindow({ width: 800, height: 600, webPreferences: {nodeIntegration: true} });
   

   
   Hey, the database is persistent under Electron ! I was trying to get to that point. I don't see where it's being stored, though; no new files have popped up in the development tree, that I can see. I thought it would not be persistent, because Electron provides a fresh copy of Chromium engine every time it starts ?
   
   Later, found out my database keys are not auto-incrementing. Strange. Looking in Github, found this issue was reported over 3 years ago and still not fixed. Bummer. And still seeing occasional hiccups where AlaSQL gives errors opening the database or a table of it.
   
   Decided to switch from AlaSQL to Dexie.

   
   npm remove alasql
   

   Later was told "Please remember that any interaction with localstorage is async, so you risk running into problems if you don't handle the async behaviour. I recommend the promise notation from Async" So probably I was doing that wrong.
   
   
9. Switch to Dexie:
   
   

   
   npm install dexie --save
   npm install webpack -g
   

   Took a few hours to get things to compile, had to rework various constructors and such. And then started the battle with Promises; I like synchronous code, but for this I have to use asynchronous.
   
   Took a while just to get opening the database to work properly. Then I had to rework the code a couple of times to get Promises working and data going in and out. Then I still ended up with startup not working: NgInit() requests all the data, but then the HTML code executes before the data has arrived, blowing up everything. Consulting with people online, and they're saying I have to learn about more Angular things, resolvers and services and such. Beginning to think I shouldn't use Angular.
   
   Yes, the more they explain "reactive programming" to me, the more I think I want nothing to do with it. I'll have to try a different approach.
   
   

Java

1. Starting, with NetBeans and Swing:
   
   Downloaded incubating-netbeans-10.0-bin.zip
   Extracted it to /usr/local/share
   apt install ant
   At CLI, run /usr/local/share/netbeans/bin/netbeans
   
   Followed Saleem Gul and Tomas Pavek's "Introduction to GUI Building":
   Created new project of type Java / Java Application, unchecking "Create Main Class".
   IDE downloaded and installed an extension manager.
   IDE activated Java SE.
   
   Created a quick GUI in Swing and ran it:
   In Projects window, right-click on main project's node and choose New / Other.
   In the New File dialog box, choose the Swing GUI Forms category and the JFrame Form file type.
   Set <projectname>UI as the class name.
   Enter my.<projectname> as the package.
   Files are created and GUI builder opens.
   Drag and drop GUI items, when done select Run / Run Project menu item.
   
   
   
2. Get SQLite and JDBC driver:
   
   (There also is "Java DB / Derby", but it seems more complicated than SQLite. Apache Derby)
   
   Followed SQLite Tutorial's "Getting started with SQLite":
   Download Linux binary version of SQLite from https://www.sqlite.org/download.html (it's only about 2 MB)
   Extracted it to /usr/local/share
   cd /usr/local/share/sqlite-tools-linux-x86-3270200
   sqlite3
   type ".quit" to quit
   
   Download SQLite Studio from https://sqlitestudio.pl/index.rvt
   Set Execute permission on the file
   Double-click it to run it
   Installed in /opt/SQLStudio
   Tried it, decided it's better to create database from inside the IDE.
   
   Followed SQLite Tutorial's "SQLite Java: Connect To The SQLite Database Using SQLite JDBC Driver":
   Went to https://bitbucket.org/xerial/sqlite-jdbc/downloads/ and downloaded sqlite-jdbc-3.27.2.1.jar
   Moved JAR file into my project folder
   In NetBean IDE with your project open:
   Select main project node and click on Services tab
   Right-click on Drivers and select New Driver ...
   Specify JAR file
   
   Set up for app to connect through JDBC to database:
   In Services tab, right-click on SQLite driver and select Connect Using ...
   For "JDBC URL" use connection string jdbc:sqlite:matrixdashboard.sqlite3
   Click Finish
   See database appear in next area below Drivers.
   "KDE Wallet" dialog opens up; NetBeans IDE wants to store database login credentials in a secure way (even though there are no credentials).
   Click Cancel two or three times to get rid of dialog.
   
   
   
3. Connect app through JDBC to database:
   
   tutorialspoint's "JDBC - Sample, Example Code"
   mkyong's "Java JDBC Tutorials"
   
   Created table definitions: under Services / JDBC, right-click on Tables and select Create Table ...
   But there seems to be no way to write those definitions into the database, they're just used by the IDE.
   
   In NetBeans IDE, tried right-clicking on main project node and selecting New / Entity classes from database ...
   Interesting code got created, but not quite useful.
   
   Telosys does automatic code-generation from an existing database.
   Laurent Guerin's "Telosys : the concept of lightweight model for code-generation"
   After installing the CLI version, have to edit CFG file to set editor.
   But the documentation is incredibly cryptic, apparently you need a .dbcfg file which I have no idea how to get.
   Gave up on it.
   
   Finally started copying/writing code to connect to database. Took a bit of trial-and-error to get the connect working, key steps were:
   • In NetBeans IDE, right-click on Libraries, select Add JAR/Folder, add sqlite JAR.
   • In code, use driver class name "org.sqlite.JDBC".
   • In code, use connection URL "jdbc:sqlite:matrixdashboard.sqlite3".
   Got the code working, database to table etc.
   
   Some quirks of NetBeans IDE:
   
   
   • Somehow, the main "form" file disappears from the project, so the "Design" button disappears. File still was on disk, so just did an Open File on it, and Design button came back.
     
     
   • In Design mode, can't do GUI design of components that are not top-level ? Found the answer: have to right-click on your main package icon, select New... For modal dialog, select JPanel Form.
     
     
   • But Design mode imposes some restriction: one source file for each UI element (form) you design. So if you have four dialogs which are very similar, figure out a way to design it once, in one class, and use code to hide/reveal/enable/disable elements in the form.
     
     
   • Javadocs: Go to Tools / Java Platforms, for JDK 10 select Javadoc tab. Click on Add URL button, add url "http://docs.oracle.com/javase/10/docs/api/". Now you can right-click on Java classes and see the docs for it.
     
     
   • To generate a Javadocs file for your new classes, go to Run / Generate javadoc (yourprojectname).
     
     
   Put the code into GitHub: BillDietrich / MatrixDashboard
   
   

• Zip the project's dist folder into a ZIP archive. (The dist folder might also contain a lib folder, which you would also need to include.)
• Rename ZIP file to JAR file ?
• On CLI: java -jar <jar_name>.jar

> Why do you think Java is a bad choice?

Lots of reasons.

Java is an old language. It has many problems with it that are never fixed, especially with respect to security. They just let the problems continue from one version to the next.

Java was not designed with security in mind: many parts of it are not secure by default (examples: all the XML parsers are vulnerable to XXE by default, the deserialization vulnerabilities, the crypto, etc). The Java Cryptography Architecture is a disaster. Very few developers can write Java crypto code securely because the architecture assumes the developer is expert in crypto (none are) and warns that it is the developer's responsibility to achieve such expertise before using it (the exact opposite approach of NaCl). The Java documentation is generally poor quality. You get a vague, half-useful explanation of many API methods in the sunny day case, with no explanation of what explanation of what happens if not-so-friendly data is sent in. There are so many little gotchas in the language that are not explained, and are left for the developer or security-reviewer to figure out on their own. For example, Google the dangers of seeding SecureRandom or specifying a default SecureRandom provider, and really there are many, many obscure examples like this.

There are lots of other problems with Java other than security. For example it did not support unsigned ints because one of the people who created it thought it was too complicated (ironically, signed ints are more complicated than unsigned). Java generally takes a lot more code to do simple things than modern languages do. Worst of all, they are now trying to get people to pay for Java SE. And don't forget that fight with Google for Google using the APIs in Android -- Java was originally free for everybody, and then Oracle tried to find a way to get money for it by changing the rules.

Back in the 1990s, Java was wonderful. It gave us an escape from the horrible crap that Microsoft was trying to force on everybody else. It was free. It had functionality built into it that other languages did not support. It had the elegance of C with added features, yet avoided the complexities of C++. That was good for back then, but the bar for software language expectations today is much higher than it was back then in the 20th century.

Since then, times have changed enormously. Nowadays Microsoft is giving us great software (.Net core) that we can use anywhere to escape the horrible mess of Java. Microsoft languages now tend to be secure by default, well documented, and easy to use. Microsoft has gone forward, whereas Java in general (especially Oracle Java) is going backwards if anywhere.

So we don't just complain about Java because it is the cool thing to do. We complain because we have lived through the torture for too many years.

I myself whose career largely involves secure code review and guidance know that I will always be in demand as long as languages like Java are around. But if I were to write production software today, Java is one of the last languages I would consider using. It's just awful.

C#

Flutter / Dart

Get started on Linux desktop app:

Linux Shell Tips' "Getting Started with Flutter on Linux Desktop"
Joey Sneddon's "Google & Ubuntu Team Up to Bring Flutter Apps to Linux"
Daniel Llewellyn's "Getting started with Flutter on Ubuntu"

snap install flutter

# to build Linux desktop apps:
flutter channel dev
flutter upgrade
flutter config --no-analytics
flutter config --enable-linux-desktop
flutter config
# now have 924 MB installed under ~/snap/flutter

snap install flutter-gallery

Install Flutter extension in editor such as VSCode (search for "Flutter" extension, install, restart editor, then run "Flutter Doctor").

cd ~/projects
flutter create flutt2

In VSCode, open folder flutt2.
Open file lib/main.dart, see code.
F5 to run.
Select environment "Dart & Flutter".
App may take 30 seconds or longer to appear.
App window may not paint until you move the mouse.

Code looks like this:

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        title: 'Flutter Demo',
        theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

Get started on Android app:

Vitaly Kuprenko's "Create a mobile app with Flutter"

# install Android studio
# https://developer.android.com/studio
# download .tar.gz file
cd                # to home
tar xf FILENAME   # creates ~/android-studio
cd ~/android-studio/bin
./studio.sh
# see dialog, choose "do not import settings"
# see data-sharing dialog, make a choice
# see welcome dialog, click Next
# see Install Type dialog, choose Standard
# eventually get to Finish, and see components downloaded
# get welcome dialog, click X to quit
# This has created ~/Android
# config is in ~/.config/Google/AndroidStudioNNN

# Edit ~/.profile to add:
export JAVA_HOME="$HOME/android-studio/jre"
export PATH="$PATH:$JAVA_HOME/bin"

sudo snap install --classic flutter
# or
# follow https://flutter.dev/docs/get-started/install/linux :
# download .tar.xz file
cd                 # to home
tar xf FILENAME    # makes ~/flutter

# Edit ~/.profile
# add:
export PATH="$PATH:~/flutter/bin"
# or:
# export PATH="$PATH:~/snap/bin/flutter"

# Edit ~/.profile
# add:
export CHROME_EXECUTABLE="???"

# log out and back in

flutter config --no-analytics
flutter channel dev
flutter upgrade
flutter doctor --android-licenses
# If you get a Java exception:
# In Android Studio, click "Configure", then
# "SDK Manager", then tab "SDK Tools", then
# enable "Command-line Tools".

# optional:
snap install flutter-gallery

flutter doctor -v
# get to point where everything passes
# can leave "chrome - to develop for web" as fail

# Run Studio:
~/android-studio/bin/studio.sh

VSCode:

Install Flutter extension in editor such as VSCode (search for "Flutter" extension, install, restart editor, then Ctrl+Shift+P and run "Flutter Doctor").

cd ~/projects
flutter create flutt2

In VSCode, open folder flutt2.
Open file lib/main.dart, see code.
Run / Open Configurations / Add Configuration "Flutter: Attach to Device".
F5 to run.
Select environment "Dart & Flutter".
App may take 30 seconds or longer to appear.
App window may not paint until you move the mouse.

Code looks like this:

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        title: 'Flutter Demo',
        theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

Android Studio / IntelliJ:

Vitaly Kuprenko's "Create a mobile app with Flutter"
Souvik Biswas' "Flutter: Getting Started"

Install Flutter plugin, which will install Dart plugin. Restart Android Studio.
Create flutter application.
Attach phone in developer mode through USB cable.
Phone has to be logged-in for app to appear.
To use an emulator instead of a phone, select Tools / AVD Manager, do Create Virtual Device, install a system image on it, in list of devices click Run icon nextt to it, see emulated phone, click power button on it.
Run / Edit Configurations, select main.dart, see message at bottom about SDK not configured, click Fix. Path to Flutter SDK is something like /home/USERNAME/snap/flutter/common/flutter (on CLI do "flutter sdk-path").
Run / Flutter Run 'main.dart' in Release Mode
Very first time, wait 5+ minutes for everything to happen. See some warnings about deprecated things in libraries.
Subsequent time, wait 30 seconds or so for everything to happen.
If see packages not resolved, add references to them in pubspec.yaml, then do "flutter pub get".
Demo app will pop up on whole screen; no need to launch it from phone.
Use demo app.
Run / stop 'main.dart' to close the app.

If your app needs permissions, it's not enough to list them in manifest.xml; you also have to go into Settings on the phone and grant the permissions. If you see an "invalid envelope" error, it probably is a permission violation.

Vitaly Kuprenko's "Create a list in a Flutter mobile app"

My first Flutter phone-app: BillDietrich / fake_contacts

Path to Flutter SDK is stored in app's android/local.properties file. Have to change it if you switch between Snap and native forms of Flutter SDK.

Key files:

• android / app / src / main / AndroidManifest.xml (package name, permissions, for Android)
• lib / main.dart
• ios / Runner / Info.plist (permissions description, for iOS)
• pubspec.yaml (name, version number, dependencies)
• build/app/outputs/flutter-apk/app-profile.apk
• build/app/outputs/flutter-apk/app.apk (executable app, for Android)
• .ipa is executable for iOS, but I don't see one produced.
• android/app/src/main/res/*/ic_launcher.png (app icon ?)
• ios/Runner/Assets.xcassets/AppIcon.appiconset/Icon-App-*.png (app icon ?)
• ios/Runner/Assets.xcassets/LaunchImage.imageset/LaunchImage*.png (app icon ?)

iOS sizes: https://jigarm.medium.com/ios-app-icon-and-launch-image-sizes-e8d5990cb72b
For LaunchImage, I picked 320x320, and 2x that, and 3x that

Wasn't able to build for iOS; I think you have to do that on a Mac.

How to publish an app:

Publish to F-Droid ? Google Play Store ? APKMirror (for beta versions of Play Store apps, or new apps from devs already established on Play Store) ? https://apkpure.com/ ? Huawei AppGallery ? Apple App Store ? Cydia (for Apple) ?

Submitting an app to Google Play Store is free, but you have to be a registered Google developer/publisher, which costs $25 one-time ? Starting 8/2021, Google Play Store will accept only AAB format, not APK format.

Submitting an app to Apple Store is free, but you have to be a registered Apple developer, which costs $99/year ?

Flutter's "Build and release an Android app"
Instabug's "How to Release Your Flutter App for iOS and Android"
Anmol Gupta's "Publishing Flutter App To PlayStore"
Gary Sims' "Publishing your first app in the Play Store" (2014)

How to publish to F-Droid:

F-Droid's "Contributing to F-Droid"
F-Droid's "Signing Process"
reddit's /r/fdroid
Wonder's Lab's "F-Droid: how is it weakening the Android security model?"

# Takes a long time and 1 GB of disk space.
# It even updates initramfs !
# Which failed, leaving an unbootable system, and a learning experience:
#   have enough free space in /boot to be able to rebuild.
sudo apt install fdroidserver

# I did this in my project home dir:
mkdir metadata
wget -O metadata/app.id.yml https://gitlab.com/fdroid/fdroiddata/raw/master/templates/app-full
cd metadata
mv app.id.yml YOURAPPID.yml
# Edit the file to fill in fields.
# see https://f-droid.org/docs/Build_Metadata_Reference/
cd ..
fdroid readmeta
# Fix errors.
fdroid lint
# Fix errors.

# Create an account on GitLab
# Create SSH keys for it.
# Fork https://gitlab.com/fdroid/fdroiddata
# Clone the fork to local disk:
cd ~/projects
git clone https://gitlab.com/BillDietrich/fdroiddata.git
# takes a couple of minutes, 500+ MB of disk

cd fdroiddata

# copy YOURAPPID.yml to the  metadata dir, and:
fdroid readmeta   # takes a couple of minutes

git remote rm origin && git remote add origin 'git@gitlab.com:BillDietrich/fdroiddata.git'
git add .
git status      # should be only your file staged
git commit -m "APP new version NNN"
git push -u origin master

Go to your GitLab repo in browser.
On left side, click on Merge Requests.
Click on button New Merge Request.

Set Source Branch to your master branch.
Click button "Compare branches and continue".
Really should set "Description / Choose a Template" to "App Inclusion", but 2/3 of stuff in it didn't seem to apply.

Submit the merge request, see it appear in main repo.
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/8246
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/8483

See "pipeline running".
Probably lots of errors.
Get email about progress.

I'm told I should use Fastlane and remove the Summary and Description variables from YML file. Also remove the commented strings in your metadata, and any "(use those which apply)".

Created a Fastlane (https://gitlab.com/snippets/1895688) directory in top of my source tree, with appropriate files (fastlane/metadata/android/en-US/*) underneath.

Also have to make a tag "v1.0" in source repo.
https://git-scm.com/book/en/v2/Git-Basics-Tagging
git tag -a v1.0 -m "my version 1.0.0"
git tag
git push origin --tags

The lint you run locally is not the same as the "lint" (really rewritemeta) run by the build process. The latter wants to see blank lines in certain places, and certain order of some lines. Tweak your YML until the build process is happy (no more diffs shown).

Thought I was finished, but then told something else (build CI) is failing. Error message "Gradle task 'assembleFdroidRelease' not found".

Eventually got closer.

Every time you change something:
- update README to list new version and description
- update metadata/APP.yml to have new "versionName" value
- update "versionCode" to new value
- update "commit" value to "v" plus "versionName" value
- update "CurrentVersion" to match "versionName"
- update "CurrentVersionCode" to match "versionCode"
- update pubspec.yaml "version" to "versionName" plus "+" plus "versionCode"
- in APP top dir, do "fdroid lint"
- in APP top dir, do "git add .", "git commit", "git push"
- in APP top dir, do "git tag -a vTAGVALUE -m 'message'""
- in APP top dir, do "git push origin --tags"
- NO: copy APP.yaml file to fdroiddata/metadata directory
- NO: in fdroiddata dir, do "git add .", "git commit", "git push"
- if did the initial merge request, get email with results
- if just an update, instead see https://f-droid.org/wiki/page/me.billdietrich.fake_contacts/lastbuild
(also see https://gitlab.com/-/snippets/1896503)

App appeared in store on phone another 1-2 weeks after merge request succeeded. I think F-Droid was having some general build problems at the time.
Fake Contacts app in store

App is set to auto-update in F-Droid, so for subsequent updates, after committing new version to GitHub, just wait for F-Droid to pick it up automatically.

Second app: single-page like the first one:

BillDietrich / fake_contacts_2

Tried to duplicate existing project and modify it, but that failed. Instead, create new project and copy old code across.
Do "git init".

Third app: multiple activities and a service worker:

aseemwangoo's "Flutter and Services"

Future<void> _myfunc() async {
  log("_myfunc: about to call ContactsService.addContact");
  // defined as: static Future addContact(Contact contact)
  await ContactsService.addContact(newContact);
  log("_myfunc: about to return");
}

My First App using Flutter Framework

I made Android app using Flutter framework in 20 days. This is related to Telegram channels, groups, stickers and Bots.

...

I have 4 years experience in programming (php) but 0% experience in app or Java. I was able to learn flutter and dart in one week from YouTube videos. Just check 2 or 3 videos from below playlist, you will find if it is easy or not.
The Net Ninja's "Flutter Tutorial for Beginners"

This is the easiest framework i found to make an app. One of the advantages is same source code will work for both Android and iOS.

PyQt

# use app "Qt 4 Designer" to edit JSONitor.ui file to manage UI
designer JSONitor.ui

# process JSONitor.ui file to create JSONitorUI.py file
pyuic5 JSONitor.ui -o JSONitorUI.py

# run application
python3 JSONitor.py

for ind, filename in enumerate(["System-Existing.json", "System-New.json"]):
    logger.debug('initUI: ind {}'.format(ind))
    logger.debug('initUI: filename {}'.format(filename))
    if filename and os.path.isfile(filename):
        self.currentTextPane = ind


import Utilities.JSONTools as jst
jsc = jst.JSONConverter(logger)
sampleJSON = jsc.getDict(text)

itemModel = StandardItemModel()
if sampleJSON:
    itemModel.populateTree(sampleJSON, itemModel.invisibleRootItem())

C++ and Qt

I think it is a long way to go before you are able to implement a Qml app from scratch, especially if it should run cross-platform (Linux, Windows, MaxOS, iOS, Android). With C/C++ there are additional difficulties that do not exist with higher-level programming languages such as: missing garbage collection (memory leaks), build/deploy management (makefiles), pointer arithmetic.

First of all, I would read the first page of the following CMake tutorial. CMake is a portable makefile-generator for all operating systems and is also used by KDE. Unfortunately, CMake is very complex and the learning curve is very steep (but there is no way around). After you have worked through the first page of the tutorial, you should have an executable program that you can compile with "cmake --build".

Now I would install an IDE. KDevelop or VSCode (with the CMake plugin) or CLion (costs money or use EAP build). Now try to get the CMake tutorial program to work within the IDE. All three IDEs mentioned can handle CMake. If you can start the program via the IDE and see the program output, you have a good starting point for further learning.

Next, I would work through the following tutorial: LearnCpp.com. Since you already have an IDE, you can skip chapters 0.9 - 0.12. Depending on how much experience you already have with Python, you can also skip further chapters. However, you should not skip chapter "9.6 Introduction to pointers". You should skip the chapter "20 Exceptions".

While you are working through the C++ tutorial, you should also continue reading the CMake tutorial.

Now that you have mastered C++ and CMake :-) you should get to grips with Qt. Qt uses a preprocessor process (called MOC) to enrich C++ with reflections and signals/slots. So you need to learn the MOC-specific macros and the behavior of the event-loop. See CleanQt. After that you could start with Qml. Qml uses JavaScript (ECMAScript 6 standard) for the logic, so you need to learn some basic JavaScript as well.

Now you can look at the KDE Tier 1 frameworks especially Kirigami2. Try to get a Kirigami example to work and build your app from there on.

Node.js

JavaScript traditionally only runs in internet browser as a client application.

Node is basically just a so-called runtime environment which allows JavaScript to be executed outside of the browser. Additionally it provides tools for filesystem access and other low-level stuff that doesn't exist in normal "browser" JavaScript as well as a package manager, which ends up making JavaScript a pretty powerful and versatile programming language.

# went to https://nodejs.org/en/download/
# downloaded "Linux Binaries (x64)" tar.xz file

# followed instructions at https://github.com/nodejs/help/wiki/Installation
VERSION=v10.15.3
DISTRO=linux-x64
sudo mkdir -p /usr/local/lib/nodejs
sudo mv node-$VERSION-$DISTRO.tar.xz /usr/local/lib/nodejs
cd /usr/local/lib/nodejs
sudo tar -xJvf node-$VERSION-$DISTRO.tar.xz
sudo rm node-$VERSION-$DISTRO.tar.xz

# added following to .bash_profile and .zshrc
# Nodejs
VERSION=v10.15.3
DISTRO=linux-x64
export PATH=/usr/local/lib/nodejs/node-$VERSION-$DISTRO/bin:$PATH

sudo ln -s /usr/local/lib/nodejs/node-$VERSION-$DISTRO/bin/node /usr/bin/node
sudo ln -s /usr/local/lib/nodejs/node-$VERSION-$DISTRO/bin/npm /usr/bin/npm
sudo ln -s /usr/local/lib/nodejs/node-$VERSION-$DISTRO/bin/npx /usr/bin/npx

# tested installation using
cd ~
node -v
npm version
npx -v

sudo npm uninstall npm -g
sudo rm -fr /usr/local/lib/nodejs
sudo rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*
cd ~
grep -s nodejs ~/.*
# edit matched files to remove *nodejs* from PATH

# went to https://nodejs.org/en/download/current/
# downloaded "Linux Binaries (x64)" tar.xz file

# followed instructions at https://github.com/nodejs/help/wiki/Installation
# But I'm not sure why the version number in the instruction is old
NODEVERSION=v13.11.0
NODEDISTRO=linux-x64
sudo mkdir -p /usr/local/lib/nodejs
sudo mv node-$NODEVERSION-$NODEDISTRO.tar.xz /usr/local/lib/nodejs
cd /usr/local/lib/nodejs
sudo tar -xJvf node-$NODEVERSION-$NODEDISTRO.tar.xz
sudo rm node-$NODEVERSION-$NODEDISTRO.tar.xz


# Added following to user's .profile and ALSO to /root/.profile
# Nodejs
NODEVERSION=v13.11.0
NODEDISTRO=linux-x64
export PATH=/usr/local/lib/nodejs/node-$NODEVERSION-$NODEDISTRO/bin:$PATH

# log out and back in, or
. ~/.profile

# tested installation using
cd ~
node -v
npm version
npx -v

# install web-ext so can develop Firefox extensions
sudo su - root
npm install -g npm
npm install --global web-ext
ctrl-D to get out of SU shell
web-ext --version

https://nodejs.org/dist/latest-v13.x/docs/api/

npm audit
npm prune --dry-run

# ???
depcheck
npm-check
# double-check before removing anything listed as "not used"

Deno

Ruby

Ruby alone:

Ruby is comparable to Python, although maybe more object-oriented, and slower ?
"Ruby isn't compiled so ruby developers have to give away their source code for desktop apps."

Tutorials Point's "Ruby Tutorial"
GeeksforGeeks' "Ruby For Beginners"

Using a text-editor, create a file mytest.rb:

# comment here
n = 100
puts "Hello World #{n}"

ruby mytest.rb

"WxRuby: cross-platform GUI toolkit that is native-looking on whatever platform you are on."

"The standard graphical user interface (GUI) for Ruby is Tk." from Tutorials Point's "Ruby - Tk Guide"

Ruby on Rails:

Rails is a MVC web application framework running on the Ruby programming language.
I think Rails is for database-centric web apps: you have a database and the web app lets users read and modify it, using app logic etc.
Rails Guides' "Getting Started with Rails"
Mehdi Farsi's "Learn Ruby on Rails"



When installing Ruby on Rails, there are some choices: RVM or rbenv or from source or from Ubuntu repos, and sqlite3 or MySQL or PostgreSQL or MariaDB database.

RVM and PostgreSQL on Ubuntu:
HowtoForge's "How to Install Ruby on Rails on Ubuntu 20.04 LTS"

Multiple choices:
Go Rails' "Install Ruby On Rails on Ubuntu 20.04 Focal Fossa"
Raj's "How To Install Ruby On Rails On Ubuntu 20.04"



I installed rbenv / MariaDB on Ubuntu 20.04 following Raj's "How To Install Ruby On Rails On Ubuntu 20.04":

sudo apt update

sudo apt install -y curl gnupg2 dirmngr git-core zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev software-properties-common libffi-dev

wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
# close terminal and re-open it
nvm install node
node -v   # get 14.n.n
npm -v    # get 6.14.n

curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt update && sudo apt install -y  yarn

cd
git clone https://github.com/rbenv/rbenv.git ~/.rbenv
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
echo 'eval "$(rbenv init -)"' >> ~/.bashrc
exec $SHELL

git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build
echo 'export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH"' >> ~/.bashrc
exec $SHELL
du -sh .rbenv

rbenv install 2.7.1
du -sh .rbenv
rbenv global 2.7.1
ruby -v   # get 2.7.1

gem install bundler
du -sh .rbenv

gem install rails
du -sh .rbenv     # 270M
rails -v

sudo apt install -y mariadb-server mariadb-client
sudo apt install -y libmariadb-dev

sudo mysql -u root -p
# At MariaDB prompt:
CREATE USER 'myuser'@'localhost' IDENTIFIED BY 'mypassword';
GRANT ALL PRIVILEGES ON *.* TO 'myuser'@'localhost';
exit

gem install mysql2

# Create new application:
cd ~/projects
rails new myrailsapp1 -d mysql
du -sh myrailsapp1    # 132M
cd myrailsapp1

# Edit config/database.yml to change username and password to values you chose:
default: &default
  adapter: mysql2
  encoding: utf8mb4
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  username: myuser
  password: mypassword
  socket: /var/run/mysqld/mysqld.sock

rake db:create

# Start the application:
rails server -b 0.0.0.0

# Open in browser:
http://localhost:3000
# See app's web page.
# Close page in browser.
ctrl+C to stop app running

# Main HTML page of app seems to be app/views/layouts/application.html.erb
https://www.tutorialspoint.com/ruby-on-rails/rails-directory-structure.htm
https://dev-yakuza.github.io/en/ruby-on-rails/folder-structure/

# Too complicated for me.
cd ~/projects
rm -fr myrailsapp1
gem uninstall mysql2
sudo apt remove libmariadb-dev
sudo apt remove mariadb-server mariadb-client
gem uninstall rails

Django

Go

Rust

sudo apt install rustc
rustc --version

fn main() {
    println!("Hello, world!");
}

rustc mytest.rs 
./mytest

JavaScript

TypeScript

Linux Shell Script

#!/usr/bin/env sh

set -o errexit    # exit on error
set -o nounset    # unset variables are an error

# this is a comment

echo "hello"

read -p 'OK? ' dummyvar

chmod a+x mytest.sh
./mytest.sh

#!/usr/bin/env bash

set -Eeuo pipefail
trap cleanup SIGINT SIGTERM ERR EXIT

cleanup() {
  trap - SIGINT SIGTERM ERR EXIT
  # script cleanup here
}

# this is a comment

echo "hello"

read -p 'OK? ' dummyvar

zenity --info --title="mytest.sh running" --text="the mytest.sh script is running"

kdialog --title "mytest.sh running" --msgbox "the mytest.sh script is running"

whiptail --title "mytest.sh running" --msgbox "the mytest.sh script is running" 10 60
# or:
dialog --title "mytest.sh running" --msgbox "the mytest.sh script is running" 10 60

trap '(( $? )) && notify-send "error happened" || notify-send "all good"' EXIT
# or:
trap 'notify-send "$FINISHED_MESSAGE"' EXIT

Python

#!/usr/bin/env python3

# this is a comment

if __name__ == '__main__':
  print('hello')

chmod a+x mytest.py
./mytest.py

#!/usr/bin/env python3

def func1 (str1):
  """
  docstring comment is here
  """
  print(str1)

if __name__ == '__main__':
  func1('hello again')

python3
# get '>>> ' prompt (Python interactive mode)

>>> import mytest
>>> help('mytest')
>>> help('mytest.func1')
>>> import math
>>> help('math')
# q to get out of help

# ctrl+d to get out of Python interactive mode

# for Linux Mint, no installation needed, Zenity is installed by default.

# For Win10, https://github.com/maravento/winzenity
# Download https://github.com/maravento/winzenity/raw/master/zenity.zip
# and copy the EXE file inside it to the same folder where ipwatch.py is located..

# https://www.linux.org/threads/zenity-gui-for-shell-scripts.9802/
# https://en.wikipedia.org/wiki/Zenity

import subprocess

# in Linux, do a (non-modal) notification, so no wait for user action
subprocess.call(['zenity','--notification','--text',sMsg])
# on Linux, see output as notifications in system tray

# in Win10, only modal-dialog choices are available with WinZenity
# open a modal dialog, so no more checking until user sees the dialog and closes it
subprocess.call(['zenity','--info','--text',sMsg])

# https://plyer.readthedocs.io/en/latest/#
# https://github.com/kivy/plyer
# no way to have notification remain permanently

# do "pip3 install plyer" or "pip install plyer"

from plyer import notification

# in Linux, notifications appear both on desktop (briefly) and in tray

notification.notify(title='SOMETITLE', message=sMsg, app_name='SOMEAPPNAME', timeout=8*60*60)

# https://docs.python.org/2/library/syslog.html

import syslog

syslog.syslog(sMsg)

# to see output:
#   sudo journalctl --pager-end
# or
#   sudo journalctl | grep ipwatch

# https://stackoverflow.com/questions/51385195/writing-to-windows-event-log-using-win32evtlog-from-pywin32-library
# https://www.programcreek.com/python/example/96660/win32evtlogutil.ReportEvent
# https://docs.microsoft.com/en-us/windows/win32/eventlog/event-logging-elements
# https://rosettacode.org/wiki/Write_to_Windows_event_log#Python

# do "pip install pywin32"

import win32evtlogutil
import win32evtlog

win32evtlogutil.ReportEvent(
                            "APPNAME",
                            #7040,       # event ID  # https://www.rapidtables.com/convert/number/decimal-to-binary.html
                            1610612737,  # event ID  # https://www.rapidtables.com/convert/number/decimal-to-binary.html
                            eventCategory=1,
                            eventType=win32evtlog.EVENTLOG_INFORMATION_TYPE,
                            strings=[sMsg],
                            data=b"")

# to see output: run Event Viewer application.

import signal       # https://docs.python.org/3/library/signal.html

# Not sure why this is needed, but it is, otherwise signal will make process exit.
# And sometimes this is not called, even though the signal came in to the main loop.
def handler(signum, frame):
    #print('Signal handler called with signal', signum)
    return

# Not sure why this is needed, but it is, otherwise signal will make process exit.
signal.signal(signal.SIGUSR1, handler)

# Create file to tell sender that it can send signals to us now.
# If we allowed it to send signal before this point, a signal would make this app exit.
gsAliveFilename = "/tmp/serverisup"
fileAlive = open(gsAliveFilename, 'w+')

# SIGUSR1 == 10 in major archs
# send does:  pkill --signal SIGUSR1 -f server.py

objSignal = signal.sigtimedwait({signal.SIGUSR1}, gnSleep)
if objSignal == None:
   print('sleep timed out')
else:
   print('received signal '+str(objSignal.si_signo))

fileAlive.close()
try:
    os.remove(gsAliveFilename)
except:
    i = 1   # placeholder

General tips for Python [to avoid dependency-hell on Linux]:

• Never, ever use "pip" to modify the system python installation. "sudo pip" is right out.
  
  
• Don't try to remove the system python. It's probably used by either distribution system management tools, or by applications installed through the distribution's tools.
  
  
• Use a new venv for each application, and you'll never need to resolve conflicts.

  
  python3 -m venv myapp1
  . myapp1/bin/activate
  pip3 install dep
  # or
  pip3 install -r requirements.txt
  

  
  

Working with python on GNU/Linux systems shouldn't be any more difficult than other operating systems, providing that you're working with venvs and not trying to share one big set of libraries among multiple apps with conflicting requirements.

python3 -m pip install mypy
mypy yourprogram.py

# change:
def greeting(name):
# to:
def greeting(name: str) -> str:

# change:
def greet_all(names):
# to:
from typing import List
def greet_all(names: List[str]):

# change:
my_global_dict = {}
# to:
my_global_dict: Dict[int, float] = {}   # Python 3.6+
or:
my_global_dict = {}  # type: Dict[int, float]   # any version of Python

PHP program

#!/usr/bin/env php
<?php

/*
  this is a comment
*/

echo "hello";

?>

php -r 'phpinfo();' | less

# if that fails, do:
sudo apt install php-cli

chmod a+x mytest.php
./mytest.php

# if you remove the "#!/usr/bin/env php" line and don't do the chmod:
php -f mytest.php

sudo apt install php-gd

Perl program

#!/usr/bin/env perl -w

# this is a comment

print "hello\n";

perl -v

# if that fails, do:
sudo apt install perl

chmod a+x mytest.pl
./mytest.pl

# if you remove the "#!/usr/bin/env perl" line and don't do the chmod:
perl mytest.pl

# to install a needed module:
# https://www.ostechnix.com/how-to-install-perl-modules-on-linux/
make -v
sudo cpan
install MODULENAME
# Expect a TON of operations and output the first time you do this.
# Installing XML::RSS set off half an hour of building on my machine,
# and created 260M of stuff under ~/.local/share/.cpan, maybe more elsewhere.
# Tried to install XML::Atom::Entry, which set off another 5-10 minutes and then failed.
exit

Building a Firefox Extension

I want to contribute to the Containers area:

https://github.com/mozilla/multi-account-containers and related/derived extensions.

Original project was called "test pilot".

Some resources:

https://discourse.mozilla.org/c/test-pilot/containers (but most recent activity is 8 months ago)

https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers (but seems outdated/proposal)

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/contextualIdentities is the missing piece.

Import/export config: issues 1427, 1409, 1420, 1282 in https://github.com/mozilla/multi-account-containers

I want to make an extension that has no UI other than a Settings page.
Started with https://github.com/mdn/webextensions-examples/tree/master/favourite-colour
https://github.com/mdn/webextensions-examples/tree/master/contextual-identities
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/downloads/download

Did:
Copied example code from github.
Changed names etc in code.

sudo bash
npm install --global web-ext
ctrl-D to get out of SU shell
/usr/local/lib/nodejs/node-v10.15.3-linux-x64/bin/web-ext --version

Created repo https://github.com/BillDietrich/ContainersExportImport

In extension project directory:

/usr/local/lib/nodejs/node-v10.15.3-linux-x64/bin/web-ext run --pref privacy.userContext.enabled=true --pref privacy.firstparty.isolate=false --pref privacy.firstparty.isolate.restrict_opener_access=false

In browser running add-on, to see console.log() messages, you don't want web console, you want add-on debugging console. Type about:debugging in the address bar. See your add-on listed. Click the "debug" link for it. A separate window/process will open, showing the output. Click on "console" and enable "persist logs". Then manipulate your add-on. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Debugging

Got the code working (I think) in debug environment.

To sign the extension for permanent but private (unlisted) use, went to Developer Hub - API Credentials. Logged in with Firefox account. Clicked on the "Generate new credentials" button to get API keys. Copied the keys.

Then in CLI, in add-on project directory:

/usr/local/lib/nodejs/node-v10.15.3-linux-x64/bin/web-ext sign --api-key=<JWT issuer> --api-secret=<JWT secret>

Got success, it returned a validation ID, and created a .web-extension-id file and a web-ext-artifacts directory. Inside that directory is the .xpi file.

In Firefox, type "about:addons" in address bar (or do alt-T, a) (or do ctrl-shft-a), see add-ons page. Click on "gear" pull-down menu, select "Install add-on from file" menu item. Navigate to web-ext-artifacts directory and select your add-on's .xpi file.

Go to Developer Hub - My Add-ons and log in to see list of your add-ons.

alert() works in debug mode but is a bit broken in "real mode" ? The text and button appear, but no box around them, and they're a bit separated. Supposed to use Notifications, not alert(), in "real mode".

Type "about:profiles" in the address bar to manage profiles or choose a profile. Click on "Launch profile in new browser" button for new/test profile.

To publish to the world:
Tweak descriptions and settings and versions:
Start at https://addons.mozilla.org/en-US/firefox/
Log in.
Go to https://addons.mozilla.org/en-US/developers/
Locate your add-on and click on its "Edit Product Page".
Click on "Manage Status & Versions"
Publish:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Distribution/Submitting_an_add-on
https://addons.mozilla.org/en-US/developers/addons

Was confused about how to change from self-distributed to AMO (public to world). Got this info: "When you submit a new version on the website, the top of the first page in the submission flow is labeled 'Where to Host'. You should see a button or link there that allows you to change the setting to hosted on the site. You can change that setting every time you submit, depending on what you need."

So, make changes and commit and push them.
Do NOT sign the extension to make XPI file.
Add files to a ZIP file: icons, manifest, package, README, LICENSE, source files:

zip archivename.zip file1 file2 ...
zip containersexportimportVERSION.zip background.js icon*.png LICENSE.md manifest.json options.* package.json README.md
zip decentraleyessimpler1.3.zip background.js icon*.png LICENSE.md manifest.json options.* package.json README.md

Login at https://addons.mozilla.org/en-US/firefox/
Go to https://addons.mozilla.org/en-US/developers/addons
Click on link for the add-on
Do NOT click on "upload new version", instead click on "View All".
Click on "Upload a New Version" button.
Click on "Upload a New Version" button.
Under "Where to Host Version", click on "change" link.
Upload ZIP file.
Click on "Sign add-on" button.
Icon did not get picked up, had to edit that setting later.

If there are errors/warnings about the content of your add-on when you try to publish, you can see same list of errors/warnings by running "web-ext lint" locally.

How to make a desktop-Firefox extension work in Android-Firefox:

MDN's "Developing extensions for Firefox for Android"

To just quickly try your extension in an Android phone:

1. On computer, create .xpi file.
2. On phone, enable Developer Options.
3. On phone, enable Android USB Debugging.
4. Connect computer to phone via USB cable.
5. On computer CLI, do "adb devices" to see that connection is good.
6. On computer CLI, do "adb push filename.xpi /mnt/sdcard/" to copy file to phone.
7. On phone, launch Firefox for Android browser.
8. In Firefox, browse to file:///mnt/sdcard
9. You may have to Allow access to files by Firefox.
10. See list of filenames.
11. Tap on filename.xpi link.
12. In Firefox, click Allow on warnings.

How to make a Firefox extension work in Chrome:

David Rousset's "Creating One Browser Extension For All Browsers: Edge, Chrome, Firefox, Opera, Brave And Vivaldi"
MDN's "Porting a Google Chrome extension"
MDN's "Building a cross-browser extension"
MDN's "Chrome incompatibilities"
mozilla / webextension-polyfill

To just quickly try your extension in Chrome:

1. In Chrome, type "chrome://extensions" in address bar.
2. Enable "Developer Mode" (button in upper-right).
3. Click on "Load unpacked", and choose the extension's project folder.
4. See a box for your extension in the Extensions page.
5. If there is a red "Errors" button for your extension, click it.

Useful snippet to allow use of "browser" in Chrome:

window.browser = (function () {
  return window.msBrowser ||
    window.browser ||
    window.chrome;
})();

But, for me, there are too many differences between Firefox and Chrome, I gave up:

• Various manifest.json differences; requires two separate files.
• Permission "browser_specific_settings" not supported in Chrome.
• Chrome doesn't support Promises (maybe use mozilla / webextension-polyfill).

![Do not use](https://www.billdietrich.me/AbnormalBrain.jpg "Do not use")

Building a Chrome Extension

Building a Thunderbird Extension

My add-on:

https://addons.thunderbird.net/en-US/thunderbird/addon/new-account-types/
https://addons.thunderbird.net/en-US/thunderbird/addon/teclib/
https://github.com/gooselinux/thunderbird
I want to add WhatsApp integration into TB. Chat accounts (e.g. Twitter) seem to be formatted as one integrated timeline from all users, which is not how WhatsApp works. Maybe I want to model it after a newsgroup integration ?

https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird/MailNews_fakeserver
http://test.xennanews.com/
https://www.ngprovider.com/free-newsgroup-server.php

Or maybe I could just have WhatsApp appear as a button on the top, like "Chat", and open as an HTML window in the main pane ?

Thunderbrowse
https://bitbucket.org/alta8888/browseintab/wiki/Home

Config setting general.useragent.override lets you set user-agent string ?
Boolean compatMode.firefox should work too, but doesn't work with WhatsApp parsing for some reason.

Building a VSCode Extension

Installing environment:

1. Install VS Code.
   See "VSCode" section of my "Using Linux" page
   
   
2. Install Node.
   "sudo apt install npm"
   "sudo npm install -g vsce"
   "sudo npm install -g typescript"
   
   
   

Generating initial code:

Use the Yeoman generator:
James Quick's "How To Create Your First Visual Studio Code Extension"
OR:

1. Find an example extension you like from Microsoft / vscode-extension-samples
   
   
2. Copy the code to a directory on your disk.
   
   
3. In VSCode, open the project folder and press F5 to run it. If it runs okay, go to next step.
   
   
4. Delete example directory from project dir.
   
   
5. Copy the code again to a directory on your disk.
   
   
6. Rename project dir from old name to MYPROJNAME.
   
   
7. Change filenames and edit files to use MYPROJNAME instead of old name.
   
   
8. In VSCode, open the project folder and press F5 to run it. [Best to have cursor in your extension.ts file when you press F5 ?]
   
   

VS Code Extension Samples
Sample code illustrating the VS Code extension API

Running code in debug mode:

1. Launch VS Code, choose File / Open Folder and pick the folder that you generated.
2. Press F5 or click on the Debug icon and click Start.
3. Your extension will be compiled and run.
4. A new instance of VS Code will start in a special mode (Extension Development Host) and this new instance is now aware of your extension.
5. If the extension operates on the document in the editor window, have the cursor in that window when you run your extension, don't have the cursor in the debug output window.

Problems:

Project is failing to compile. Typescript not installed ?
VSCode's "Editing TypeScript"
Run "tsc --version" to check.
Run "sudo npm install -g typescript" to install.


If you ever wipe out the node_modules tree (perhaps when backing up and restoring), in the project directory do "sudo npm install".

Running code in normal mode:

1. Did the stuff in Using Git and GitHub section.
2. To run the extension in normal VSCode, not debug:
   1. Make a ~/.vscode/extensions/linkcheckerhtml directory.
   2. Copy files from linkcheckerhtml development directory to that new directory. Files/trees to copy are: linkcheckerhtmlicon.jpeg, LICENSE.md, node_modules, out, package.json, README.md
3. sudo npm install -g vsce
4. To package the extension into a .vsix file, without publishing it to the store, do "sudo npm install -g vsce" and then "vsce package". If you want to share your extension with others privately, you can send them your packaged extension .vsix file.
5. To install an extension from .vsix file, either:
   • code --install-extension myextension.vsix   , or
   • In VSCode GUI, in the Extensions view command drop-down, select the "Install from VSIX" command.

Publish to the extension Marketplace:

1. You have to have an Azure DevOps organization.
2. Create a publisher in the Marketplace publisher management page.
3. Have to have a VSIX file.
4. In Marketplace publisher management page, do "add an extension", upload the VSIX file.

Update the extension in the Marketplace:

1. Have to have a VSIX file.
2. Log in to your Azure account.
3. Use this link to go to Marketplace publisher management page.
4. In Marketplace "Manage Publishers & Extensions", right-click on your extension's icon, select "Update", upload the VSIX file, click Upload button.
5. See message "It's live !" and status "Verifying", but still see old version number.
6. Log out of your Azure account, if you wish.
7. Get an email when verification is complete.
8. Quit VSCode and re-launch. Check that new version is being used (may have to do a Reload). Test.

Publish to open-vsx.org so it's available to VSCodium:

Uses your GitHub account. Need Eclipse Foundation account to sign publisher agreement.
Open VSX Registry

Automated testing of your extension ?

VSCode's "Testing Extensions"
Jan Richter's "New tools for automating end-to-end tests for VS Code extensions"
Mocha

Bash script to run via cron

systemd Service

Simple script to run when system boots:

Best if your script file /FULLPATH/SCRIPTNAME.sh is NOT under /home, because if user's home directory is encrypted or not mounted, script will be inaccessible.

Create file /etc/systemd/system/YOURSERVICENAME.service:

[Unit]
Description=MY DESCRIPTION HERE
#After=network.target
After=network-online.target
Before=graphical.target
Before=multi-user.target

[Service]
Type=simple
ExecStart=/FULLPATH/SCRIPTNAME.sh

[Install]
WantedBy=multi-user.target

Create file /home/FULLPATH/SCRIPTNAME.sh:

# whatever it's supposed to do, maybe just something like:
touch /tmp/laststartup

Set permission and enable the service:

chmod a+x /FULLPATH/SCRIPTNAME.sh
sudo systemctl enable YOURSERVICENAME
sudo systemctl status YOURSERVICENAME --full --lines 1000
sudo systemctl start YOURSERVICENAME
sudo systemctl status YOURSERVICENAME --full --lines 1000

After system boot:

sudo journalctl | grep YOURSERVICENAME

Nemo file-explorer actions/scripts

#!/usr/bin/env bash

echo "script test1.sh executed" `date` >~/test1.log.txt
echo "arguments " $* >>~/test1.log.txt
echo "env:" >>~/test1.log.txt
printenv >>~/test1.log.txt

zenity --info --title="test1.sh running" --text="the test1.sh script is running"

chmod a+x ~/.local/share/nemo/scripts/test1.sh

Dolphin file-explorer actions/scripts

Thunar file-explorer custom actions

Miscellaneous

#!/usr/bin/php
#!/usr/bin/env php
# second form is more portable than the first form

Run a script when some event occurs (such as attaching a USB drive):

Put a file "autorun.sh" on a USB stick that is EXT4 format (MS-DOS format does not work). Set execute permission on the file. When attach the drive, get a prompt asking if want to run the file, click Run.

Trickier, more flexible ways:

From Ask Ubuntu question:

Find the *.mount name for your drive:

systemctl list-units -t mount | grep media
# insert your device
systemctl list-units -t mount | grep media
# find the added name

Create file /etc/systemd/system/YOURSERVICENAME.service:

[Unit]
Description=MY SCRIPT TRIGGERED WHEN DRIVE XXX INSERTED
Requires=media-YOURMEDIALABEL.mount
After=media-YOURMEDIALABEL.mount

[Service]
ExecStart=/home/FULLPATH/SCRIPTNAME.sh

[Install]
WantedBy=media-YOURMEDIALABEL.mount

Create file /home/FULLPATH/SCRIPTNAME.sh:

Set permission and enable the service:

chmod a+x /home/FULLPATH/SCRIPTNAME.sh
sudo systemctl enable YOURSERVICENAME.service

"If the service is failed somehow (for example, the script is not executable), your mount point will change to OLDMOUNTPOINTNAME1 next time you mount the USB device. To fix this issue, execute 'sudo systemctl reset-failed'".

Another way: using udevadm and creating a file in /etc/udev/rules.d/. But using systemd (above) is better because the systemd service won't trigger until after the filesystem is mounted.

Another way: Nemo file-explorer in Mint has Edit / Preferences / Behavior / Media Handling / "Prompt or autorun/autostart programs when media are inserted" check-box. But I don't see how to specify a program. If I turn off that option, no Nemo window is opened when I attach a USB drive, even though the "automatically open a folder" option still is checked. See Nemo file-explorer actions/scripts

In Nautilus file-explorer under Edit / Preferences / Media you can choose "other action" and then "custom command". https://github.com/Alfcx/linux-mint-nemo-actions https://linuxconfig.org/how-to-extend-the-gnome-nautilus-file-manager-with-custom-scripts

In Ubuntu, Activities / Details: https://help.ubuntu.com/stable/ubuntu-help/files-autorun.html

C programming language:

An important point made by some people: we really should stop using the C language (created in 1972-3). It is not memory-safe and type-safe, doesn't have the concepts of exceptions (it always just does something and keeps going), heap, strings. Unfortunately, the Linux kernel and much of the user-space code is written in it. This leads to tens of thousands of bugs in Linux today, including security vulnerabilities. Maybe C is appropriate for very low-level system programming, as an alternative to assembly language. But for apps and services and modules, not.
John Regehr's "A Guide to Undefined Behavior in C and C++"
Alex Gaynor's "Modern C++ Won't Save Us"
Ian Barland's "Why C and C++ are Awful Programming Languages"
Quora thread "Is C that bad of a programming language?"
Catalin Cimpanu's "Chrome: 70% of all security bugs are memory safety issues"

What is better, and a reasonable evolution from C ? Probably Rust
But: Drew DeVault's "Rust is not a good C replacement"

Cross-compiler that runs on Linux and makes an EXE for Windows: MinGW ("sudo apt install mingw-w64").