Navigator for Cordova with React.js(react.cordova), This will help you to manage your pages history in the app and change pages with animation.
a toys navigation-controller
React view manager similar to UINavigationController
Navigator for JavaScript mobile app, This will help you to manage your pages history in the app and change pages with animation.
Keyboard manager which works in identical way on both iOS and Android
Attribute-based TV remote navigation controller for web apps. Initialize once and control focus, enter, and back actions using HTML attributes.
A simple abort controller library
An implementation of WHATWG AbortController interface.
View docs [here](https://radix-ui.com/primitives/docs/components/navigation-menu).
Microsoft Azure SDK for JavaScript - Aborter
AbortController for Node based on EventEmitter
A responsive navigation controller for showing two related views
React Native integration for React Navigation
UI Components for React Navigation
Native stack navigator using react-native-screens
Bottom tab navigator following iOS design guidelines
Abortable async function helpers
This library allows developers to opt-in to using Navigation Preload in their service worker.
Routers to help build custom navigators
Core utilities for building navigators
React Freeze
Stack navigator component for iOS and Android with animated transitions and gestures
Types for the store controller
The Atlassian navigation component.
Great and easy way to control ACL with simple-navigation in your Rails project
Sailboat Guidance System - an autonomous navigation and control system for robotic sailboats.
Byebug is a Ruby debugger. It's implemented using the TracePoint C API for execution control and the Debug Inspector C API for call stack navigation. The core component provides support that front-ends can build on. It provides breakpoint handling and bindings for stack frames among other things and it comes with an easy to use command line interface.
Make your website more user-friendly with this Rails 7 helper engine! Our tool will add an active classes to menu items based on the controller and controller action, making navigation easier and more intuitive for your visitors.
Magellan is a navigation framework for Windows Presentation Foundation and Silverlight. It helps you to build inductive, navigation-oriented applications. Features include routing, Model-View-Controller and Model-View-ViewModel support.
Enables HMR (Hot Module Replacement) for ES modules during Turbo navigations, with special support for Stimulus controllers.
An open source Rails 8+ engine built on Tailwind CSS, providing customisable WCAG 2.2 AA compliant design tokens, utility classes, and Stimulus controllers for theme switching, mobile navigation, slide-out panels, modals, and tabs. Integrates with the gems you already use (Devise, Pagy, Ransack).
Byebug is a Ruby debugger. It's implemented using the TracePoint C API for execution control and the Debug Inspector C API for call stack navigation. The core component provides support that front-ends can build on. It provides breakpoint handling and bindings for stack frames among other things and it comes with an easy to use command line interface.
You can use Spotify's Web API to discover music and podcasts, manage your Spotify library, control audio playback, and much more. Browse our available Web API endpoints using the sidebar at left, or via the navigation bar on top of this page on smaller screens.
Easy floatable grid structures for Rails. Don't have too much data to display but still need to fill up that screen? Why don't you present your data in a grid of boxes. Provided you color them right, boxes are very easy to the eyes because the mind understands its structure. Add to that custom coloring, (e.g. each controller can have its own color) background images and clickable boxes and you have a navigation that is not only great looking, but is also very easy to use on touchpad-enabled devices such as an iPad. This is what it looks like: https://github.com/cmdjohnson/gridomatic/blob/master/screenshots/overview.png
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.
l is a frontend for ls and less, invoking either depending on if it is fed directories or files. This makes navigating a shell a bit smoother and easier, as it is common to switch between the two commands while poking around the file system (see Sample session). The program filters the switches for ls and less, keeping the most useful and common for each. Sample session: user@box:~ l Documents Music Projects user@box:~ l Documents/ Personal some_doc.pdf example.txt Work user@box:~ l Documents/example.txt This is just an example Documents/example.txt (END) user@box:~ l Documents/Work/ proposal.odt document.pdf user@box:~ l -l Documents/Work/ -rw-r--r-- 1 user user 32974 2006-03-31 12:29 proposal.odt -rw-r--r-- 1 user user 451726 2006-04-13 10:33 document.pdf Aliases: Most aliases for ls as used in .bashrc will work as usual if ls is replaced with l, but there's more: you can combine switches for both ls and less in your alias and l will filter out the inappropriate ones. The following will set ll to use long lists for directories and to ignore case for searches when displaying files: alias ll='l -I -l' Because ls and less can't safely share the same switches, there are a few cases where a workaround is needed: For ls: -i doesn't work, use --inode instead -I doesn't work, use --ignore=PATTERN For less: -r and -R doesn't work, use --raw-control-chars instead
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.