jellybob / activo-rails Goto Github PK

Any plans on releasing the Rails 3.1 branch as a gem? Is something preventing that from happening?

Hey there!

Activo-rails is a pretty nice piece of software!
We're starting to use it in production soon.
Just one question:

Have you thought about abstracting the

stuff?

I could think of stuff like

<% content_box :headline => 'foobar' do |box| %>
<% box.controls do |c| %>
...
<% end %>

my content
<% end %>

are you still doing something like that?
seems pretty copy-intensive otherwise...

best,

tobi

We still have to.

I think it would be pretty handy to write some generators for using activo and form/attrtastic. Should those go into web-app-theme, or do you think we should add them to activo-rails?

I ask because it appears that activo has diverged from web-app-theme. Including web-app-theme just to use the "themed" generators seems confusing.

Opinions?

Trying out current rail3_1 branch (w/activo2) and still having issues with asset pipeline. Just by inclusion of

gem 'activo-rails', :git=>'git://github.com/jellybob/activo-rails.git', :branch => 'rails3_1'

assets stops working for whole application (tested both with the existing and new app). Not even default application.css works.

No route matches [GET] "/assets/application.css"

Rails.application.config.assets.paths is correct (as it seems)
["/home/radim/dev/skladomat/app/assets/stylesheets", "/home/radim/dev/skladomat/app/assets/javascripts", "/home/radim/dev/skladomat/app/assets/images", "/home/radim/dev/skladomat/vendor/assets/stylesheets", "/usr/local/rvm/gems/ruby-1.9.2-p180@skladomat/gems/jquery-rails-1.0.11/vendor/assets/javascripts", "/usr/local/rvm/gems/ruby-1.9.2-p180@skladomat/bundler/gems/activo-rails-24c64ee392b0/app/assets/stylesheets", "/usr/local/rvm/gems/ruby-1.9.2-p180@skladomat/bundler/gems/activo-rails-24c64ee392b0/app/assets/fonts", "/usr/local/rvm/gems/ruby-1.9.2-p180@skladomat/bundler/gems/activo-rails-24c64ee392b0/app/assets/javascripts", "/usr/local/rvm/gems/ruby-1.9.2-p180@skladomat/bundler/gems/activo-rails-24c64ee392b0/app/assets/images"]

The documentation for formtastic integration appears to be a bit misleading. It says:

Using Formtastic

Activo is already set up to be used with Formtastic, but doesn't directly depend on it, since form builders are very much a matter of taste.

If you would like to use it (and I recommend it), then just add gem 'formtastic' to your Gemfile, and everything will work out of the box.

However, If you just use semantic_form_for, the buttons are the standard rails buttons.

I've generated my layouts using web-app-theme, and modified the forms manually to use formtastic, but I don't think that should matter.

Hi guys,

I don't see this even on the original activio site, but shouldn't there be some accompanying javascript (for instance for hiding and showing tabs)?

Thanks for clarifying:)

--j

If I use the following:

layout 'activo'

It won't work because the layout in your gem is called 'application.html.erb'

Renaming "/gems/activo-rails-1.0.1/app/views/layouts/application.html.erb" to "active.html.erb" solves the problem.

I'm on Rails 3.0.9

On the Rails 3_1 branch (did not check the other one) I get a

Started GET "/assets/activo-rails/application.css" for 192.168.0.164 at 2011-06-22 12:15:40 -0300
Error compiling asset activo-rails/application.css:
Sprockets::FileNotFound: couldn't find file './themes/activo/fonts'
  (in /home/jan/.rvm/gems/ruby-1.9.2-p180@rails31/bundler/gems/activo-rails-24c64ee392b0/app/assets/stylesheets/activo-rails/application.css.scss:6)

Sprockets::FileNotFound (couldn't find file './themes/activo/fonts'
  (in /home/jan/.rvm/gems/ruby-1.9.2-p180@rails31/bundler/gems/activo-rails-24c64ee392b0/app/assets/stylesheets/activo-rails/application.css.scss:6)):

killing the rest of the show. I cannot find these files in my gem clone. Something is not right there, I suppose...

Currently only the view helpers are covered by integration tests. Now the example app is in place for doing integration testing against the following things also need integration testing:

• Main navigation
• User status
• Icon navigation
• Sidebar content
• Turning the sidebar on and off

I was trying to run my project in production mode, and in that mode a css compilation error ocours with this message:

ActionView::Template::Error (Invalid CSS after "...: alpha(opacity": expected comma, was ":0);"

It turns out that both Jquery-UI and Uniform uses alpha opacity and are causing the compilation problem. As I was not using them in my project, I just removed them from my fork, but I think this is something to take a look.

The icon specs are failing at the moment because Hash doesn't define a perform_caching method - this seems to be a known bug in Rails' Sprockets support, with an open pull request: rails/rails#1816

I'm going to work around it for now, but I'll leave this open to remind me to roll that back once the permanent fix is in.

The old icon set is not included in the repository right now. We'll have to add a fetch job for it.

Would be the Rails way, IMHO.

What do you think?

Hi there,

it would be nice to have an unstable release which relies on the new asset mechanisms in rails 3.1
See this post:
http://jackdempsey.me/2011/04/22/rails-3-1-sprockets-and-coffeescript.html

Best,

Tobias

How do you do your activo merges? I'm looking at fixing a couple more of the style issues upstream, specifically relating to formtastic.

Also, he's got his own set of helpers, and it would be nice come up with a way to keep this all in sync, and get better documentation. see dmfrancisco/activo#4