# "*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml" # "base:title": "0oo - Appless OS" "og:title": "Appless OS" "og:description": "Today, pretty much all operating systems allow installation of apps. However, apps share basic functionalities, for example, there is a plethora of calling apps, messaging apps, payment apps, drawing apps, etc. etc. etc. Since all that people really need is the functionality and data, not the apps per se, "Appless OS" virtualizes all the apps and runs them in virtual containers under the hood, and has drivers to emulate the user, and virtualization layers, that provides the functionality of the apps via drivers framework (like "Metadrive") that drives apps, rather than exposing user to interact with them manually, collects and …" "og:image": "https://avatars0.githubusercontent.com/u/28134655" "og:url": "/method/3001/" "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": "Kalba" "layout:set-language-post-action": "/i18n/setlang/" "layout:csrf-token": "c2FQCAZPnyoOURdH1VjfJEjxA1IMMA5q7oGch7N4g7hseIgWNvU6YqTrdERsYMkv" "layout:input-next": "/method/3001/" "layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "true", "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/4001/", "title": "Computer: Operating System"}, {"url": "/intent/105001/", "title": "Programmatic Access and Control"}] "item:title": "Appless OS" "item:summary": "Operating system without user-facing apps. Instead, exposes basic functionalities, high level programming language, API and data." "item:voting": +2 "item:voting:add": "/admin/hlog/voting/add/?method=3001" "item:voting:csrf_token": "c2FQCAZPnyoOURdH1VjfJEjxA1IMMA5q7oGch7N4g7hseIgWNvU6YqTrdERsYMkv" "item:voting:submit-value-option": {"selected": "[-]", "value": "-"} "item:voting:submit-value-option": {"selected": "[+]", "value": "+"} "item:base-administration": false "item:body": | Today, pretty much all operating systems allow installation of apps. However, apps share basic functionalities, for example, there is a plethora of calling apps, messaging apps, payment apps, drawing apps, etc. etc. etc. Since all that people really need is the functionality and data, not the apps per se, "Appless OS" virtualizes all the apps and runs them in virtual containers under the hood, and has drivers to emulate the user, and virtualization layers, that provides the functionality of the apps via drivers framework (like "Metadrive") that drives apps, rather than exposing user to interact with them manually, collects and organizes the data from those apps, and provides it for the user in a unified interface, that implements viewer for items with arbitrary properties as generalized: - Lists - Matrices - Trees - Graphs The "Appless Merge OS / DB" would introduce a high level programming language and a unified API, that allows user to have true ownership of their OS. Instead of "OS" as a framework for apps, it is just an "easily programmable OS, that takes care of being a good DB of everything on it". "item:source-date": "" "item:permalink": "/method/3001/?l=lt" "item:owner": "Mindey" "item:created": "2021-03-14T23:20:57.751286" "item:ownerlink": "/user/147/Mindey" # "item:link:items": "item:link:add": "/admin/hlog/link/add/?parent=3001" "item:project:items": "item:project:add": "/admin/hlog/project/add/?parent=3001" "item:comment:add": "/methods/addnote?parent=3001" "item:comment:add:csrf_token": "c2FQCAZPnyoOURdH1VjfJEjxA1IMMA5q7oGch7N4g7hseIgWNvU6YqTrdERsYMkv" "item:comment:form": |
  • Pažymėkite, jei komentaras kelia naujų klausimų.
  • Pažymėkite, jei komentaras siųlo galimus sprendimus.
  • Pažymėkite, jei komentaras pateikia potencialiai naudingų faktų.
  • Prašome prisijungti. # "item:comment:items": - "id": "a-3001" "mtrans": | Aš pritariu idėjai apie didesnę abstrakciją ir funkcionalumą, taip pat turėti visą išmanųjį telefoną kaip duomenų bazę. Esu įsitikinęs, kad dabartinės „Android“ API jau leidžia tam tikram tikslui priartėti, bet (galbūt) ne taip paprasta, kaip pateikti užklausą duomenų bazėje. Iš esmės, ko norite, yra programų su OS savininko tapatybe skaidrumas iki privačių programų metodų ir saugojimo, bet ne su kitomis programomis be aiškaus leidimo ir ne kitų tapatybių (pvz., Pardavėjo, kuris galbūt įdiegė OS). "text": | I welcome the idea of greater abstraction, and functionality first mindset, as well as having entire smart phone as a database is nice. I'm sure the current Android APIs already allow something approaching that, but (perhaps) not as simply as querying a database. Basically, what you want is the transparency of apps with the OS owner identity up to the private methods and storage of the apps, but not with other apps without explicit permission, and not other identities (like that of vendor, who may have installed the OS). "owner": "Inyuki" "ownerlink": "/user/206/Inyuki" "permalink": "/method/3001/?l=lt#a-3001" "created": "" - "id": "a-4001" "mtrans": | Programos turėtų būti distiliuotos pagal užklausų planus. Yra užklausų planas, kuriame pateikiamos visos programos pateikiamos užklausos ir santykinis kiekvieno tipo užklausų dažnis. Žmonės galėjo suprojektuoti visas programos sąveikas - visus ekranus, kuriuose rodomi duomenys arba kurie leidžia duomenis keisti. Tada užklausų planavimo priemonė gali sukurti efektyvią programą iki atskirų užklausų, naudojamų duomenų išdėstymui. Leiskite kompiuteriams išdėstyti duomenis mums. "text": | Apps should be distilled to query plans. There is a query plan that represents all the queries that an app makes and the relative frequency of each type of query. People could design all the interactions of an app -- all the screens that show data or allow data to be modified. Then the query planner can generate an efficient app, down to the individual queries used to the layout of data. Let's let computers layout data for us. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/3001/?l=lt#a-4001" "created": "" - "id": "a-5001" "mtrans": | Skambinkite jiems „APP PLAN“. Programų planuose yra sąsajos ekranų sąrašas ..... ir ekrane rodomi arba keičiami duomenų laukai. Programų planuose taip pat nurodomas vidinės programos integravimo API, kuris bus naudojamas su ekrane rodomais duomenimis. Taigi būtų skambučio API. ir skambučio API ima skaitmeninį lauką, kuris yra telefono numeris, galite prijungti skambučio API naudodami lauką ekrane "text": | Call them APP PLANS. App plans contains a list of UI screens.....and the fields of data that is displayed or modifiable on the screen. App plans also specify the backend integration API to be used with the data that is on the screen. So there would be a call API. and the call API takes a numeric field as input which is the phone number, you can wire up the call API with the field on the screen "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/3001/?l=lt#a-5001" "created": "" - "id": "a-6001" "mtrans": | Užklausų planuotojai duomenų bazėje nustato, kaip efektyviai vykdyti užklausas, atsižvelgdami į tai, kiek eilučių yra ir indeksų, kuriuos reikia ieškoti. Programų planuose nustatoma, kaip efektyviai išsiaiškinti, kaip įdiegti programas. Gaunant duomenis programų planavimo priemonė atsižvelgs į šiuos dalykus: - duomenys, kuriuos reikia gauti norint parodyti sąsają - kaip struktūrizuoti užklausas, pateiktas į serverį - siųsti užklausą ar siųsti užklausos pavadinimą? - duomenų transformacijos prieš rodant. Kaip sukurti vartotojo sąsają iš duomenų struktūros: Duomenų bazėje duomenys gali būti saugomi kaip medis, grafikas ar matrica. Kaip vartotojui suprantamu būdu pateikti šią informaciją? Programų planavimo priemonė naudos tam tikras euristines savybes, kad generuotų vartotojo sąsajas su skirtukais, sąrašais ir turtingu elementų atvaizdavimu. Šiek tiek panašūs į django administratoriaus ekranus. Planuotojas turėtų įtraukti įvairius įgūdžius į skaičiuojamą ekspertų sistemą, pvz., Prieinamumo reikalavimus, sukurti efektyvias pakartojamas užduotis. "text": | Query planners in database work out how to efficiently execute queries based on how many rows there are and the indexes that need to be consulted. App plans work out how to efficiently work out how to implement apps. The app planner will consider the following things when retrieving data: - data that needs to be retrieved to show the interface - how to structure the queries made to the server - send the query or send a query name? - transformations of the data before displaying. How to generate a UI from a data structure: The database might store the data as a tree, graph or matrix. How to surface this information in a user understandable way? The app planner will use some heuristics to generate UIs with tabs, and lists and rich rendering of items. A bit like django admin screens. The planner should capture various skills into a computable expert system such as accessibility requirements, create efficient repeatable tasks. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/3001/?l=lt#a-6001" "created": "" - "id": "a-21001" "mtrans": | Įdomu tai, kad beveik bet kuri programa yra tik susijusių objektų su modifikavimo taisyklėmis išdėstymas. Galima įsivaizduoti, kad yra kažkas panašaus į „nuo programos nepriklausomus objektus“ (AIRO), kurie kartu elgiasi kaip programa, bet nėra programa, veikiau yra laisvi objektai su savo nepriklausomomis tapatybėmis ir vietomis adresų erdvėse. "text": | It is interesting to consider, that pretty much any application is just an arrangement of related objects of types with modification rules. One could imagine having something like "Application-Independent-Related Objects" (AIRO), that in combination behaves like an application, but are not an application, but rather are free objects with their independent identities and locations in address spaces. "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/3001/?l=lt#a-21001" "created": "" "base:js": "/static/js/base.c7357c06cc89.js"