# <!-- METAHEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"*": "https://raw.githubusercontent.com/wefindx/schema/master/intent/oo-item.yaml"
# <!-- HEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"base:title": "0oo - Web Apps Integration"
"og:title": "Web Apps Integration"
"og:description": "It&#x27;s time consuming to describe ideas in one app and then visualise ideas in another app. For example, writing down tasks for implementing ideas in project management tools like WorkFlowy and then following multiple steps to open content management systems like WordPress, and within them visual builders like Elementor. The same problem exists with presentation tools like Google Slides, Canva, etc. Could both steps - explaining the idea and visualising the idea - happen in one window?"
"og:image": "https://avatars0.githubusercontent.com/u/28134655"
"og:url": "/intent/1260/"
"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": "p5nxPTk6Mpga7KavIVZ7vxCCcaaTENLbxXpWBZSJq3xeSpBlErPsbxXF76CxrYRH"
"layout:input-next": "/intent/1260/"
"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,"}]
# <!-- TOPIC
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:parent:intents": [{"title": "技術", "url": "/intent/924/"}, {"title": "Information and Communication Technologies", "url": "/intent/1035/"}]
"item:title": "Web Apps Integration"
"item:votes": +1
"item:add-vote": "#addnote"
"item:intent": "/intent/1260/?l=ja"
"item:base-administration": false
"item:body": |
    It's time consuming to describe ideas in one app and then visualise ideas in another app.
    
    For example, writing down tasks for implementing ideas in project management tools like WorkFlowy and then following multiple steps to open content management systems like WordPress, and within them visual builders like Elementor.
    
    The same problem exists with presentation tools like Google Slides, Canva, etc.
    
    Could both steps - explaining the idea and visualising the idea - happen in one window?
"item:permalink": "/intent/1260/?l=ja"
"item:source-date": ""
"item:owner": "Ruta"
"item:ownerlink": "/user/170/Ruta"
"item:created": "2020-03-22T23:15:50.105000"
"item:intent:child:add": "/admin/hlog/intent/add/?parent=1260"
# <!-- LINKS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:method:items":
"item:method:add": "/admin/hlog/method/add/?parent=1260"
"item:comment:add": "/intents/addnote?parent=1260"
"item:comment:add:csrf_token": "p5nxPTk6Mpga7KavIVZ7vxCCcaaTENLbxXpWBZSJq3xeSpBlErPsbxXF76CxrYRH"
"item:comment:form": |
    <li> <textarea name="text" cols="40" rows="10" id="addnote" class="comment-textarea" required>
    </textarea></li>
    <li><label for="id_vote">投票：</label> <select name="vote" id="id_vote">
      <option value="-1">[−]</option>
      <option value="0" selected>-</option>
      <option value="1">[+]</option>
    </select></li>
    <li><label for="id_crawl">静かに：</label> <input type="checkbox" name="crawl" onchange="handleSilently(this)" id="id_crawl"></li>
    <li><label for="id_has_questions">概念：</label> <input type="checkbox" name="has_questions" id="id_has_questions"> <span class="helptext">コメントが新しい問題を挙げるとマークする。</span></li>
    <li><label for="id_has_ideas">発想：</label> <input type="checkbox" name="has_ideas" id="id_has_ideas"> <span class="helptext">コメントが潜在的な解決を提供するとマークする。</span></li>
    <li><label for="id_has_facts">事実：</label> <input type="checkbox" name="has_facts" id="id_has_facts"> <span class="helptext">コメントが推論に役に立つの事実があるとマークする。</span></li>
    <a href="/accounts/login/"><u>ログイン</u>してください。</a>
# <!-- COMMENTS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:comment:items":
  - "id": "r-63"
    "mtrans": |

        これは実際には、サービスの統合、およびユーザーインターフェイスの生成というより一般的な問題の一部である可能性があります。

    "text": |
        This may actually be part of a more general problem of integration of services, and generation of user interfaces.
    "owner": "Mindey"
    "ownerlink": "/user/147/Mindey"
    "permalink": "/intent/1260/?l=ja#r-63"
    "created": "2020-03-23T06:17:21.366000"
    "vote": "[+]"
  - "id": "r-230"
    "mtrans": |

        GUIがステートメントで構成され、クエリを形成するGUIを生成するための[additive guis](https://github.com/samsquire/additive-guis)というシステムがあります。次に、ランタイムはクエリに基づいてGUIを生成します。

    "text": |
        I have a system called [additive guis](https://github.com/samsquire/additive-guis) for generating GUIs where GUIs are composed of statements and form a query. The runtime then generates a GUI based on the query.
    "owner": "chronological"
    "ownerlink": "/user/198/chronological"
    "permalink": "/intent/1260/?l=ja#r-230"
    "created": "2021-01-27T19:40:10.579452"
    "vote": ""
"base:js": "/static/js/base.c7357c06cc89.js"