Re: how to create a list in easyJSON

[Matt Maier via use-livecode]

As a warning for others, fastJSON is not directly interchangeable with
easyJSON.

I'm using a big array that has a couple levels of numeric keys before you
get to the text keys. When fastJSON converts the array to JSON it throws
out the numeric keys and just turns everything into a list.

I don't think that would actually be a problem, except that in my data
structure the [0] key has important metadata in it and when fastJSON
converts back from JSON to an array it doesn't start counting at 0, so all
of the data comes back but it's offset.

At least, this is the newest version of fastJSON from github and some old
version of easyJSON that I've had around for a long time (not sure what
version it is).

On Tue, Jan 3, 2017 at 8:05 AM, Bob Sneidar 
wrote:

> Hmmm... all of this may explain why a table in a PDF fillable form breaks
> the controls out as columns, not records. So when populating an FDF file,
> my data needs to have each column in it's own variable, or else I have to
> do nested repeats to place it all correctly.
>
> Bob S
>
>
>
> ___
> 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
>
___
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

Re: I'm a stupid GIT

[Roger Eller via use-livecode]

On Jan 7, 2017 4:01 PM, "Richard Gaskin via use-livecode" <
use-livecode@lists.runrev.com> wrote:
>
> Malte Brill wrote:
>
> > I also am a stupid GIT. Way over my head. That said - can’t this be
> > somehow automated so that one could download nightly builds?
>
> While nightly builds can be a good practice for many projects, LC is
unusually complex, and requires a LOT of time to run their build system.

Would it take longer than, um... a night?

> So while most apps only need a single build for one or two platforms, LC
needs to run multiple steps across a much larger number of platforms.

I am a huge fan of automation.  I own a robotic lawnmower.  The robot takes
2 to 3 hours to cut my lawn, which I used to cut manually using a push
mower.  I don't care how much longer the robot "works" in the summer heat
because I stay inside.

> This multiplies the time so much that I would imagine it would take many
hours to build a release, making it impractical to run daily.

If it's automated, you don't run it.  It just runs.  If it fails, so what!
It provides a bleeding edge version for those who can handle some risk.

>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  
>  ambassa...@fourthworld.comhttp://www.FourthWorld.com

~Roger
___
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

Buildling Standalone for Mac on 8.1.2 - Can't Copy Icons/Resources/Inclusions

[Sannyasin Brahmanathaswami via use-livecode]

We are facing an old bug in various stacks. Some are very old stacks that have 
moved forward over time from as far back as 5.*  with standalone builder (SAB) 
settings revised along the way until we are up to Sierra and LC 8.1.2 where 
attempts to make a standalone fail due to an old bug where the standalone 
builder cannot copy icons.

to make matters more challenging SAB's  final error message cannot be save for 
pasting here.

we get a dialog with errors looking like this

241.1405,1 revCopyIcons
also errors relation to revCopyResources,revStandaloneCopyIncludes, 
revSaveAsMacStandalone

etc.

I'm only assuming that it is a problem with icons. Deleting the internal SA 
custom prop from the stack and re-saving does not help.

Meanwhile some other simple stacks *do* build without issues.  to make things 
even more mysterious. We passed a copy from a Windows machine where the SA 
build was done for Mac… on a Surface machine… andpull this down to a Mac… 
Switching to 64 bit "experimental " worked earlier the morning, and then later 
in the day, failed.

There is *no* way to debug this… any ideas?

Svasti Astu, Be Well
Brahmanathaswami
www.himalayanacademy.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

Re: I'm a stupid GIT

[Richard Gaskin via use-livecode]

Malte Brill wrote:

> I also am a stupid GIT. Way over my head. That said - can’t this be
> somehow automated so that one could download nightly builds?

While nightly builds can be a good practice for many projects, LC is 
unusually complex, and requires a LOT of time to run their build system.


In addition to compiling for desktop for Mac, Windows, and Linux, they 
also need to compile deployment engines for iOS and Android, and Server 
engines for Mac, Windows, and Linux.  All but the Server engines then 
need to be copied into each deliverable so we can deploy to all the 
platforms we enjoy with LC, and those then need to go through the tool 
that builds the installers.


So while most apps only need a single build for one or two platforms, LC 
needs to run multiple steps across a much larger number of platforms.


This multiplies the time so much that I would imagine it would take many 
hours to build a release, making it impractical to run daily.


The team makes _using_ LC so easy that we often forget that the 
behind-the-scenes work is so complex almost no other company even 
attempts to support as many platforms with this level of integrated GUI 
support.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://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

I'm a stupid GIT

[Malte Brill via use-livecode]

I also am a stupid GIT. Way over my head. That said - can’t this be somehow 
automated so that one could download nightly builds? If it could I would be 
willing to throw in a couple of Euros to make that happen (to be honest, not 
before the end of April though and most likely not enough Euros to make it 
happen alone).

Cheers,

Malte

___
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

Re: I'm a stupid GIT

[Richmond Mathewson via use-livecode]

Thank you.

On 1/7/17 7:13 pm, Richard Gaskin via use-livecode wrote:

Richmond Mathewson wrote:

> 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?

I guess that would depend on how comfortable you are in setting up the 
environment need to run the make file.


I've not done it myself so I can't advise; maybe Mark Wieder or one of 
the core team folks can offer guidance if you get stuck.


I should probably get around to setting that up myself sometime, but 
I'm a scripter at heart and do primarily UX/UI by trade, so it's been 
a low priority for me.  And with the turnaround time the team's been 
doing lately, just about every time I think I may want to set that up 
a new build is available so I haven't needed to.


