After the tutorial of Install Fedora 27 LXDE Desktop and this tutorial is mainly to see what to expect from a freshly installed Fedora 27 LXDE Desktop – the look and feel of the LXDE GUI – https://lxde.org/
The idea of this tutorial is just to see what to expect from Fedora 27 LXDE – the look and feel of the GUI, the default installed programs and their look and how to do some basic steps with them, it is included also screenshots of the LXDE settings programs. Here you’ll find more than 87 screenshots and not so many text we do not want to turn this review of many text and version information and 3 meaningless screenshot, which you cannot see anything for the user interface, which these days is the primary goal of a Desktop system. You can expect more of this kind reviews in the future…
Fedora 27 LXDE is really light and fast. The default installation includes only minimum software, but you could always install additional packages. It really should be used on a old system or embedded devices (like ex-windows tablets with low memory), because the GUI do not have many features like panel customization and build-in programs. Still it is extremely fast and if you do not need a fancy look and customization you could use it!
After the tutorial of Install Fedora 27 KDE Plasma Desktop this tutorial is mainly to see what to expect from a freshly installed Fedora 27 KDE Plasma Desktop – the look and feel of the new KDE GUI (version 5.12 of KDE Plasma).
The idea of this tutorial is just to see what to expect from Fedora 27 KDE Plasma – the look and feel of the GUI, the default installed programs and their look and how to do some basic steps with them, it is included also screenshots of the KDE settings program. Here you’ll find more than 160 screenshots and not so many text we do not want to turn this review of many text and version information and 3 meaningless screenshot, which you cannot see anything for the user interface, which these days is the primary goal of a Desktop system. You can expect more of this kind reviews in the future…
SCREENSHOT 1) Select and boot Fedora 27 KDE Plasma Desktop from our installed operating systems in grub menu
After the tutorial of Install Fedora Workstation 27 (Gnome GUI) this tutorial is mainly to see what to expect from a freshly installed Fedora 27 Workstation – the look and feel of the GUI (Gnome – version 3.26).
The idea of this tutorial is just to see what to expect from Fedora 27 Workstation (Gnome) – the look and feel of the GUI, the default installed programs and their look and how to do some basic steps with them. Here you’ll find more than 130 screenshots and not so many text we do not want to turn this review of many text and version information and 3 meaningless screenshot, which you cannot see anything for the user interface, which these days is the primary goal of a Desktop system. You can expect more of this kind reviews in the future…
screenshot 1) The default desktop look after logging
This tutorial will show you the simple steps of installing a modern Linux Distribution like Fedora 27 Workstation with Gnome for the user graphical interface. First we present the basic steps for installing the Operating system in addition to your present operating systems (here we have two: Windows 10 and Ubuntu 17) and then you can see some screenshots of the installed system and the look and feel of it. We have another tutorials showing more screenshots of the installed and working Fedora 27 (Gnome and KDE plasma) – so you can decide which of them to try first – coming soon.
We used the following ISO for the installation process:
It is a LIVE image so you can try it before installing. The easiest way is just to download the image and burn it to a DVD disk and then follow the installation below:
STEP 1) Boot your machine from the CD or USB (whatever you made for the installation device)
1) all active connections; 2) requests per second to nginx Nginx Graphs
CHART 2) Nginx Graphs 2
1) nginx active connections by their status – reading (from client), writing (from client), idle (doing nothing, but opened to the client); 2) connections rate – accepted and handled Nginx Graphs 2
1) active connections – active (executing PHP code on the CPU right now – “php running”), max active, idle; 2) requests; 3) performance – max children reached or slow requests (it depends on your version of netdata). PHP-FPM – FastCGI PHP performance metrics
CHART 4) PHP-FPM – request information
1) reuqest duration – minimum, maximum, avarage – how much time do a request take time – very useful to see how fast is your backend application. 2) request CPU in procentages; 3) request memory – reuested memory by your php fpm processes. PHP-FPM – request information
CHART 5) MySQL – performance metrics
1) bandwidth – The amount of data sent to mysql clients (out) and received from mysql clients (in); 2) queries – The number of statements executed by the server. To see a slow queries the slow query log should be enabled. MySQL – performance metrics
CHART 6) MySQL – handlers and locks
1) handlers – netdata Quotation: “Usage of the internal handlers of mysql. This chart provides very good insights of what the mysql server is actually doing. – commit, the number of internal COMMIT statements; delete, the number of times that rows have been deleted from tables; prepare, a counter for the prepare phase of two-phase commit operations; read first, the number of times the first entry in an index was read. A high value suggests that the server is doing a lot of full index scans; e.g. SELECT col1 FROM foo, with col1 indexed; read key, the number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries; read next, the number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan; read prev, the number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY … DESC; read rnd, the number of requests to read a row based on a fixed position. A high value indicates you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan entire tables or you have joins that do not use keys properly; read rnd next, the number of requests to read the next row in the data file. This value is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have; rollback, the number of requests for a storage engine to perform a rollback operation; savepoint, the number of requests for a storage engine to place a savepoint; savepoint rollback, the number of requests for a storage engine to roll back to a savepoint; update, the number of requests to update a row in a table; write, the number of requests to insert a row in a table.” 2) MySQL table locks counters, netdata Quotation: ” immediate, the number of times that a request for a table lock could be granted immediately – waited, the number of times that a request for a table lock could not be granted immediately and a wait was needed. If this is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.” MySQL – handlers and locks
CHART 7) MySQL – sorts, selects and temporaries
1) mysql SELECT JOIN – full range, range, scan; 2) mysql sorts – range and scan; 3) temporaries – disk tables (writing to the disk is slow and should be avoided!!!) and tables. MySQL – sorts, selects and temporaries
CHART 8) MySQL – connections and binlog
1) connections in seconds – all and aborted – if you are using persistent connections to MySQL you can see a busy MySQL server could have 2-3 new connections in a minute, because all the application backend uses the pool of already opened connections to the server. 2) connection errors – accepted, internal, max, peer_addr, select, tcpwrap; 3) binlog transactions per second MySQL – connections and binlog
CHART 9) MySQL – binlog and threads
1) binlog statement cache; 2) MySQL threads – connected, cached, running; 3) threads cache misses MySQL – binlog and threads
CHART 10) MySQL – Innodb engine infromation
1) Innodb I/O bandwidth – reads and writes; 2) Innodb I/O Operations – reads, writes and fsyncs; 3) Innodb Pending I/O Operations – reads and fsyncs; 4) Innodb Log Operations – write requests and writes. MySQL – Innodb engine infromation
CHART 11) MySQL – Innodb engine infromation 2
1) Innodb OS Log Operations – fsyncs; 2) Innodb OS Log bandwidth – write (megabytes/s); 3) Innodb current row locks – current_waits; 4) Innodb row operations – inserted, read, updated and deleted. MySQL – Innodb engine infromation 2
CHART 12) MySQL – Innodb engine infromation 3
1) Innodb buffer pool pages – data, dirty, free, flushed, misc, total; 2) Innodb buffer pool bytes – data and dirty; 3) Innodb buffer pool read ahaed – all, evicted, random; 4) Innodb buffer pool requests – reads and writes per second. MySQL – Innodb engine infromation 3
CHART 13) MySQL – Innodb engine infromation 4
1) Innodb buffer pool operations – disk reads – operations per second. MySQL – Innodb engine infromation 4
CHART 14) MySQL – query cache (qcache)
1) query cache operations – hits, low memory prunes, inserts, not cached; 2) queries in the cache; 3) query cache free memory; 4) query cache memory blocks – free and total. MySQL – query cache (qcache)
CHART 15) MySQL – myisam engine information
This server does not uses MyISAM engine, so you can see almost everything is zero – 1) MyISAM key cache blocks – unused and used; 2) MyISAM key cache requests – reads and writes; 3) MyISAM key cache disk operation – reads and writes. MySQL – myisam engine information
CHART 16) MySQL – files
1) open files – how many files are opened at the moment; 2) opened file rate – files per second. MySQL – files
1) cache size – available and used; 2) network – in and out megabytes per second. Memcached – distributed memory caching system. A key-value memory storage.
CHART 18) Memcached – connections and items
1) connections – current and total. Persistent connections are used, so no new connections often; 2) items cached – current and total. 3) items – evicted (forced removed – be careful here, this means your cached items are forcedly removed by the server because of lack of memory?) and reclaims (expired items). Memcached – connections and items
CHART 19) Memcached – get and set operations
1) get operation requests – hits and misses; 2) get operations rate – requests per second; 3) set operation requests – requests per second. Memcached – get and set operations
CHART 20) Memcached – check and set ops, delete ops, increment ops
1) check and set operation requests – hits, misses, bad value; 2) delete operation requests – hits and misses; increment operation requests – hits and misses Memcached – check and set ops, delete ops, increment ops
1) Postfix Queue Emails – the emails in the queue of the mail transfer agent, these mails are in transfer state; 2) Postfix Queue Emails size – size. Postfix – mail service
CHART 23) Redis – performance metrics for in-memory data structure store, used as a database, cache and message broker.
1) operations – commands and operations per second; 2) hit rate – persentage, the effectiveness of the cache. Redis – performance metrics for in-memory data structure store, used as a database, cache and message broker.
CHART 24) Redis – memory, keys, network
1) Redis memory utilization – total and lua; 2) keys – how many keys does each database have – keys per database name; 3) network – Redis network bandwidth – in and out in megabytes per second. Redis – memory, keys, network
CHART 25) Redis – connections and replication
1) Redis connections – received per second – it’s like new connections and if you use persistent connections no new connections are opened often; 2) Redis clients – connected processes to the redis server; 3) replication – connected slave servers. Redis – connections and replication
CHART 26) Redis – persistence (save the databases to the disks)
1) Persistence changes since last save – changes – how many changed items have been there since last save of the databases to the disks. 2) Duration of the RDB Save operation – rdb save in time; 3) Status of the last RDB Save Operation – rdb status. Redis – persistence (save the databases to the disks)
CHART 27) Web server access logs information
Live parsing of the access logs – be careful here, because this could take a good deal of CPU and I/O of your busy server. Here we included only the default nginx log, which does not save many records. netdata Quotation: “Information extracted from a server log file. web_log plugin incrementally parses the server log file to provide, in real-time, a break down of key server performance metrics. For web servers, an extended log file format may optionally be used (for nginx and apache) offering timing information and bandwidth for both requests and responses. web_log plugin may also be configured to provide a break down of requests per URL pattern (check /etc/netdata/python.d/web_log.conf).” – 1) responses – success and bad requests per second; 2) Response codes – 1xx and 4xx and more if any in the logs. Web server access logs information
CHART 28) Web server access logs information – detailed response code, bandwidth, http methods
1) detailed response code – requests per second; 2) bandwidth of the requests and reponses; 3) Requests per HTTP Method – GET, POST, PUT, DELETE and so on if they present in the logs. Web server access logs information – detailed response code, bandwidth, http methods
CHART 29) Web server access logs information – http versions, ip protocols, clients
1) Requests per HTTP Version – 1.0, 1.1 and 2.0 if any in the logs; 2) Requests per IP protocol – IPv4 and IPv6 (if used); 3) clients – unique client IPs per data collection. Web server access logs information – http versions, ip protocols, clients
CHART 30) Web server access logs information – unique client IPs
Unique client IPs since last restart of netdata Web server access logs information – unique client IPs
This is a review of the netdata graphs. Here you can see what you can expect to have when you install netdata (version 1.10) in you server.
As you can see many of the graphs have detailed explanations and some of them have hits what to monitor and pay attention to.
CHART 1) System Overview and grapsh which gather statistics from all parts of the system like CPU, load, disk, ram, swap, network, processes, idlejitter, interrups, softirqs, softnet, entropy, ipc semaphores, uptime.
This is a fst view of the resources of the system and it presents summarized statistics, not detailed! For example you can expect to have the total CPU usage not per core or processor and so on. System Overview
CHART 2) CPU and Load
1) Total CPU utilization, netdata Quotation: “Total CPU utilization (all cores). 100% here means there is no CPU idle time at all. You can get per core usage at the CPUs section and per application usage at the Applications Monitoring section. Keep an eye on iowait. If it is constantly high, your disks are a bottleneck and they slow your system down. Another important metric worth monitoring, is softirq. A constantly high percentage of softirq may indicate network driver issues.” and 2) System Load Average – netdata Quotation: “Current system load, i.e. the number of processes using CPU or waiting for system resources (usually CPU and disk). The 3 metrics refer to 1, 5 and 15 minute averages. Linux calculates this once every 5 seconds. Netdata reads them from /proc/loadavg.”” CPU and Load
CHART 3) Disk
1) Total Disk I/O for all disks from /proc/vmstat. You can easily match how much of the read/written data is from/to disks. 2) Memory paged form/to disk. Disk I/O and Memory Paged from/to disk
CHART 4) RAM
1) Read from /proc/meminfo. It shows the total RAM and how much is free, used, cached and in buffers. Together with swap graph this is like “free” linux command in the browser. 2) Read from /proc/meminfo. It shows total, free and used swap memory. 3) Swap I/O – Read from /proc/vmstat. More interesting than the previous one, because here you can get aware how often is used your swap device. In fact if you have ins and outs here even a couple of them you probably need more physical RAM or you have misconfigured a service or a application, which could be identified by graphs in Applications->mem or User->mem – which shows the applications’ and users’ ram usage. System memory and System swap memory
CHART 5) All network traffic on all interfaces – no virtual ones included, but it includes IPv4 and IPv6 traffic.
Physical Network Interfaces Aggregated Bandwidth
CHART 6) Processes
1) Read /proc/stat. It appears the Running are “processes in the CPU” and Blocked are in Disk sleep. netdata Quotation: “System processes, read from /proc/stat. Running are the processes in the CPU. Blocked are processes that are willing to enter the CPU, but they cannot, e.g. because they wait for disk activity.” 2) The number of new processes created per second. 3) All system processes – the total number for the given time. System processes
CHART 7) Context Switches and idle
1) Context Switches – how many times the CPU is switching from one process, thread or task to another. 2) netdata Quotation: “idle jitter is calculated by netdata. A thread is spawned that requests to sleep for a few microseconds. When the system wakes it up, it measures how many microseconds have passed. The difference between the requested and the actual duration of the sleep, is the idle jitter. This number is useful in real-time environments, where CPU jitter can affect the quality of the service (like VoIP media gateways).” Context Switches and idlejitter
CHART 8) Interrupts and softirqs
1) Total number of CPU interrupts, 2) System interrupts – hardware interrupts – which part of your hardware system is doing the interrups – you could identify a hardware abuser. 3) CPU softirqs in detail, read from /proc/softirqs – you could identify a software abuser – a service or a processes Interrups and softirqs
CHART 9) softnet and entropy
1) netdata Quotation: “Statistics for CPUs SoftIRQs related to network receive work. Break down per CPU core can be found at CPU / softnet statistics. processed states the number of packets processed, dropped is the number packets dropped because the network device backlog was full (to fix them on Linux use sysctl to increase net.core.netdev_max_backlog), squeezed is the number of packets dropped because the network device budget ran out (to fix them on Linux use sysctl to increase net.core.netdev_budget).” 2) netdata Quotation: “Entropy, is a pool of random numbers (/dev/random) that is mainly used in cryptography. If the pool of entropy gets empty, processes requiring random numbers may run a lot slower (it depends on the interface each program uses), waiting for the pool to be replenished. Ideally a system with high entropy demands should have a hardware device for that purpose (TPM is one such device). There are also several software-only options you may install, like haveged, although these are generally useful only in servers.” softnet and entropy
CHART 10) IPC Semaphores and Uptime
1) The total ipc semaphores used in the system 3) uptime of the system ipc semaphores and uptime
CHART 11) CPU
Utilization by core/logical processor. You can see how much percentage of the CPU is spent in user, system, iowait (probably disk operations!) and softirq (mainly network, but could be also a program with many threads with a lot context switching between them). Here you can see the first Core utilization graph has softirq of 6.0 and the other have none – this is due to the network card is using only the first core/processor (more to follow on the subject). CPUs
CHART 12) Interrupts
Interrupts by core/logical processor. Hardware interrups – enp3s0_28 (the network card), NMI, LOC, PMI, IWI, RES, CAL, TLB and so on. You can see the network interrupts are processed only by the first core/processor. You can change this by setting cpu affinity and to split across all CPU – in most cases you do not need this, because using one core/processor the latency is better, but on a busy server easily could reach 100% busy of the first core and the network packets processing will get in troubles. Interrupts
CHART 13) softirqs
Software interrupts – TIMER, NET_TX, NET_RX, TASKLET, SCHED, RCU – network, context switches synchronization and so on. softirqs
CHART 14) softnet
Quotation netdata: “Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at System / softnet statistics. processed states the number of packets processed, dropped is the number packets dropped because the network device backlog was full (to fix them on Linux use sysctl to increase net.core.netdev_max_backlog), squeezed is the number of packets dropped because the network device budget ran out (to fix them on Linux use sysctl to increase net.core.netdev_budget).” You can see how much SoftIRQs related to network receive each CPU. As you can see again the network is processed by the first core/processor. softnet
CHART 15) throttling and cpufreq
1) The throttling of the CPU cores if any and 2) cpu frequency changes. If your server is in idle probably you can see more often to get to lower frequency on some cores/processors. Throttling and cpufreq
CHART 16) C-state residency for each core/processor.
Cpuidle
CHART 17) Memory
1) Total available RAM for applications, 2) Commited Memory is the all the memory allocated by processes and 3) page faults – Quotation netdata: “A page fault is a type of interrupt, called trap, raised by computer hardware when a running program accesses a memory page that is mapped into the virtual address space, but not actually loaded into main memory. If the page is loaded in memory at the time the fault is generated, but is not marked in the memory management unit as being loaded in memory, then it is called a minor or soft page fault. A major page fault is generated when the system needs to load the memory page from disk or swap memory.” Memory
CHART 18) Kernel and Swap memory
1) Quotation netdata: “Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk.” – you can tune kernel to how much dirty memory to hold. 2) Memory used by kernel – netdata Quotation: “The total amount of memory being used by the kernel. Slab is the amount of memory used by the kernel to cache data structures for its own use. KernelStack is the amount of memory allocated for each task done by the kernel. PageTables is the amount of memory dedicated to the lowest level of page tables (A page table is used to turn a virtual address into a physical memory address). VmallocUsed is the amount of memory being used as virtual address space.” 3) slab – netdata Quotation: “Reclaimable is the amount of memory which the kernel can reuse. Unreclaimable can not be reused even when the kernel is lacking memory.” kernel
CHART 19) Hugepages
netdata Quotation: “Hugepages is a feature that allows the kernel to utilize the multiple page size capabilities of modern hardware architectures. The kernel creates multiple pages of virtual memory, mapped from both physical RAM and swap. There is a mechanism in the CPU architecture called “Translation Lookaside Buffers” (TLB) to manage the mapping of virtual memory pages to actual physical memory addresses. The TLB is a limited hardware resource, so utilizing a large amount of physical memory with the default page size consumes the TLB and adds processing overhead. By utilizing Huge Pages, the kernel is able to create pages of much larger sizes, each page consuming a single resource in the TLB. Huge Pages are pinned to physical RAM and cannot be swapped/paged out.” hugepages
CHART 20) deduper (ksm)
You can save some RAM with this feature. netdata Quotation: “Kernel Same-page Merging (KSM) performance monitoring, read from several files in /sys/kernel/mm/ksm/. KSM is a memory-saving de-duplication feature in the Linux kernel (since version 2.6.32). The KSM daemon ksmd periodically scans those areas of user memory which have been registered with it, looking for pages of identical content which can be replaced by a single write-protected page (which is automatically copied if a process later wants to update its content). KSM was originally developed for use with KVM (where it was known as Kernel Shared Memory), to fit more virtual machines into physical memory, by sharing the data common between them. But it can be useful to any application which generates many instances of the same data.” deduper (ksm)
CHART 21) Charts with the performance of the disks and disk devices like raids – charts for every device in the system. Most important charts here are the disk utilization where you can see how busy is your device!
1) The disk I/O Bandwidth – Amount of data transferred to and from disk – “md2”. 2) Disk Completed I/O operations – netdata Quotation: “Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart).” Disks
CHART 22) Disk I/O
1) The average I/O Operations size of device “md2”, 2) Disk space utilization of device “md2” and 3) inodes usage of device “md2”. Disks
CHART 23) Disk I/O of md0
1) Disk I/O Bandwidth, 2) Disk Completed I/O Operations, 3) The average I/O Operations Disk statitsics for device md0
CHART 24) Disk I/O of sda
1) Disk I/O Bandwidth, 2) Disk Completed I/O Operations, 3) Disk current I/O Operations Disk statitsics for device sda
CHART 25) Disk I/O of sda 2
1) Backlog – netdata Quotation: “Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress.”, 2) Disk Utilization Time – one of the most important charts, you can see if you disk is saturated, netdata Quotation: “Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion.” 3) Average Completed I/O Operation Time 4) Average Completed I/O Operation Time Disk statitsics for device sda – 2
CHART 26) Disk I/O of sda 3
1) netdata Quotation: “The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading.” 2) netdata Quotation: “The number of merged disk operations. The system is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk.” 3) netdata Quotation: “The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel.” Disk statitsics for device sda – 3
CHART 27) Performance statistics for a NFS client working on the system.
1) RPC – calls per second, 2) What kind of RPC calls and how many of them. NFS Client
This is a basic review of the Eclipse new Angular IDE. What is the basic functionality of the IDE and how we can work with it. The main purpose is to show what it looks like creating an angular project.
STEP 1) Launch the Angular IDE and select the Workspace you used for your projects.
Angular IDE
STEP 2) Eclipse IDE started for the first time – no projects opened and no history projects.
eclipse-workspace
STEP 3) Create project by clicking the down array (the second icon from the left) and then Angular Project
Angular Project
STEP 4) A new window will pop up asking for the name of the project and as you can see you can tune the specific versions of Angular CLI, Node.js and NPM. Click “Next”.
New Angular Project
STEP 5) Here you see the commands that will be executed by the eclipse IDE to create a new Angular Project. Click “Finish”.
New Angular Project Finish
STEP 6) The commands of the previous step are executed and the needed packages and their dependecies will be installed. There a progress status with percetages right bottom of the IDE. When the percetages reach 100% the view for the angular project will be opened.
Creating the Angular Project
STEP 7) Angular project opened, the “main.ts” file is showed in the typescript editor. A proper hilighting of typescript language.
ReviewIDEApp
STEP 8) We open the “app.component.ts” file in the typescript editor and we add “body” variable for testing the IDE.
ReviewIDEApp – app.component.ts
STEP 9) The html file of the AppComponent – it has a proposals (autocomplete) even in the angular string interpolation {{}}. So we use the proposal of our AppComponent variable “body”.
ReviewIDEApp – app.component.html
STEP 10) There is a tab “Servers” left bottom with all the Angular CLI applications. We have only one ReviewIDEApp, mark it and then click on the “play” button and the project will be built and started on the local ip port 4200.
ReviewIDEApp – Servers
STEP 11) in the terminal you can see all the commands and their output. Our angular application is being built.
ReviewIDEApp – Terminal
STEP 12) Again in the “Servers” tab we see our application is running on http://localhost:4200/ Also you see our modification of the default code.
ReviewIDEApp – running – build OK
STEP 13) Open your browser and load http://localhost:4200/ you’ll see something similar and our variable “body” (“Hello World”) showed in the header.
ReviewIDEApp – browser http://localhost:4200/
STEP 14) Create a new angular component with the IDE is simple, just mark your application in the “Project Explorer” -> right mouse click -> “New” -> “Component”.
New Component
STEP 15) Set the “Element Name” and you also could click on “Advanced” to see more options for the component creation.
New Angular CLI Component
STEP 16) For example you can uncheck “Create component with Unit Test (–spec)” and then Next. It will not generate the spec file.
New Angular CLI Component – Advanced
STEP 17) You see the commands to be executed in the terminal and then click “Finish” to execute the commands.
New Angular CLI Component – Generated Command
STEP 18) The files for the component are generated – ts (typescript file), html (the template file) and css (the style file). The three file are placed in a separate directory with the name of the component. The typescript file has the skeleton of your angular component.
myfirstcom.component.ts
STEP 19) As you can see the CLI inlcuded the component we created from the previous step in our global app.module file.
app.modules.ts
STEP 20) Create a new angular pipe with the IDE is simple, just mark your application in the “Project Explorer” -> right mouse click -> “New” -> “Pipe”.
New Pipe
STEP 21) Set the “Element Name” and you also could click on “Advanced” to see more options for the pipe creation.
New Angular CLI Pipe
STEP 22) For example you can uncheck “Create component with Unit Test (–spec)” and then Next. It will not generate the spec file.
New Angular CLI Pipe – Advanced
STEP 23) You see the commands to be executed in the terminal and then click “Finish” to execute the commands.
New Angular CLI Pipe – Generated Command
STEP 24) One typescript file is generated. The typescript mypipe.pipe.ts file has the skeleton of a pipe component. There is the definition of the pipe class implementing the the mandatory class “PipeTransform” and the method transform to override.
mypipe.pipe.ts
STEP 25) Create a new angular service with the IDE is simple, just mark your application in the “Project Explorer” -> right mouse click -> “New” -> “Service” and you’ll see the window for creating a service. Enter “Element Name”, click “Advanced” to see more options for the angular services.
New Angular CLI Service
STEP 26) You see the commands to be executed in the terminal and then click “Finish” to execute the commands.
New Angular CLI Service – Generated Command
STEP 27) The typescript file for our service is generated: a an exported class with blank constuctor.
myserver.service.ts
STEP 28) There is autocomplete for the import directive.
import – autocomplete
STEP 29) There is autocomplete for the exported class of the imported file/library.
import class – autocomplete
STEP 30) There is autocomplete for the component names in the html. If you write “html component autocomplete
STEP 31) Our component works!
Our app in the Browser
STEP 32) There is an autocomplete of the all html tags.
Html template file
STEP 33) There is an autocomplete of the all html tags.
Html template file
STEP 34) Information is available for all properties.
Property information
STEP 35) Autocomplete proposal for all the available classes of an import.
Autocomplete proposal for classes
STEP 36) Autocomplete proposal fired in a funtion body.
Autocomplete proposal of keywords
Manage Cookie Consent
We use technologies like cookies to store and/or access device information. We do this to improve browsing experience and to show (non-) personalized ads. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
