teccm1994 / company_project Goto Github PK

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Control pattern.

This pattern splits the view (also called the presentation) into “dumb” templates that are primarily responsible for inserting pre-built data in between HTML tags. The model contains the “smart” domain objects (such as Account, Product, Person, Post) that holds all the business logic and knows how to persist themselves to a database. The controller handles the incoming requests (such as Save New Account, Update Product, Show Post) by manipulating the model and directing data to the view.

In Rails, the model is handled by what’s called an object-relational mapping layer entitled Active Record. This layer allows you to present the data from database rows as objects and embellish these data objects with business logic methods. You can read more about Active Record in files/vendor/rails/activerecord/README.html.

The controller and view are handled by the Action Pack, which handles both layers by its two parts: Action View and Action Controller. These two layers are bundled in a single package due to their heavy interdependence. This is unlike the relationship between the Active Record and Action Pack that is much more separate. Each of these packages can be used independently outside of Rails. You can read more about Action Pack in files/vendor/rails/actionpack/README.html.

1. At the command prompt, create a new Rails application:

   <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)

2. Change directory to myapp and start the web server:

   <tt>cd myapp; rails server</tt> (run with --help for options)

3. Go to localhost:3000/ and you’ll see:

   "Welcome aboard: You're riding Ruby on Rails!"
   

4. Follow the guidelines to start developing your application. You can find

the following resources handy:

• The Getting Started Guide: guides.rubyonrails.org/getting_started.html

• Ruby on Rails Tutorial Book: www.railstutorial.org/

Sometimes your application goes wrong. Fortunately there are a lot of tools that will help you debug it and get it back on the rails.

First area to check is the application log files. Have “tail -f” commands running on the server.log and development.log. Rails will automatically display debugging and runtime information to these files. Debugging info will also be shown in the browser on requests from 127.0.0.1.

You can also log your own messages directly into the log file from your code using the Ruby logger class from inside your controllers. Example:

class WeblogController < ActionController::Base
  def destroy
    @weblog = Weblog.find(params[:id])
    @weblog.destroy
    logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
  end
end

The result will be a message in your log file along the lines of:

Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!

More information on how to use the logger is at www.ruby-doc.org/core/

Also, Ruby documentation can be found at www.ruby-lang.org/. There are several books available online as well:

• Programming Ruby: www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)

• Learn to Program: pine.fm/LearnToProgram/ (a beginners guide)

These two books will bring you up to speed on the Ruby language and also on programming in general.

Debugger support is available through the debugger command when you start your Mongrel or WEBrick server with –debugger. This means that you can break out of execution at any point in the code, investigate and change the model, and then, resume execution! You need to install ruby-debug to run the server in debugging mode. With gems, use sudo gem install ruby-debug. Example:

class WeblogController < ActionController::Base
  def index
    @posts = Post.all
    debugger
  end
end

So the controller will accept the action, run the first line, then present you with a IRB prompt in the server window. Here you can do things like:

>> @posts.inspect
=> "[#<Post:0x14a6be8
        @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
     #<Post:0x14a6620
        @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
>> @posts.first.title = "hello from a debugger"
=> "hello from a debugger"

…and even better, you can examine how your runtime objects actually work:

>> f = @posts.first
=> #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
>> f.
Display all 152 possibilities? (y or n)

Finally, when you’re ready to resume execution, you can enter “cont”.

The console is a Ruby shell, which allows you to interact with your application’s domain model. Here you’ll have all parts of the application configured, just like it is when the application is running. You can inspect domain models, change values, and save to the database. Starting the script without arguments will launch it in the development environment.

To start the console, run rails console from the application directory.

Options:

• Passing the -s, --sandbox argument will rollback any modifications made to the database.

• Passing an environment name as an argument will load the corresponding environment. Example: rails console production.

To reload your controllers and models after launching the console run reload!

More information about irb can be found at: http://www.rubycentral.org/pickaxe/irb.html

You can go to the command line of your database directly through rails dbconsole. You would be connected to the database with the credentials defined in database.yml. Starting the script without arguments will connect you to the development database. Passing an argument will connect you to a different database, like rails dbconsole production. Currently works for MySQL, PostgreSQL and SQLite 3.

The default directory structure of a generated Ruby on Rails application:

