Possible to merge the iOS and Android DPF projects?

[Paul]

I was wondering why the DPF Android and DPF iOS are separate projects. Merging them would have several advantages:

1) Only one set of DPF native components to download and install.
2) Easier to manage the project. Only one set of ancillary files (e.g. readme etc) needs to be maintained.
3) Only one Sourceforge project to manage.
4) Possible to share common classes between the native component types.
5) When Embarcadero introduce additional platforms we can simply add additional components to the same project.
6) May increase the usage of both Android and iOS components.

Just my opinion of course. There may be very valid reasons to keep them separate.

Cheers,
Paul

[Diego]

Android and IOS are very different OS, So achieve that would be almost impossible.

Both components have different properties for each SDK, and different features and you would need millions of {IFDEFS} in the source.

[Paul]

Hi Diego,

I'm not talking about merging the components, just merging the projects. I know it is virtually impossible to produce a single native Delphi component of any complexity that will work on both Android and iOS. I'm pretty sure though that there are areas of common functionality and classes that can be used for both sets of components.

I just think it would be easier to manage, maintain, develop and promote D.P.F. if everything was located within a single project instead of being split into two. And in the future possibly three, four, five different native component projects, depending on how Delphi develops.