hshristov

One of the main goals of [email protected] is to enable more flexible composition of UI. Let's start with some history. Before 4.0 we create Frame control for you (check application.ios.ts and frame.android.ts). Frame control allows you to do navigation forward or backward. While this is convenient it introduce other issues that can't be workaround easliy. For example if you want to have TabView in all pages you have to include it in the xml and set its selectedIndex so that once you navigate to different page a correct TabViewItem is selected. This leads to several problems:

• parse more xml
• increase memory usage
• increase loading time

Same issues apply if you want to have SideDrawer control as a root component.

So in order to resolve these starting with 4.0 applicat

dlucidone

/*
 * Convert A String to Base64 String or Vice-Versa  
 */

declare const android: any;
declare const java: any;
declare const NSData: any;
declare const NSUTF8StringEncoding: any;
declare const NSString: any;

atinux

const waitFor = (ms) => new Promise(r => setTimeout(r, ms))
const asyncForEach = async (array, callback) => {
  for (let index = 0; index < array.length; index++) {
    await callback(array[index], index, array)
  }
}

const start = async () => {
  await asyncForEach([1, 2, 3], async (num) => {
    await waitFor(50)

nilsmehlhorn

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
	package="__PACKAGE__"
	android:versionCode="1"
	android:versionName="1.0">

	<supports-screens
		android:smallScreens="true"
		android:normalScreens="true"
		android:largeScreens="true"

jogboms

import { Pipe, PipeTransform, NgZone } from '@angular/core';
import { Observable } from 'rxjs/Observable';

import { ImageSource, fromResource } from 'image-source';
import { Cache } from 'ui/image-cache';

import { isFileOrResourcePath, isDataURI } from 'utils/utils';

let cache = new Cache();
cache.placeholder = fromResource('placeholder');

lattner

Async/Await for Swift

• Proposal: SE-XXXX
• Authors: Chris Lattner, Joe Groff

Introduction

Modern Cocoa development involves a lot of asynchronous programming using closures and completion handlers, but these APIs are hard to use. This gets particularly problematic when many asynchronous operations are used, error handling is required, or control flow between asynchronous calls gets complicated. This proposal describes a language extension to make this a lot more natural and less error prone.

This paper introduces a first class Coroutine model to Swift. Functions can opt into to being async, allowing the programmer to compose complex logic involving asynchronous operations, leaving the compiler in charge of producing the necessary closures and state machines to implement that logic.

EddyVerbruggen

// In case of Angular, this is the component that contains a view with a <RadSideDrawer>

export class MenuComponent implements AfterViewInit {

  @ViewChild(RadSideDrawerComponent) public drawerComponent: RadSideDrawerComponent;
  private _drawer: SideDrawerType;

  ngAfterViewInit(): void {
    this._drawer = this.drawerComponent.sideDrawer;
    this._changeDetectionRef.detectChanges();

kevmoo

// Ran with http://www.cryptosys.net/pki/uuid-rfc4122.html

import 'dart:math' as m;

void main() {
  for (var i = 0; i < 1000000; i++) {
    var thing = getThing();

    print(thing);
    print(thing.length);

EddyVerbruggen

// Usage: <Label maxLines="3" .. />

import { Directive, ElementRef, Input, OnInit, OnChanges } from '@angular/core';
import { Label } from 'tns-core-modules/ui/label';

declare const android, NSLineBreakMode: any;

@Directive({
  selector: 'Label[maxLines]',
})

m-abs

import { Directive, ElementRef, Input, OnInit, OnChanges } from '@angular/core';
import { Label } from 'ui/label';

@Directive({
  selector: '[maxLines]',
})
export class LabelMaxLinesDirective implements OnInit, OnChanges {
  @Input('maxLines') public maxLines: number = 1;

  public get nativeView(): Label {