Taylor Lapeyre taylorlapeyre

## fizzbuzz.rb
30.times do |num|
  puts (num % 15 == 0) ? "Fizzbuzz" : (num % 5 == 0) ? "Fizz" : (num % 3 == 0) ? "Buzz" : num
end

## form.html
<html>
  <head>
    <title>Basic Form</title>
    <style type="text/css">
      label, input { display: block; }
    </style>
  </head>
  <body>
   <h2>Basic Form</h2>
    <form method="post" action="report.php">

## rectangle.rb
# A simple Rectangle class
class Rectangle
  attr_accessor :x, :y, :width, :height

  def initialize(x, y, width, height)
    @x, @y = x, y
    @width, @height = width, height
  end

  def empty?

## Guardfile
guard 'rspec', :version => 2, :cli => "-c -fs" do
  watch(%r{^spec/.+_spec\.rb$})
  watch(%r{^lib/(.+)\.rb$})     { |m| "spec/#{m[1]}_spec.rb" }
  watch('spec/spec_helper.rb')  { "spec" }
  watch(%r{^views/(.+)\.(slim|scss)$})
end

## answer.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                taylorlapeyre
                / answer.md
            
            
              Created
              December 13, 2012 00:26
            
              
                Question: "If you were asked to design a role-based (users, moderators, admins, etc) user system, how would you approach the problem? Briefly explain."
              
          
    Question 3

There would first be a base User class, which would take necessary attributes, such as an ID, username, password, etc. Users would be able to do anything that any user of the system can do - for instance, post a comment or submit something.
There would then be other User classes that inherit from the User superclass, such as moderators or administrators. These Users would have respective abilities which extend the basic User model. For instance, a moderator may have a ban_user action and an administrator might have the ability to edit other User's profiles.
Users would be perhaps kept in a UserList object that would contain a hash of users and their respective IDs. The UserList could be the superclass of a ModeratorList or AdminList. Alternatively (depending on the scale of the system), we could store the Users in a database - probably mysql - with tables.

  
## gallery.rb
class Gallery
  attr_reader :id, :name, :description, :images, :default_image_id

  def initialize(id, name, description, images={})
    @id = id
    @name = name
    @description = description
    @images = images
  end


## galleryimage.rb
class GalleryImage
  attr_reader :url, :description

  def initialize(url, description)
    @url = url
    @description = description
  end

  def to_html
    "<img src=\"#{@url}\" alt=\"#{@description}\" />"

## Gallery.php
<?php

/**
 * Gallery class.
 * A Gallery holds images which can be formatted to html
 * and displayed onto the a web page
 */
class Gallery
{
  public $id;

## ImageGallery.php
<?php

/**
 * This is the model class for table "image_galleries".
 *
 * The followings are the available columns in table 'image_galleries':
 * @property integer $gallery_id
 * @property string $gallery_name
 * @property string $description
 * @property integer $default_image_id

## directorytest.rb
IMAGE_DIRECTORY = '/images'

def determine_image_location
  for base_directory in IMAGE_DIRECTORY
    for 2nd_level_directory in base_directory
      if number_of_files_in(2nd_level_directory) < 100
        return 2nd_level_directory.name
      end
    if number_of_files_in(base_directory) < 100
      return base_directory.name
	30.times do \|num\|
	puts (num % 15 == 0) ? "Fizzbuzz" : (num % 5 == 0) ? "Fizz" : (num % 3 == 0) ? "Buzz" : num
	end
	<html>
	<head>
	<title>Basic Form</title>
	<style type="text/css">
	label, input { display: block; }
	</style>
	</head>
	<body>
	<h2>Basic Form</h2>
	<form method="post" action="report.php">
	# A simple Rectangle class
	class Rectangle
	attr_accessor :x, :y, :width, :height

	def initialize(x, y, width, height)
	@x, @y = x, y
	@width, @height = width, height
	end

	def empty?
	guard 'rspec', :version => 2, :cli => "-c -fs" do
	watch(%r{^spec/.+_spec\.rb$})
	watch(%r{^lib/(.+)\.rb$}) { \|m\| "spec/#{m[1]}_spec.rb" }
	watch('spec/spec_helper.rb') { "spec" }
	watch(%r{^views/(.+)\.(slim\|scss)$})
	end
	class Gallery
	attr_reader :id, :name, :description, :images, :default_image_id

	def initialize(id, name, description, images={})
	@id = id
	@name = name
	@description = description
	@images = images
	end
	class GalleryImage
	attr_reader :url, :description

	def initialize(url, description)
	@url = url
	@description = description
	end

	def to_html
	"<img src=\"#{@url}\" alt=\"#{@description}\" />"
	<?php

	/**
	* Gallery class.
	* A Gallery holds images which can be formatted to html
	* and displayed onto the a web page
	*/
	class Gallery
	{
	public $id;
	<?php

	/**
	* This is the model class for table "image_galleries".
	*
	* The followings are the available columns in table 'image_galleries':
	* @property integer $gallery_id
	* @property string $gallery_name
	* @property string $description
	* @property integer $default_image_id
	IMAGE_DIRECTORY = '/images'

	def determine_image_location
	for base_directory in IMAGE_DIRECTORY
	for 2nd_level_directory in base_directory
	if number_of_files_in(2nd_level_directory) < 100
	return 2nd_level_directory.name
	end
	if number_of_files_in(base_directory) < 100
	return base_directory.name