Happy Tutorial Tuesday! Last week I had to create a keyboard extension for iOS that displays images and a search bar to be able to search for certain images. I looked up several tutorials, everything seemed straight forward… Until I started typing in the search and I couldn’t get the focus back on the the third party app (msg / or any other app). The nightmare began! Continue reading
And we’re back with a fresh tasty new tutorial for you!
Hey everyone! I’m the new Romaine and today I’m gonna teach you how to implement localization in your Swift app. Let’s get started by creating a new Project for our tutorial.
In this tutorial we’ll review how to use Drupal 8 Restful Web Services. We’ll take you through viewing, creating, editing, and updating entities for your Drupal site. (Note: I am using Beta 14 version in this tutorial.)
Alright, let’s begin!
So it’s not Tuesday but we’ve been really busy doing exciting stuff, so we apologize that it’s a day late. But get ready to forgive us because in this tutorial we will learn how EASY it is to allow for the rotation of videos to landscape mode when displayed in a portrait-only iOS app.
Happy Tuesday, everyone! This week for our tutorial, we welcome our developer Matthieu to the blog. He’s going to walk us through setting up a canvas in Swift with dragging and boundaries.
We’re always on the lookout for ways we can improve our development and deployment processes. Most projects we undertake make use of Amazon AWS vast infrastructure. The ever popular AWS has grown leaps and bounds since its introduction to the startup world. Controlling startup cost is essential and AWS is a great asset to have in that regard.
Today we’ll take a peak at the CodeDeploy feature within the web service and how to integrate your app deployed on AWS with Github.
It’s not always easy to know if you’re writing good, robust code if you don’t have anyone looking over your shoulder and telling you how you could do things better.
This is where Codeclimate comes in to play!
In Drupal 8 we are allowed to create our custom entity types and add multiple data fields of different data types. However, this process can be very time-consuming without using any modules or template tools.
CSS preprocessors make CSS way better and anyone who writes a significant amount of styles should be using some kind of preprocessor. It’s understandable why some people are hesitant to switch to this workflow. It adds more complexity to the development process, you have to install extra stuff, maybe work from the terminal, and figure out how to automatically compile your code to regular CSS. It can be a lot of stuff to do, but while initially it may take more time and work to set up a project, it will pay off in the long run. The reason why CSS preprocessors exist is because CSS by itself can be pretty limited. Two very popular CSS preprocessors are Sass and Less, so I will focus on these two. With something like Sass or Less you get the ability to use variables, functions, mixings, you get nesting capabilities and more stuff that you just can’t do with css. Variables are one really useful thing you get with Sass and Less. You can define things like your site colors in one place, use the variables in your styles and if you ever need to change these colors you just go back and edit the variables. You would not have to go through your styles, copying and pasting new values or do a search and replace which can sometimes be unsafe.
Both Sass and Less also have these things called “mixins” which are these kind of reusable grouping of styles. Mixins can be useful to deal with something like CSS vendor prefixes, for example. To use the latest CSS tricks you sometimes have to repeat the style with a vendor prefix for each of the major browsers so you end up with a bunch of repeated stuff in your CSS, like so:
One thing you can do with a mixin is that you can wrap up all of those styles and call the mixin when you need it, and as many times as you need it. You can even pass parameters into a mixin and reuse it differently in different sections or pages.
Another cool thing about sass and less is the nesting capabilities. I’m a big fan of the nesting thing; here is an example of what I’m talking about:
And here is some Sass:
This nested structure helps you avoid repetition, organize your styles, and makes your CSS more closely resemble your HTML structure which I think is really neat. CSS just makes more sense to me written in this way. These are just some of the reasons why css preprocessors are awesome and why writers of css should be using them. You can get started with sass or less by checking out their documentation at http://sass-lang.com/ for sass and http://lesscss.org/ for less. So check them out, try them, they will make your css much better.