Rubygems | Latest Versions for e9_tagshttps://rubygems.org/gems2023-09-28T02:42:04Ze9_tags (0.0.14)https://rubygems.org/gems/e9_tags/versions/0.0.142011-10-07T16:06:59ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.13)https://rubygems.org/gems/e9_tags/versions/0.0.132011-07-20T20:13:48ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.12)https://rubygems.org/gems/e9_tags/versions/0.0.122011-05-26T23:30:47ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.11)https://rubygems.org/gems/e9_tags/versions/0.0.112011-05-02T21:31:16ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.10)https://rubygems.org/gems/e9_tags/versions/0.0.102011-05-02T16:25:50ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.9)https://rubygems.org/gems/e9_tags/versions/0.0.92011-04-21T19:06:27ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.8)https://rubygems.org/gems/e9_tags/versions/0.0.82011-04-15T14:19:56ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.7)https://rubygems.org/gems/e9_tags/versions/0.0.72011-04-11T18:34:31ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.6)https://rubygems.org/gems/e9_tags/versions/0.0.62011-03-23T23:24:24ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.5)https://rubygems.org/gems/e9_tags/versions/0.0.52011-03-23T23:18:43ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
== 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.
e9_tags (0.0.4)https://rubygems.org/gems/e9_tags/versions/0.0.42011-03-16T20:06:11ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
NOTE: This gem is in the process of being extracted from code used in other projects. It is untested and a few features haven't been extracted yet, including the form views/javascripts and autocompletion for tags/contexts.
An extension to ActsAsTaggable on which "improves" on custom tagging, or at least makes it more dynamic.
Installation
------------
1. E9Tags requires jquery and jquery-ui, 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
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]
e9_tags (0.0.3)https://rubygems.org/gems/e9_tags/versions/0.0.32011-03-16T18:54:30ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
NOTE: This gem is in the process of being extracted from code used in other projects. It is untested and a few features haven't been extracted yet, including the form views/javascripts and autocompletion for tags/contexts.
An extension to ActsAsTaggable on which "improves" on custom tagging, or at least makes it more dynamic.
Installation
------------
1. E9Tags requires jquery and jquery-ui, 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
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]
e9_tags (0.0.2)https://rubygems.org/gems/e9_tags/versions/0.0.22011-03-16T17:13:51ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
NOTE: This gem is in the process of being extracted from code used in other projects. It is untested and a few features haven't been extracted yet, including the form views/javascripts and autocompletion for tags/contexts.
An extension to ActsAsTaggable on which "improves" on custom tagging, or at least makes it more dynamic.
Installation
------------
1. E9Tags requires jquery and jquery-ui, 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
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]
e9_tags (0.0.1)https://rubygems.org/gems/e9_tags/versions/0.0.12011-03-16T16:04:41ZTravis CoxExtension to ActsAsTaggableOn used in e9 Rails 3 projects
NOTE: This gem is in the process of being extracted from code used in other projects. It is untested and a few features haven't been extracted yet, including the form views/javascripts and autocompletion for tags/contexts.
An extension to ActsAsTaggable on which "improves" on custom tagging, or at least makes it more dynamic.
Installation
------------
1. E9Tags requires jquery and jquery-ui, 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
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]