Re: some thoughts on version 9.0.0

[Monte Goulding via use-livecode]

> On 20 Apr 2018, at 2:27 pm, J. Landman Gay via use-livecode 
>  wrote:
> 
> Another disadvantage is that you can't debug them remotely, which for some 
> projects means you can't debug remotely at all.

You can use the breakpoint command can’t you? There is a general issue here 
that we have in the past stuffed things like breakpoints and last selection etc 
into the custom properties of objects but really they should be separate. It’s 
probably a big project to sort that out though!

Cheers

Monte
___
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: some thoughts on version 9.0.0

[J. Landman Gay via use-livecode]

On 4/19/18 10:41 PM, James At The Hale via use-livecode wrote:

One downer I have noticed with the advent of behaviors being in script only 
stacks is you lose the ability to edit them when you click on the behavior 
badge.


Another disadvantage is that you can't debug them remotely, which for 
some projects means you can't debug remotely at all.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: some thoughts on version 9.0.0

[Monte Goulding via use-livecode]

> On 20 Apr 2018, at 1:41 pm, James At The Hale via use-livecode 
>  wrote:
> 
> One downer I have noticed with the advent of behaviors being in script only 
> stacks is you lose the ability to edit them when you click on the behavior 
> badge.
> 
> If the behavior resides in a button, as before, all is well.

That sounds like a bug which we can fix. Could you report it.
> 
> Recently while looking into something with the data grid I noticed all the 
> behavior badges open an empty script window. It seems all the behaviors that 
> were contained in these buttons (that reside in the revDataGridLibrary) now 
> reside in script only stacks that are chained to the buttons.

Yes, we used the scriptifier on the datagrid to make it more maintainable. As a 
result the buttons on the revDataGridLibrary stack which used to be the 
behaviors now have behaviors themselves. One advantage to this is any image 
references will still be resolved correctly.

Cheers

Monte
___
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: some thoughts on version 9.0.0

[James At The Hale via use-livecode]

One downer I have noticed with the advent of behaviors being in script only 
stacks is you lose the ability to edit them when you click on the behavior 
badge.

If the behavior resides in a button, as before, all is well.

Recently while looking into something with the data grid I noticed all the 
behavior badges open an empty script window. It seems all the behaviors that 
were contained in these buttons (that reside in the revDataGridLibrary) now 
reside in script only stacks that are chained to the buttons.

James

___
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: Contributing to the IDE

[Monte Goulding via use-livecode]

I also just remembered that much of the information that you may find helpful 
is in the contributing to docs page which you may not have read if your 
interest is in source contributions. 
https://github.com/livecode/livecode/blob/develop/docs/contributing_to_docs.md 


I’m thinking we would do well to reorganise this doc by moving the docs style 
stuff to the docs style guide and the rest into a more general (not just about 
docs) your first PR doc.

> On 20 Apr 2018, at 12:39 pm, Monte Goulding via use-livecode 
>  wrote:
> 
> Hmm… OK Geoff, sorry for being flippant and causing a rant!

___
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: Contributing to the IDE

[Brian Milby via use-livecode]

I will add that building from source is not that hard for Mac or Linux
(have not tried Windows). I didn’t know what platform you were using which
is why I referenced the Readme since it had a section with links for each
one.

