-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
-
LMS:
A learning management system (LMS) is a software application for the administration, documentation, tracking, reporting and delivery of educational courses or training programs. Learning management system is a concept emerging directly from e-Learning, even though there were other tools, informatics or not which have encouraged distance education Distance Education Learning Environments Survey. The first introduction of LMS is in the late of 1990s
-
IMS:
IMS Global is a non-profit member collaborative inventing the future of education and learning technology.
The IMS LTI standard aims to deliver a single framework for integrating any LMS product with any learning application.
When using the LTI standard, the Tool Consumer (TC) is how we call the LMS
When using the LTI standard, the Tool Provider (TP) is the application which receives the TC data and requests.
In object-oriented web applications with databases, the Model consists of the classes that represent the tables in the database.
In Ruby on Rails, the Model classes are managed by ActiveRecord. In general, all the programmer has to do is inherit one of the ActiveRecord :: Base classes and the program will automatically find out which table to use and which columns it has.
The definitions of the classes also detail the relationships between classes with relational object mapping statements.
In MVC, it is the visualization logic, or how the data of the Controller classes are displayed. Often in web applications, the view consists of a minimum amount of code included in HTML.
There are currently many ways to manage views. The method used in Rails by default is to use Embedded Ruby (files.rhtml, from version 2.x onwards of RoR files.html.erb), which are basically HTML code fragments with some code in Ruby, following a syntax similar to JSP. You can also build views in HTML and XML with Builder or use the Liquid template system.
It is necessary to write a small piece of code in HTML for each method of the controller that needs to show information to the user. The "layout" or layout of the elements of the page is described separately from the action of the controller and the fragments can invoke each other.
In MVC, Controller classes respond to user interaction and invoke the logic of the application, which in turn manipulates the data of the Model classes and displays the results using the Views. In web applications based on MVC, the controller methods are invoked by the user using the web browser.
The implementation of the Controller is handled by the Rails ActionPack, which contains the ApplicationController class. A Rails application simply inherits from this class and defines the necessary actions as methods, which can be invoked from the web, usually in the form http://application/example/method, which invokes ExampleController#method, and presents the data using the template file /app/views/example/method.html.erb, unless the method redirects to some other place.
Rails also provides scaffolding, which can quickly build most of the logic and views needed to perform the most frequent operations.
A resource represents a MVC bundle of a certain object.
While you're developing Rails applications, especially those which are mainly providing you with a simple interface to store data in a database, it can often be useful to use the scaffold method. Scaffolding provides more than cheap demo thrills.
This are some benefits:
Quickly get code in front of your users for feedback.
Motivation by faster success.
Learn how Rails works by looking at the generated code.
Use scaffolding as a foundation to jump start your development.
Gems are plugins and / or codes added to our Ruby on Rails projects, which allow us new features such as new create, new predefined functions (such as user login) or new tools for development such as Haml and SASS (the first is a new form of template based on HTML but more simple and powerful, and the second is the same but in the case of CSS). To find the list of available gems you can go to RubyForge.
An image is a read-only template with instructions for creating a Docker container. Often, an image is based on another image, with some additional customization. For example, you may build an image which is based on the Ubuntu image but installs the Apache web server and your application, as well as the configuration details needed to make your application run.
A container is a runnable instance of an image. You can create, start, stop, move, or delete a container using the Docker API or CLI. You can connect a container to one or more networks, attach storage to it, or even create a new image based on its current state.
By default, a container is relatively well isolated from other containers and its host machine. You can control how isolated a container’s network, storage, or other underlying subsystems are from other containers or from the host machine.
Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services and link them to work together if necessary. Then, with a single command, you create and start all the services from your configuration.