Projects
A project is a folder
That is the whole model. There is no library, no database, no designated root folder, and nothing registered anywhere.
A project is any folder containing a project.fdraw file. It can live
wherever you keep your work — beside your game’s source, on a memory stick, in a
folder your team syncs. Move it and it is still a project. Copy it and you have
two.
sprites/fluffy cloud/
project.fdraw the drawing — this is your work
exports/ everything you have exported
latest/ the copy your game loads
Making one
New project — from the startup chooser or the Project pane — opens a browser on the folder your project will live inside.
Browse to where it should go, type a name in the row under the listing, and press
Create. That makes a folder of that name inside the one you are standing in,
and puts a project.fdraw in it.
The line at the bottom spells out exactly what is about to be written:
-> /home/you/sprites/fluffy cloud/project.fdraw
The answer is always a child of what you are looking at. The panel browses the parent and names the project underneath, so there is no way to accidentally turn the folder you were merely passing through into a project. The new-folder key in the toolbar makes a parent; the Name row names the project, and the two no longer compete.
The folder is the project’s identity, but not its name for ever: the Project pane’s Name field renames it whenever you like. Folder names are literal — spaces and all — and only characters no filesystem accepts are refused.
A folder that already holds a project is refused, with the reason shown in the panel rather than after the click.
The Project pane
Where the document’s own settings live. Everything about the drawing as an object rather than as a picture.
| Card | Holds |
|---|---|
| Project | Name, Location, and Save, Save as…, New project…, Open project… |
| Recent projects | the ones you have opened before |
| Canvas | size presets from 16 to 256, width and height, a ratio lock, the anchor pad, Apply / Revert, auto-grow, and how much undo history is being held |
| Side walls | Shade — side = front pixel × shade — and a reminder that a rim face in 3D overrides it |
| World placement | Layers bottom to top, Pivot and Px / unit, with the world size that gives you |
Location names where the open project lives, and says not saved yet when it
has no home. With no root folder anywhere in the design, “where is this?” has
exactly one honest answer and it is written down.
Save as… moves a project without renaming it. A document that already has a name keeps it. Only a document that has never been named takes its name from the folder.
Nothing that writes a file you asked for is here — that is the
Export pane. This pane writes project.fdraw, and that is all.
Opening one
Flatty opens on a chooser listing the projects you have opened before, newest first, with Continue “your project” at the top for the one you were last in. Browse… finds one that is not on the list, and New project starts a new one.
The button that is filled is the one you can actually press. With a project picked that is Open; with nothing picked — a first launch — it is New project, because Open cannot work and the strongest mark on the screen has no business sitting on a dead control.
The left column says what you are running: the letterhead, the version, one line about what the program is for, one line saying it is free and that your work is yours, the address, and the credits. Nothing on that screen asks anything of you.
Untick don’t show this at startup to skip the chooser in future; Settings turns it back on. Esc, or Skip, passes it for one run.
Opening or starting a project asks first, whenever there is unsaved work. The document is replaced outright and there is nothing to undo back through, so you get Save first, a button that names what it will lose, and Cancel. There is no don’t ask again on that one: a checkbox agreeing in advance to discard work you have not seen is not the same offer as skipping a question with no stakes.
The status bar shows a * while there are unsaved changes, which is exactly when
that question has something to warn about.
Projects that go missing
A project on an unplugged drive, or in a folder moved outside the app, stays on
the list, greyed and marked (missing), rather than quietly disappearing. An
unplugged drive is not a deleted project, and the entry is the only record the app
holds of where that work lives.
Selecting a missing one in the Project pane offers Forget in place of Open — the one useful thing left to do with it, and the only way an entry ever leaves the history.
The file browser
The same browser serves every job that needs a path: opening a project, creating one, importing a palette, exporting one, adding a brush texture, choosing where to pack one up.
| Part | What it does |
|---|---|
| the path bar | type or paste a path to go there |
| the three keys | up one folder · new folder · your system’s own dialog |
| hidden folders | show dotfiles |
| Places | Home, Downloads, Documents and your filesystem roots, named the way your desktop names them |
| the listing | a .. row at the top, then folders; click to select, double-click to enter, the headers sort |
Folders that already hold a project are badged project, so finding one is reading rather than opening each in turn.
Type a few letters with the listing focused to jump to a name. The image preview at the foot of the sidebar shows PNG, JPEG and GIF files as you highlight them.
The system dialog is offered as a shortcut when one is available, but the built-in browser always works — there is no guarantee a desktop portal is installed, and on a machine with no session there is nothing to call at all. For a new project the system dialog can only navigate, never answer, because it can only hand back a folder that already exists.
Sending one to somebody
Because your textures and palettes live in your libraries rather than inside each project, a project folder on its own is the artwork without the things it was made with.
Pack for sharing…, in the Export pane, copies the project and everything it uses into one new folder you can zip and send.
Where your settings live
The recent-project list, your workspaces and your preferences share one file, and your libraries sit beside it as folders:
| Platform | Settings folder |
|---|---|
| Linux | ~/.config/flatty/ |
| macOS | ~/Library/Application Support/flatty/ |
| Windows | %AppData%\flatty\ |
flatty/
config.json recent projects, workspaces, preferences, your keymap
palettes/ one file per palette
media/ one file per texture or reference
themes/ one file per theme you have made or imported
layouts/ one file per saved layout
Everything is written atomically, so an interrupted write cannot leave you with a truncated file.
Your projects are somewhere else entirely — wherever you put them. Nothing about a project lives in here.