FluidFrameDev — a funny, opinionated Anvil guide. Tiny apps that teach client/server patterns, Data Tables, Uplink tricks, auth, and deploys. Python in a tux, code in sweatpants.
https://hirabarton.io/
|
||
---|---|---|
.gitea | ||
tutorials | ||
README.md |
README.md
FluidFrameDev 🧪🐍
Anvil tutorials that slip smoothly from client to server.
Python in a tux, code in sweatpants.
What’s inside
A set of small, sarcastic, and surprisingly practical Anvil guides you can finish in coffee-sized chunks:
- 01 – Hello, Fluid Frame: Button → server call → dopamine.
- 02 – Data Tables: Persist stuff like a functioning adult.
- 03 – Server Modules: Secrets and logic where JavaScript can’t see them.
- 04 – Uplink: Talk to your local machine like it owes you money.
- 05 – Auth: Users, roles, and pretending to be an enterprise.
TL;DR demo
Client (Form1
)
from anvil import *
import anvil.server
class Form1(Form1Template):
def button_1_click(self, **event_args):
msg = anvil.server.call('hello_server', self.text_box_1.text or "World")
Notification(msg, timeout=2).show()
Server (ServerModule1
)
import anvil.server
@anvil.server.callable
def hello_server(name):
return f"Hello from the server, {name} 👋"
Run ▶️. If it works, nod like you meant that to happen.
Repo map
tutorials/
– step-by-steps you can copy/pasteexamples/
– tiny scripts showing patternsassets/
– screenshots, gifs, and banners
Why FluidFrameDev?
- No JavaScript required (but you can still flex).
- Python everywhere.
- Deploy in minutes, not after the next sprint.
- Learn by building, breaking, and laughing at your own mistakes.
Tutorials
- 01 — Hello Fluid Frame
- 02 — Data Tables
- 03 — Security (RBAC + secrets)
- 04 — Uplink: File Hash
- 05 — Auth: Roles + UI
License
MIT. Steal the jokes too.