Most of the blogs are related to ruby and rails developer problems.
Angular 2 basic terminologies
Get link
Facebook
X
Pinterest
Email
Other Apps
-
Transpiler :
A source-to-source compiler, transcompiler or transpiler
is a type of compiler that takes the source code of a program written
in one programming language as its input and produces the equivalent
source code in another programming language.
Decorator :
Decorators are a proposed standard
for ECMAScript 2016 by Yehuda Katz, to annotate and modify classes and
properties at design time. This sounds pretty much like what annotations
do right? Well… sort of. Let’s take a look at what a decorator looks
like:
// A simple decorator@decoratorExpressionclassMyClass{}
Wait. This looks exactly like an AtScript annotation! That’s right.
But it isn’t. From a consumer perspective, a decorator indeed looks like
the thing that we know as “AtScript Annotation”. There is a significant
difference though. We are in charge of what our decorator does to our code. Taking the code above, a corresponding decorator implementation for @decoratorExpression could look like this:
functiondecoratorExpression(target){// Add a property on targettarget.annotated=true;}
Right. A decorator is just a function that gives you access to the target
that needs to be decorated. Get the idea? Instead of having a
transpiler that decides where your annotations go, we are in charge of
defining what a specific decoration/annotation does.
This, of course, also enables us to implement a decorator that adds
metadata to our code the same way AtScript annotations do (I keep
referring to “AtScript annotations” because what they do, is really an
AtScript specific thing). Or in other words: with decorators, we can
build annotations. ===================================================
Some basic files and terminologies which are used in angular 2 application : package.json lists packages the QuickStart app depends on and
defines some useful scripts.
tsconfig.json is the TypeScript compiler configuration file.
When you complete the free trial form you will get a screen like this: click whatever the linux version you do have then it will install the .run file. Linux– In the folder where you downloaded the Linux package, run the commands below for your platform. Then, follow the wizard instructions. 64-bit Linux Systems sudo chmod +x WowzaStreamingEngine-4.4.0-linux-x64-installer.run sudo ./WowzaStreamingEngine-4.4.0-linux-x64-installer.run 32-bit Linux Systems sudo chmod +x WowzaStreamingEngine-4.4.0-linux-installer.run sudo ./WowzaStreamingEngine-4.4.0-linux-installer.run If you acquired a new license key, you'll find it in the email that you received from Wowza Sales. To create a user name and password for an Administrator account. You'll use this account to sign in to the browser-based Wowza Streaming Engine Manager. The user name and password values are case-sensitive. Linux – /usr/local/WowzaStreamingEngine-4.4.0/ (as the root user) Starting and Stopping ...
In highcharts may be some time you need subcategories of a category or more deep nested categories for that you need to use a js file called grouped-categories.js it is a plugin provided by highcharts for grouped categories. this plugin can be downloaded from https://github.com/blacklabel/grouped_categories/ after download please refer to the home page for examples http://www.highcharts.com/plugin-registry/single/11/Grouped-Categories but even though I followed there documentation but I haven't found it easy for me to implement it in column range chart <div id="container" style="width: 100%; height: 100%;"></div> <script src =''> </script> var chart = new Highcharts.Chart({ chart: { renderTo: "container", ...
I’ve been writing this web app that has the following models: Order, Recipient, Message. An order has many recipients and a recipient has many messages. The recipients are also dependent upon the order and the messages are dependent upon the recipient. In Ruby code this looks like: Order.rb class Order < ActiveRecord::Base has_many :recipients, :dependent => :destroy has_many :messages, :through => :recipients end Recipient.rb class Recipient < ActiveRecord::Base belongs_to :order has_many :messages, :dependent => :destroy end The idea here is that when I delete an order, I also delete any associated recipients and any associated messages. My controller looked like this: def delete Order.delete(params[:id]) end There are a couple things wrong with this. The first and most important thing is that when I delete a row in the order table, it leaves orphaned rows in the order and messages table. I want to delete these rows as well...
Comments
Post a Comment