HackIllinois Developer Survey

There was an error on your page. Please correct any required fields and submit again. Go to the first error

HackIllinois Hacker Feedback

1. Had you heard of The Climate Corporation before this event? 

• Yes
• No

2. How did you implement Login with Climate? *This question is required.

• Web (Single page JavaScript)
• Web App (Backend)
• iOS Module
• Android Module

3. How easy was it for you to integrate with Login with Climate? *This question is required.

• Extremely easy
• Very easy
• Moderately easy
• Slightly easy
• Not at all easy

4. Any other feedback about our Login with Climate modules? 

5. What additional APIs would you like to see from Climate?

• Weather
• Soil
• Satellite Imagery
• Other - Write In Please enter an 'other' value for this selection.
• Other - Write In Please enter an 'other' value for this selection.

6. How helpful were our team of engineers?

• Extremely helpful
• Very helpful
• Somewhat helpful
• Not at all helpful
• Other - Write In Please enter an 'other' value for this selection.

7. How helpful was our documentation?

• Extremely helpful
• Very helpful
• Somewhat helpful
• Not at all helpful
• Other - Write In Please enter an 'other' value for this selection.

8. What other APIs did you mashup with Climate's APIs?

• None
• Other - Write In Please enter an 'other' value for this selection.
• Other - Write In Please enter an 'other' value for this selection.
• Other - Write In Please enter an 'other' value for this selection.

9. Any other feedback you'd like to provide to the Climate API team (difficulties you faced, development portal, sign-up flow, test data)?

0%

Command Line Tag Cloud ~ 2/23/2016

branch brew cd checkout clear com commit components demothumbnails-master dev-portal downloads fieldflickr git github gulp history home https icanhazthumbnail images install js loginwithclimate ls markdown master md node npm open origin pianobar pod podfile pull push python setup simplehttpserver src status theclimatecorporation update upgrade verbose version visa watch xcode xcworkspace

created at TagCrowd.com

Command Line Tag Cloud ~ 2/17

Command Line Tag Cloud ~ 2/15/2016

add app applewatchfielddisplay beanless cd clear commit components content cp create-dev-account desktop dev-portal downloads droz git grandprizes gulp hero history home images index install jpeg jpg js ls markdown markdownlink markdownutils md npm png push python pythong react readme requestutil sidebar simplehttpserver src status stores styles userappview vim visa watch

created at TagCrowd.com

Command Line Tag Cloud ~ 2/14/2016

acres application boundary cd clear client clientname commit content curl farm farmname field git gulp https json ls name oada polygon python resources simplehttpserver source ssh type vnd watch xpost

created at TagCrowd.com

Command Line Tag Cloud ~ 12/23/2015

ad add amazonaws api authorization bearer bin cd cleanup clear commit content-type css curl echo exit fb file git heroku history html https image imagery install jp local ls master mooberry-jpg partnerapis pip postgres push py python pythonw qa routes static status templates txt type users usr vim vv x-user-name

created at TagCrowd.com

Command Line Tag Cloud :: 11/29/2015

add api clear commit css forms geolocations git heroku history home html layout login ls main master michael models origin pianobar push py python routes sed static status templates txt vim wikipedia working wrapper

created at TagCrowd.com

Introducing Command Line Tag Clouds

It's late so I'll write the introduction another time. All you get tonight is the first tag cloud of my command line history for the past 24 hours. I think it says a lot...

activate add app bin bitbucket brew cached cd chdir cleanup clear clone commit create css deactivate demo drozprojects echo env exit fb-logo flask-sqlalchemy flasktest forms git grep gunicorn heroku history home html https images index info install instantflask jpeg js launchagents layout learningflask library load local localhost login logo logs ls main master mkdir models name open org origin pg pianobar piece pip plist png postgres postgresql procfile psql pull push py python pythonw requirements riverdroz rm routes runpsql scripts sh signup site-packages source static status styles su templates touch txt uninstall users usr venv vim virtualenv web worker wsgiapp

created at TagCrowd.com

Android Emulator

Programmatically Creating an iOS Swift Based UITableView and Supporting Detail View

This is a quick tutorial on how to create an iOS Swift based UITableView and supporting detail view. I will also point out mistakes I made along the way and the errors that I came across. I hope that at least one other person in this tiny world of ours finds this blog and is able to avoid the common pitfalls that come with trying to learn something new.

Part 1: Creating the UITableView controller and populating its cells with data from a webservice.

Setting up the app

1. Create a new Single Page Application 
2. Delete Story Board
3. Delete ViewController.swift file 
4. Delete Main from General 

Programmatically Create View 

1. Create new cocoa class > File > New > Cocoa Class
1. Change class from NSObject to UITableView 
2. Don't select "create xib" 
3. Make sure language is "Swift" 
4. Name the file EventsViewController
2. Open AppDelegate.swift and add the following lines of code:

 //  
 // AppDelegate.swift  
 // BlogPostiOSUITABLEVIEW  
 //  
 // Created by Michael Droz on 11/28/14.  
 // Copyright (c) 2014 Michael Droz. All rights reserved.  
 //  
 import UIKit  
 @UIApplicationMain  
 class AppDelegate: UIResponder, UIApplicationDelegate {  
   var window: UIWindow?  
   func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {  
     // Override point for customization after application launch.  
     window = UIWindow(frame: UIScreen.mainScreen().bounds)  
     //Create an EventsViewController  
     let evc = EventsViewController(style: .Plain)  
     //create an instance of UINavigationController  
     let navController = UINavigationController(rootViewController: evc)  
     //place nav controller's view in the window hierarchy  
     window!.rootViewController = navController  
     //can I delete these two lines?   
     window!.backgroundColor = UIColor.whiteColor()  
     window!.makeKeyAndVisible()  
     return true  
   }  
   func applicationWillResignActive(application: UIApplication) {  
     // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state.  
     // Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game.  
   }  
   func applicationDidEnterBackground(application: UIApplication) {  
     // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later.  
     // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits.  
   }  
   func applicationWillEnterForeground(application: UIApplication) {  
     // Called as part of the transition from the background to the inactive state; here you can undo many of the changes made on entering the background.  
   }  
   func applicationDidBecomeActive(application: UIApplication) {  
     // Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface.  
   }  
   func applicationWillTerminate(application: UIApplication) {  
     // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:.  
   }  
 }