A social network which allows users to share data more efficiently, including apps, creating an efficient environment for collaboration.
A novel paradigm in human – data interfacing. Warp works differently than Windows or POSIX systems.
Drives are software implementations, always the same API with different backends.
File Types are not a part of the system, they are loaded on session basis, through Layouts.
Layouts are packages that can be published and carry Apps, Brands, FileTypes but can basically store any user defined data.
Brands are data definitions, test functions returning true/false which Warp uses during inspection and App evoking.
Apps are created as small as possible, almost at component level and aren’t triggered directly by User. App life-cycle is handled by Warp.
Development tools are integrated and are also based on Brands. Vector IDE developers can expose any data as a GUI component, appearance and behavior rendered based on currently loaded Brands.
A Vendor agnostic cloud interface bringing researchers, vendors and end users together. Instead of building massive frontend apps and systems, content providers can use Warp components to quickly build and deploy GUI Apps for their services – cloud, browser or native. Since Warp is integrating development tools, Users can change these Apps, and collaborate on further development. Quote from Redhat : “No single cloud holds the keys to your success. Vendor-agnostic, open source platforms do. With an open hybrid cloud strategy, you stay agile no matter the complexity or environment.”
Operating environment implemented as a hybrid of a classic Browser ( Chrome ) and a Desktop/App Manager ( MS Windows Explorer for example ). It exposes relevant API’s , programable through an integrated IDE, allowing developers and users instant App changing, reloading, hot swapping, sharing.
A Browser with extended capabilities. The extended API’s are not part of “window” variable, they are exposed as Javascript var “warp”, this makes Warp content backward compatible. On older Browsers most these features are accessible by loading the Engine.js as a script. Some of Engine’s features are accessible only through native Warp app, as they are implemented on native side, such as CORSless fetch, native OS drive access through Drive, Sockets etc.