Be able to push to Heroku as any of three Heroku users from a single computer and a single user.
For this, you will not be allowed to copy and paste anything - except SSH keys themselves, because we're not THAT evil.
If you get error messages, read them carefully, and make note of what you understand, what you don't understand, and what you think you understand.
I hate to say it but our view controllers have gotten fat, and it's our fault! We feed them protocol after protocol, business rule after business rule. They don't know any better and they just gobble them all up...
This will be a 3 part "Tune up your table view" series in which we will take an old fat view controller, slim it down with some refactoring, freshen it up with some MVVM and then make it fly with some better asynchronous operation management!
In part 1 using refactoring and a couple of Interface Builder tricks hopefully I can provide some motivation to start your journey towards getting your view controllers back in fighting shape!
UITableViews are pretty integral to most iOS apps so I'm going to use it as an example of how to change a 'fat' view controller into a 'slim' one.
Welcome back for the conclusion of this 3 part series! In part 1 we learnt how to slim down our view controllers to a manageable size. In part 2 we learnt how to strip out all the non-ui related logic. This time we are going to focus solely on the UITableView and how we can properly handle multiple asynchronous operations in its cells for maximum performance!
As always we will be starting with our project from last time.
Our current implementation is very bad... our UITableViewCells are performing an expensive operation, and on the main thread no less!
The following code is currently in the setup method of our cell:
| # You must require this file in application.rb, above the Application | |
| # definition, for this to work. For example: | |
| # | |
| # # Syslog-like Rails logs | |
| # if Rails.env.production? | |
| # require File.expand_path('../../lib/better_logger', __FILE__) | |
| # end | |
| # | |
| # module MyApp | |
| # class Application < Rails::Application |
| Model.new.foo |
| // 1. Add Bootstrap as a dependency in package.json | |
| { | |
| ... | |
| "dependencies": { | |
| ... | |
| "bootstrap": "~3.3.6" | |
| } | |
| } |
| module Jekyll | |
| class CategoryIndex < Page | |
| def initialize(site, base, dir, category) | |
| @site = site | |
| @base = base | |
| @dir = dir | |
| @name = 'index.html' | |
| self.process(@name) | |
| self.read_yaml(File.join(base, '_layouts'), 'category_index.html') |
| /** | |
| * The following preprocessor macros can be used to adopt the new nullability annotations and generics | |
| * features available in Xcode 7, while maintaining backwards compatibility with earlier versions of | |
| * Xcode that do not support these features. | |
| */ | |
| #if __has_feature(nullability) | |
| # define __ASSUME_NONNULL_BEGIN NS_ASSUME_NONNULL_BEGIN | |
| # define __ASSUME_NONNULL_END NS_ASSUME_NONNULL_END | |
| # define __NULLABLE nullable |
I have been struggling to start a new project with Phoenix 1.3 and the new vue-cli 3 for Vue.js. There are tons of example already but none of them suited my needs, because:
Assuming that you have Elixir and Phoenix 1.3 are both installed, let's build our new App.
| // first run: | |
| // yarn add glob-all purgecss-webpack-plugin --dev | |
| /* | |
| config/webpack/environment.js | |
| PurgeCSS configuration for Rails 5 + Webpacker + Tailwind CSS + Vue.js | |
| Optionally, put this in production.js if you only want this to apply to production. | |
| For example, your app is large and you want to optimize dev compilation speed. | |
| */ |
