Skip to content
CEagle

TI-BASIC by upload

No repository, no build, no GitHub App. You write the listing once and attach a file for each version.

A TI-BASIC project publishes by upload. There is nothing to compile, so there is no repository, no manifest and no GitHub App.

The shape of it#

  1. Create a project and choose TI-BASIC

    The language is fixed once set, so a TI-BASIC project cannot later become an ASM/C one.

  2. Open the Flight tab

    Connecting the source needs no input at all. An upload source is created for you.

  3. Write the listing

    Title, summary, description, author, categories and tags. This belongs to the project, not to a version, so you write it once.

  4. Publish a version

    Attach the file and give it a version number. That is a release.

  5. Publish the next version

    Attach the new file, bump the version. The listing is reused.

The listing#

Written once, on the Flight page, and reused by every version afterwards.

Fields
Title1 to 64 charactersRequired

The program name on Roost.

Summaryat most 140 characters

One line. This is what appears in listings and search results.

Descriptionat most 4000 characters

The long text on the program page.

Authorat most 64 charactersdefaults to the project owner

Who to credit.

Categories1 to 4Required

From the registry catalog.

Tagsup to 12

Free-form.

Hiddenoff by default

Downloadable by address, but left out of listings and search.

The publish button stays unavailable until the listing has everything a release needs, which is the console's way of telling you the listing is not finished yet.

Publishing a version#

Attach the file and give it a version number. That is the whole form: the listing is already on the project and is reused.

What a version takes
Fileusually an .8xpRequired

The calculator file itself.

Versionat most 24 charactersRequired

No format is enforced, but pick one convention and keep it.

Variable namedefaults to read from the file

Override it only if the file carries the wrong one.

Variable typedefaults to read from the file
Archiveddefaults to read from the file

Whether the program should land in archive memory.

What you do not get#

Repository projectsTI-BASIC
Build logyesthere is no build
Build on pushyesno
Dependenciesyesno
Manifest in the repositoryyesthe listing is in the console
Library archivelibraries onlyno

Dependencies are the one that occasionally surprises people. A TI-BASIC program cannot declare that it needs a library, because TI-BASIC programs do not link against LibLoad libraries.

Moving to ASM/C later#

You cannot. The language is fixed once set.

If a TI-BASIC program grows into a C program, create a second project at a new address, and archive the first one with a description pointing at the new one. Both addresses stay claimed, which is the whole point of them being permanent.

CEagle documentation