Author
Topic: iOS application development tutorial (Read 4428 times)

I'm working on a Mac OS 10.12.3. The latest stable version of Lazarus is installed.My Lazarus works with gdb 8. I use components from TMS Software and Devart's Unidac. Many components of these 2 companies are supposed to work with iOS and Android.

But I don't know how to develop with Lazarus on iOS with the latest versions of Lazarus and Mac OS. So I'm looking for a tutorial step by step.

I do this with Qt 5 on both Android and iOS, Android : Android from Linux version (Ubuntu 16.04) and iOS from Mac OS 10.12.3.

That's why I am looking for any useful and reliable information to approach these developments with Lazarus. Thank you in advance. With kind regards, Gilles.

Well, I couldn't know that you gave up some of your projects. What I realised, however, is a confusing variety of (mostly unfinished) approaches. Therefore, a tutorial would have been (and would be) welcome.

I will give ProjectXC a try, but that it "might work" is not very encouraging (given my chronic lack of time).

Well, I couldn't know that you gave up some of your projects. What I realised, however, is a confusing variety of (mostly unfinished) approaches. Therefore, a tutorial would have been (and would be) welcome.

I will give ProjectXC a try, but that it "might work" is not very encouraging (given my chronic lack of time).

ProjectXC doesn't have any templates for iOS development, although that would be a possibility.

Another approach would be to do the UI with Swift. Think of Swift as the UI language of iOS the way Javascript is the UI language of Web apps. Then put common Pascal code in a dynamic library and call it from the Swift code. Swift can digest any header file (.h) for C and Obj C libraries and frameworks. If the Pascal dynamic library has a C interface and a header file, then you're good to go.

Another approach would be to do the UI with Swift. Think of Swift as the UI language of iOS the way Javascript is the UI language of Web apps. Then put common Pascal code in a dynamic library and call it from the Swift code. Swift can digest any header file (.h) for C and Obj C libraries and frameworks. If the Pascal dynamic library has a C interface and a header file, then you're good to go.

That defeats the benefits of Pascal being cross-platform.Why learn pascal, if in the end you've to learn C/ObjC or Swift any way?!

I can accept that approach on an earlier stage of development - back in a days, when there were no Objective-Pascal. But, with objective-pascal such language mix looks redundant

Hello,actually, I don't know how to start. But maybe Lazarus doesn't make it possible to do...

My lazarus projects are currently targeted for Windows, Linux and OS X in which I use TMS Software components. However, this TMS FNC Controls can be simultaneously used on these operating systems: [...], iOS, [...]. I'm obviously putting them in TForms and of course, exclusively in Lazarus Tforms (and not UI Xcode). Is this approach possible in the case of an iOS application produced with Lazarus or does it mean that these components can only be used with Firemonkey ?

You need to separate front end and back end when thinking about mobile platforms anyway - there's no one-GUI-fits-all concept with Lazarus (or anything else). But FPC for iOS allows you to re-use your programs logic cross-platform; I wouldn't call that a defeat

Btw, many posts by simonsayz here document a way to dynamically create even the UI in FPC - it's just not RAD using Lazarus.