Home » Forums » PHP OpenBiz 2.X Forums » Developer Help

Migrate From 2.3 to 2.4

Submitted by jim on Thu, 01/07/2010 - 14:22.

I've got a couple of applications developed on the 2.3 version and I'm wondering what to do in terms of migrating.  2.4 is progress and leaving behind some core concepts used in 2.3 so I'm not sure if it is even possible to migrate so much as rewrite the apps.

For example, we've switched from BizForm to EasyForm along with extensive changes the underlying Metadata structure.  Also, I've got some custom tweaks to the 2.3 code base that I'll need to port.  And of course there are custom BizForm, BizDataObj classes that will also need to be ported.

The big questions is, what are you doing or planning when it comes to migrating moderatly complex 2.3 applications to 2.4?

 

-Jim

‹ Multiselect in Openbiz clear field and Database Value "onchange" ›
#1Submitted by rocky on Fri, 01/08/2010 - 18:56.

It is not trivial work to

It is not trivial work to migrate 2.3 app to 2.4. The main change is on the Form metadata. Ideally, we can develop a script to convert 2.3 BizForm to 2.4 EasyForm. It won't be hard. The differences are

  BizForm EasyForm
DisplayMode

Yes. typically 3 display modes.

Each mode has template attribute

No display mode

Template attribute is moved to Form level
Search Panel No Yes. EasyForm has new Search Panel
Data Panel (BizCtrls) 2.3 has name as "BizCtrls" 2.4 has name as "DataPanel"
Action Panel (Toolbar) 2.3 has name as "Toolbar" 2.4 has name as "ActionPanel"
NavPanel (Navbar) 2.3 has name as "Navbar" 2.4 has name as "NavPanel"
Element (Control)

2.3 has 2 elements classes

- HTMLControl.

- BizControl.

For each control, use "Type" in metadata to indicate how to render it.

In 2.4, each element is defined as a class. This gives more flexibility to write new elements.

The "Class" attribute can map to "Type" attribute in 2.3

The conversion between BizView and EasyView is much easier than the Form.

For custom Form class in 2.3, it has to be recode to extend from EasyForm. But I don't see too much change needed on the main logic.
#2Submitted by andrewseagull on Fri, 01/08/2010 - 17:40.

Jim, Back to September 2009

Jim,

Back to September 2009 I tried to migrate my OB2.2 based application to OB2.4 and I hit couple of road blocks. Due to a limitted time I was not able to finalize it :(

I would say the best way to upgrade complex applications is by minimizing amount of code changes / new additions at the time of upgrade as much as possible. The good thing is that OB2.3 BizDataObj, BizForm classes are unchaged from 2.3 and are available in 2.4. It means that whatever you developped in 2.3 should work in 2.4 without metadata changes. I believe BizView was changed and there some inconsistencies with ViewWizard class.

My plan was to upgrade what is upgradable and then start changing metadata from 2.2 to 2.4 after upgrade is completed.

Here is the list of issue I experienced during this upgrade. Most of them had resolution(s), but with some I did not have time to finish.There were a lot of OB2.4 changes/fixes after that, so I'm not sure what applies and what not at this time.

Hopefully it helped. Let me know if any questions arise.

Thanks,

Andrew