# ipad Published articles for ipad. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A document-based app in Swift Playgrounds for iPad DevFeed: [A document-based app in Swift Playgrounds for iPad]() Original publisher: [Read original article]() Published: 2021-12-28T17:00:00Z Content type: tutorial Language: en Sources: [Rambo Codes]() Topics: [Swift](), [iOS](), [SwiftUI](), [plist](), [Xcode]() Tags: [coding](), [ios](), [ipad](), [plist](), [swift](), [swift-playgrounds](), [swiftui]() ### AI overview A developer describes building a document-based app in Swift Playgrounds 4 for iPad. The article discusses adapting to Swift Playgrounds, comparing its code editor experience with Xcode, using SwiftUI for the app interface, and declaring custom document types in Info.plist. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## IKEA TRÅDFRI for Rebooting a Server or Modem DevFeed: [IKEA TRÅDFRI for Rebooting a Server or Modem]() Original publisher: [Read original article]() Published: 2020-11-25T11:20:33Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [gateway](), [Linux](), [zigbee](), [USB](), [Android](), [ipad](), [iphone](), [MQTT]() Tags: [android](), [gateway](), [internet](), [ipad](), [iphone](), [linux](), [mqtt](), [script](), [security](), [usb](), [zigbee]() ### AI overview A practical guide to using IKEA TRÅDFRI equipment to automate power cycling for a modem or server, including the required hardware, gateway, mobile device, and an alternative MQTT-controlled power socket. ### Source excerpt Recently I revamped my home internet, and (hopefully) temporarily ended up with a modem that needs to be power cycled from time to time. We're working on getting it fixed, but in the meantime I needed a solution for automated power cycling. There are various ways to turn the power off or on from a Linux computer, and some of these are very karmic. You can get a zigbee USB stick and ditto power plugs, and I am sure this is a lot of fun. ## Implementing mouse pointer interactions on iPad DevFeed: [Implementing mouse pointer interactions on iPad]() Original publisher: [Read original article]() Published: 2020-03-24T21:00:00Z Content type: tutorial Language: en Sources: [Rambo Codes]() Topics: [iOS](), [ui](), [coding](), [GUI](), [Xcode](), [keyboard]() Tags: [animations](), [apple](), [coding](), [gui](), [implementing](), [interaction](), [ios](), [ipad](), [keyboard](), [sdk]() ### AI overview A guide to implementing mouse and trackpad pointer interactions on iPadOS 13.4. It covers the relevant APIs, setup requirements, UIHoverGestureRecognizer, and hover animations while noting that iPad pointer behavior differs from macOS. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## When Zoom Is Too Heavy for Your Laptop Just Use Your Phone or iPad DevFeed: [When Zoom Is Too Heavy for Your Laptop Just Use Your Phone or iPad]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-19T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [zoom](), [Development]() Tags: [chat](), [ipad](), [laptop](), [remote-work](), [zoom]() ### AI overview The author reports that Zoom is slow and occasionally causes crashes on a 2015 MacBook Pro, while Zoom performs better on their phone and iPad. The iPad, particularly with a keyboard case, becomes the preferred workstation for video calls and chat while coding. ### Source excerpt This one is short but sweet and, honestly, the bulk of it is right in the title. I'm a pretty hard core software developer and I've found that the Zoom video chat tool, which my team uses every single day, tends to be big, fat and slow - to such a degree that my MacBook crashes from time to time. You should note that I do run a 2015 MacBook Pro 13" so not the best machine by today's standards but still absolutely serviceable as a daily driver for most development chores. It occurred to me recently that both my phone and my iPad are actually faster than my laptop so I fired up Zoom on them for a conference all and wow was it better. I was able to code through my team call and participate in the team video chat. While my phone worked perfectly well, it had a tendency to slide a bit leading me to break out my home made phone stand (no pic; since my phone is in it how can I take a pic; ask me personally if you care or want one). My iPad, however, since it has the keyboard case, works fantastically well for this tho. I'm also starting to use my iPad as my "chat workstation" allowing me to more easily partition the myriad chat apps that we all seem to use concurrently and focus on development more while still participating in chats without getting list in them. Recommended. ## Essential Technology for a Team Offsite DevFeed: [Essential Technology for a Team Offsite]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-10-30T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [hdmi](), [USB](), [Chrome](), [Windows](), [dropbox](), [Google]() Tags: [battery](), [beats](), [cast](), [chrome](), [chrome-cast](), [connectivity](), [dropbox](), [hdmi](), [hotspot](), [ipad](), [mac](), [management](), [offsite](), [startup](), [team](), [technology](), [wifi](), [windows]() ### AI overview A personal checklist of technology to bring to a team offsite, based on difficulties connecting several devices to a Chromecast-equipped TV. The recommendations include cables, USB storage, power accessories, a hotspot, a Chromecast, and a USB speaker, with dongles suggested for newer MacBooks. ### Source excerpt I'm in the process of wrapping up a team offsite even though I was ostensibly the lead technologist present, I was not actually prepared in terms of bringing the right technology with me to facilitate the team's needs. The single worst omission was the lack of an HDMI cable without which, I saw three tech folk (me, other engineer #1, team coordinator) fail to be able to connect a Mac, an iPad and a Windows box to a Chrome Cast equipped TV. Here is my list of the technical stuff I will never again be without for a team meeting: A couple of USB sticks. Even today in the age of Google Drive and DropBox, USB sticks can still be more convenient An Anker USB battery just in case 2 lightning cables, at least one of which is 6 foot like this Amazon cable 1 6' USB type C cable 1 USB 2 cable 1 power strip with USB ports 1 extension cord with USB ports 1 Verizon Mifi Hotspot able to share connectivity if WiFi fails 1 ChromeCast 1 6' HDMI Cable 1 USB Speaker like a Beats Pill This is roughly enough technology to support a team offsite of 6 to 8 people (imho). Note: I use a MacBook 2015 classic so I still have real ports. If you are using newer MacBooks then you likely need dongles as well. ## Big Improvements In Ebook Creation DevFeed: [Big Improvements In Ebook Creation]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2015-03-31T00:00:00Z Content type: article Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Scala](), [Python](), [HTML](), [CSS](), [Library](), [Programming]() Tags: [css](), [html](), [improvements](), [ipad](), [library](), [python](), [scala]() ### AI overview The author describes producing the second-edition Atomic Scala eBook from Word, using a Python build script, BeautifulSoup4, filtered HTML, CSS, and Calibre. Calibre generated an apparently flawless EPUB for iPad, while its MOBI output remained inadequate. ### Source excerpt I just finished the eBook of the 2nd edition of Atomic Scala. The PDF is, of course, the easiest since it gets created directly from Word (before you tell me I should use something other than Word -- I have done numerous experiments, and Word still provides the most power of anything I've found that allows a single document to produce camera-ready publishable pages, and at the same time generates and maintains a table of contents and index). ## Fortigate - VPN IPSec PSK XAuth z Android'a 4.x DevFeed: [Fortigate - VPN IPSec PSK XAuth z Android'a 4.x]() Original publisher: [Read original article]() Author: Tom Published: 2013-03-30T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Virtual Private Network](), [Android](), [Command-line interface](), [active directory](), [iOS]() Tags: [active-directory](), [android](), [cli](), [fortigate](), [fortios](), [ios](), [ipad](), [ldap](), [os](), [security](), [vpn]() ### AI overview A tutorial on configuring a Fortigate IPsec XAuth PSK VPN for Android 4.x phones and tablets to access an intranet. It covers CLI-based VPN setup, firewall rules, DNS access, and optional routing to external services, with notes about iOS compatibility. ### Source excerpt Do niedawna na moim telefonie VPN'ami były: PPTP lub L2TP - oba niespecjalnie mi się podobały. Ale od wersji 4-tej pojawiły się dwa nowe tryby: IPSec Xauth PSK i IPSec Xauth RSA. W pierwszym autoryzacja wykorzystuje login i hasło, w drugim certyfikaty. Tryb IPSec Xauth PSK jest bardzo wygodny bo łatwo można połączyć go z zewnętrznymi mechanizmami uwierzytelniającymi np. LDAP, Active Directory, itp. Pokażę jak skonfigurować swojego Fortigate'a by umożliwić połączenie z telefonów i tabletów na Androidzie 4.x do "Intranetu"1. Większość konfiguracji można przeprowadzić tylko w trybie CLI - zakładam że wiesz jak to zrobić. To co wygodniej można zrobić w trybie WWW to głównie tworzenie reguł dostępu na zaporze. ## Why I prefer Android to iOS DevFeed: [Why I prefer Android to iOS]() Original publisher: [Read original article]() Author: Graham King Published: 2012-12-31T17:53:58Z Content type: opinion Language: en Sources: [Graham King]() Topics: [Android](), [iOS](), [account](), [React Native]() Tags: [account](), [android](), [devices](), [email](), [ios](), [ipad](), [samsung](), [screen](), [software](), [tablet](), [terminal](), [weather]() ### AI overview The author explains a personal preference for Android over iOS, citing multi-user accounts, home-screen widgets, ad blocking, and greater access to internal device information. The comparison is based on the author's household devices, with Android devices described as newer. ### Source excerpt Our house has two iOS devices (an iPad and and iPod Touch), and two Android devices (Nexus 7 tablet, Samsung Galaxy phone). The Androids are newer than the iOS. So far, I prefer the Android devices for these reasons: - Android is multi-user. Just swipe down, select a different account. iOS seems designed for individuals living alone. - Widgets on the home screen. Just by glancing at my Nexus 7's screen I can check my email, my calendar, and the weather. ## Ad-blocking your iPad DevFeed: [Ad-blocking your iPad]() Original publisher: [Read original article]() Author: Graham King Published: 2011-10-25T00:01:54Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [proxy](), [Network](), [Ubuntu](), [iOS](), [Monitoring]() Tags: [ads](), [guide](), [ipad](), [monitoring](), [network](), [privacy](), [proxy](), [request](), [router](), [software](), [squid](), [tcp](), [ubuntu]() ### AI overview A tutorial on routing iPad network traffic through a Squid proxy on Ubuntu, inspecting GET and POST requests with tcpdump, and blocking ad servers through a router. It also describes observed app traffic that included a device identifier and, in some cases, location data. ### Source excerpt Uncover hidden iPad traffic and block pesky ads with this tech-savvy guide. ## How to get a job at FINN.no DevFeed: [How to get a job at FINN.no]() Original publisher: [Read original article]() Author: espen Published: 2011-09-02T08:08:46Z Content type: article Language: en Sources: [Finn.no]() Topics: [Job](), [iOS](), [iphone]() Tags: [company](), [developer](), [intern](), [internship](), [ios](), [ipad](), [teams]() ### AI overview An interview describes how a summer internship at FINN.no helped a university student gain experience, work on an iPhone/iPad proof of concept, and later become a developer at the company. ### Source excerpt If you're a student or just someone who is looking for a job you might be wondering: "How could I get to work for FINN.no?". One guy found an answer and is now one of the key developers on our iOS applications. We did an advert for summer interns last year and he was one of the people who came in to do some proof of concept work on iOS. The end result was an iPad application that never hit the AppStore, but for one of the participant this internship was the first step towards landing a job as a developer at FINN.no. What made you apply for the summer internship at FINN.no? It all started with my university teacher pointed out that FINN.no had an open internship during the summer. At first I did not want to apply, because I wanted to have vacation all summer (Like all other informatics students). However, I ended up with applying and just a few hours later I got a call; the internship was mine! The main reason to apply for the internship was that I was finishing my master's degree and was lacking work experience in the field of informatics. Secondly, I did not know that much about FINN.no and I could always need the extra money :) What did you learn during that summer? I learned that FINN.no is not just a big website, it is also a big company. And there are not just developers at FINN.no, but also a range of different jobs (Like finance, marketing, economics and so on). When taking about the technical aspects I learned how to develop for the iPhone/iPad. Furthermore, I learned that to get things working you are depended on a range of different "teams" to develop what you need. And this is not always trivial, because all "teams" have their own focus areas and problems. So you never work independent! What was it like to be a summer intern at FINN.no? It was both interesting and rich on experiences. The one thing I want to point out is how the atmosphere and the peoples at FINN.no are. The atmosphere is comfortable and "chill" and the people are welcoming and easy to ta ## Graded browser support version 1.1 DevFeed: [Graded browser support version 1.1]() Original publisher: [Read original article]() Author: espen Published: 2011-06-27T13:41:23Z Content type: article Language: en Sources: [Finn.no]() Topics: [browser](), [browsers](), [Mobile](), [Website]() Tags: [browser](), [browsers](), [ipad](), [mobile](), [mobile-web](), [phones](), [updated](), [version]() ### AI overview The article announces version 1.1 of the company's graded browser support matrix. It simplifies browser version targeting, adds support guidance for the mobile web service m.finn.no, and includes tablets in the desktop service matrix. Android-powered devices are not supported. ### Source excerpt We have reworked our graded browser support matrix which was released last year. Following the Laws of Simplicity we reduced the complexity in order to make it easier for everyone at our company to understand. We cut a lot of the version number into targeting latest for browsers which are frequently updated. There is also a support matrix for mobile phones which is targeting our new mobile web service m.finn.no. In addition to updating the versions we have also made the decision to include tablets in the support matrix for our desktop verison of our service. This is because we are currently not looking at creating specialized versions for tablets and our service works just fine on the tablets currently hitting our site. Currently almost all of our trafic is coming from iPad's, therefor Andoid powered devices are not supported. ## Why The Cloud Will Finally Work DevFeed: [Why The Cloud Will Finally Work]() Original publisher: [Read original article]() Author: Map Published: 2010-04-06T00:29:35Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Cloud](), [Users](), [App]() Tags: [apple](), [cloud](), [desktop](), [ipad]() ### AI overview The article argues that cloud computing will become mainstream when it is transparent and effortless for consumers. It highlights cross-device continuity, using iPad, MobileMe, and shared files as examples of experiences that could raise user expectations and pressure developers to deliver seamless cloud functionality. ### Source excerpt The cloud has a lot of technical arguments going for it. The problem is consumers don't understand the cloud, they don't understand virtual storage and growth and syncing and the complexities of things. The average consumer is generally pretty dumb, they just want to be able to do things and it just work. If they ask a question they want an answer, not the deduction behind the answer. It's why I loved mint.com so much when it launched. I gave it accounts and it told me everything I wanted to know. If it was wrong I seldom noticed it, such as classifying a purchase into a wrong category. My suspicion is that 98% of the users don't notice much of the mis-classification that happens. They look the first time and it looks pretty good so they trust it, because if you look at 90% of purchases and classify them, why use mint, why not just use excel, or even go back to a paper and notebook? Cloud is that same type of issue, it needs to just work, users need to just expect their document to always be the same. I think the iPad but more specifically MobileMe will have a great shot at doing this. The reason the iPad will play a role is now the average consumer will have more than 1 device. They'll have their laptop/desktop and an iPad. This user will want to work on the device, and more than just email. Having their application open a file, work for 15 minutes on a train/bus, turn it off, walk in their front door and open the same file on their computer will really bring cloud storage/computing to a consumer. Because apple controls the reins on the primary applications where this has value: This will push the expectation on developers to deliver the same kind of experience with the cloud, it's going to become the norm now. Not because its cost effective, not because of the technical benefits, but because it's going to be transparent to users, and users are just going to expect it from now on.