Team development solution

[Bob Sneidar]

A versioning solution having the stack as the atomic unit is fairly useless for a large application like an accounting app for instance. I can conceive of a web based solution that could handle this, taking a stack on the server, adding handlers for managing versioning in a frontscript, and then allowing devs to download a copy to work with. Any attempt to edit a script for example would trigger a handler that would call back to the server and "lock" the object so subsequent users would be locked out, or at least given read only access until the object was unlocked. You could unlock on save, or else have a control interface that posted the changes. 

It would be really complicated to build something like this and until there is a real demand for it, I don't think it would be profitable. 

Bob


On Aug 27, 2012, at 2:48 PM, Peter Haworth wrote:

> The "stack file as atomic unit" always seems to be the sticking point when
> this comes up.  I imagine in a large application with multiple developers,
> you might very well have a need for them to work individually on different
> stacks within a stack file, either on the layout or the script.  I'm
> definitely not a git expert but isn't the point of it the ability to check
> out/in individual modules within a project?  Or maybe glx2/git deal with
> individual scripts?
> Pete
> lcSQL Software <http://www.lcsql.com>
> 
> 
> 
> On Mon, Aug 27, 2012 at 1:47 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:
> 
>> As Andre points out, if you can get by with the monolithic stack structure
>> as
>> your atomic unit
>> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode