User Guide Overview
Relevant source files
The following files were used as context for generating this wiki page:
Acode is a lightweight code editor for Android that provides syntax highlighting, a Linux terminal environment, and a plugin system. This guide covers the core components and configuration options available to users.
Sources: user-guide/index.md:17-21
Core Components and Navigation
Acode organizes its functionality into several primary modules accessible via the main interface or specific triggers.
File Management
The File Browser manages local storage, external SD cards through the Storage Access Framework (SAF), and remote FTP/SFTP connections. It features a Home View for connection management and a Project View for file-level operations like creating new files, folders, or initializing projects from templates.
Sources: user-guide/file-browser.md:14-16, user-guide/file-browser.md:54-58
Integrated Terminal
The Terminal module provides an Alpine Linux environment using proot. It operates as a foreground service and appears as an editor tab. Users interact with the environment through the apk package manager and a dedicated acode CLI tool to open files directly in the editor.
Sources: user-guide/terminal.md:10-14, user-guide/terminal.md:27-35, user-guide/terminal.md:46-51
Command Access and Efficiency
The Command Palette and QuickTools provide rapid access to editor functions. The Command Palette executes commands via a searchable list, while QuickTools offers a customizable toolbar for coding symbols and navigation keys.
Sources: user-guide/quicktools.md:1-5, user-guide/index.md:32-37
System Architecture Flow
The following diagram illustrates how a user interacts with different Acode modules to manage projects and execute commands.
The diagram shows the relationship between user interface components and the underlying file systems or processes.
Sources: user-guide/file-browser.md:14-25, user-guide/terminal.md:46-55, user-guide/index.md:25-80
Configuration and Settings
Acode provides extensive customization through several settings categories.
Settings Categories
| Category | Description | Access Method |
|---|---|---|
| App Settings | General application behavior, QuickTools, and file handling. | Menu -> Settings |
| Editor Settings | CodeMirror customization including fonts, tabs, and linting. | Ctrl + , |
| Terminal Settings | Terminal appearance, permissions, and backups. | Command Palette |
| Theme | Visual styling for the application UI and syntax highlighting. | Settings -> Theme |
Sources: user-guide/settings.md:13-33, user-guide/settings/app-settings.md:1-5
Terminal File Access Logic
Terminal file access depends on specific system permissions and device versions.
Access to internal storage within the terminal requires specific conditions regarding the application build and OS version.
Sources: user-guide/terminal.md:18-23
Plugin Ecosystem
Plugins extend the core functionality of Acode. Users manage these through the Plugins page, which is divided into three functional areas.
- Installed: Used to update, configure, or remove existing plugins.
- Explore: Used to discover and install new plugins from the official registry.
- Purchased: Used to manage acquired premium plugins.
Sources: user-guide/plugins.md:11-25
Summary
The Acode User Guide outlines a modular environment where file management, terminal operations, and customizable input tools converge. By configuring App and Editor settings, users can tailor the development environment to mobile-specific workflows, while the plugin system allows for further feature expansion.
Sources: user-guide/index.md:17-21, user-guide/settings.md:13-33