If you run into specific issues getting things set up then we can probably
help.
On Thu, Apr 19, 2018 at 9:40 PM Monte Goulding via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hmm… OK Geoff, sorry for being flippant and causing a rant!
>
> I must admit I don’t know anything about GitKracken. I used to use
> SourceTree which I found quite reasonable, however, once working for the LC
> team I found it too slow and hard to do some of the more complicated things
> like interactive rebasing so I moved to command line.
>
> > None of it comes close to describing the steps necessary to set up on my
> computer to contribute.
>
> The issue I think you are bumping in to is you only really want to
> contribute to the IDE, however, to do so you really need to build livecode
> from source so you can work on the IDE directly in the respository. Because
> of that the notes linked in the README.md about building LC on different
> platforms under the section `Detailed instructions` are really what you are
> looking for. https://github.com/livecode/livecode#detailed-instructions <
> https://github.com/livecode/livecode#detailed-instructions>
> >
> > it offers nothing useful to figuring out how to set up to contribute.
>
> Yes it does. See above ^.
> >
> > I ran into this same problem when I started to put Navigator into
> GitHub: the GitHub documentation is absolutely abysmal. In that instance,
> the blame lies with literally everyone associated with Git and GitHub, but
> in the case of wanting to contribute to the LC IDE, the buck stops with the
> LC crew. I have asked others who are decades-long LC developers for
> guidance, and found that they don't understand how to contribute. That
> holds back development of LC and the IDE.
>
> OK, well we’d like to do better in this regard, however, we do tend to run
> into the problem that a large chunk of our experienced LC developers have
> no interest in reading about git or github. The very best thing you can do
> before anything else is understand git. There is bucket loads of freely
> available information online. This is a great free book
> https://git-scm.com/book/en/v2 
> >
> > To be clear: reasonable documentation for contributing to the IDE would
> include a section something like:
> >
> > 1. Create an account on GitHub. Follow the guidelines mentioned
> elsewhere in this documentation.
>
> OK, this has presumably been seen as assumed knowledge til now… and/or
> GitHub’s responsibility do document how to use GitHub. I’m sure we can add
> something though!
>
> > 2. (optional) Install the graphic Git client of your choice (a list of
> possibilities is included at the bottom of this documentation).
>
> The problem here is there are lots of graphic git clients. All look
> different. Ali has spent quite some time documenting how to contribute via
> GitHub’s web interface.
>
> > 3. Determine which version of LC you want to contribute to. Note that
> only contributions to  are being accepted at present.
>
> See
> https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md#branches-in-github
> <
> https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md#branches-in-github
> >
> > 4. Clone the repository for the LC version you have selected to your
> local drive.
>
> Yes, I agree there’s some missing bits here on forking on github, cloning
> and setting up the clone. I can give command line instructions and or write
> a script for you to run.
>
> Basically we use multiple repositories to build LiveCode. Ignoring the
> commercial repositories that only the team have access to the structure is:
>
> livecode
>ide -> livecode-ide
>thirdparty -> livecode-thirdparty
>
> Most of the ide stacks are in the livecode-ide repository, however, there
> are some in the ide-support folder of the livecode repository and we are
> gradually moving as many modular libraries as possible to the
> extensions/script-libraries folder of the livecode repository.
>
> The thirdparty repository is something that anyone outside the team is
> unlikely to need to patch so we can ignore that for now.
>
> So to work on the ide you really need to fork both
> https://github.com/livecode/livecode 
> and https://github.com/livecode/livecode-ide <
> https://github.com/livecode/livecode-ide>
>
> From there you need to do the equivalent of the following in your git
> client:
>
> git clone —recursive https://github.com//livecode.git
> 
>
> This is basically downloading the source folder and it’s history into a
> folder named livecode.
>
> Once that is complete then there are a few changes to make to get setup:
>
> cd livecode
> git remote 

Re: Contributing to the IDE

[Monte Goulding via use-livecode]

Hmm… OK Geoff, sorry for being flippant and causing a rant!

I must admit I don’t know anything about GitKracken. I used to use SourceTree 
which I found quite reasonable, however, once working for the LC team I found 
it too slow and hard to do some of the more complicated things like interactive 
rebasing so I moved to command line.

> None of it comes close to describing the steps necessary to set up on my 
> computer to contribute.

The issue I think you are bumping in to is you only really want to contribute 
to the IDE, however, to do so you really need to build livecode from source so 
you can work on the IDE directly in the respository. Because of that the notes 
linked in the README.md about building LC on different platforms under the 
section `Detailed instructions` are really what you are looking for. 
https://github.com/livecode/livecode#detailed-instructions 

> 
> it offers nothing useful to figuring out how to set up to contribute.

Yes it does. See above ^.
> 
> I ran into this same problem when I started to put Navigator into GitHub: the 
> GitHub documentation is absolutely abysmal. In that instance, the blame lies 
> with literally everyone associated with Git and GitHub, but in the case of 
> wanting to contribute to the LC IDE, the buck stops with the LC crew. I have 
> asked others who are decades-long LC developers for guidance, and found that 
> they don't understand how to contribute. That holds back development of LC 
> and the IDE.

OK, well we’d like to do better in this regard, however, we do tend to run into 
the problem that a large chunk of our experienced LC developers have no 
interest in reading about git or github. The very best thing you can do before 
anything else is understand git. There is bucket loads of freely available 
information online. This is a great free book https://git-scm.com/book/en/v2 

> 
> To be clear: reasonable documentation for contributing to the IDE would 
> include a section something like:
> 
> 1. Create an account on GitHub. Follow the guidelines mentioned elsewhere in 
> this documentation.

OK, this has presumably been seen as assumed knowledge til now… and/or GitHub’s 
responsibility do document how to use GitHub. I’m sure we can add something 
though!