|-- app
|   |-- assets
|   |   |-- images
|   |   |-- javascripts
|   |   `-- stylesheets
|   |-- controllers
|   |-- helpers
|   |-- mailers
|   |-- models
|   `-- views
|       `-- layouts
|-- config
|   |-- environments
|   |-- initializers
|   `-- locales
|-- db
|-- doc
|-- lib
|   |-- assets
|   `-- tasks
|-- log
|-- public
|-- script
|-- test
|   |-- fixtures
|   |-- functional
|   |-- integration
|   |-- performance
|   `-- unit
|-- tmp
|   `-- cache
|       `-- assets
`-- vendor
    |-- assets
    |   |-- javascripts
    |   `-- stylesheets
    `-- plugins

app

Holds all the code that's specific to this particular application.

app/assets

Contains subdirectories for images, stylesheets, and JavaScript files.

app/controllers

Holds controllers that should be named like weblogs_controller.rb for
automated URL mapping. All controllers should descend from
ApplicationController which itself descends from ActionController::Base.

app/models

Holds models that should be named like post.rb. Models descend from
ActiveRecord::Base by default.

app/views

Holds the template files for the view that should be named like
weblogs/index.html.erb for the WeblogsController#index action. All views use
eRuby syntax by default.

app/views/layouts

Holds the template files for layouts to be used with views. This models the
common header/footer method of wrapping views. In your views, define a layout
using the <tt>layout :default</tt> and create a file named default.html.erb.
Inside default.html.erb, call <% yield %> to render the view using this
layout.

app/helpers

Holds view helpers that should be named like weblogs_helper.rb. These are
generated for you automatically when using generators for controllers.
Helpers can be used to wrap functionality for your views into methods.

config

Configuration files for the Rails environment, the routing map, the database,
and other dependencies.

db

Contains the database schema in schema.rb. db/migrate contains all the
sequence of Migrations for your schema.

doc

This directory is where your application documentation will be stored when
generated using <tt>rake doc:app</tt>

lib

Application specific libraries. Basically, any kind of custom code that
doesn't belong under controllers, models, or helpers. This directory is in
the load path.

public

The directory available for the web server. Also contains the dispatchers and the
default HTML files. This should be set as the DOCUMENT_ROOT of your web
server.

script

Helper scripts for automation and generation.

test

Unit and functional tests along with fixtures. When using the rails generate
command, template test files will be generated for you and placed in this
directory.

vendor

External libraries that the application depends on. Also includes the plugins
subdirectory. If the app has frozen rails, those gems also go here, under
vendor/rails/. This directory is in the load path.

企业汇报系统简介
  基本功能
    1.添加单个企业 展示
    2.在企业下 可以添加 层级，可以无限叠加
    3.每个层级下可以展示汇报文档，点击单个文档标题可以查看文档内容
    注：层级机构在一个页面里 完全展示
  附加功能
    1.文档批注，审核等
    2.查看某个部门下文档
    (N多条件同时条件可选的，比如发布时间，审核时间，审核状态)
    3.对一个部门或者企业下面的所有的汇报，出报表 最好能出chart。比如我选择时间段之后可以列表每一天的汇报数字，或者所有人的数字
   4.权限管理。上级可以查看下级的，反之不能。
   5.文档或者用户的软删除，可以进行恢复。
   6.用户的操作日志。
  追加功能
   1.发布时间和 审核时间 查询 加上 日期控件
   2.添加 每层级 上传功能 下载功能
   3.文档列表 加上分页功能

李明
陈明

|service_project　
|-- app
|   |-- assets
|   |   |-- images
|   |   |  |-- bkg2.png
|   |   |-- javascripts
|   |   |  |-- application.js
|   |   |  |-- bar.js
|   |   |  |-- line.js
|   |   |  |-- pie.js
|   |   |  |-- bootstrap-datetimepicker.fr.js
|   |   |  |-- bootstrap-datetimepicker.js
|   |   |  |-- bootstrap.min.js
|   |   |  |-- company.js.coffee
|   |   |  |-- doc.js.coffee
|   |   |  |-- user.js.coffee
|   |   |  |-- operationlog.js.coffee
|   |   `-- stylesheets
|   |   `--`-- application.css  
|   |   `--`-- bootstrap-datetimepicker.css  
|   |   `--`-- bootstrap-theme.min.css  
|   |   `--`-- bootstrap.min.css  
|   |   `--`-- build.css 
|   |   `--`-- build_standalone.css  
|   |   `--`-- datetimepicker.css  
|   |   `--`-- doc.css.css
|   |   `--`-- company.css.scss
|   |   `--`-- user.css.scss
|   |   `--`-- operationlog.css.scss
|   |-- controllers
|   |   |-- company_controller.rb
|   |   |-- application_controller.rb
|   |   |-- doc_controller.rb
|   |   |-- user_controller.rb
|   |   |-- operationlog_controller.rb
|   |-- helpers
|   |   |-- application_helper.rb
|   |   |-- company_helper.rb
|   |   |-- doc_helper.rb
|   |   |-- user_helper.rb
|   |   |-- operationlog_helper.rb
|   |-- mailers
|   |   |-- .gitkeep
|   |-- models
|   |   |-- .gitkeep
|   |   |-- company.rb
|   |   |-- doc.rb
|   |   |-- question.rb
|   |   |-- user.rb
|   |   |-- operationlog.rb
|   `-- views
|       `-- layouts
|          `-- application.html.erb
|       `-- answer
|          `-- check.html.erb
|          `-- index.html.erb
|          `-- yonghu_check.html.erb
|       `-- jixiao
|       `-- question
|       `-- score
|       `-- user

介绍每个文件相应的功能（缩进两个空格）举个例子：app/views/user/index 用户登录首页（详细介绍）

列出每个页面的相关链接（缩进两个空格）举个例子：［登录页面］114.215.203.42:10086/user/index

用户：ｌ
密码：１