Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

The corner is turned

Ouverte
  • Quelque chose ne va pas ?
#17 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Documentation
Clarté
À clarifier
Activité
Active
Stack technique
electron, javascript, sqlite
Domaine
desktop

Piste de recherche

This issue is a project announcement rather than a specific change request. No files or tests are mentioned for modification. To find work to contribute, browse other open issues in the repository for tasks labeled as bugs, features, or documentation improvements. The project is an Electron-based desktop application written in JavaScript.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

I sent this email to longtime friends who are interested, a small group, including people who worked on Frontier at UserLand.

Good morning, the product release is complete now.

  1. Source is available. Includes worknotes on every new release.
  2. A key written by Claude to be ingested by your LLM, so it comes knowing a lot about the app, and how to work on it. An overview. I want to work on this and make it really shine. Make it be that you have all the same stuff I have.
  3. Build instructions, to create the app we're running from the source code.
  4. Download page for getting something you can try out without building anything.
Notes

If you poke around you'll find all of this easily, the repo is not yet cluttered, and I hope to keep it that way.

There's a lot being released here.

Caveat -- there are lots of bugs, you will find many and also many missing pieces. And there are new features that have never been in Frontier before and there will be more of those.

It uses SQLite for the odb. That has advantages, but makes the connection betw Guest Database files and the data in the files not one and the same, but you can export to get a transportable version of the file. I'm not sure I would have agreed to this if I knew how different it would be, but I only found out later, and Claude seems to think this the right way to go. Will be interested in hearing what friends think.

BTW one of the advantages of SQLite that we have yet to explore at all is that we will be able to use SQL queries on the odb content. And you will be able to use Frontier to create databases and query them. I think that easily makes the inconvenience worthwhile.

There are root updates flowing, every time there's a new capability they often come with glue scripts and example scripts. So even if you're not running the software yet, it may make sense to subscribe in your feed reader.

https://bits.codecasting.org/frontier.root/rss.xml

Right now the menubar is just what came out of my last release of the OPML Editor. I have on my list to do a fairly large scale-down of that to just the essential stuff.

I want to have an RSS feed so these emails are unnecessary, but we're not there yet. But the bits.codecasting feed is a pretty good standby -- from that you can extrapolate whether there's been recent activity, and what its been about.

One former Frontier user show up. I didn't know him, but he posted a support request and from that it sounded like he knew his way around the root, and he did.

I haven't been promoting the existence of this repo. I am happy with the process as it is now.

Also one new person on the list today, Andre Radke who was like the OG Anunoby of the team at UserLand. I apologize for making an analogy to the NBA. I'm a fairly rabid Knicks fan esp after last season. Oh man.

We're gettin somewhere! ;-)

Langage dominant
JavaScript
Étoiles
3
Forks
0
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de scripting/helloFrontier

Toutes les issues de scripting/helloFrontier

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.