2fc7d12ae7
Previously, individual components had to ask the peer to hide and show the keyboard, by calling textInputRequired() and dismissPendingTextInput() respectively. When an onscreen keyboard (OSK) was required, most Peer implementation would directly hide/show the OSK inside these function. However, the iOS ComponentPeer implementation instead listened to the application's global keyboard focus, and only opened the OSK when the focused component was also a TextInputTarget with active input. The iOS scheme seems like a better design, as it enforces that the OSK hiding and showing is synced with the keyboard focus of the application. In the other implementations, it was possible for a Component to call textInputRequired even when it didn't have the keyboard focus, putting the application into an inconsistent state. The iOS scheme also makes the TextInputTarget interface more useful, as it enforces that the OSK will only display for components that implement TextInputTarget, and return true from isTextInputActive(). This patch changes all Peer implementations to match the iOS implementation, improving consistency. Each time the global keyboard focus changes, refreshTextInputTarget is called automatically, and the OSK is shown if the focused component is a TextInputTarget that returns true from isTextInputActive, and hidden otherwise. Components can also call refreshTextInputTarget manually. This should be done whenever the component updates the return value of isTextInputActive(). Effectively, the Peer is now responsible for keeping track of the focused TextInputTarget, rather than allowing individual components to hide and show the OSK at will. Additionally, this patch adds an option to the TextEditor to automatically dismiss the OSK when the mouse is clicked outside of the editor. This should improve user experience on mobile platforms, where touches on sibling components may cause a TextEditor to gain keyboard focus and unnecessarily display the OSK. |
||
|---|---|---|
| .github | ||
| docs | ||
| examples | ||
| extras | ||
| modules | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| BREAKING-CHANGES.txt | ||
| ChangeList.txt | ||
| CMakeLists.txt | ||
| LICENSE.md | ||
| README.md | ||
JUCE is an open-source cross-platform C++ application framework for creating high quality desktop and mobile applications, including VST, VST3, AU, AUv3, RTAS and AAX audio plug-ins. JUCE can be easily integrated with existing projects via CMake, or can be used as a project generation tool via the Projucer, which supports exporting projects for Xcode (macOS and iOS), Visual Studio, Android Studio, Code::Blocks and Linux Makefiles as well as containing a source code editor.
Getting Started
The JUCE repository contains a master and develop branch. The develop branch contains the latest bugfixes and features and is periodically merged into the master branch in stable tagged releases (the latest release containing pre-built binaries can be also downloaded from the JUCE website).
JUCE projects can be managed with either the Projucer (JUCE's own project-configuration tool) or with CMake.
The Projucer
The repository doesn't contain a pre-built Projucer so you will need to build it for your platform - Xcode, Visual Studio and Linux Makefile projects are located in extras/Projucer/Builds (the minimum system requirements are listed in the System Requirements section below). The Projucer can then be used to create new JUCE projects, view tutorials and run examples. It is also possible to include the JUCE modules source code in an existing project directly, or build them into a static or dynamic library which can be linked into a project.
For further help getting started, please refer to the JUCE documentation and tutorials.
CMake
Version 3.15 or higher is required. To use CMake, you will need to install it, either from your system package manager or from the official download page. For comprehensive documentation on JUCE's CMake API, see the JUCE CMake documentation. For examples which may be useful as starting points for new CMake projects, see the CMake examples directory.
Building Examples
To use CMake to build the examples and extras bundled with JUCE, simply clone JUCE and then run the following commands, replacing "DemoRunner" with the name of the target you wish to build.
cd /path/to/JUCE
cmake . -B cmake-build -DJUCE_BUILD_EXAMPLES=ON -DJUCE_BUILD_EXTRAS=ON
cmake --build cmake-build --target DemoRunner
Minimum System Requirements
Building JUCE Projects
- macOS/iOS: Xcode 9.2 (macOS 10.12.6)
- Windows: Windows 8.1 and Visual Studio 2015 Update 3 64-bit
- Linux: g++ 5.0 or Clang 3.4 (for a full list of dependencies, see here).
- Android: Android Studio on Windows, macOS or Linux
Deployment Targets
- macOS: macOS 10.7
- Windows: Windows Vista
- Linux: Mainstream Linux distributions
- iOS: iOS 9.0
- Android: Jelly Bean (API 16)
Contributing
Please see our contribution guidelines.
License
The core JUCE modules (juce_audio_basics, juce_audio_devices, juce_core and juce_events) are permissively licensed under the terms of the ISC license. Other modules are covered by a GPL/Commercial license.
There are multiple commercial licensing tiers for JUCE, with different terms for each:
- JUCE Personal (developers or startup businesses with revenue under 50K USD) - free
- JUCE Indie (small businesses with revenue under 500K USD) - $40/month
- JUCE Pro (no revenue limit) - $130/month
- JUCE Educational (no revenue limit) - free for bona fide educational institutes
For full terms see LICENSE.md.