I very much appreciate that the team often includes a link to the 
Github pull request in the Bugzilla report it relates to, such as this 
one Mark Waddingham included for #19045:


https://github.com/livecode/livecode/pull/5020

I've found that reading the comments at those links can help me better 
understand the scope of a change.


And when I see the Vulcan (automated test system) report "pass" I feel 
pretty confident it's gone well, such as we see there in a comment 
from two days ago:


  livecode-vulcan commented 2 days ago
:sunglasses: test success 5deb2cd
try-community-linux-x86: success
try-community-mac: success
try-community-linux-x86_64: success
try-community-emscripten: success
try-community-ios: success
try-community-win-x86: success
try-community-android-armv6: success

I also saw that and was impressed at the speed with which the team 
sorted things out; that is why I am "slavering at the chops".


Richmond.
___
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

Re: I'm a stupid GIT

[Richard Gaskin via use-livecode]

Richmond Mathewson wrote:

> 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?

I guess that would depend on how comfortable you are in setting up the 
environment need to run the make file.


I've not done it myself so I can't advise; maybe Mark Wieder or one of 
the core team folks can offer guidance if you get stuck.


I should probably get around to setting that up myself sometime, but I'm 
a scripter at heart and do primarily UX/UI by trade, so it's been a low 
priority for me.  And with the turnaround time the team's been doing 
lately, just about every time I think I may want to set that up a new 
build is available so I haven't needed to.


I very much appreciate that the team often includes a link to the Github 
pull request in the Bugzilla report it relates to, such as this one Mark 
Waddingham included for #19045:


https://github.com/livecode/livecode/pull/5020

I've found that reading the comments at those links can help me better 
understand the scope of a change.


And when I see the Vulcan (automated test system) report "pass" I feel 
pretty confident it's gone well, such as we see there in a comment from 
two days ago:


  livecode-vulcan commented 2 days ago
:sunglasses: test success 5deb2cd
try-community-linux-x86: success
try-community-mac: success
try-community-linux-x86_64: success
try-community-emscripten: success
try-community-ios: success
try-community-win-x86: success
try-community-android-armv6: success

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://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

Re: I'm a stupid GIT

[Richmond Mathewson via use-livecode]

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

Re: I'm a stupid GIT

[Richard Gaskin via use-livecode]

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?


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://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

I'm a stupid GIT

[Richmond Mathewson via use-livecode]

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.

Richmond.
___
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

Re: Subject - LiveCode - I'm not a very happy Bunny

[Richmond Mathewson via use-livecode]

I thought the theory was that getting lots of people to use the open 
source version would lead

to all sorts of benefits to LiveCode:

1. A certain proportion of O.S. users would contribute with bug reports 
and so on.


2. A certain proportion of O.S. users would, in due course, pay for a 
commercial licence when they

felt a need to protect their code from prying eyes.

However, if the "road to the isles" (how to get hold of the O.S. 
version) is hidden away down the bottom of
LiveCode's website's landing page, instead of being "right there", the 
chances of that uptake seems

minimal.

I do get the feeling that LiveCode have an ambivalent view to their 
decision to release an O.S. version;
part of which may be that points #1 and #2 have not happened with such a 
whoosh as perhaps they
had hoped. But this is a circular situation which, I believe, might get 
untangled if LiveCode shouted louder, and all and everywhere, about 
their O.S. version, as well as presenting one of those easy-to-ken charts
showing the differences between the 3 versions of LiveCode they produce 
that is easily accessible to
people who find their way (and part of the problem in "find their way" 
rather than

"have it rammed down their throats") to LiveCode's website.

I have made most of my teaching resources and sample stacks available to 
people here:


http://community.computingatschool.org.uk/door

nobody seems really interested, because they are all stuck on C++, 
Python and VB.Net. Could that
be because, if they get to the LiveCode page the first thing they see is 
an "expensive" piece of

software?

This is, to put things mildly, "an awful pity".

Richmond.

On 1/7/17 12:17 am, Tom Glod via use-livecode wrote:

gotta say... looking at livecode.com it  is very clear that livecode is
nearly hoping that people won't notice that there is an open source version
and buy a license because they didn't know any better.

shadyshady.. almost understandable, but why go open source if you
gonna pretend like you aren't?

On Wed, Jan 4, 2017 at 10:59 AM, Keith Martin  wrote:


On 4 Jan 2017, at 14:11, Richmond Mathewson wrote:

What this message should tell the people on the mother-ship is that they

need to shout a bit louder
about the Open Source version


Amen! The FOSS, Community edition is a great thing, and it's

It'd also be great if the mother ship would also consider, one day, a more
inexpensive way to step up to the level where App Store submission is
possible, perhaps as a short-term (say, 1 month?) window, bundled with
advice for efficient App Store submission? Perhaps something similar for
HTML5 publication in the future? LC is wonderful, but it is feeling more
and more like a product with a 'keep out, professionals only' label on the
virtual box... :-/

Me, I'd SO glad I got Indy in time to keep annual cost just about
affordable. I make peanuts (at most!) from what I build, but that's not the
point for me; it's just too much fun not to be part of the LC builder
community. I did once hope HTML5 would be available as part of that, but
sadly it's separate. :(

k

---

Keith Martin
Senior Lecturer, LCC (University of the Arts London)
Technical Editor, MacUser magazine (1997-2015)
http://PanoramaPhotographer.com
http://thatkeith.com
+44 (0)7909541365

---

___
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


___
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


___
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