A tiny add-on to autoload your initializer files in ember-cli.
Wrap class field initializers with IIFE to workaround https://webkit.org/b/236843
Powerful Incremental Type-driven Settings Engine.
A package encapsulating common code across neeto projects including initializers, utility functions, common components and hooks and so on.
Sitecore JSS initializer
Simple broccoli utility function to filter ember initializers based upon build mode.
MermaidJS parser
ESLint rules for controlling where and how mutation is used.
A topologically ordered map of key/value pairs with a simple API for adding constraints.
Simple authorization addon for Ember apps
typescript-json-schema generates JSON Schema files from your Typescript sources
Addon for configuring ember-cli-rails (the ruby gem) with the ember app(s) it wraps.
typescript-json-schema generates JSON Schema files from your Typescript sources
Client Side Validations made easy for your Rails 7.2 and 8.x applications
A set of custom eslint rules that make working with myUL projects easier.
Official Sentry SDK for Ember.js
Module that installs globals ember-inspector support
Responsive Theme for ActiveAdmin
This package contains decoders and types for settings required to prepare and deploy the Dark Forest smart contracts.
ONNX model parser - extracts graph structure (nodes, edges, shapes) from .onnx files
Genkit AI framework plugin for Google AI & Vertex APIs, including Gemini APIs.
oulu is a sass mixin libraly.
TODO
Use meta tags to pass your Ember.js app options.
Avoid JS mayhem on your Rails app! js-initializers is an engine that adds a micro-framework for initializing and organizing client-side logic in a modular way
optimize-js makes JavaScript scripts initialize faster. This gem provides Ruby and Rails asset pipeline integration for optimize-js.
This gem handles animations in a beautifull way keeping the integrity of the initial efforts of AOS Vue js Library
** NOTE - This gem depends on e9_base, but does not reference it. It WILL NOT FUNCTION for apps which aren't built on the e9 Rails 3 CMS ** == E9Polls Provites a Poll renderable for the e9 Rails 3 CMS. == Installation 1. Include the gem and run the install generator to copy over the necessary files, then migrate. rails g e9_polls:install This will install the db migration, the JS and CSS required for the plugin to function properly, and an initializer. Modify the CSS as you see fit and the JS as required (carefully). Check out the initializer and modify if necessary. For non-Ajax fallbacks it uses the 'application' layout. This should be changed if the app doesn't use application layout as a sensible default. 2. Migrate the database. rake db:migrate 3. Finally, include the generated javascript and css (e9_polls.js and e9_polls.css) in the fashion suited to the app. 4. There is no #4.
== E9Tags An extension to ActsAsTaggableOn[http://github.com/mbleigh/acts-as-taggable-on] which "improves" on custom tagging, or at least makes it more dynamic. Additionally it provides some autocomplete rack apps and the corresponding javascript. == Installation 1. E9Tags requires jquery and jquery-ui for the autocompletion and tag-adding form, be sure they're loaded in your pages where the tags form will be rendered. 2. E9Tags extends ActsAsTaggableOn and requires it. Run it's generator if you have not. 3. Run the E9Tags install script to copy over the required JS rails g e9_tags:install 4. Then make sure it is loaded, how you do that doesn't matter, e.g. <%= javascript_include_tag 'e9_tags' %> 5. Create an initializer for that sets up the taggable models and their controllers. This gives the models the tag associations and methods and prepares their controller to handle the otherwise unexpected tag params. require 'e9_tags' require 'contacts_controller' require 'contact' E9Tags.controllers << ContactsController E9Tags.models << Contact OR You can just include the modules in your classes yourself. The first way really exists for the case where the classes you wish to extend are part of another plugin/gem. # in contact.rb include E9Tags:Model # in contacts_controller.rb include E9Tags::Controller 6. Render the tags form partial in whatever model forms require it. = render 'e9_tags/form', :f => f If you pass a context, it will be locked and no longer possible to change/add the contexts on the form (and as a side effect, the tags autocompletion will be restricted to that context). = render 'e9_tags/form', :f => f, :context => :users Finally if you pass a 2nd arg to :context you can set a tag context to be "private" (default is false). In this case the tag context will be locked as private (typically suffixed with *), meaning that the tags will not be publicly searchable/visible. This is useful for organizational tags tags, say if you wanted to arbitrarily group records, or create a custom search based on a tag context. = render 'e9_tags/form', :f => f, :context => [:users, true] NOTE: The form and javascript are intended to work out of the box, but the certainly aren't going to look pretty. If you do intend to use the forms, you'll no doubt need to style them.