0.0
No commit activity in last 3 years
No release in over 3 years
this gem adds basecamps's trix.js to the assets-pipeline
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0.4.0
~> 5.1
 Project Readme

TrixOnRails

Please take a look at https://github.com/basecamp/trix All credits go to the fine people of the basecamp-family.

This gem's only purpose is to add the trix- js and -css files to the assets-pipeline. Technically it is a plugin.

The goal is to add some WYSIWYG-methods to my website and play along with rails5.

Dependency

The Trix -project is currently (0.11.1) created with ruby 2.3.1, TrixOnRails was build using ruby 2.3.2. The development- and test- environment of this gem depends on mysql2 and rails 5.1. Why? Since rails removerd the jQuery-dependency, I want to find out where this is bringing me...

Installation

Add this line to your application's Gemfile:

gem 'trix_on_rails'

or if you want to install the latest from github:

gem 'trix_on_rails',  :git => 'git@github.com:l-plan/trix_on_rails.git'

And then execute:

$ bundle

Or install it yourself as:

$ gem install trix_on_rails

Usage

please take a look at https://github.com/basecamp/trix

add to application.js

 //= require trix

or

//= require trix-core

add to application.css

 *= require trix

Test

todo

For now I only added a dummy-app in 'test', adding only one model ("page.rb") to experiment.

TrixOnRails will use minitest. But as for now, the only thing to test is its presence Run rake to start the test-suite.

Contributing

  1. Fork it ( https://github.com/[my-github-username]/trix_on_rails/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

Gem Version