Delphixe4 firemonkey trial record, IOS application development or transplantation

Xe4 was released six days ago. added and subtracted. it is no longer the way FPC works. You can compile it on win. FPC is used to generate a project and compile and debug it on Mac. In fact, this is also a bit painful.

Can I only create a wizard-based application?

What about more features? IAP Social Share gamecenter and so on. Can I write new component by myself? The key is how to connect the native part of IOS?

The debugging mechanism is different from the previous one. It is similar to the flashbuilder method. However, this time, a PA server is run on Mac to connect devices or simulators (also in xcode version ). the flashbuilder is running on the device, and the simulator is a false version of win.

This debugging method is still quite painful. It is hard to imagine that a brand new person who wants to develop iOS devices will choose this one. you can't use the SDK. Once you have learned the SDK, you can directly write it on xcode. Why should you go to Delphi.

To sum up, if the requirements are not high, or only the previous application systems are integrated. it can be used once. otherwise, it seems impossible to extend the service. it is also possible that other components will soon become available .. therefore, it is a little useful to me. It provides a new technical scenario: Using IOS devices to operate the previous MIS

System. Is it cool? In addition to cool points, what else is there.

We hope that Embarcadero can solve an extension Problem Based on firemonkey and allow the addition of embedded lib to be simulated directly on win. (It may also be difficult, so it is not done)

The second point is that the component libraries in the Delphi ERA can be revived on iOS. Now, only the Indy TMS version supports IOS.

But it is true that it is faster to build an application, and the code written is much less than that written in xcode.

UPDATE: The trail version does not contain source \ *. Pas, that is, it does not contain source code. Naturally, the components cannot be extended.

Indy is known to support Ios. the SSL library cannot be found as soon as it is used. (The solution has been found later)