+1
On Mar 8, 2017 7:42 PM, "Andre Garzia via use-livecode" <
use-livecode@lists.runrev.com> wrote:
> On Mon, Mar 6, 2017 at 5:12 PM, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Besides, this is not
> > debugging, this is remote debugging, and if anything screams "
On Mon, Mar 6, 2017 at 5:12 PM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Besides, this is not
> debugging, this is remote debugging, and if anything screams "premium",
> it's a feature like this. Anyone who has been building for mobile since we
> could do that with L
Richmond Mathewson wrote:
> One of the points that might be brought up at this point is that
> LiveCode in presented as a complete programming language/packet
> in itself; there is no indication given that users of LiveCode
> are expected to know other, lower-level languages too.
>
> I suspect th
One of the points that might be brought up at this point is that
LiveCode in presented as a complete
programming language/packet in itself; there is no indication given that
users of LiveCode are expected
to know other, lower-level languages too.
I suspect that a very high proportion of people
Andre Garzia wrote:
> The fact that these decisions are being taken, where the HQ appears
> to be focusing more and more on business licensees feels like I am
> being forced into such license. At this moment, I am starting to
> wonder if there is any reason to be indy at all.
...or Community.
F
You can't build ios with community, so that's moot. Besides, this is not
debugging, this is remote debugging, and if anything screams "premium",
it's a feature like this. Anyone who has been building for mobile since we
could do that with LC has been working with their own personal debugging
hack
On Thu, Feb 23, 2017 at 5:41 PM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:
> - Implementation of a remote debugger (Business only):
> Run a standalone for the local platform from the IDE and debug it whilst it
> runs locally
> Run a standalone for iOS or Android f
oh baby i just read the blog on the profiler. I am going to have fun with
this, too.
On Fri, Feb 24, 2017 at 12:27 PM, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> panagiotis merakos wrote:
>
> > http://quality.livecode.com/show_bug.cgi?id=19248
>
> Unfortunate to se
panagiotis merakos wrote:
> http://quality.livecode.com/show_bug.cgi?id=19248
Unfortunate to see complication after complication pile up from the
IDE's insistence that stacks with the same name should not be in memory
at the same time.
As we've discussed earlier, the engine does not appear t
Trevor, I've said it before and I'll say it again. You are da bomb! :-)
Bob S
> On Feb 24, 2017, at 09:18 , Trevor DeVore via use-livecode
> wrote:
>
> On Fri, Feb 24, 2017 at 11:00 AM, panagiotis merakos via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> If you want, you can ap
On Fri, Feb 24, 2017 at 11:00 AM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:
> If you want, you can apply those changes locally:
>
> https://github.com/livecode/livecode/pull/5180/files
>
> and see if the problem is fixed.
>
I have a stack that will install the st
If you want, you can apply those changes locally:
https://github.com/livecode/livecode/pull/5180/files
and see if the problem is fixed.
1. Type in the msg box "edit the script of stack revsaveasstandalone"
2. Make those changes
3. Make sure you click on the "Apply" button
4. Try to create a stan
Bob you are probably affected by this bug:
http://quality.livecode.com/show_bug.cgi?id=19248
This will be fixed in 8.1.4 RC-1 (thanks to Trevor who identified the cause
and submitted a pull request)
Best,
Panos
--
On Fri, Feb 24, 2017 at 3:41 PM, Bob Sneidar via use-livecode <
use-livecode@list
That would be it, although I do not use any behaviors, except for data grids.
Bob S
> On Feb 24, 2017, at 08:13 , panagiotis merakos via use-livecode
> wrote:
>
> Bob you are probably affected by this bug:
>
> http://quality.livecode.com/show_bug.cgi?id=19248
>
> This will be fixed in 8.1.
That is interesting because I am still struggling with a bug
http://quality.livecode.com/show_bug.cgi?id=19322 where compiling to more than
one OS from a splash stack and with stack files seems to "corrupt" (I use the
term loosely) the mainstack where the libraries have been added to the list of
I like the way these tracks are going. This is a very sensible and logical
way to progress. The cool new dangerous toys go into the newest version,
and the sensible stuff goes into both.
On Fri, Feb 24, 2017 at 5:07 AM, Ali Lloyd via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Richmo
Richmond,
In general that is the case, yes. When for example 8.1.3 GM has been
released, we merge the branches all the way up so that the develop branch
(from which DPs are released) contains everything from that branch. In some
cases there may be things that are in earlier releases but not in a DP
Apart from all the other changes, Its great to see Android getting some
updates and attention.
A big well done to the team!
-
Andy Piddock
My software never has bugs. It just develops random features.
TinyIDE a Free alternative minimalist IDE Plugin for LiveCode
TinyIDE
Script edito
I wish I could understand the way different "levels" come out
concurrently. Are we to assume
that all the new things in 8.1.3 are also bound into 9.0.0 DP-5?
Richmond.
On 2/23/17 10:41 pm, panagiotis merakos via use-livecode wrote:
Dear list members,
We are pleased to announce the release of
Sannyasin Brahmanathaswami wrote:
> @Richard who wrote:
>
> "for deployment -- most recent stable…"
> "for dev -- most recent build, know current state of engine as
> pertains to your work."
>
> How logical! thanks… assuming there is no change in file format and
> stacks are backward compatible,
@ Bob (who wrote)
" Do you suggest that all development and improvement for version 8 and that
we all wait for certain bugs to be addressed in the next major release? That
would be unfortunate. Already since the earlier versions of 8, there have been
marked improvements and bug fixes, such a
Probably a typo, but shouldn't the backslash be INSIDE the quotes in the
example for Specifying local host and port when opening a socket?
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscr
> On 24 Feb 2017, at 9:42 am, Mike Kerner via use-livecode
> wrote:
>
> Another question: Does the mobile have to be tethered to the desktop? If
> I build a standalone, how are we going to communicate?
They communicate via sockets so no it doesn’t need to be tethered.
Cheers
Monte
LC Team,
Congratulations and many thanks for this feature-packed release.
Brilliant!
Jim Lambert
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http
Sannyasin Brahmanathaswami wrote:
> Why even continue in 8.* ?
>
> What issues are there with 9.* that would make it advisable not to
> try it for production?
For deployment it's usually best to use the most recent Stable build.
But for development it's usually best to use the most recent bui
I'm drooling. I once told Kevin that about half of the lines of code in my
mobile apps wind up being debugging code (granted the end up being
commented out, eventually, but I digress). The biggest issue on mobile has
always been debugging. I even have a debugging library that I have added
to all
Another question: Does the mobile have to be tethered to the desktop? If
I build a standalone, how are we going to communicate?
Did you guys also see that we will have a regular message box context with
the app? That's just one less thing I have to include with my stack (and
then use the mobile
First of all this is a Developer Preview. Note the, "This is not a stable
release" disclaimer. Consider also that some may be unwilling to move to
version 9 until such a time as they feel confident that most of the issues have
been shaken out of it. I am one of these.
Do you suggest that all d
I'm behind here in the overview:
Why even continue in 8.* ?
What issues are there with 9.* that would make it advisable not to try it for
production?
BR
On 2/23/17, 10:41 AM, "use-livecode on behalf of panagiotis merakos via
use-livecode" wrote:
Dear list members,
We are p
29 matches
Mail list logo