Es importante llevar el entorno instalado, el SDK de Android ocupa más de 1GB, no se puede descargar para instalación offline y es más que probable que la red no soporte descargas de ese tamaño.
npm install -g nativescript
| import { | |
| Component, ComponentFactoryResolver, ElementRef, EventEmitter, Input, OnInit, Output, ViewChild, | |
| ViewContainerRef | |
| } from '@angular/core'; | |
| import {ActivatedRoute} from '@angular/router'; | |
| import {Observable} from 'rxjs/Observable'; | |
| @Component({ | |
| selector: 'app-talk', | |
| styles: [ |
| import {AfterViewInit, Component, ElementRef, OnInit, ViewChild} from '@angular/core'; | |
| import {Observable} from 'rxjs/Observable'; | |
| import 'rxjs/add/observable/fromEvent'; | |
| @Component({ | |
| selector: 'app-hola', | |
| template: ` | |
| <p> | |
| hola works! | |
| <button #hola>Hola!</button> |
| { | |
| "title": "Liferay Portal API", | |
| "description": "A set of APIs that allows you to consume all of Liferay Portal resources", | |
| "@context": { | |
| "hydra": "https://www.w3.org/ns/hydra/core#", | |
| "ApiDocumentation": "hydra:ApiDocumentation", | |
| "property": { | |
| "@id": "property", | |
| "@type": "@id" | |
| }, |
As some of you already know, we are focusing our efforts on a new headless API strategy.
This past year we have tested several approaches to simplify API development and offer our users powerful APIs: from extending JAX-RS, through a heavily-typed builder, to using annotations similar to JAX-RS. Along the way, several alternative approaches appeared, pure JAX-RS approaches, GraphQL or OpenAPI-first designs.
Having several API initiatives at the same time, although great for maximizing learning, also meant a difficult time offering a consistent and uniform experience for developers and end users.
That's why Brian decided to unify them in a common approach, trying to get the best of each of them. As of today, the common approach for APIs under liferay will be an OpenAPI first design, with JAX-RS endpoints created by a gradle/java generator. This new approach will be lead by Brian Chan and Peter Shin.
