LiveCode Forums

Oh I'm enjoying the difference already - we've had a few little 'eh?' moments in the office (particularly with git submodules) but stackoverflow has always come to the rescue in a timely fashion

We're starting an abbreviated 6.0.1 maintenance cycle today to clean up a few issues from the first 6.0 community build. I'm hoping this branch will start to appear today - the compiling with newer versions of Xcode is on the list to include. We could potentially use gcc-llvm-4.2 rather than just gc...

Yes - there are a few niggling issues when compiling against > 10.4 and gcc 4.2 - mainly to do with newer versions of the openssl libraries present in 10.5 and above. 3.2.6 will happily run on newer Mac versions - installing it is the issue - we just copy it across from a Snow Leopard machine onto n...

Essentially yes - maintanance forks from each stable point on master and is used to ensure all the maintainance patches don't break anything. When stable it merges back into master as something like 6.0.1 tag, then branches again for 6.0.2. Yes - fork 'master' for now, we've got a bunch of changes w...

We do need to make testing out standalone changes a bit easier - we can tweak the SB to do this (so it picks up the binaries from the _build folder within the repo, overriding My LiveCode or the IDE Runtime folder). In the meantime though a couple of things: 1) You can't use standalone engines built...

Looks like you've figured out how to add functions :) Stepping back a bit there's a couple of things to consider here: 1) Are there any use-cases beyond lcVCS that make resolveImage() useful? 3) Is the usefulness of this function restricted to actions the IDE takes (e.g. for VCS integration), or are...

It will be something like JavaDoc :) At the moment the problem is that things like commands exec functions contain code for all the different commands that start with the same word. Functions tend not to be overloaded in this way so it would work okay for those. The refactoring project solves this b...

Welcome to our world - don't get scared, think of it as a challenge :) The engine source-code is quite opaque until you start to get your head around how it all works - although this can take some time (I've been working with it for nigh on 10 years...). In terms of docs - then we are working on doi...

This might be a result of docs that need refinement so your comments help - the model I have in my head is precisely what you suggest. Indeed, the flow is (essentially) git-flow with a facility for fixed frequency maintenance releases. The 'master' branch will only ever contain commits (and tags) fo...

Thanks for the heads up - this is on the list to resolve.

Unfortunately Apple do not make it easy to build an application that supports the wide range of Mac platform versions we do. We haven't yet pulled the plug on 10.4 support (we've just said we intend to in a near term version - the Cocoa transition will probably force this, there's been no code reaso...

I've put this on the list to look into - thanks for the heads up.

The _IREVIAM define is used to optional include the remote debugging service that is used by the on-rev server engine on the on-rev hosting. The source to those components hasn't been released yet but will be in due course