> 2. (optional) Install the graphic Git client of your choice (a list of 
> possibilities is included at the bottom of this documentation).

The problem here is there are lots of graphic git clients. All look different. 
Ali has spent quite some time documenting how to contribute via GitHub’s web 
interface.

> 3. Determine which version of LC you want to contribute to. Note that only 
> contributions to  are being accepted at present.

See 
https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md#branches-in-github
 

> 4. Clone the repository for the LC version you have selected to your local 
> drive.

Yes, I agree there’s some missing bits here on forking on github, cloning and 
setting up the clone. I can give command line instructions and or write a 
script for you to run.

Basically we use multiple repositories to build LiveCode. Ignoring the 
commercial repositories that only the team have access to the structure is:

livecode
   ide -> livecode-ide
   thirdparty -> livecode-thirdparty

Most of the ide stacks are in the livecode-ide repository, however, there are 
some in the ide-support folder of the livecode repository and we are gradually 
moving as many modular libraries as possible to the extensions/script-libraries 
folder of the livecode repository.

The thirdparty repository is something that anyone outside the team is unlikely 
to need to patch so we can ignore that for now.

So to work on the ide you really need to fork both 
https://github.com/livecode/livecode  and 
https://github.com/livecode/livecode-ide 


From there you need to do the equivalent of the following in your git client:

git clone —recursive https://github.com//livecode.git 


This is basically downloading the source folder and it’s history into a folder 
named livecode.

Once that is complete then there are a few changes to make to get setup:

cd livecode
git remote add upstream https://github.com/livecode/livecode.git 

cd ide
git remote rename origin upstream
git remote add origin https://github.com//livecode.git 
 
/livecode.git

Now you are ready to follow the configure and build instructions for your 
platform. If you are on mac you can build and run directly from Xcode, edit IDE 
stacks, save them and then make the patch 

Re: Contributing to the IDE

[Geoff Canyon via use-livecode]

I have to admit, this is very frustrating. I *have* read both documents
referenced, and neither comes close to answering my question. I remember
reading those documents, or their ancestors, when LC first went open
source, and I would likely have started contributing to the IDE then except
they were no more clear then than now.

Let's start with
https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md, which
does not include the word "IDE" anywhere in it. Really, the only
information it contains that is remotely relevant to my question is:

"The LiveCode workflow is a typical git workflow, where contributors fork
the livecode/livecode repository, make their changes on a branch, and then
submit a pull request."

From what I have read, there is no such thing as a "typical git workflow."
Git is designed to be flexible, and there are as many workflows as there
are git users.

And:

"You should base your changes on an appropriate branch: "

None of it comes close to describing the steps necessary to set up on my
computer to contribute.

The other document,
https://github.com/livecode/livecode/blob/develop/README.md, describes
LiveCode, and is not even about contributing. Apart from mentioning:

"engine/ — The main LiveCode engine. This directory produces the IDE,
"standalone", "installer" and "server" engines"

it offers nothing useful to figuring out how to set up to contribute.

I ran into this same problem when I started to put Navigator into GitHub:
the GitHub documentation is absolutely abysmal. In that instance, the blame
lies with literally everyone associated with Git and GitHub, but in the
case of wanting to contribute to the LC IDE, the buck stops with the LC
crew. I have asked others who are decades-long LC developers for guidance,
and found that they don't understand how to contribute. That holds back
development of LC and the IDE.

To be clear: reasonable documentation for contributing to the IDE would
include a section something like:

1. Create an account on GitHub. Follow the guidelines mentioned elsewhere
in this documentation.
2. (optional) Install the graphic Git client of your choice (a list of
possibilities is included at the bottom of this documentation).
3. Determine which version of LC you want to contribute to. Note that only
contributions to  are being accepted at present.
4. Clone the repository for the LC version you have selected to your local
drive. Save it to your Applications folder. Do not overwrite your working
copy of LiveCode.
5. You will need to follow these additional steps to make that repository
functional:
...
6. License the copy of LC included in the repository.
7. Make whatever changes to the IDE you wish. Note that you must segment
your changes in individual branches; if you lump a large number of changes
in one branch, your updates will almost certainly be rejected.
8. When you have a branch ready to merge into the production copy of
LiveCode, issue a pull request. Please follow the documentation
descriptions listed below; if we can't understand your change, it will be
rejected.

To be more clear, I have no idea if the above is the correct sequence of
steps. That's the problem I'm trying to solve, and neither of the
referenced documents, nor any admonishment to study them in greater detail,
will solve it.



