ClosedBit Guide Part 1: Project Basics

#Part 1. Project Basics

#Part 1 Section 1. Files You Actually Touch

Most work starts in a .cbp file. That file is the source you edit in ClosedBit Studio. A compiled app becomes .cba while you are testing, .exe when you want a Windows program, .dll when another host needs to load it, and .cbl when you are packaging a reusable ClosedBit library.

Use .cb for ClosedBit-owned data: saves, packed resources, validated containers, and compiled asset sidecars. Use .cbs for object or asset scripts that belong beside a scene or component.

Extension	Role
`.cbp`	Program source
`.cbs`	ClosedBit Scripting source used by servers, scenes, and components
`.cbw`	ClosedBit Web container holding HTML, CSS, sandboxed JavaScript, images, and other page files
`.cb`	Validated ClosedBit data
`.cba`	Runtime package
`.cbl`	Compiled library
`.dll`	Native library export
`.exe`	Windows app export

#Part 1 Section 2. A Clean Folder

Keep source and output separate. The compiler should write to bin; your original source and assets should stay outside that folder.

MyApp/
  app.cbp
  ui.html
  assets/
    logo.png
    player.obj
  scripts/
    door.cbs
  bin/

If a compiled .exe only works from the source folder, the package is incomplete. Rebuild it instead of manually copying random DLLs.