There are many workflows to search the App Store on Editorial, SearchLink, by Brett Terpstra, has been ported to the platform and allows you to search many other places as well. All I needed was really a good and flexible App Store search. At first, I built one without a custom UI to test if I could do it and was fairly easy since I based it on SearchLink's bit for iTunes. Then I decided to build an interface for it and things, as always, got tricky.
I'm a very weird workflow builder, I must admit. I'd rather build everything into a single Python script rather than appeal to multiple steps or the Interface Builder. The ladder is definitely something I can't get my head around since I find it easier to see everything at the same place. Of course, this generates a wall of code, but it is fairly easy.
I believe that visualizing your whole structure as code helps when you're developing the actions for the your views. The core of this workflow is the
TextView and the
TableView since I knew both would require the use of features I haven't touched yet: custom delegates and the
We delegate twice, when you tap Return in the search field it triggers an App Store search, the output generates the content of the
TableView, then when you select an item it also delegates the link generation.
What we need the most when it comes to Editorial's
ui module right now are good examples and I think this one can definitely help you by uncomplicating such views. This second time I didn't even request for Ole's1 help, so I may be getting better at this.
When I asked on Twitter it was about an undocumented function I found out minutes later to activate a
TextViewafter loading. If you pay close attention to the docs (and I definitely read those in a regular basis), you'll find a
textview.end_editing()function. Two tries and I found the
begin_editing()as well. ↩