On Thu, Apr 19, 2018 at 3:10 PM, Monte Goulding via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Just a guessing based on your response that you possibly didn’t read the
> docs that you asked for and Brian responded with ;-)
>
> > On 20 Apr 2018, at 5:43 am, Geoff Canyon via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > I have GitKraken; is it as simple as initializing a new repository
> > in /Applications/LiveCode Indy 8.1.8.app/Contents/Tools/
> Toolset/libraries?
>
>
> ___
> 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: some thoughts on version 9.0.0

[Monte Goulding via use-livecode]

> On 20 Apr 2018, at 10:28 am, Mark Wieder via use-livecode 
>  wrote:
> 
> On 04/19/2018 03:03 PM, Niggemann, Bernd via use-livecode wrote:
> 
>> actually the problem was that if you use the number of lines of the 
>> behaviors and you have a couple of behaviors stacked then the space needed 
>> for the behaviors would run into the text. The current solution was the one 
>> which used the least space. If you look in the Project Browser at "Message 
>> Box" or "revIDEProjectBrowser" that have two behaviors that the spacing for 
>> between the behaviors is minimal to save space, also that is the reason why 
>> they are oval so you can reduce the spacing between behaviors.
> 
> Sorry, I'm missing something in that explanation.
> Yes, what I see for the messagebox is 2,1,9 meaning that there are nine lines 
> in the object script and two stacked behaviors. The first behavior has 839 
> lines and the second one has 805 lines. I fail to see why it would be a 
> problem if the displayed numbers were 805,839,9.

I think it’s just a space issue. Around the time Bernd did his patch for this I 
had a play with a collapsing breadcrumb widget which can pack as much info as 
there is space to do so for this type of thing. I never cleaned it up for use 
but if someone has some time to do so it could be a good addition:

https://github.com/montegoulding/livecode/blob/breadcrumb/extensions/widgets/breakdcrumb/breadcrumb.lcb
 


It actually used a hitTestPath function of widgetutils that was never merged 
too so that would need to be copied from here 
https://github.com/montegoulding/livecode/blob/hittest/extensions/modules/widget-utils/widget-utils.lcb#L287
 


Cheers

Monte
___
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: some thoughts on version 9.0.0

[Mark Wieder via use-livecode]

On 04/19/2018 03:03 PM, Niggemann, Bernd via use-livecode wrote:


actually the problem was that if you use the number of lines of the behaviors and you have a couple 
of behaviors stacked then the space needed for the behaviors would run into the text. The current 
solution was the one which used the least space. If you look in the Project Browser at 
"Message Box" or "revIDEProjectBrowser" that have two behaviors that the 
spacing for between the behaviors is minimal to save space, also that is the reason why they are 
oval so you can reduce the spacing between behaviors.


Sorry, I'm missing something in that explanation.
Yes, what I see for the messagebox is 2,1,9 meaning that there are nine 
lines in the object script and two stacked behaviors. The first behavior 
has 839 lines and the second one has 805 lines. I fail to see why it 
would be a problem if the displayed numbers were 805,839,9.



I agree that counting from 1 to 10 is not really a big help, could have been 
greek letters instead, but what you gather from the number of lines of the 
behavior script escapes me.


Well, for one thing, it gives me an idea of how much effort I'm about to 
get into when looking at modifying a behavior script. And gives me some 
direction as to whether I'd want to add more code to an 
already-overloaded behavior or spawn a second one or put code in a main 
script.


--
 Mark Wieder
 ahsoftw...@gmail.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: mergAccessory

[Monte Goulding via use-livecode]

> On 20 Apr 2018, at 2:01 am, Douglas Ruisaard via use-livecode 
>  wrote:
> 
> I am pursuing another course of action for my iOS USB investigation... in the 
> meantime, in case I need it, I'd appreciate some assistance with 
> mergeAccessory.
> 
> 
> 
> first, the associated doc (api.lcdoc) to mergAccessory is a tad out of 
> date... referencing LC v 5.5 ... but adjusting for version 8.1.9, while there 
> is a "Settings.plist" file in the specified path, it is "unreadable by either 
> by  Xcode 9.2 or  Xcode 8.2 ==> "The data couldn't be read because it isn't 
> in the correct format".  Using an alternative plist reader "Perf Setter", I 
> get a "The document 'Settings.plist" could not be opened”.


