Use engine instead of railtie & remove assets precompile tasks about tinymce-rails

[spohlenz]

That was actually how I originally wrote the library, and in fact roughly how the gem works in development mode. However because of the large number of files included in TinyMCE (and the fact that they are already minified by the upstream vendor), it is much quicker to have the custom rake task simply copy the assets when precompiling the app's assets, rather than pass them through all of the Sprockets processors.

You're right that an engine provides the asset paths automatically. However it provides a lot of functionality that isn't needed by the gem. Using a railtie is the "lightweight" solution.

[gucki]

I'm not sure if the little overhead in compile time (runtime shouldn't have any difference at all) it worth the trouble. As I also just discovered this huge bug #16 I'll now fork tinymce-rails and see what I can do. Maybe you like it in the end :)

[gucki]

So here it is: #17