Re: externalPackages

2014-08-13 Thread JB
This will be a fantastic improvement. John Balgenorth On Aug 13, 2014, at 3:46 PM, Björnke von Gierke wrote: > Richard is wrong. The goal is to be able to use any language, including > anything that is available for the separate OS-es. However, there'll be a > meta-LC like language, that is

Re: externalPackages

2014-08-13 Thread JB
I just watched the widget video and it sounds really great. The video like all of their videos was well done too. It sounds like Kevin wants more people developing externals and that is good. Balgenorth On Aug 13, 2014, at 3:25 PM, Richard Gaskin wrote: > JB wrote: > > > Changing the subjec

Re: externalPackages

2014-08-13 Thread Richard Gaskin
Björnke von Gierke wrote: > On 14 Aug 2014, at 01:12, Richard Gaskin wrote: > >> > Richard is wrong. The goal is to be able to use any language, >> > including anything that is available for the separate OS-es. >> >> Well, it certainly wouldn't be the first time I was wrong. But >> given that th

Re: externalPackages

2014-08-13 Thread Björnke von Gierke
On 14 Aug 2014, at 01:12, Richard Gaskin wrote: > > Richard is wrong. The goal is to be able to use any language, > > including anything that is available for the separate OS-es. > > Well, it certainly wouldn't be the first time I was wrong. But given that > the engine is currently written in

Re: externalPackages

2014-08-13 Thread Richard Gaskin
Björnke von Gierke wrote: > Richard is wrong. The goal is to be able to use any language, > including anything that is available for the separate OS-es. Well, it certainly wouldn't be the first time I was wrong. But given that the engine is currently written in C++ and much of the code is pla

Re: externalPackages

2014-08-13 Thread Björnke von Gierke
Richard is wrong. The goal is to be able to use any language, including anything that is available for the separate OS-es. However, there'll be a meta-LC like language, that is not quite LC, but similar-ish, which will allow to write externals too. The Idea is that it's similar enough for more p

Re: externalPackages

2014-08-13 Thread Richard Gaskin
JB wrote: > Changing the subject a little bit you mentioned > LiveCode is going to improve things so you can > actually do more external type code from within > LiveCode. Are they going to be using Apples new > programming language Swift at all? I don't think so. Swift is a very interesting la

Re: externalPackages

2014-08-13 Thread JB
I see your point. Changing the subject a little bit you mentioned LiveCode is going to improve things so you can actually do more external type code from within LiveCode. Are they going to be using Apples new programming language Swift at all? John Balgenorth On Aug 13, 2014, at 2:10 PM, Richa

Re: externalPackages

2014-08-13 Thread Richard Gaskin
JB wrote: I am surprised that as long as LiveCode has been around there are not more externals available. If you have developed externals for LiveCode why not sell them like was done for HyperCard? I don't need 'em. As I wrote earlier: ...aside from the database externals included with LC

Re: externalPackages

2014-08-13 Thread JB
Thanks for the info. I don’t really need any of them I was just trying to use them if it was possible. Your information shows it is not possible and therefore I won’t waste my time on it. I am surprised that as long as LiveCode has been around there are not more externals available. If you have

Re: externalPackages

2014-08-13 Thread Richard Gaskin
JB wrote: Since you come from a SuperCard background could you answer a question for me? I am a registered owner of SuperCard 4.6 and SuperEdit 4.6. The Xtend section allows you to export externals. I contacted SuperCard Support and they said I could use the SuperCard externals in other program

Re: externalPackages

2014-08-13 Thread JB
Hi Richard, Since you come from a SuperCard background could you answer a question for me? I am a registered owner of SuperCard 4.6 and SuperEdit 4.6. The Xtend section allows you to export externals. I contacted SuperCard Support and they said I could use the SuperCard externals in other progra

Re: externalPackages

2014-08-13 Thread Richard Gaskin
Trevor DeVore wrote: > If the externals property is pointing to the property external file on > disk, you can make sure the "destroyWindow" property of the stack is > set to true, close the stack, and then open it again. This will > attempt to reload the external. That's a helpful tip and I appre

Re: externalPackages

2014-08-12 Thread Trevor DeVore
On Sun, Aug 10, 2014 at 11:06 PM, JB wrote: > I created a button and put the following script into it. > > on mouseUp > put the externalPackages of stack "rnahelloTest" into fld id 1004 > end mouseUp > > What happens is it sets my field to empty. > I was th

externalPackages

2014-08-10 Thread JB
I built a external using the external examples and have created the stack and installed the external. Everything works and now I want to see the externalPackages of my stack. I created a button and put the following script into it. on mouseUp put the externalPackages of stack "rnahell

Re: AW: which Externals show up in the externalPackages?

2012-08-15 Thread Mark Schonewille
Jacque, It depends on what you mean by "instant". I believe one still had to start using the stack containing the external resources if one wanted to call the external from another stack. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://eco

Re: AW: which Externals show up in the externalPackages?

2012-08-15 Thread J. Landman Gay
On 8/15/12 10:29 AM, Richard Gaskin wrote: I believe this is another area SuperCard got right: you import an external into your stack file (what that tool calls a "project" file), and that's it. You never need to think about them again. From that point forward they're immediately and always a

Re: AW: which Externals show up in the externalPackages?

2012-08-15 Thread Richard Gaskin
Mark Schonewille wrote: > In standalones, there is a stack "revExternalsLibrary" of your > mainstack, which has all externals attached to it. AFAIK this > only applies to the default externals. You need to attach > customer externals to your own mainstack. No, I don't think > this is straighforwa

Re: AW: which Externals show up in the externalPackages?

2012-08-15 Thread Mark Schonewille
instack" in > the standalone there doesn't show up all externals. > > Is it straight forward to differentiate between the development environment > and standalone where to ask for the externals? > And what does an external force to show up

AW: which Externals show up in the externalPackages?

2012-08-15 Thread Tiemo Hollmann TB
ween the development environment and standalone where to ask for the externals? And what does an external force to show up at all in the externalPackages of "myMainstack"? Tiemo > -Ursprüngliche Nachricht- > Von: use-livecode-boun...@lists.runrev.com [mailto:use-livecode- > b

AW: which Externals show up in the externalPackages?

2012-08-15 Thread Tiemo Hollmann TB
eCode > Betreff: Re: which Externals show up in the externalPackages? > > Tiemo, > > Try: put the externalPackages of stack "Home" > > -- > Best regards, > > Mark Schonewille > > Economy-x-Talk Consulting and Software Engineering > H

Re: which Externals show up in the externalPackages?

2012-08-15 Thread Mark Schonewille
Tiemo, Try: put the externalPackages of stack "Home" -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 Economy-x-Talk is looking for an amateur painter/

which Externals show up in the externalPackages?

2012-08-15 Thread Tiemo Hollmann TB
work, BUT when asking for the externalPackages of stack "myMainStack" it is empty. After copying all three externals into the Runrev program\externals folder at C:\Program Files\RunRev\LiveCode 4.6.4\Externals one of the three externals shows up in the externalPackages. And creating