Results for e9s

API d'accès aux données de la bibliothèque de Toulouse

E9s was created due to the need of simply implementing I18n within a Rails application. This simplifies internationalization of your Rails application making a Rails developers life much easier. E9s is divided into modules (as gem and plugin): Rich-CMS (http://github.com/archan937/rich_cms) , Rich-i18n (http://github.com/archan937/rich_i18n) and Rich-pluralization (http://github.com/archan937/rich_pluralization).

*NOTE his plugin requires the private e9_base CMS gem and WILL NOT WORK without it.* CRM Plugin for the e9 CMS ========================= To use, add as a gem and install by running: rails g e9_crm:install Then modify the installed initializer as per your app, including the controller module in your desired controllers, with the final result looking something like this: \ require 'e9_crm' User.send :include, E9Crm::Backend::ActiveRecord \ Rails.configuration.after_initialize do [ MyFirstTrackedController, \ MySecondTrackedController ].each {|c| c.send(:include, E9Crm::TrackingController) } end NOTE: A few assumptions are made: --------------------------------- 1. \ Your app has a "User" model 2. Your app has a controller method #current_user to return the currently logged in user.

Rich-i18n is a module of E9s (http://github.com/archan937/e9s) which enriches I18n, Formtastic, the String and Symbol classes. This simplifies internationalization of your Rails application making a Rails developers life much easier.

Rich-CMS is a module of E9s (http://github.com/archan937/e9s) which provides a frontend for your CMS content. You can use this gem to manage CMS content or translations (in an internationalized application). The installation and setup process is very easily done. You will have to register content at the Rich-CMS engine and also you will have to specify the authentication mechanism. Both are one-liners.

** 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.

Rich-pluralization is a module of E9s (http://github.com/archan937/e9s) which provides localized pluralization in combination with i18n. Doing this enables you to only translate words in singular form as the module pluralizes the translation for you.

== 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.

A collection of helpers and extensions used in e9 Rails 3 projects

E9 Attributes ============= Searchable attributes engine

E9 Vendors ============ Vendor directory plugin for use with the e9 CMS Although it doesn't speficy requirements, this gem is dependent on e9_base and its environment.

Rich-Support is a small module of E9s (http://github.com/archan937/e9s) making your own gem Rails 2 and 3 compliant. It also adds a small amount of handy methods to the String class.