How can two people work on a Business Space at the same time

joselv

I am looking to get another developer license but have a question, how can two of us work on the same business space at the same time? It wont make sense for me to buy another license if we cannot work in the same project concurrently.

Is this possible?

BenHayat

I've heard it is "Possible". But after 2 years of intense work and see how the IDE's internal are so tightly integrated, it would not dare to have it expose to more than one person. Heck, sometime I change some process or rule name somewhere and all hell break loose. For example we have areas to insert rule for "applicability or visibility or availability" and some other changes in attribute name or rules are not seen by this areas and suddenly your app is not working correctly anymore. And that's just me changing it and still I can screw it up. Imagine two people.

The best way would be if each developer is working on two separate modules sharing same DB and rules and both developers communicate very closely when changes are being made to DB.
The hardest part is to merge the two BSVs to make one final one that combines both modules.

Do some testing first. Create two Business Space, do some work in each and then see if you can export/import to merge them.

joselv

That is what I was afraid of. 🙁

That presents some challenges if I want to have more than one person working on the same project.

Support, could you offer some advice, tips, steps to accomplish this? I like the idea of containerizing aspects of the project and then combining them but it would be nice to get more detail on feasibility.

BenHayat

joselv wrote
That is what I was afraid of. 🙁

That presents some challenges if I want to have more than one person working on the same project.

Support, could you offer some advice, tips, steps to accomplish this? I like the idea of containerizing aspects of the project and then combining them but it would be nice to get more detail on feasibility.

Generally, team work on a product like Aware (that is very interconnected) is very difficult to pull off. Even products like VS that work with individual source code files have had many challenges. And you could easily wipe out someone's work if you were not careful.

My suggestion is, before you ask support for tips and suggestion, first lay out "HOW" you plan to do team development, what's your expectations? There are many ways to skin the cat, but first specify your exact goals, then perhaps they can give you tips for "that" goal.
Just my two cents.

customaware

Jose,

I would have no problem doing it with one absolutely I breakable caveat.

Create ALL BOs, Main, References and Main Forms first and forbid either developer from making ANY changes to
ANY of them.

Then each work from the standpoint of mini tasks such as Queries, Processes, Documents using the locked BO set.

The Gateakeeper developer then cuts and pastes each mini task into the control business space.

If done properly it can very efficient and done safely.

So, no true multi developer capability but workable.

joselv

Ben,

Good advice. I will put some thought into that.

Mark,

I agree, that is along the tact that I was thinking. It seems that it should be straightforward (with a disciplined team) to keeping a control BSV with the database setup and adding 'modules' to it later.

I'm gonna explore this idea.

tford

Jose,

I would have no problem doing it with one absolutely I breakable caveat.

Create ALL BOs, Main, References and Main Forms first and forbid either developer from making ANY changes to
ANY of them.

Then each work from the standpoint of mini tasks such as Queries, Processes, Documents using the locked BO set.

The Gateakeeper developer then cuts and pastes each mini task into the control business space.

If done properly it can very efficient and done safely.

So, no true multi developer capability but workable.
Cheers,
Mark

Excellent advice, Mark!

BLOMASKY

I would do it with a slightly diff. focus that Mark suggested

One of the developers is the Master. The other one is the (mmm, lets see, slave is the wrong word, sub-master, sounds confusing... mmm,) NOT the master.

The Master can do whatever he wants to do as far as adding / changing the BO's. This will NOT affect what the other(s) are doing. Obviously the others will have defined tasks (like, you work on these 3 queries, on this VP, etc.) If they need any changes made to the BO's / Relationships, new fields added to RegularUser (which I seem to do constantly), they will convey the request to the Master).

Then, the subs BSV is imported into a NEW application on the Master's system, and Queries, processes, forms are copied over. Should be easy - peasy

Bruce

(oh yea, with a backup BEFORE you ever attempt to merge any of the applications... Lots of backups!)

BLOMASKY

It's easy to copy a form between applications, why do you want to restrict anyone else from working on forms (which, for me, take the most time, since I am always testing them, moving things a pixel left or right, testing again, etc. etc.) If Aware had an accurate visual form designer, I think my applications could be built in 1/2 the total time. Queries take only minutes to write and design. Complicated forms can take hours... blaaahhhh

Bruce

customaware

I agree regarding additional Forms Bruce but I would think best not to have additional Devs working or or changing Main From

baskosi

Since there is an export of BSVs to XML, you could use GitHub (or git) to merge the changes from different developers. Then import the merged XML to a "master" BSV that is used for testing.

Basically this is a flow that most teams that work on source code files are using nowadays.

If one large XML is too long, you (or AwareSoft) could prepare a tool to split it into one file per object. This way there is less chance that both developers changed the same small XML. There would also need to be a tool to merge all the small XML files before importing them into AwareIM.

Jose: "Aware IM Developer Edition covers up to 10 developers."