Runs live, versioned Python application objects on one VM, with a suite of apps: projects, notes, tasks, files and more.

0 downloads

Download zip
Clone
Clone with git
git clone https://gitstable.com/git/askrobots/dbbasic-object-server.git
HTTPS
https://gitstable.com/git/askrobots/dbbasic-object-server.git
SSH
ssh://git@gitstable.com:2222/askrobots/dbbasic-object-server.git

Cloning needs no sign-in. Pushing over HTTPS asks for your username and an access token. SSH needs your key under SSH keys.

danq9 signup: the person chooses the password and name on the confirm page 83c7aa6 2 weeks, 5 days ago History
dbbasic-package.json · 3.4 KB · 61 lines
1{
2 "id": "app-views",
3 "name": "Views",
4 "version": "0.4.0",
5 "description": "Dynamic UI: views as records. One universal renderer draws any view from a blocks descriptor (list, form, detail, count, markdown), so pages, dashboards, and saved searches are created and reshaped by writing data, not code. Routed pages need a site_routes record mapping /views/{view_id:uuid} to site_view_render. 0.2.0 adds /flow -- the workflow, viewable: one page per collection showing its state machine (server-rendered SVG, no JS dependencies), every transition with its guard, what gates writes, what reacts, what gets composed, notifications, derived fields, and where it renders -- compiled live by object_governance from the same declarations the server enforces, so the docs cannot disagree with the system. Most apps forgot help and most frameworks forgot docs because their workflow existed only as the union of what every callback did; a compiled picture cannot rot. 0.3.0 adds /urls: every URL the server answers, compiled from convention, the site_routes and views collections, and the fixed core API constants -- with shadowing called out (convention wins over data). A hand-written sitemap is wrong within a week; a compiled one cannot be. 0.4.0 gives the `list` block a `where` key -- the same standing, server-side narrowing `related` has always compiled to (one field=value param, applied after the permission row filter), now available to a block that is not a child list. It exists because the block vocabulary had a hole an index page kept falling into: a view over ONE SLICE of a shared collection could only say `filters`, which drops the page into the client-side fallback renderer and loses the schema's table, its filter bar, search, sort and the row cap, rendering each row as whatever `title || name || id` happens to be -- a raw id, for most collections. app-returns' bench is the worked case: every shipment with direction=inbound is a permanent property of that page, not a filter a warehouse hand should have to re-pick each morning, and rendering it as a column of shipment ids would have been a page nobody used. `where` takes literals only and is deliberately not run through $record_id resolution: a parent-scoped child list is what `related` is for, and two spellings of one thing is how a block vocabulary rots.",
6 "compatibility": {
7 "dbbasic_object_server": ">=0.1.0"
8 },
9 "objects": [
10 {
11 "id": "site_view_render",
12 "path": "objects/site/view_render.py"
13 },
14 {
15 "id": "site_flow",
16 "path": "objects/site/flow.py"
17 },
18 {
19 "id": "site_urls",
20 "path": "objects/site/urls.py"
21 }
22 ],
23 "schemas": [
24 {
25 "collection": "views",
26 "path": "schemas/views.json"
27 }
28 ],
29 "permissions": [
30 {
31 "path": "permissions/rules.json"
32 }
33 ],
34 "seed": [
35 {
36 "collection": "site_routes",
37 "path": "seed/site_routes.tsv"
38 }
39 ],
40 "migrations": [],
41 "nav": [
42 {
43 "id": "flow",
44 "label": "Flow",
45 "path": "/flow",
46 "blurb": "The compiled workflow: transitions, guards, hooks and reactions",
47 "surface": "operator",
48 "group": "System",
49 "order": 630
50 },
51 {
52 "id": "urls",
53 "label": "URLs",
54 "path": "/urls",
55 "blurb": "Every URL this server answers, compiled from routes rather than listed",
56 "surface": "operator",
57 "group": "System",
58 "order": 640
59 }
60 ]
61}