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.
When it comes to Markdown editors, iPad users are pretty much spoilt for choice. From Byword to iA Writer, there’s something for almost everyone and each app boasts a myriad of features that makes choosing one a pretty lacklustre affair. I personally use Drafts when I’m working on my iPad, as I can use it for both scribbling down a quick note and typing a longer document and I’ve been a four-month relationship with Ulysses III on my Mac, which is simply awesome — I do pretty much all my writing on there.
So, you’d probably guess that when a new Markdown editor comes along, I don’t get that excited, right? Yes, that’s right, but there was a certain amount of mystery surrounding the release of Editorial. Federico Viticci has had his hands on the beta for quite some time now, and the developer Ole Zorn released a few pretty awesome-looking screenshots as well, which really started the wheel turning. Now, the final version is out — and it’s mighty impressive. Editorial has now become the Markdown editor on the iPad — and here’s why.
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.
Back in June, we ran a series of 4 tutorials designed to give you a really simple introduction to Pythonista, the wonderful programming tool available on iOS. We’re really pleased to announce that we’re running the second part of this course, which started yesterday, throughout August and September to give you a deeper knowledge of Pythonista and to help you solve problems within Python.
In the meantime, we’d really like to get your feedback on what you thought of the first part of our Pythonista tutorial! Go ahead and cast your votes in the poll box on the right, and please feel free to include any additional comments in the section below!
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.
If you missed these fantastic articles from iPad.AppStorm this month, then here’s another chance to catch up on some of my favourite writing from the site in June. And remember, if you have any suggestions then please feel free to post them in the Comments section below.
In the last Pythonista 101 article we discussed modules. Modules are Python scripts that come bundled with Pythonista giving us access to new and interesting features. Because of the sandboxed nature of iOS, what comes bundled in with apps like Pythonista is really all that we have to work with. When compared with the free reign found on Mac OS X, Linux, and even Windows, this may seem restrictive. Fortunately the developers of Pythonista have done a fantastic job packing as many modules into Pythonista as possible. Today we’re going to look over some more, as well as examine some real-world scenarios that Pythonista could assist with.