Sometimes we need code accessible from everywhere. Usually models relate to structure of data for storage and business logic. Controllers are for the gluing of interface to model and views are interface related. Ask questions if you get stuck
Blog: http://random8.zenunit.com/ Learn rails: http://sensei.zenunit.com/ On 08/02/2009, at 1:08 PM, fmh <[email protected]> wrote: > > ok, > i think i rushed coding this, i now rethinking my code. > i am not familiar with MVC. > > > On 7 fév, 22:27, Rick <[email protected]> wrote: >> Ok, >> >> So once we get past the "Why would you ever want to do something dumb >> like that?" and "Bad things will happen..." which I assume means the >> Rails Police will come during the night and kill your cat, how can >> FMH >> actually get the job done? >> >> Seriously guys, give the guy at least a pointer to a real reason not >> to do what he's trying - don't just spit dogma. >> >> This has worked for me with: >> About your application's environment >> Ruby version 1.8.7 (powerpc-darwin9) >> RubyGems version 1.3.1 >> Rails version 2.2.2 >> Active Record version 2.2.2 >> Action Pack version 2.2.2 >> Active Resource version 2.2.2 >> Action Mailer version 2.2.2 >> Active Support version 2.2.2 >> Application root /Users/rick/Journeys >> Environment development >> Database adapter postgresql >> >> 1) put your needed methods in a module in "lib/your_stuff.rb" where >> your_stuff.rb looks like: >> >> module YourStuff >> protected >> def thing1 >> ... >> end >> end >> >> 2) add the line "include YourStuff" to the controller for the class >> you want to make thing1 available in: >> >> class PagesController < ApplicationController >> include AuthenticatedSystem >> >> or, optionally, add it to app/controllers/application.rb to make >> thing1 available everywhere. >> >> Now let's see if there can be some reasonable discussion about why >> this is a "bad idea" and how soon you should expect your cat to die. >> >> Rick >> On Feb 7, 5:50 am, fmh <[email protected]> wrote: >> >>> i did this , because i dont want integrate my users admin with >>> simple >>> users >> >>> class Admin < ActiveRecord::BaseWithoutTable >>> column :username , :string >>> column :userpass , :string >> >>> def self.authenticate?(username,userpass) >>> admin = Admin.new >>> admin.username = "admin" >>> admin.userpass = "1234" >>> if (admin.username == username && admin.userpass == userpass) >>> true >>> end >>> end >>> end >> >>> how to affect this admin to a current_user ? >> >>> because if my current_user is an admin user i skip my other problem >> >>> On 7 fév, 16:35, Fernando Perez <[email protected]> >>> wrote: >> >>>> fmh wrote: >>>>> because i have a special controller authentication (an admin model >>>>> without table) and in my model i have a method to authorize some >>>>> action. >> >>>> You are trying to break the MVC pattern, only bad things will >>>> happen to >>>> you, you certainly have to refactor / rethink your code. >>>> -- >>>> Posted viahttp://www.ruby-forum.com/. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