You need to edit in a regular text editor. We have some replacement fields that 
the standard plist editors don’t like.
> 
> Next, I do not see any key as referenced in the api doc:  
> UISupportedExternalAccessoryProtocols ... that's OK.. I assume I'd 
> have to create this key but the example only show how to specify the protocol 
> ... the docs say:
> 
> 
> 
> "... Each device in the MFi program has a name and one or more protocols it 
> supports ..." .. so where does the "name" go?

You just specify the protocols
> 
> 
> 
> Finally, I don't see what the example code is supposed to be demonstrating.  
> A bit more explanation on that would be appreciated.

I’m pretty sure the example code will be printing to a portable bluetooth 
receipt printer because that’s the use case that mergAccessory was implemented 
for even though it can work with any made for iphone accessory as long as you 
have the protocol docs.

Cheers

Monte
___
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: Contributing to the IDE

[Monte Goulding via use-livecode]

Just a guessing based on your response that you possibly didn’t read the docs 
that you asked for and Brian responded with ;-)

> On 20 Apr 2018, at 5:43 am, Geoff Canyon via use-livecode 
>  wrote:
> 
> I have GitKraken; is it as simple as initializing a new repository
> in /Applications/LiveCode Indy 8.1.8.app/Contents/Tools/Toolset/libraries?


___
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: some thoughts on version 9.0.0

[Niggemann, Bernd via use-livecode]

Mark Wieder via use-livecode Thu, 19 Apr 2018 13:46:24 -0700
>
>On 04/19/2018 01:15 PM, Niggemann, Bernd via use-livecode wrote:
>
>the number 1 indicates that this is the first behavior. Behaviors can be 
>stacked and then you would have 2,3 or whatever up to ten behaviors. The 
>number 
>of lines is useful for the object but not so much for the behavior. The 
>tooltip 
>indicates the the name of the behavior, clicking on it opens the script of the 
>behavior.

Unless it's somehow possible for the displayed behaviors to get out of order, 
then the numbers seem somewhat useless. I think this is a big step backwards 
from displaying the number of lines in the behavior script
--
 Mark Wieder
 ahsoftw...@gmail.com


Hi Mark,

actually the problem was that if you use the number of lines of the behaviors 
and you have a couple of behaviors stacked then the space needed for the 
behaviors would run into the text. The current solution was the one which used 
the least space. If you look in the Project Browser at "Message Box" or 
"revIDEProjectBrowser" that have two behaviors that the spacing for between the 
behaviors is minimal to save space, also that is the reason why they are oval 
so you can reduce the spacing between behaviors.

I agree that counting from 1 to 10 is not really a big help, could have been 
greek letters instead, but what you gather from the number of lines of the 
behavior script escapes me.

Kind regards

Bernd
___
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: some thoughts on version 9.0.0

[gcanyon via use-livecode]

Self-promotion: Navigator's
 script menu
displays all the behaviors, and the handlers in them, of an object. The
theoretical limit is 100,000 stacked behaviors, but I suspect the menu
system would break before reaching that limit. You need to update from the
built-in Navigator to get this functionality.

On Thu, Apr 19, 2018 at 9:00 AM, Douglas Ruisaard via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I use the Project Browser heavily ... one change in 9.0.0 I definitely DO
> NOT like is the "new" way of indicating a "behavior" assignment on an
> object.  What's with the little oval with a "1" in it???  I used the
> (previous) line counts to visually match to the "source" button line
> counts.. easy... now, I have to open the Properties to see which object is
> the source behavior.. not good, IMO
>
>
>
> Next is the significant decrease in the "Ink" choices... I've found (by
> process of elimination) the "notSrcOrReverse" ink works for me in several
> situations there ain't no such thing in v9.0.0.  And sometimes the drop
> down Ink listing gets "stuck" behind the Property window ... blocking some
> of the choices... inconsistent and not reproducible between stacks but
> consistent within a stack.
>
>
>
> A few other inconsistencies and quirks which are not consistent between
> stacks but demonstrable on specific stacks are not going to encourage me to
> use the v9.0.0 for production stuff.. until new revisions are produced.
>
>
>
> Doug
>
> ___
> 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: some thoughts on version 9.0.0

[Mark Wieder via use-livecode]

On 04/19/2018 01:15 PM, Niggemann, Bernd via use-livecode wrote:

the number 1 indicates that this is the first behavior. Behaviors can be 
stacked and then you would have 2,3 or whatever up to ten behaviors. The number 
of lines is useful for the object but not so much for the behavior. The tooltip 
indicates the the name of the behavior, clicking on it opens the script of the 
behavior.


