java example

http://www.java2s.com/Code/Java/Database-SQL-JDBC/Insertarecordintodatabasetable.htm

Logo nxt

http://tiltedtwister.com

html5 framework

http://davidbcalhoun.com/2010/mobile-javascript-libraries-and-frameworks
http://zeptojs.com
iUI
http://joapp.com/
Sproutcore

Rails: Cron Job Scheduling using Redis, Resque and Rufus

http://hemju.com/2011/03/04/rails-cron-job-scheduling-using-redis-resque-and-rufus/

用JavaScript玩转游戏物理(一)运动学模拟与粒子系统

http://www.cnblogs.com/miloyip/archive/2010/06/14/Kinematics_ParticleSystem.html

Good Ruby reference

http://blog.rubybestpractices.com/
http://www.slideshare.net/robbinfan/design-pattern-from-java-to-ruby

Ruby on Rails 3 View Form Helper, File Upload & Download

http://jonathanhui.com/ruby-rails-3-view-form-helper-file-upload-download

COLLECTION & MEMBER METHODS WITHIN A ROUTE

RubyHunt: What’s the use of the :collection and :member methods within a route? What’s the difference between the two?

melvinram: Collection adds routes to the entire collection

RubyHunt: So the collection is used to add another action inside the controller

melvinram: If you had a resource of Contacts, a collection route you might add would be delete_all_older_than_6_months

melvinram: and the route to get to it would be be/contacts/delete_all_older_than_6_months/

RubyHunt: Which otherwise would be restricted to only 7 actions ?

melvinram: yes

melvinram: A member method applies only to one record. For example, you might add a member method called upgrade_to_vip that would update one record to have a status of VIP or something…

melvinram: And the route would be /contacts/1/upgrade_to_vip

RubyHunt: So the :collection is used to add action inside a RESTful controller and the :member would be used to apply action for individual object.

melvinram: you got it!

Source:http://railsnotes.com/5-collection-member-methods-within-a-route/

Ruby and Rails Naming Conventions

Copy By :http://itsignals.cascadia.com.au/?p=7

I’ve been looking for a consolidated list of all Ruby and Rails naming conventions without too much luck so I’ve started my own. I find I always forget the naming convention especially as I move between projects that use different languages.

Please let me know of any others that I have missed. 

Naming Conventions

Ruby Naming Convention

Ruby uses the first character of the name to help it determine it’s intended use.

Local Variables
Lowercase letter followed by other characters, naming convention states that it is better to use underscores rather than camelBack for multiple word names, e.g. mileage, variable_xyz

Instance VariablesInstance variables are defined using the single "at" sign (@) followed by a name. It is suggested that a lowercase letter should be used after the @, e.g. @colour 

Instance MethodsMethod names should start with a lowercase letter, and may be followed by digits, underscores, and letters, e.g. paint, close_the_door

Class VariablesClass variable names start with a double "at" sign (@@) and may be followed by digits, underscores, and letters, e.g. @@colour

Constant Constant names start with an uppercase letter followed by other characters. Constant objects are by convention named using all uppercase letters and underscores between words, e.g. THIS_IS_A_CONSTANT

Class and Module Class and module names starts with an uppercase letter, by convention they are named using MixedCase, e.g. module Encryption, class MixedCase

Global VariablesStarts with a dollar ($) sign followed by other characters, e.g. $global

Rails Naming Convention

Rails use the same naming convention as Ruby with some additions:

Variable Variables are named where all letters are lowercase and words are separated by underscores, e.g. order_amount, total

Class and Module Classes and modules use MixedCase and have no underscores, each word starts with a uppercase letter, e.g. InvoiceItem

Database Table
Table names have all lowercase letters and underscores between words, also all table names need to be plural, e.g. invoice_items, orders

Model
The model is named using the class naming convention of unbroken MixedCase and is always the singular of the table name, e.g. table name might be orders, the model name would be Order. Rails will then look for the class definition in a file called order.rb in the /app/models directory. If the model class name has multiple capitalised words, the table name is assumed to have underscores between these words.

Controller
Controller class names are pluralized, such that OrdersController would be the controller class for the orders table.  Rails will then look for the class definition in a file called orders_controller.rb in the /app/controllers directory.

Files, Directories and other pluralizationFiles are named using lowercase and underscores. Assuming we have an Orders controller then the following other conventions will apply:

• That there is a helper module named OrdersHelper in the orders_helper.rb found in the app/helpers directory
• Rails will look for view template files for the controller in the app/views/orders directory
• Output from this view will then be used in the layout defined in the orders.html.erb in the app/views/layouts directory
• Test files including order_test.rb will be created in the /test/unit directory, a file will be created in the /test/fixtures directory called orders.yml and finally a file called orders_controller_test.rb will be created in the /test/functional directory

Primary KeyThe primary key of a table is assumed to be named id.

Foreign Key
The foreign key is named with the singular version of the target table name with _id appended to it, e.g. order_id in the items table where we have items linked to the orders table.

Many to Many Link TablesTables used to join two tables in a many to many relationship is named using the table names they link, with the table names in alphabetical order, for example items_orders.

Automated Record TimestampsYou can get ActiveRecord to automatically update the create and update times of records in a database table. To do this create two specially named columns created_at and updated_at to your table, i.e. t.datetime :created_at and t.datetime :updated_at. If you only want to store the date rather than a date and time, use :created_on and :updated_on.

Naming Convention Summary 

Model Naming Convention

Table: orders
Class: Order
File: /app/models/order.rb
Primary Key: id
Foreign Key: customer_id
Link Tables: items_orders

Controller Naming Convention

Class: OrdersController
File: /app/controllers/orders_controller.rb
Layout: /app/layouts/orders.html.erb

View Naming Convention

Helper: /app/helpers/orders_helper.rb
Helper Module: OrdersHelper
Views: /app/views/orders/… (list.html.erb for example)

Tests Naming Convention

Unit: /test/unit/order_test.rb
Functional: /test/functional/orders_controller_test.rb
Fixtures: /test/fixtures/orders.yml

  

MACRuby AppStore

http://redwoodapp.posterous.com/macruby-and-xcode-4-build-a-self-contained-ma