Source Control using stacks instead of cards

[matthellstrom]

I'm trying to figure out how to allow multiple developers to work on the same project. I don't see any source control solutions out there, so I was thinking that I may be able to use stacks instead of cards for different parts of the same application. Then, one developer could work on one stack while another worked on another stack.

I have a main screen application (desktop) with buttons across the top and down the left side. When I click on one of the buttons it will bring up a different application: Item maintenance, order entry, accounts receivable, etc. in the same window. I guess if I created different stacks and somehow kept them all the same size, I could go from one to the next.

I don't know if I'm explaining myself very well, do you understand what I mean, and is this a viable option?

[dunbarx]

Hi.

Using stacks instead of cards within a stack seems fine to me. Make sure that nobody changes the window size, not that this could not be dealt with if required, but why tempt fate? It is simple to create a single stack from the various "substacks". It is important, of course, to separate the tasks.

But wouldn't each stack developer need access to the other stacks? If I write a handler that loads a field on a remote card, it is nice to have that card available. This will no longer be the case.

Craig Newman

[matthellstrom]

I don't think I like the idea of doing it this way, I just can't see any other way that 2 people can work on the project at one time.

Most of these screens in this application are reasonably standalone, so I don't think we'll have to access another stack very often. If we do, we'll just make sure to coordinate that.

Is there any other way to do this? I haven't been able to find any source control options, because of the binary issue.

[bn]

Matt,

would it be an option to put your scripts into libraries? Mark Waddingham posted to the use-list a new feature of a text-only stack. This is just a text file that has no binaries. You can use this as library. As Mark states Livecode uses this technique for quite a lot of the IDE stacks. And they do it for exactly the reason you state: to be able to use a version control system.

http://runtime-revolution.278305.n4.nab ... l#a4691400

I have not experience with this, but maybe it is an option for the time being.

Kind regards
Bernd

[bn]

Matt,

there is also thing called lcVCS done by Monte Goulding, he translates stacks to text files

https://github.com/montegoulding/lcVCS

again, I did not use it but he also did this to use version control systems. From what I gathered it is a bit more involved than the script only stack techniques, but then he uses the whole stack.

Kind regards

Bernd

[matthellstrom]

That looks hopeful, Bernd. Thanks for the info!

[Simon]

Hi Matt,
Here is my little journey;
http://forums.livecode.com/viewtopic.php?f=8&t=24411

Simon

[MaxV]

I'm developing a simple DIFF viewer for livecode files. However I can only show what changed (properties, codes, etc.), but it doesn't merge the differences.