Web design and development is a complex process — one that often necessitates either a great deal of skill or a great deal of money. Unfortunately, this isn’t always possible and, for websites with a much smaller audience, not always needed. However, with a massive market of WYSIWYG-esque web creation tools out there, it’s not too difficult of an issue to overcome.
Jimdo is one such service that allows you to produce, manage and maintain a basic website through a complimentary iPad app. In this article, we’re going to take a look at Jimdo for iPad, take a tour to get you started and see whether it’s the solution you should be choosing for website creation and management on your iPad. (more…)
Document organisation is becoming ever more popular with those wanting to move to a paperless workflow. Whilst apps such as Evernote allows us to keep everything in one place, it’s multipurpose functionality can make it a little bit overwhelming when wanting to organise specific documents.
Doo attempts to be your central location for all your documents, regardless of what popular syncing service they may be stored in, whilst using some iOS-specific features that add to the experience. Unfortunately, the experience is one lacking many things. I test drive Doo for iPad to see what it does, though perhaps more accurately, doesn’t do.
VLC has had a turbulent history on iOS, having already been released before being removed due to a disagreement on the compatibility of VLC’s open-source development with the licensing and DRM that Apple places upon all apps listed on the App Store.
After an absence of a couple of years, VLC is now back in the App Store but this time, it’s here to stay. Let’s take a look at one of the most popular cross-platform media playback apps, now available on iOS.
Well, we’ve come to the conclusion of our Secondary Pythonista series. “Evaluating the End Product” is the title, but if you’ve been following along at home, you know our script is not complete. In the first part of this article we’ll finalize the script. In the second part we’ll review what we’ve done through this series, and where we could go with our little script.
In our last Secondary Pythonista article we covered a lot of good ground. We went from no written code to a working script which collects ids corresponding to the articles we’re looking to compile. And it’s all been with less than 30 lines of code. Pretty fantastic.
But we still have a ways to go before we can consider our script even remotely “finished”. Today we’ll start harvesting the output we want to compile, storing it in the best manner possible to be retrieved later, all with a view towards final output.
Welcome to the fourth installment of Secondary Pythonista. After careful consideration and research over the last two articles we now have a project brief, a plan of attack, and have chosen the tools we’ll need to execute on that plan.
In this article, using the information we’ve compiled previously, we’ll begin executing on those plans. We’ll begin writing code in Pythonista. As we do that, the value of all the pre-work that we did will become quickly apparent. There’s a strong temptation to dive head-first into writing code, but the careful and methodical approach we’ve gone with for this tutorial as many benefits, including giving you, dear reader, a better understanding of the why we’re programming a certain way in addition to the how to program in that manner.
So let’s get to it!
Hopefully you’ve been keeping pace with our new Secondary Pythonista series. In our last article we were presented with the project brief for our script. This kind of brief, some sort of starting point, is essential to creating a good script. Without a sense of direction, without a clear goal in mind, the script will be aimless, essentially useless, and may never end up being completed to any functional degree.
Programming languages are practical tools used to solve real-life problems. So naturally, the best way to learn a programming language — and by extension a programming utility like Pythonista — is by solving a real-life problem with it. That’s what we’re going to do here in Secondary Python, take an idea for a program, something that solves a problem, and then use Python and Pythonista to build a solution to that problem.
So without further ado, lets examine the project brief.
We’re back! As promised at the conclusion of Pythonista 101, we’re back with a new series detailing Pythonista and the process of building useful utilities in the Python language.
Before you’re introduced to the course material for Secondary Pythonista, let us briefly review what was covered in Pythonista 101.
How many productivity apps have you downloaded but don’t really use? Productivity apps are meant to make our lives easier, but it can take a bit of work to put a new planning and organization system in place. Many of us are using our iPads like printed books, failing to take advantage of all the useful features that can make our lives more organized and efficient. I downloaded the Paprika desktop app for Mac months ago, but it wasn’t until I purchased the iPad version that I truly utilized the capabilities of this cloud-based system for recipe collection, meal planning, grocery shopping and cooking in the kitchen.
Are you tired of being disorganized in the kitchen? Does poor meal planning result in eating out more often than you’d like? Have you been using Paprika to collect recipes that you never end up cooking?
If you answered yes to any of these questions, keep reading to learn how to use Paprika for iPad to make cooking at home more organized, efficient and enjoyable.