LiveCode Forums.

I posted this question in my previous thred, but I suppose is better to have it separated.

How projects are structured in Livecode?

I mean, It's suppose, every stack, with it's substacks and cards, is a project itself? (a whole application?)

How dev teams share work through internet and control locks, version, branchs, and so on?(something like CVS, SVN)

Cheers.

Hi,

You can look at

http://support.runrev.com/scriptingconf ... ucture.zip
http://support.runrev.com/scriptingconf ... rarchy.zip


Best

Jean-Marc

Hi Jean-Marc,

This clear me a lot, thanks, but, Still having the same doubts.

A large project, is composed of a Stack with substacks? or could be various stacks each with it's own substacks?

Imagine for example I will do an ERP. I must have a stack for Sales, other for Buys, Customers, and so on? or this is substacks? If so, how can I share code with other developers¿?

Thanks.

Hi gipunzi,

Yes,
Sorry, my english is poor
You can have one stack with substack and a stack can open an other stack
You can also shareg script for some stack

for that you can lock at "insert script" in the dictionary

You can post your stack in attachment to share your code

I hope this help

All the best

Jean-Marc

While it has advantages to keep everything together in a single 'project' stack, you are free to split the stacks over multiple stack files (for instance, one per module). You can then treat your 'main' stack as an entry point to all the other stacks, adding references to the other stacks in its stackFiles property. The bonus is that you'll have a collection of stacks that you can re-use over multiple projects, if you like (handy for 'library' stacks).

While LiveCode has no built-in support for CVS, SVN or other well-known version control systems, there is a tool called MagicCarpet written by the guys of Altuit, which works pretty well for this style of projects, involving only binary files.
I recall several projects to 'serialize' stacks out into XML format, which can then be stored in a traditional version control system, and then 'reassemble' them into a binary stack for development - but I'm not sure how those panned out. You could post your question on the use-livecode mailing list to see if that turns up more information.

HTH,

Jan Schenkel.

Oh, ok, thanks a lot,

I didn't noticed thath I can calls "external" stacks.

Cheers.