33 Matching Annotations
  1. Jul 2015
    1. UML (Unified Modeling Language) is so general-purpose modeling language that could be used to express any kinds of software-intensive systems. In this reason, using UML for a specific domain or platform is not sufficient, so you may need to define UML Profile.
    2. part of a project saved as a separate file with the extension name .mfj
    3. A fragmen
    4. A model element typically may have multiple corresponding view elements. Model element have its own data such as name, stereotype, type, etc. View element just renders the corresponding model element in a diagram. View elements may exists multiple times in a diagram or different diagrams.
    5. visual geometric symbolic representation of a software model
    6. Diagram
    7. description of any aspect of a software system such as structure, behavior, requirement, and so on
    8. Model or software model
    9. Many users are confusing the difference between diagramming or drawing tool such as Microsoft Visio and modeling tools such StarUML or Rational Software Architect. First you need to understand a diagram is not a model.
    1. If a string is passed as the parameter to $(), jQuery examines the string to see if it looks like HTML (i.e., it starts with <tag ... >). If not, the string is interpreted as a selector expression
    1. This behaves in almost the same way as outlined previously, with a couple of small exceptions. First, the prefix used to name the input elements within the form (hence the key that denotes them in the params hash) is actually derived from the object's class, e.g. params[:post] if the object's class is Post. However, this can be overwritten using the :as option, e.g. -

      <%= form_for(@person, as: :client) do |f| %> is not working

      <%= form_for @person, as: :client do |f| %> is right syntax.

    2. if @post is an existing record you wish to edit, you can create the form using
    3. a form can be created by passing form_for a string or symbol representing the object we are concerned with:
    4. For fields generated in this way using the FormBuilder, if :person also happens to be the name of an instance variable @person, the default value of the field shown when the form is initially displayed (e.g. in the situation where you are editing an existing record) will be the value of the corresponding attribute of @person.
    5. This means that when the form is submitted, the value entered by the user will be available in the controller as params[:person][:first_name].
    6. The variable f yielded to the block is a FormBuilder object that incorporates the knowledge about the model object represented by :person passed to form_for. Methods defined on the FormBuilder are used to generate fields bound to this model. Thus, for example,
    7. The method can be used in several slightly different ways, depending on how much you wish to rely on Rails to infer automatically from the model how the form should be constructed.
    1. A FormBuilder object is associated with a particular model object and allows you to generate fields associated with the model object.
    1. You don't have to rely on the automated rendering. For example, actions that could result in the rendering of different templates will use the manual rendering methods:
    2. An action may contain only a single render or a single redirect. Attempting to try to do either again will result in a DoubleRenderError:
    3. Redirects are used to move from one action to another.
    4. It's automatically configured.
    5. Action Controller sends content to the user by using one of five rendering methods.
    6. This is useful for objects that are not yet ready to be persisted, such as a Signup object constructed in a multi-paged process, or objects that don't change much and are needed all the time, such as a User object for a system that requires login.

      objects that are ready to be persisted 한 것들은, server에 지속적으로 저장되는 객체들로 생각할 수 있다. 반면 session에 저장되는 obejct들은 브라우저가 켜져 있는 동안만 저장되는 것들이다.

    7. Sessions allow you to store objects in between requests
    8. All request parameters, whether they come from a GET or POST request, or from the URL, are available through the params method which returns a hash
    9. For every request, the router determines the value of the controller and action keys.
    10. These two methods represent the two basic action archetypes used in Action Controllers. Get-and-show and do-and-redirect.
    11. Actions, by default, render a template in the app/views directory corresponding to the name of the controller and action after executing code in the action.
    12. Unlike index, the create action will not render a template. After performing its main purpose (creating a new post), it initiates a redirect instead.
    13. only the ApplicationController in a Rails application inherits from ActionController::Base. All other controllers in turn inherit from ApplicationController