Where we at

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
electron, javascript
Domain
desktop

Research direction

The issue lists broad work areas including the debugger, wp-text window, webserver, guest database verbs, undo, signing, and Electron distribution, but names no files or tests. Start by reviewing the installation plan for virgin frontier.root and nodeEditor.root; completion criteria are not defined beyond getting the desktop app running across Electron-supported platforms.

Written by the indexing model from the issue text.

Description

  • The menu editor
  • The debugger
  • Writing text, the wp-text window
  • Serving websites, tcp stream verbs and the kernelized webserver
  • Guest database verbs
  • The rendering half of the website framework
  • Undo
  • The download, what a user gets, plus signing and notarization
  • The kernel's value types
  • The no-cards decision
  • Regex

I got rid of all the claude verbiage. everyone knows what the menu editor is, and all the rest of it.

the menu editor is working now.

we're moving toward getting a shipping disk put together, ready to be installed on a user's machine.

that's my next step, installing the virgin frontier.root and then bringing in nodeEditor.root as a guest database, and shake that out.

my aim is to have the desktop app running everywhere Electron runs, i want to get this thing going, tired of being the only user.

it is starting to feel reliable, but not all the way there yet, the outliner is the core, and it's very much debugged, having been part of my JS outliners since 2013.

Dominant language
No language data
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/helloFrontier

All issues in scripting/helloFrontier

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.