ih2502mk

Lecture 1: Introduction to Research — [📝Lecture Notebooks] [▶️Video]
Lecture 2: Introduction to Python — [📝Lecture Notebooks] [▶️Video]
Lecture 3: Introduction to NumPy — [📝Lecture Notebooks] [▶️Video]
Lecture 4: Introduction to pandas — [📝Lecture Notebooks] [▶️Video]
Lecture 5: Plotting Data — [📝Lecture Notebooks] [[▶️Vide

putraxor

import 'dart:async';

import 'package:flutter/material.dart';

class InfiniteScroll extends StatefulWidget {
  @override
  _InfiniteScrollState createState() => new _InfiniteScrollState();
}

class _InfiniteScrollState extends State<InfiniteScroll> {

jdee

The iOS Knob Control and a new project, a framework for iOS called Violation, were both spun out of other large app projects I've been working on. The knob control came first. It resides in its own repo, has an unimaginative name that invites conflicts and is distributed simply as a single .h and .m file pair you can insert into your project.

That effort went well enough, and I was inspired to release some further custom iOS components from the same project. But the way the knob control was released would not scale to many classes, particularly with the introduction of things like base classes and private extensions.

Clearly all these things ought to share a single repo and be collected into a framework or other sort of

chrisbanes

/*
 * Copyright 2014 Chris Banes
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *    http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

tyvsmith

public class CrashReporting {

  public static class GenericReportingException extends Exception {
      public GenericReportingException(){}
  
      public GenericReportingException(String str){
        super(str);
      }
  }