Android Question Switching to P4XPages [SOLVED]

[AHilberink]

You should also switch to B4XPages.

Is there a Step-by-step manual of switching a B4A app to B4XPages? I read Klaus was making one, but cannot find it.
My App is big, will it be easy or will it take a lot of time?

Kind regards,
André

 

[Erel]

I recommend you to:

1. Learn a bit about B4XPages in a separate project. Download a few examples and see that you understand them.
2. Create a new project and start by moving each activity code to a new B4XPages class.

The interaction between modules is different (much simpler).

 

[udg]

My App is big, will it be easy or will it take a lot of time?

In general, it will be easy. It largely depends on how many B4X (opposed to platform-specific) components you used in your original project.
I converted a large and complex sw in almost no time. It started as a Windows-only B4J sw and now I can run it on Android as well.
Most of the conversion time went to UI elements (adapting PC layouts to Android/tablet), but more than 80% of code (maybe more) remained untouched.

Take some time to study the B4xPages paradigm and everything will be easier than you can imagine.

 

[klaus]

I read Klaus was making one, but cannot find it.

It is in the B4XPages Cross-platform projects booklet.
You can download all the booklets or read them online.
More specific chapter 9 B4XPages version of SecondProgram.

 

[AHilberink]

It is in the B4XPages Cross-platform projects booklet.
You can download all the booklets or read them online.
More specific chapter 9 B4XPages version of SecondProgram.

Thanks a lot!!

 

[Erel]

It largely depends on how many B4X (opposed to platform-specific) components you used in your original project.

That's not exactly true. You can keep the platform specific code and still use B4XPages.

 

[udg]

That's not exactly true. You can keep the platform specific code and still use B4XPages.

Sure. I was replying about the time taken and the effort required.
IMHO, taking some time to port platform-specific code to B4X multi-platform is a very low price to pay in order to have our code aligned to the direction taken by the language itself, even if we don't plan to use more the one platform. It's kind of "standardization" (which buys you easier maintenance, among other things).

 

[Erel]

IMHO, taking some time to port platform-specific code to B4X multi-platform is a very low price to pay in order to have our code aligned to the direction taken by the language itself, even if we don't plan to use more the one platform. It's kind of "standardization" (which buys you easier maintenance, among other things).

I completely agree. As this topic (B4XPages, B4XViews, XUI, etc.) can cause confusion, I wanted to clarify it.