Um, a broad "thang" . . . I've never measured one myself.
How about an impatient chap whose GANTT chart of his 4th SDLC has been
completely thrown out of
kilter owing to a bug (19045) in existing builds of LiveCode, knowing
that that bug has been sorted
out but that the next official RC build is waiting on at least another 4
bugs being sorted out . . .
Am I daft to want to try to build an unofficial "8.1.2 and a half" to
see if the bug has really been sorted
out, or would I be more sensible to "bite down hard" and hang on for an
official build?
IFF I know that everything with respect to that bug has been sorted out
I can continue coding (I have about
2000 lines to get in place prior to a build); if it has not I don't
really feel inclined to go ahead with those lines
of code to find that I have to re-do or undo them all over again.
Probably discretion is the better part of valour . . . but . . .
Richmond.
On 1/7/17 5:23 pm, Richard Gaskin via use-livecode wrote:
Richmond Mathewson wrote:
> I would be extremely grateful if someone in the know could post
> a recipe for simple souls like myself to build a LiveCode "thang" from
> github.
"Thang" is very broad. Stack? External? Engine? What do you want
to build?
_______________________________________________
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
