Brian Milby wrote:
> The end goal is to enable a binary stack to have the scripts within
> tracked via GitHub. A closely related goal is to enable editing of
> said scripts via an external editor. Script only stacks are not the
> way that I want to go for these projects (they are distributed as
> stacks and used within the IDE as plugins). I've got import/export
> working and a directory watcher that will start an import when a file
> is updated. Unlike lcVCS, this does not attempt to do anything with
> tracking the other parts of the stack, just the scripts.
Ah, very cool. Thanks.
As for the inconsistent bg refs which started this thread, my first
inclination is that since consistent absolute refs are critical, any
differences in what "long ID" returns based on what card you're on (or
where you're sitting, or what day of the week it is, or other factors
that don't change the object being referred to) would be a bug, since
it's counter to the design goal of "long ID".
Was that resolved in a way that would illuminate me?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