Unless it's somehow possible for the displayed behaviors to get out of 
order, then the numbers seem somewhat useless. I think this is a big 
step backwards from displaying the number of lines in the behavior script


--
 Mark Wieder
 ahsoftw...@gmail.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: some thoughts on version 9.0.0

[Niggemann, Bernd via use-livecode]

I use the Project Browser heavily ... one change in 9.0.0 I definitely DO NOT
like is the "new" way of indicating a "behavior" assignment on an object.
What's with the little oval with a "1" in it???  I used the (previous) line
counts to visually match to the "source" button line counts.. easy... now, I
have to open the Properties to see which object is the source behavior.. not
good, IMO

Hi Douglas,

the number 1 indicates that this is the first behavior. Behaviors can be 
stacked and then you would have 2,3 or whatever up to ten behaviors. The number 
of lines is useful for the object but not so much for the behavior. The tooltip 
indicates the the name of the behavior, clicking on it opens the script of the 
behavior.

Page 33 of the release notes states:

Show up to 10 nested behavior in the Project Browser

It is now possible to view up to 10 nested behaviors of an object in the PB. 
The behaviors are shown using oval graphics. Clicking on the graphic takes you 
to the script of the behavior. The tooltip of the graphic shows the long name 
of the behavior.

https://github.com/livecode/livecode-ide/pull/1508

Kind regards

Bernd
___
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: Contributing to the IDE

[Geoff Canyon via use-livecode]

I have GitKraken; is it as simple as initializing a new repository
in /Applications/LiveCode Indy 8.1.8.app/Contents/Tools/Toolset/libraries?

On Mon, Apr 16, 2018 at 7:48 PM, Brian Milby  wrote:

> https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md
>
> https://github.com/livecode/livecode/blob/develop/README.md
>
> Those two docs have most of what you will need. If you have purchased
> LiveCode Global 2018 then you can watch the talk I gave last month on
> setting up your system to build from source (Linux was the demo).
>
> Once you have the repo on your seat, you can branch and make any changes
> required and do a PR. Just be sure to keep straight which project you are
> in. The IDE is separate and most of the stuff related to the IDE is in that
> sub project. I find it easier to just do everything in a branch and build
> from source to check my work - even when working on widgets. I do have a
> stack I use to check dictionary updates though (but it doesn’t check that
> examples compile... need to get that included at some point).
>
> Brian
> On Mon, Apr 16, 2018 at 8:45 PM Geoff Canyon via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Are there instructions available somewhere on how to set up the IDE in
>> GitHub so I can make changes and submit pull requests?
>>
>> gc
>> ___
>> 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: Has Anyone Got A Directory "Walker" Available

[Paul Hibbert via use-livecode]

> On 19 Apr 2018, at 11:20, Sannyasin Brahmanathaswami via use-livecode 
> > wrote:
> 
> Never mind…
> 
> I found this in a toolbox. Sent by some ago, by a LiveCode deva 


That looks very much like the code supplied under the “Resources” menu, from 
Tutorials>General>Files and Folders.

I’ve used it on a few projects n the past and it has worked pretty well for me.

Paul
___
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

mergAccessory

[Douglas Ruisaard via use-livecode]

I am pursuing another course of action for my iOS USB investigation... in the 
meantime, in case I need it, I'd appreciate some assistance with mergeAccessory.

 

first, the associated doc (api.lcdoc) to mergAccessory is a tad out of date... 
referencing LC v 5.5 ... but adjusting for version 8.1.9, while there is a 
"Settings.plist" file in the specified path, it is "unreadable by either by  
Xcode 9.2 or  Xcode 8.2 ==> "The data couldn't be read because it isn't in the 
correct format".  Using an alternative plist reader "Perf Setter", I get a "The 
document 'Settings.plist" could not be opened".

 

I checked the permissions, even copied the file to my user directory, changed 
the permission to Read/Write and get the same messages.  I can open it in 
TextEdit but am hesitant to make and save any changes using that editor since 
the file itself seems to be non-standard... embedded control characters???  Any 
idea of why this file is "inaccessible"?

 

Next, I do not see any key as referenced in the api doc:  
UISupportedExternalAccessoryProtocols ... that's OK.. I assume I'd 
have to create this key but the example only show how to specify the protocol 
... the docs say:

 

"... Each device in the MFi program has a name and one or more protocols it 
supports ..." .. so where does the "name" go?

 

Finally, I don't see what the example code is supposed to be demonstrating.  A 
bit more explanation on that would be appreciated.

 

