The Quasar Framework monorepo is a comprehensive Vue 3 UI component library and cross-platform application development toolkit. It provides a rich set of reusable components (QBtn, QTable, QDialog, QLayout, etc.), composables (useTimeout, useDark, useForm, etc.), directives (v-ripple, v-touch-pan, etc.), and plugins (Notify, Dialog, Loading, Dark mode, etc.) that enable building responsive web, mobile, and desktop applications from a single codebase. The framework is distributed as multiple packages: the core UI library (`quasar`), a Vite-based CLI (`@quasar/app-vite`) that supports building for SPA, SSR, SSG, PWA, browser extensions (BEX), Cordova, Capacitor, and Electron targets, a project scaffolder (`create-quasar`), a global CLI (`@quasar/cli`), a Vite plugin for auto-imports and Sass variable injection, an icon generation tool (`icongenie`), and an MCP server for AI agent integration. The architecture follows a monorepo pattern managed with pnpm workspaces. The core UI library is built with Vue 3 and exposes a plugin-based system where components, composables, and directives are registered via a central `install-quasar` entry point. The CLI (`app-vite`) uses Vite and Rolldown as build backends, with mode-specific builders that generate optimized output for each target platform. The scaffolding system (`create-quasar`) generates project templates with optional TypeScript, Pinia state management, i18n, and linting configurations. The documentation site (`docs/`) is itself a Quasar SSR application that dogfoods the framework and includes a custom markdown build pipeline with API documentation extraction from JSON descriptors. Key entry points include `ui/src/vue-plugin.js` (framework installation), `app-vite/bin/quasar.js` (CLI dispatcher), `create-quasar/bin/create-quasar.js` (project creation), and `mcp/src/server.js` (AI agent server). External dependencies include Vue 3, Vite, Rolldown, Vitest, Playwright, and various icon libraries. The codebase demonstrates strong engineering practices with extensive unit, integration, and SSR hydration tests, a well-defined composable lifecycle pattern, and a modular build system that abstracts platform-specific concerns behind consistent interfaces.
Outline Apps is a production-grade, open-source VPN ecosystem consisting of two primary applications: a cross-platform VPN client and a server manager. The client, built for Windows, macOS, Linux, Android, iOS, and the web, connects users to Shadowsocks-based proxy servers by creating a system TUN/TAP interface and relaying packets through a Go-based tun2socks core. It exposes a unified TypeScript UI across Electron, Cordova, Capacitor, and browser shells, with native VPN lifecycle management implemented in Go, Java/Kotlin, Swift/Objective-C, and C#. The server manager is an Electron/desktop and web application that provisions and administers Outline servers on DigitalOcean, Google Cloud, AWS Lightsail, and arbitrary Linux machines, including access-key management, bandwidth metrics, data limits, and OAuth-based cloud onboarding. The architecture is a monorepo that separates a Go networking core, TypeScript web UI layers, platform-specific native bridges, and an infrastructure library of shared utilities. The codebase demonstrates careful engineering in several areas: a composable YAML configuration registry for transport strategies (Shadowsocks, WebSocket, TCP/UDP, multi-hop), a generic IP routing table for split tunneling, structured cross-language error types, and a consistent method-channel abstraction for JavaScript-to-native IPC. Strong test coverage exists across Go packages, TypeScript modules, and native platform code, supported by an extensive CI matrix. However, the repository carries significant technical debt from an incomplete migration from Polymer to Lit, the coexistence of legacy Cordova and newer Capacitor mobile stacks, and numerous platform-specific build scripts. This is squarely an application repository, not a data or research project. The only data-related aspects are telemetry and anonymized usage metrics sent to Sentry and server-administrator-controlled collectors, which are operational concerns rather than research pipelines. Maintenance activity is current, with frequent commits, active issue triage, and a large contributor base, but the broad platform surface and legacy framework overlap make ongoing modernization costly.
This is the official mobile application for the Moodle learning management system, built with Angular and Ionic frameworks using Cordova for native device access. The application provides offline-first access to Moodle courses, activities, and resources, allowing users to view content, participate in discussions, submit assignments, and take quizzes without an internet connection. Data synchronizes with the Moodle server when online. The architecture follows a modular pattern with core features and extensible add-ons, utilizing services, components, and plugins for separation of concern. Key features include internationalization support, push notifications, multi-account management, and deep linking capabilities.
This repository implements the Apache Cordova Camera plugin, which provides a cross-platform interface for accessing device cameras and photo libraries. The plugin supports Android, iOS, and browser platforms, allowing developers to capture images, select from galleries, and manipulate images (resize, rotate, etc.) through a JavaScript API. The architecture follows Cordova's plugin pattern with platform-specific implementations in Java (Android), Objective-C (iOS), and JavaScript (browser). The plugin handles image processing, EXIF data handling, file URI management, and permission handling across platforms. It returns images as either base64-encoded data URIs or file URIs, with appropriate handling for memory management and platform-specific quirks.
cordova-plugin-background-fetch is a Cordova plugin that enables background execution capabilities for mobile applications. It allows apps to wake up periodically (approximately every 15 minutes) to perform background tasks, with support for both timed background fetch events and custom scheduled tasks. The plugin provides platform-specific implementations for iOS (using BGTaskScheduler) and Android (using JobScheduler/AlarmManager with optional headless continuation after app termination). It features a JavaScript/TypeScript interface that communicates with native code via Cordova's bridge, and includes handling for background task completion signaling and timeout scenarios. The plugin is actively maintained with recent updates supporting modern platform versions and build tools.
Onsen UI is a comprehensive mobile UI framework for building hybrid mobile apps and progressive web apps (PWAs) with native-like interfaces. The repository is a monorepo containing a core library built on Web Components, CSS components with iOS and Material Design theming, and official bindings for React, Vue 2, Vue 3, Angular 2+, and legacy AngularJS. The core defines custom HTML elements (e.g., `<ons-navigator>`, `<ons-tabbar>`, `<ons-dialog>`) that encapsulate mobile-specific UI patterns such as navigation stacks, tab bars, side menus, pull-to-refresh, lazy lists, and various form controls. The CSS component library provides a consistent, themable styling layer via CSS custom properties and BEM-like modifier classes. Framework bindings wrap these core elements for seamless integration with modern frontend frameworks. The repository also includes example applications, a CSS component previewer, and extensive documentation schemas. While the framework is mature and feature-rich, it shows signs of technical drift with deprecated APIs, multiple legacy binding packages, and a complex build infrastructure. It is actively maintained but appears to be in a stabilization phase rather than rapid development.
cordova-plugin-ionic-webview is a Cordova plugin that provides high-performance web views for hybrid mobile applications. On iOS, it replaces UIWebView with WKWebView for better performance and features. On Android, it uses the latest evergreen webview (Chrome-based). The plugin implements a local HTTP server to serve app assets via HTTP(S) URLs instead of file:// URLs, which is necessary due to webview security restrictions. It supports custom URL schemes (ionic://, http://, https://), HTML5 mode routing for single-page applications, service worker request handling, and provides JavaScript APIs for converting file paths to webview-accessible URLs. The architecture consists of platform-specific native implementations (Java for Android, Objective-C for iOS) with a common JavaScript interface through Cordova's plugin system.
Apache Cordova CLI is a command-line tool for creating, building, deploying, and managing Apache Cordova-based mobile applications. It serves as a thin orchestration layer over the `cordova-lib` and `cordova-create` libraries, parsing user commands and delegating to those libraries for project management, platform/plugin operations, building, and running. The architecture is straightforward: a single entry point (`bin/cordova`) invokes `src/cli.js`, which uses `nopt` for argument parsing, then dispatches to appropriate functions (e.g., `create`, `platform`, `plugin`, `build`, `run`, `info`). The codebase is mature, well-tested, and actively maintained with CI, CodeQL, and license auditing. However, the CLI is tightly coupled to the Cordova ecosystem and offers no reusable components outside that context. The implementation is solid but follows standard patterns without exceptional craftsmanship.
This repository is a Visual Studio Code extension for developing, debugging, and simulating Apache Cordova and Ionic mobile applications. It provides a comprehensive debug adapter that supports launching and attaching to Android, iOS, browser, and simulated targets. The extension integrates with the Chrome DevTools Protocol (CDP) via a custom proxy to enable sourcemap rewriting and cross-platform debugging, and it offers IntelliSense for Cordova plugin APIs and Ionic framework components. It also includes commands for building, running, preparing, and cleaning Cordova/Ionic projects, as well as telemetry and localization support across 14 languages. The architecture is modular: the core debug session (`CordovaDebugSession`) delegates to platform-specific implementations (`AndroidPlatform`, `IosPlatform`, `BrowserPlatform`) that inherit from abstract base classes (`AbstractPlatform`, `AbstractMobilePlatform`). A CDP proxy layer (`CordovaCDPProxy`) intercepts and transforms messages between the debugger and the target runtime, with specialized message handlers for Chrome and Safari runtimes. Target management is handled by `MobileTargetManager` subclasses (`AndroidTargetManager`, `IOSTargetManager`) that enumerate devices and emulators. The extension also includes a plugin simulator (`PluginSimulator`) that serves the app via `cordova-simulate` and a Socket.IO connection. Key entry points include the extension activation (`src/extension/cordova-extension.ts`), the debug configuration provider (`src/extension/debugConfigurationProvider.ts`), and the debug session class (`src/debugger/cordovaDebugSession.ts`). External dependencies include the Cordova CLI, Ionic CLI, Android SDK, iOS toolchain (Xcode, ios-webkit-debug-proxy), and npm packages like `cordova-simulate`, `socket.io-client`, and `vscode-js-debug-browsers`. The codebase is written in TypeScript and uses Gulp and Webpack for building. While the extension is functionally complete and well-structured, it shows signs of technical drift: many dependencies are outdated (e.g., `applicationinsights` 0.15.6, `socket.io-client` 2.4.0), the Cordova ecosystem has declined in favor of Capacitor, and the large i18n file set (200+ files) adds maintenance overhead. The code contains some legacy patterns (e.g., `eval` for custom require, extensive use of `any` types) and hardcoded timeouts. Despite this, the core abstractions for platform handling and CDP message processing are well-designed and potentially reusable.