# <!-- 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": "L4wsHeoM47FHO9DsZrkcqwgcDwvnsvn2sQ7SVVIUMIQQCrLthPRQVJppgZOWkb2V"
"layout:input-next": "/intent/1260/"
"layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "false", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "true", "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": "信息通讯技术", "url": "/intent/1035/"}]
"item:title": "Web Apps Integration"
"item:votes": +1
"item:add-vote": "#addnote"
"item:intent": "/intent/1260/?l=cn"
"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=cn"
"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": "L4wsHeoM47FHO9DsZrkcqwgcDwvnsvn2sQ7SVVIUMIQQCrLthPRQVJppgZOWkb2V"
"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/">请，<i><u>登录</u></i>。</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=cn#r-63"
    "created": "2020-03-23T06:17:21.366000"
    "vote": "[+]"
  - "id": "r-230"
    "mtrans": |

        我有一个名为[additive guis](https://github.com/samsquire/additive-guis)的系统，用于生成GUI，其中GUI由语句组成并构成查询。然后，运行时将基于查询生成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=cn#r-230"
    "created": "2021-01-27T19:40:10.579452"
    "vote": ""
"base:js": "/static/js/base.c7357c06cc89.js"