Framework for web development
Senna UI core framework
This package provides a series of JS and SCSS extensions that augment the base functionality provided by the celeritas-ui-core framework.
`@aws-amplify/ui` contains low-level logic & styles for stand-alone usage or re-use in framework-specific implementations.
Core UI framework for Perazim SPACE Platform
TypeScript definitions & runtime schemas for the **Agent-User Interaction (AG-UI) Protocol**.
Positioning library for floating elements: tooltips, popovers, dropdowns, and more
Large-scale declarative graphic ui core framework
A framework-agnostic toolkit for building UI extensions on top of the Netlify platform.
Floating UI for the web
UI-Router Core: Framework agnostic, State-based routing for JavaScript Single Page Apps
Core components of react-admin, a frontend Framework for building admin applications on top of REST services, using ES6, React
Modern and scalable routing for React applications
Modern and scalable routing for React applications
Modern and scalable routing for React applications
A supported set of Office UI Fabric Core definitions bundled for use in the SharePoint Framework
Important: this is an internal API. Expect breaking changes.
Framework-agnostic core runtime for assistant-ui
The front-end framework for building experiences for Office 365.
Base components for Ionic
Core primitives for building autocomplete experiences.
base library for oclif CLIs
Nested/Data-driven/Framework-agnostic Routing
The UI framework and standard UI library of CKEditor 5.
Include the Office UI Fabric Core framework in your rails app
Provides an application infrastructure based on the Sencha/extjs UI framework, as well as several utilities and example applications. It houses the core application container framework and component model infrastructure that play a key role in the RAD/Agile orientation of CompassAE.
Context is a contextual UI framework. It is based on the Model View Presentor model. The idea is that you have model objects that represent the core data in your application. You also have views that represent the user interface input and output. Finally you have "contexts" that represent a user situation in the application. The logic that ties the models and views resides in the contexts. The main advantages to this model are that you can easily write UI unit tests and you can easily create bridge patterns for supporting multiple widget sets (although only GTK+ is supported at the moment). Context is intended to be extremely minimal. Only the top level abstract classes are included. It is *not* a widget set! You have to write your own models, views and contexts.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.