> That might be nice. I'd love to be able to do dynamic Sass per user > more easily, to allow for custom styling. > >
> No. Just have multiple CSS or Sass files (each one defining the same > classes), then do > = stylesheet_tag "hour...@hour}". > > Or run a Rake task every hour to regenerate the CSS files from Sass with > the variable. > > This is what the gem is for, to avoid all the above. > ...whenever that is. Session ending is not always easy to determine, > which is why we need brute-force expiration logic. > that is to have a sass per client during session so they can style the thier profile page an such. And only if they want to save it. > And veeeeery wrong. The database should store the whole block of text. > The view and controller should decide how to split it. This makes the > presentation more flexible: what if you want short pages on the mobile > phone, long pages on the computer, and whole articles in the RSS feed? > I dont care about how to create the solution i just want the result , that i could have my view of one specific size and paginate the text, i dont care how is done i just want a gem to do it, right now i am using ajax for this. > Why do you think I know how to do this? :) I'm just starting to write > my first AR plugin. > > Because you are very active in the forum and have been programing ruby longer than me =). Where are you getting the info for your plugin? how are you figuring out how to do it? right now i jsut look at other polugins but reverse engineering is not fun. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