Cheers!

Doug

___
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

some thoughts on version 9.0.0

[Douglas Ruisaard via use-livecode]

I use the Project Browser heavily ... one change in 9.0.0 I definitely DO NOT 
like is the "new" way of indicating a "behavior" assignment on an object.  
What's with the little oval with a "1" in it???  I used the (previous) line 
counts to visually match to the "source" button line counts.. easy... now, I 
have to open the Properties to see which object is the source behavior.. not 
good, IMO

 

Next is the significant decrease in the "Ink" choices... I've found (by process 
of elimination) the "notSrcOrReverse" ink works for me in several 
situations there ain't no such thing in v9.0.0.  And sometimes the drop 
down Ink listing gets "stuck" behind the Property window ... blocking some of 
the choices... inconsistent and not reproducible between stacks but consistent 
within a stack.  

 

A few other inconsistencies and quirks which are not consistent between stacks 
but demonstrable on specific stacks are not going to encourage me to use the 
v9.0.0 for production stuff.. until new revisions are produced.

 

Doug

___
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

Android assistance / information?

[Douglas Ruisaard via use-livecode]

Anyone is this community as versed in Android as Monte Goulding is in iOS?  One 
of the beauties of LC is its cross-platform ability.  The app I've written in 
iOS ports just fine to Android .. at least the user-interactive and data 
processing parts do.  .. without changing one line of code (and it's a complex 
app) ... how slick is that??? Obviously, there is a lack of an equivalent 
Android BLE function for communicating to my Arduino which I have working 
splendidly in iOS.  So... I'm looking for information / assistance on how to 
implement a "hardwired" connection from an Arduino to an Android device  
(currently have an older- Galaxy Tab 4 running v 5.1.1) ... but if I need a 
newer model, newer OS, that's do-able.

 

I'm hoping (?against hope?) that all I need is the "device name" for the USB 
port on the Android and the rest I can handle using the "open device" serial 
handles in LC.  I understand that one reason that LC may have and still is 
avoiding the Android BLE topic is due to the varieties and variations within 
the numerous version of the Android OS's.  For me, I just need to be able to 
demonstrate a mobile device (iOS or Android) being able to communicate with an 
Arduino app via a USB hardwire connection.  I REALLY don't care which OS it is 
and if I have to use iOS for BLE and Android for USB... that's just fine!

 

Any help would be greatly appreciated!!

 

Cheers

Doug

___
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

Has Anyone Got A Directory "Walker" Available

[Sannyasin Brahmanathaswami via use-livecode]

I have directory available this days of Ken Ray, in the on system of set the 
default folder and get the the files, registered that path. descend recursively 
to the level… etc.

Do anyone has a new one handy they could share using the folder and file 
function?

BR


___
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: DataGrid Column Labels

[Bob Sneidar via use-livecode]

Ah. My problem was that my datagrids had different objects when I checked. 
Probably because I have been working with this project since the v6 days. 

BTW I replaced my datagrids which were showing non-3D column labels with fresh 
ones and they look fine now. I have 2 scripts that help me with this. They do 
not account for custom properties though. I need to update them to account for 
that: 

on saveDatagrid pDataGrid
   if pDatagrid is empty then
  put the short name of the selectedObject into pDataGrid
   end if
   
   if not there is a group pDataGrid then
  put "Invalid arguement. pDataGrid must be the name of a datagrid in the 
current stack." into mmsg
  answer info mmsg as sheet
  exit saveDatagrid
   end if
   
   put the short name of group pDataGrid into aSavedDataGrids 
[pDataGrid]["name"]
   put the height of group pDataGrid into aSavedDataGrids [pDataGrid]["height"]
   put the width of group pDataGrid into aSavedDataGrids [pDataGrid]["width"]
   put the loc of group pDataGrid into aSavedDataGrids [pDataGrid]["loc"]
   put the script of group pDataGrid into aSavedDataGrids [pDataGrid]["script"]
   put the dgprop ["columns"] of group pDataGrid into aSavedDataGrids 
[pDataGrid]["columns"]
   put the dgprop ["column labels"] of group pDataGrid into aSavedDataGrids 
[pDataGrid]["column labels"]
   put the dgprop ["column widths"] of group pDataGrid into aSavedDataGrids 
[pDataGrid]["column widths"]
   put the dgprop ["allow editing"] of group pDataGrid into aSavedDataGrids 
[pDataGrid]["allow editing"]
   put the dgProp ["multiple lines"] of group pDataGrid into aSavedDataGrids 
