jebright

void main() {
  List<String> names = ["Joe", "Frankie", "Tom"];
  for (var n in names) {
    print('Hello ${n}');
  }
}

jebright

void main() {
  List<String> names = ["Joe", "Frankie", "Tom"];
  names.forEach((n) => 
    print('Hello Mr. ${n}'));
}

jebright

void main() {
  
  //Fix lengthed list
  var namesFixed = new List<String>(3);
  namesFixed[0] = "Joe";
  namesFixed[1] = "Frankie";
  namesFixed[2] = "Tom";
  //namesFixed[3] = "Kaboom!"; //this would be an error
  log(namesFixed)  ;
  

jebright

class Person 
{
  String firstName;
  String lastName;
  
  Person(this.firstName, this.lastName);
}

void main() {
	List<Person> people = new List<Person>();

jebright

void main() {
  List<double> prices = [0.25, 1.00, 3.33, 0.75, 4.25, 5.99];  
  var overOneDollar = prices.where((p) => p > 1.00);
  log(overOneDollar); //prints 3.33, 4.25, 5.99
}
  
void log(var lst) {
  lst.forEach((n) => print(n));
}

jebright

void main() {
  List<double> prices = [0.25, 1.00, 3.33, 0.75, 4.25, 5.99];  
  prices.sort();
  log(prices); //prints 0.25, 0.75, 1, 3.33, 4.25, 5.99
  
  List<String> alphabet = ["b", "c", "a"];
  alphabet.sort();
  log(alphabet); //prints a,b,c
}
  

jebright

class Sale {
  int employeeId;
  double price;
  Sale(this.employeeId, this.price);
}

class Employee {
  int id;
  List<Sale> sales;
  Employee (this.id, this.sales);  

jebright

import 'dart:async';
import 'package:flutter/material.dart';
import 'dart:isolate';

void main() => runApp(new MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return new MaterialApp(

jebright

Project Charter Template

1. Project Title

The project title section serves as the official name of the project. It should be clear, concise, and reflective of the project's primary purpose. The title provides a quick reference point for all stakeholders and helps in creating a common understanding of the project's scope and objectives.

**Example:**Project Title: Enhancement of Sales CRM System

2. Project Overview

jebright

Revision History

Purpose: The revision history section tracks changes made to the SRS document over time. It provides transparency and accountability for modifications, ensuring that stakeholders are aware of the document's evolution. Best practices involve documenting the date, author, and a brief description of each revision, facilitating clear communication and traceability.

|Date|Author|Description|:(table="column-widths:-1,132,152,500"): |||| ||||

1. Introduction