A quick-and-dirty loading bar for use in your larger demos
An automatic loading bar for AngularJS
Simple Loading Bar for Redux and React
react loading bar
TypeScript definitions for angular-loading-bar
A Next.js Top Loading Bar component made using nprogress, works with Next.js 15 and Next.js 14 and React.
Angular2 component shows slim loading bar at the top of the page
loading bar
A Svelte component for showing a loading bar.
Loading Bar
Unmaintained fork of react-redux-loading-bar to avoid any breaking changes.
Simple loading bar on the top of the page to indicate page loading process.
A progress/loading bar using Pace (https://github.hubspot.com/pace/docs/welcome/).
A very simple, highly customisable react top loader component.
Youtube Like Loading Bar Component for Vue 2
Yet another top progress loading bar component for Vue.js
A SvelteKit top loading bar component made using nprogress.
Automatic page loading / progress bar for Angular
Remix and React Router Top Loading bar using NProgress.
react-simple-loading-bar React component
Automatic page loading / progress bar for Angular
Controlled loading bar component
A small loading bar, listening to navigation state
Automatic page loading / progress bar for Angular
This is a gem for Pace. It's based on version 0.4.10.
Automatic page load progress bar
Automatic page load progress bar
Spinning Cursor is a flexible DSL that allows you to easily produce a customizable waiting/loading message for your Ruby command line program. Beautifully keep your users informed with what your program is doing when a more complex solution, such as a progress bar, doesn't fit your needs.
Descriptive configuration files for Ruby written in Ruby. Loquacious provides a very open configuration system written in ruby and descriptions for each configuration attribute. The attributes and descriptions can be iterated over allowing for helpful information about those attributes to be displayed to the user. In the simple case we have a file something like: Loquacious.configuration_for('app') { name 'value', :desc => "Defines the name" foo 'bar', :desc => "FooBar" id 42, :desc => "Ara T. Howard" } Which can be loaded via the standard Ruby loading mechanisms load 'config/app.rb' The attributes and their descriptions can be printed by using a Help object help = Loquacious.help_for('app') help.show :values => true # show the values for the attributes, too Descriptions are optional, and configurations can be nested arbitrarily deep. Loquacious.configuration_for('nested') { desc "The outermost level" a { desc "One more level in" b { desc "Finally, a real value" c 'value' } } } config = Loquacious.configuration_for 'nested' p config.a.b.c #=> "value" And as you can see, descriptions can either be given inline after the value or they can appear above the attribute and value on their own line.
Descriptive configuration files for Ruby written in Ruby. Loquacious provides a very open configuration system written in ruby and descriptions for each configuration attribute. The attributes and descriptions can be iterated over allowing for helpful information about those attributes to be displayed to the user. In the simple case we have a file something like Loquacious.configuration_for('app') { name 'value', :desc => "Defines the name" foo 'bar', :desc => "FooBar" id 42, :desc => "Ara T. Howard" } Which can be loaded via the standard Ruby loading mechanisms Kernel.load 'config/app.rb' The attributes and their descriptions can be printed by using a Help object help = Loquacious.help_for('app') help.show :values => true # show the values for the attributes, too Descriptions are optional, and configurations can be nested arbitrarily deep. Loquacious.configuration_for('nested') { desc "The outermost level" a { desc "One more level in" b { desc "Finally, a real value" c 'value' } } } config = Loquacious.configuration_for('nested') p config.a.b.c #=> "value" And as you can see, descriptions can either be given inline after the value or they can appear above the attribute and value on their own line.
Ruby Scientist and Graphics is a practical data science toolkit for Ruby. It includes a lightweight built-in DataFrame for loading, cleaning, and transforming data; quick descriptive statistics and correlations; charting via Gruff (bar and line); and simple ML utilities (linear regression and k-means)—all behind a small, unified, pandas-inspired API. Key features: - Load data from CSV and JSON. - Clean and transform (remove/add columns, handle missing values, limit rows). - Describe datasets and compute correlations quickly. - Create bar and line charts with customization options. - Train/predict with linear regression; cluster with k-means. - Save/load project state (data + trained model) and run simple pipelines. - Optional backend adapters (e.g., Rover) while keeping the same API. Ideal for analysts and developers who want to explore data in Ruby without relying on Python or R. Note: plotting via Gruff uses rmagick, which requires ImageMagick installed on the system.
# Flicks Command-line app/gem to play and review movies. ## Features - Load a movie list from CSV. - Review system using a virtual die (thumbs up/down/skip). - Snack bar with carbs tracking per movie. - 3D movies (`Movie3D`) with a “wow factor” that boosts thumbs ups. - Save final rankings to a text file. ## Installation ```bash gem install flicks_alec
For all applications (you are not a mouseclicker, are u?), once in a while you need to supply some configuration values to overrule the built-in defaults. The app-ctx gem does unify and organize built-in constants, config files and commandline option with a clearly defined priority, from low to high: - procedural: set from your implementation App::Config#set_default_values - YAML default values file loaded from next to the $0 script - user supplied configuration file, eg.: --config=/tmp/foo.yml - command line options and flags: --foo --bar=foo But for your application it is of no interesst from where the values are coming: command line option: "--port=1234", a user configuration file or from the applications built-in default values. Therefor +app-ctx+ combines value settings from various sources into a single configuration hash.
Descriptive configuration files for Ruby written in Ruby. Loquacious provides a very open configuration system written in ruby and descriptions for each configuration attribute. The attributes and descriptions can be iterated over allowing for helpful information about those attributes to be displayed to the user. In the simple case we have a file something like Loquacious.configuration_for('app') { name 'value', :desc => "Defines the name" foo 'bar', :desc => "FooBar" id 42, :desc => "Ara T. Howard" } Which can be loaded via the standard Ruby loading mechanisms Kernel.load 'config/app.rb' The attributes and their descriptions can be printed by using a Help object help = Loquacious.help_for('app') help.show :values => true # show the values for the attributes, too Descriptions are optional, and configurations can be nested arbitrarily deep. Loquacious.configuration_for('nested') { desc "The outermost level" a { desc "One more level in" b { desc "Finally, a real value" c 'value' } } } config = Loquacious.configuration_for('nested') p config.a.b.c #=> "value" And as you can see, descriptions can either be given inline after the value or they can appear above the attribute and value on their own line.
"Harsh: Another Rails Syntax Highlighter," is just that - it highlights code in Rails, much like Radiograph or tm_syntax_highlighting. However, it does it well, _better_. Oh, and it also supports Haml, as well as ERb. And it comes with rake tasks. Firstly, it allows block form: <% harsh :theme => :dawn do %> class Testing def initialize(str) puts str end end <% end %> as well as the form the other plugins offer, which is text as a parameter: <% harsh %Q{ class Testing def initialize(str) puts str end end }, :theme => :dawn For haml, harsh is implemented as a filter. First, add this to the bottom of your environment.rb: Harsh.enable_haml Then, to use harsh in Haml: :harsh class Foo < Bar end However, haml's filters can't take options. So how on earth are we going to customize it to our heart's delight? Easily, my friend, fret not! Enter the BCL (Bootleg Configuration Line): :harsh #!harsh theme = all_hallows_eve lines=true syntax=css h1 { float:left; clear:left; position:relative; } It has to be the first line in the filter. You don't need the config line, though. Also, notice that you can have spaces between the arguments and the little = sign. Harsh also offers rake tasks for what tm_syntax_highlighting provides in generators, and a :harsh as a stylesheet-includer to load all syntax-highlighting files, as such: <%= stylesheet_include_tag :harsh %> The rake tasks for setting up your stylesheets are these: rake harsh:theme:list # lists available themes rake harsh:theme:install[twilight] # installs the twilight theme into /public/stylesheets/harsh/ rake harsh:theme:install THEME=twilight # also installs the twilight theme (for *csh shells) rake harsh:theme:uninstall[twilight] # removes the twilight theme rake harsh:theme:uninstall THEME=twilight # also uninstalls the twilight theme (for *csh shells) While purely informative, you can find out the available syntaxes as follows: rake harsh:syntax:list
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.