[pDataGrid]["multiple lines"]
   put getParentStack(the long id of group pDataGrid) into tThisStack
   set the pSavedDataGrids of tThisStack to  aSavedDataGrids
end saveDatagrid

on restoreDataGrid pDataGrid
   put getParentStack(the long id of group pDataGrid) into tThisStack
   put the pSavedDataGrids of tThisStack into  aSavedDataGrids
   
   if aSavedDataGrids is not an array then
  answer info "Invalid arguement. pDataGrid must be an array." as sheet
  exit restoreDataGrid
   end if
   
   if there is a group pDataGrid then delete group pDataGrid
   copy group "DataGrid" of group "Templates" of stack "revDataGridLibrary" to 
tThisStack
   put it into tDataGridRef
   set the name of tDataGridRef to aSavedDataGrids [pDataGrid]["name"]
   set the height of group pDataGrid to aSavedDataGrids [pDataGrid]["height"]
   set the width of group pDataGrid to aSavedDataGrids [pDataGrid]["width"]
   set the loc of group pDataGrid to aSavedDataGrids [pDataGrid]["loc"]
   set the script of group pDataGrid to aSavedDataGrids [pDataGrid]["script"]
   set the dgprop ["columns"] of group pDataGrid to aSavedDataGrids 
[pDataGrid]["columns"]
   set the dgprop ["column labels"] of group pDataGrid to aSavedDataGrids 
[pDataGrid]["column labels"]
   set the dgprop ["column widths"] of group pDataGrid to aSavedDataGrids 
[pDataGrid]["column widths"]
   set the dgprop ["allow editing"] of group pDataGrid to aSavedDataGrids 
[pDataGrid]["allow editing"]
   set the dgProp ["multiple lines"] of group pDataGrid to aSavedDataGrids 
[pDataGrid]["multiple lines"]
end restoreDataGrid


Bob S


> On Apr 18, 2018, at 10:43 , Terence Heaford via use-livecode 
>  wrote:
> 
> All my tables just say
> 
> button id 1005 of stack "revDataGridLibrary"
> 
> 
> Did the copy and paste thing and it did not work.
> 
> ??
> 
> Terry


___
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: Posting to LiveCode Server

[Bob Sneidar via use-livecode]

URL Encode it.

Bob S


> On Apr 18, 2018, at 22:48 , David Bovill via use-livecode 
>  wrote:
> 
> Todd, the browser auto-translates things you type / copy paste in the url
> bar to something it expects you want as a url.
> 
> You have characters in the url that need to be escaped (<>)


___
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

OpenLanguage: abstract syntax trees

[David Bovill via use-livecode]

I'm doing some research around languages for a new project. I'd like to get
a firmer handle on where Livecode as a language is going, and need to learn
a bit more computer science regarding compilers, abstract syntax trees and
language design.

So let's ask some dumb questions:

   1. Is there an abstract syntax tree (AST) for the Livecode language?
   2. Where can I buy it?
   3. How hard would it be to create one?

Google told me that I should use Coco, to generate an AST from the C++
code. But i don't trust Google, I much prefer Siri due to her business
model. My hope is that Mark Waddingham will explain this properly. I trust
Mark.

*Open Language*
My understanding is that we are steadily, if not slower than hoped, moving
towards open language in Livecode. It's something I need, hence my interest
in DSL's, AST's and compilers. I'd like to know more.

At the moment I believe from previous posts, it is possible to create DSL's
in Livecode, but you have to compile from source. I'd like to have a go at
that if possible, as it may well be a shorter path to creating my DSL, than
trying to get Siri to teach me about abstract syntax trees.

Mark any chance of sending the gift of your knowledge our way?
___
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: DataGrid Column Labels

[Terence Heaford via use-livecode]

It’s weird but placing this in the preopenCard script sorts out the issue for 
now.

set the dgProp[ "column labels" ] of group  “myTable" to the dgProp[ "column 
labels" ] of group "myTable"


All the best

Terry

> On 18 Apr 2018, at 18:43, Terence Heaford via use-livecode 
>  wrote:
> 
> All my tables just say
> 
> button id 1005 of stack "revDataGridLibrary"
> 
> 
> Did the copy and paste thing and it did not work.
> 
> ??
> 
> Terry
> 
>> On 18 Apr 2018, at 15:53, Bob Sneidar via use-livecode 
>>  wrote:
>> 
>> 2. Copy what's in the message 
> 
> ___
> 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