# "*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml" # "base:title": "0oo - Additive GUIs" "og:title": "Additive GUIs" "og:description": "I have a idea whereby you specify the relationships of widgets on the screen and the computer generates the layout. Rather than positioning widgets manually, the computer generates the layout. Essentially the widgets are an inequality formula where X and y is set relative to one another. We say that one widget is left of another widget or another widget is below another. This is how you might describe practically any GUI The idea is that the computer generates variations of the layout and the human reviews them. You also define the data flow between widgets. BackedBy is how we …" "og:image": "https://avatars0.githubusercontent.com/u/28134655" "og:url": "/method/67001/" "base:css": "/static/css/bootstrap.min.9c25540d6272.css" "base:extra-css": "/static/css/base.57997aeac1df.css" "base:favicon": "/static/favicon.acaa334f0136.ico" "base:body_class": "" "layout:logo": "/static/0oo.8d2a8bbef612.svg" "layout:index": "/" "layout:menu": "/menu/" "layout:categories": "/intents/" "layout:ideas": "/methods/" "layout:projects": "/projects/" "layout:users": "/users/" "layout:about": "/about/" "layout:help": "/help/" "layout:bug_report": "https://github.com/wefindx/0oo" "layout:login": "/accounts/login/" "layout:light-off": "/darken/?darken=true" "layout:set-multilingual": "/mulang/?mulang=true" "layout:lang": "言語" "layout:set-language-post-action": "/i18n/setlang/" "layout:csrf-token": "sg9I0lGuVQCt53MsxYNeY6KhjPizv8TjFn6gi0PXNcgDy64idEDOSqou2tNBna8J" "layout:input-next": "/method/67001/" "layout:languages": [{"code": "ja", "is-active": "true", "name": "日本語"}, {"code": "lt", "is-active": "false", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "false", "name": "简体中文"}, {"code": "en", "is-active": "false", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}] # "item:parent:intents": [{"url": "/intent/19001/", "title": "Programming too difficult"}] "item:title": "Additive GUIs" "item:summary": "Specify the attributes of the GUI and let the computer generate the GUI" "item:voting": +1 "item:voting:add": "/admin/hlog/voting/add/?method=67001" "item:voting:csrf_token": "sg9I0lGuVQCt53MsxYNeY6KhjPizv8TjFn6gi0PXNcgDy64idEDOSqou2tNBna8J" "item:voting:submit-value-option": {"selected": "[-]", "value": "-"} "item:voting:submit-value-option": {"selected": "[+]", "value": "+"} "item:base-administration": false "item:body": | I have a idea whereby you specify the relationships of widgets on the screen and the computer generates the layout. Rather than positioning widgets manually, the computer generates the layout. Essentially the widgets are an inequality formula where X and y is set relative to one another. We say that one widget is left of another widget or another widget is below another. This is how you might describe practically any GUI The idea is that the computer generates variations of the layout and the human reviews them. You also define the data flow between widgets. BackedBy is how we set the data source for a widget. MappedTo is a reference to a template that defines the GUI for an item in a collection. It's the same as a functional map. The system is configured in triples. Have you ever heard of Todo MVC? https://todomvc.com/ It's a simple problem implemented in many frameworks. The problem is a to-do list. This is a to-do app written in additive GUIs. You should notice that it is extremely compact. { "predicates": [ "NewTodo leftOf insertButton", "Todos below insertButton", "Todos backedBy todos", "Todos mappedTo todos", "Todos key .description", "Todos editable $item.description", "insertButton on:click insert-new-item", "insert-new-item 0.pushes {\"description\": \"$item.NewTodo.description\"}", "insert-new-item 0.pushTo $item.todos", "NewTodo backedBy NewTodo", "NewTodo mappedTo editBox", "NewTodo editable $item.description", "NewTodo key .description" ], "widgets": { "todos": { "predicates": [ "label hasContent .description" ] }, "editBox": { "predicates": [ "NewItemField hasContent .description" ] } }, "data": { "NewTodo": { "description": "Hello world" }, "todos": [ { "description": "todo one" }, { "description": "todo two" }, { "description": "todo three" } ] } } "item:source-date": "" "item:permalink": "/method/67001/?l=ja" "item:owner": "chronological" "item:created": "2021-09-05T14:14:02.288898" "item:ownerlink": "/user/198/chronological" # "item:link:items": - "id": "l-28001" "url": "https://github.com/samsquire/additive-guis" "text": "Project homepage" "note": "I have a working implementation of additive GUIs here." "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/67001/?l=ja#l-28001" "created": "2021-09-05T14:17:26.054608" "item:link:add": "/admin/hlog/link/add/?parent=67001" "item:project:items": "item:project:add": "/admin/hlog/project/add/?parent=67001" "item:comment:add": "/methods/addnote?parent=67001" "item:comment:add:csrf_token": "sg9I0lGuVQCt53MsxYNeY6KhjPizv8TjFn6gi0PXNcgDy64idEDOSqou2tNBna8J" "item:comment:form": |
  • コメントが新しい問題を挙げるとマークする。
  • コメントが潜在的な解決を提供するとマークする。
  • コメントが推論に役に立つの事実があるとマークする。
  • ログインしてください。 # "item:comment:items": - "id": "a-155001" "mtrans": | [this](https:/ /youtu.be/Zm9B-DvwOgw?t=53)ビデオ? UIをより厳密に定義することは非常に単純化されると思います。 API応答などのコンパクトなUI仕様を提供するだけで、すべてのブラウザーに特定のライブラリがプリロードされている場合(たとえば、誰かがnmpプリロードブラウザー拡張機能を作成した場合)、基本的に、追加のWeb要求なしでUIを非常に高速にレンダリングできます。 、フロントエンド開発を不要にし、そのような宣言型ステートメントの標準化されたAPIビューに置き換えます。 "text": | I wonder, is the [OpenAI Codex](https://openai.com/blog/openai-codex) making an internal representation similar to your formalism of Additive GUIs, when being instructed informally, like in [this](https://youtu.be/Zm9B-DvwOgw?t=53) video? I think it would be great simplification for defining UIs more rigorously. We could just provide such compact UI specifications as an API response, and if all browsers just had the certain libraries preloaded (e.g., by someone making an nmp preloading browser extension), it could render the UI very fast, without extra web requests, basically, making the front-end development unnecessary, and replacing it by standardized API views of such declarative statements. "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/67001/?l=ja#a-155001" "created": "" - "id": "a-156001" "mtrans": | はいMindeyAdditive GUIは、GUIが複数の次元の多次元平面をスプライスするクエリであるという概念に基づいています。ここで、各ディメンションはウィジェットであり、ポイントはそのウィジェットの状態です。おそらく人間の相互作用またはサーバーの相互作用によって、各次元のポイントと各次元の別のポイントのセットとの関係を定義する関数があります。 APIがGUIの動作とレンダリングの方法について非常に高密度の定義を返すことができれば、多くのカスタムコードを削除できます。 無限大のようなデータ指向のGUIとのほとんどの相互作用は、リスト内の項目に対する動詞にすぎません。それらはデータ収集に応じて反応します。または、コレクションにアイテムを追加します。 PowerPointやペイントなどのダイアグラムツールのようなGUIを描画するには、別のモデルが必要だと思います。 "text": | Yes Mindey Additive GUIs is based on the concept that a GUI is a query that splices multiple dimensions multidimensional plane. Where each dimension is a widget and the points are states of that widget. There is a function that defines the relation of the points of each dimension to another set of points for each dimension, perhaps by human interaction or server interaction. If APIs can return a highly dense definition of how the GUI should work and be rendered, then we can remove a lot of custom code. Most interaction with data orientated GUIs like infinity are just verbs against items in lists. They are reactive in response to data collections. Or add items to collections. For drawing GUIs like diagram tools like PowerPoint or paint I think you need a different model. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/67001/?l=ja#a-156001" "created": "" - "id": "a-157001" "mtrans": | // APIがGUIの動作とレンダリングの方法について非常に高密度の定義を返すことができる場合は、多くのカスタムコードを削除できます。 分かりました。問題を単純化するために、問題はそのような宣言型言語を完全に定義し、そのような言語の仕様とコンポーネントとしての(HTML、JS、CSS)トリプレットを介した実装の間のマッピングを構築することです。純粋なDOMか仮想DOMかに関係なく。コンポーネントとしてのそのような各トリプレットの状態空間は、次元として定義するものに対応し、UI全体の状態空間は、それらのコンポーネントの終域の直積としてUI全体の状態空間であり、UI全体の特定の状態はそれぞれ「多次元平面」です。 この概念はうまくいき、重要だと思いますが、実際に機能させるには、用語の完全なセットを定義し、これを実行するためにブラウザーにバインドされたインタープリターを定義するために多くの作業が必要です。 "text": | // If APIs can return a highly dense definition of how the GUI should work and be rendered, then we can remove a lot of custom code. I see. To simplify the matters, the problem then is fully-defining such declarative language, and then constructing the mapping between specification of such language and the implementation via the (HTML, JS, CSS) triplets as components, that is what defines reactive UI elements, regardless of whether its in pure or virtual DOM. The state space of each such triplet as component then corresponds to what you define as the dimension, and state space of entire UI as the Cartesian product of the codomains of those components, each particular state of entire UI being a "multidimensional plane". I see this concept go, and being important, but to get it actually working, I see a lot of work being required to define the exhaustive set of terms, and then the browser-bound interpreter for this to run. "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/67001/?l=ja#a-157001" "created": "" - "id": "a-158001" "mtrans": | この例で機能する非常に単純なインタープリターを作成しました。 Reactを使用しています。レンダリングされたHTMLは見苦しいですが、Todoの追加は機能します。 難しい部分はあなたが言うことであり、ほとんどのGUIをサポートできる十分に柔軟な言語を提供します。 私の目標は、IDEをこの形式のGUIで表現できるようにすることでした。 IntelliJのコードを見るのが怖いです。非常に複雑だと思います。 "text": | I've written a very simple interpreter that works with the example. It uses React. The rendered HTML is ugly but Todo adding works. The hard part is what you say, providing a flexible enough language that can support most GUIs. My goal was for IDEs to be representable with this format of GUI. I dread to look at the code for IntelliJ I bet it's very very very complicated. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/67001/?l=ja#a-158001" "created": "" "base:js": "/static/js/base.c7357c06cc89.js"