Results for component-updater

Freshen up installed components on your system (OS X and Linux only)

Monkey patch ActionView to track and digest view components within cached fragments.

Updates the view_component generators to remove the Component suffix.

Access active-record models inside Reactrb components. Model data is calculated during pre-rerendering, and then dynamically loaded as components update.

Web component framework for Rails providing widgets that trigger events and know when and how to update themselves with AJAX.

This is a simple progress bar component for Volt. The progress bar updates dynamically with a Volt reactive value.

FlexUri is a powerful and user-friendly Ruby gem designed to create, manipulate, and manage URIs with ease. Its fluent interface allows you to intuitively build, update, and combine various URI components, making it the perfect tool for handling query parameters, paths, and URI segments. With FlexUri, you can effortlessly navigate the complexities of URI manipulation and focus on crafting clean, efficient, and maintainable code.

HyperMesh gives your HyperReact components CRUD access to your ActiveRecord models on the client, using the the standard ActiveRecord API. HyperMesh also implements push notifications (via a number of possible technologies) so changes to records on the server are dynamically updated on all authorised clients.

Guilded is a framework for building web based components centered around current web standards and best practices. The current framework is written in ruby, but could be ported to other languages. Guilded intends to provide a toolset for creating and consuming reusable web components. Currently, this problem domain is filled with JavaScript frameworks. These frameworks are wonderful and work very well. However, they do not degrade gracefully and are not accessible. Guilded seeks to provide the same level of "componentization" and ease of use without sacrificing degradability and accessibility. Guilded will achieve these goals by applying each technology at our disposal to do what it was intended. XHTML will be employed for content. CSS used for layout and styling. Behavior will be added to a component with JavaScript through progressive enhancement. The user will have the best experience with a Guilded component when CSS and JavaScript are enabled in their browser, but will still be able to use the component when CSS and JavaScript are disabled. Guilded will use jQuery as it's base JavaScript framework. jQuery was chosen because it lends itself to progressive enhancement due to the way it was authored. In addition, the tight integration of jQuery's selectors with CSS selectors is also highly desirable. When authoring a Guilded component, it is encouraged to write the behavior code as a jQuery plugin. This will allow the jQuery plugin to be used outside of the Guilded project, if desired. Guilded also seeks to provide a standardized CSS framework for creating layouts that are reusable and predictable. Guilded will utilize the currently existing RubyGems system to package its components. A new Guilded component will be packaged in a Gem and have a dependency on the Guilded gem. The Guilded gem contains the framework to build Guilded components. Update: Due to the quality components, etc. being generated by the MooTools community and the general quality of the library, we have decided to include support for it in Guilded as of release 0.3.0.

Cache partials and update them asynchronously after a page renders. Slow method calls happen synchronously as the page renders for the first time. Subsequent page loads retrieve cached objects and render the page quickly, and then Ajax calls can be used to refresh components asynchronously after the page loads.

Implements a gateway server to allow barebone basic sensor components to report state change updates as simple via TCP/UDP ports without the 'overhead' of the HTTP protocol. A power sensor for example might just broadcast a four byte floating point binary number once every second to an UDP port or an arduino board sends a UDP datagram whenever a button is pushed. You get the idea, this is how to bring embedded devices into the world of HTTP and Javascript...

== OceanDynamo As one important use case for OceanDynamo is to facilitate the conversion of SQL databases to no-SQL DynamoDB databases, it is important that the syntax and semantics of OceanDynamo are as close as possible to those of ActiveRecord. This includes callbacks, exceptions and method chaining semantics. OceanDynamo follows this pattern closely and is of course based on ActiveModel. The attribute and persistence layer of OceanDynamo is modeled on that of ActiveRecord: there's +save+, +save!+, +create+, +update+, +update!+, +update_attributes+, +find_each+, +destroy_all+, +delete_all+, +read_attribute+, +write_attribute+ and all the other methods you're used to. The design goal is always to implement as much of the ActiveRecord interface as possible, without compromising scalability. This makes the task of switching from SQL to no-SQL much easier. OceanDynamo uses only primary indices to retrieve related table items and collections, which means it will scale without limits. OceanDynamo is fully usable as an ActiveModel and can be used by Rails controllers. Thanks to its structural similarity to ActiveRecord, OceanDynamo works with FactoryBot. See also Ocean, a Rails framework for creating highly scalable SOAs in the cloud, in which ocean-dynamo is used as a central component: http://wiki.oceanframework.net

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.