Re: Graphing Solution...

[Mike Bonner via use-livecode]

Actually, change 2 lines and I think it'll work better:
Line 932, change to:  updateGridRect(rectangle [gridLeft(), tPadding +
tNeededTop, mWidth - tPadding - mMaxYLabelWidth, gridBottom()])

Line 1061 change to: fill text tString at left of rectangle [tYRight +
gridPadding(),tY-20,tYRight + mMaxYLabelWidth + gridPadding(),tY+20] on
this canvas


On Sun, May 27, 2018 at 10:05 PM, Mike Bonner  wrote:

> I floundered around cluelessly with it for a bit, randomly changing a few
> things till I got something that seems to work.  I'm sure there are things
> I still misunderstand about this, and that I've added code that probably
> doesn't need to be there.  Also not sure if there will be issues with
> larger labels etc, but if you're interested, the modified stuff can be
> found here: https://www.dropbox.com/s/bsj0u87tlg54xt2/com.livecode.widget.
> linegraphyright.zip?dl=1
>
> If you do a diff of the stock lcb and the lcb in the zip archive, you can
> see all my (unremarked) floundering differences.  As it sits though, the
> default data comes up and displays fine.  Just checked with larger values,
> some of the numbers I poked in there should probably be increased a little,
> though i'm sure theres a better way to calculate such things.
>
> On Sun, May 27, 2018 at 9:28 PM, Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Here is the link on GitHub...
>>
>> https://github.com/livecode/livecode/tree/develop/extensions
>> /widgets/graph
>>
>> On May 27, 2018, 10:24 PM -0500, Mark Wieder via use-livecode <
>> use-livecode@lists.runrev.com>, wrote:
>> > On 05/27/2018 07:15 PM, Glen Bojsza via use-livecode wrote:
>> > > Hi Brian,
>> > >
>> > > They are good ideas...I haven't done anything with widgets.
>> > >
>> > > How do I get access to the source code?
>> >
>> > The source file is graph.lcb, and where it's stored depends on what
>> > operating system you're working with.
>> >
>> > /Extensions/com.livecode.widget.linegraph
>> >
>> > so on my linux system, I've got it in
>> > /opt/livecodecommunity-9.0.0.x86_64/Extensions...
>> >
>> > and obviously it will be in different places on Windows and OSX.
>> >
>> > But beware that coding in LCB is quite different from "normal" LiveCode
>> > coding. Copy the source file, put it into its own folder somewhere, edit
>> > it (it's a text file), then open it in the extension builder and test
>> > the changes. Have fun.
>> >
>> > --
>> > 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
>> ___
>> 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: Graphing Solution...

[Mike Bonner via use-livecode]

I floundered around cluelessly with it for a bit, randomly changing a few
things till I got something that seems to work.  I'm sure there are things
I still misunderstand about this, and that I've added code that probably
doesn't need to be there.  Also not sure if there will be issues with
larger labels etc, but if you're interested, the modified stuff can be
found here:
https://www.dropbox.com/s/bsj0u87tlg54xt2/com.livecode.widget.linegraphyright.zip?dl=1


If you do a diff of the stock lcb and the lcb in the zip archive, you can
see all my (unremarked) floundering differences.  As it sits though, the
default data comes up and displays fine.  Just checked with larger values,
some of the numbers I poked in there should probably be increased a little,
though i'm sure theres a better way to calculate such things.

On Sun, May 27, 2018 at 9:28 PM, Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Here is the link on GitHub...
>
> https://github.com/livecode/livecode/tree/develop/extensions/widgets/graph
>
> On May 27, 2018, 10:24 PM -0500, Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
> > On 05/27/2018 07:15 PM, Glen Bojsza via use-livecode wrote:
> > > Hi Brian,
> > >
> > > They are good ideas...I haven't done anything with widgets.
> > >
> > > How do I get access to the source code?
> >
> > The source file is graph.lcb, and where it's stored depends on what
> > operating system you're working with.
> >
> > /Extensions/com.livecode.widget.linegraph
> >
> > so on my linux system, I've got it in
> > /opt/livecodecommunity-9.0.0.x86_64/Extensions...
> >
> > and obviously it will be in different places on Windows and OSX.
> >
> > But beware that coding in LCB is quite different from "normal" LiveCode
> > coding. Copy the source file, put it into its own folder somewhere, edit
> > it (it's a text file), then open it in the extension builder and test
> > the changes. Have fun.
> >
> > --
> > 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
> ___
> 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: Is anyone using tsNet external with LCserver?

[Charles Warwick via use-livecode]

Hi Matthias,

You should just need to copy the relevant tsNet external (for Linux x64 it is 
tsNet-x64.so) into the external directory from your normal commercial desktop 
installation.

After that, just make sure you call tsNetInit before making any other tsNet 
calls.

Regards,

Charles

> On 28 May 2018, at 9:06 am, Matthias Rebbe via use-livecode 
>  wrote:
> 
> Hi,
> is anyone already using tsNet external with Livecode server? If so, is there 
> something i should take care of when trying to “install” / copy the external 
> to my custom installation?
> 
> Unfortunately the commercial LC server builds still do not contain the 
> external.
> 
> Regards,
> 
> Matthias Rebbe
> 
> 
> 
> 
> ___
> 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: Graphing Solution...

[Brian Milby via use-livecode]

Here is the link on GitHub...

https://github.com/livecode/livecode/tree/develop/extensions/widgets/graph

On May 27, 2018, 10:24 PM -0500, Mark Wieder via use-livecode 
, wrote:
> On 05/27/2018 07:15 PM, Glen Bojsza via use-livecode wrote:
> > Hi Brian,
> >
> > They are good ideas...I haven't done anything with widgets.
> >
> > How do I get access to the source code?
>
> The source file is graph.lcb, and where it's stored depends on what
> operating system you're working with.
>
> /Extensions/com.livecode.widget.linegraph
>
> so on my linux system, I've got it in
> /opt/livecodecommunity-9.0.0.x86_64/Extensions...
>
> and obviously it will be in different places on Windows and OSX.
>
> But beware that coding in LCB is quite different from "normal" LiveCode
> coding. Copy the source file, put it into its own folder somewhere, edit
> it (it's a text file), then open it in the extension builder and test
> the changes. Have fun.
>
> --
> 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
___
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: Graphing Solution...

[Mark Wieder via use-livecode]

On 05/27/2018 07:15 PM, Glen Bojsza via use-livecode wrote:

Hi Brian,

They are good ideas...I haven't done anything with widgets.

How do I get access to the source code?


The source file is graph.lcb, and where it's stored depends on what 
operating system you're working with.


/Extensions/com.livecode.widget.linegraph

so on my linux system, I've got it in
/opt/livecodecommunity-9.0.0.x86_64/Extensions...

and obviously it will be in different places on Windows and OSX.

But beware that coding in LCB is quite different from "normal" LiveCode 
coding. Copy the source file, put it into its own folder somewhere, edit 
it (it's a text file), then open it in the extension builder and test 
the changes. Have fun.


--
 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: Graphing Solution...

[Glen Bojsza via use-livecode]

Hi Brian,

They are good ideas...I haven't done anything with widgets.

How do I get access to the source code?


On Sun, May 27, 2018 at 8:40 PM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> In LC9, you could possibly use the line graph widget.  The source is
> available, so you could modify it to support dual y-axis (but I'll admit
> this wouldn't be trivial to complete).
>
> A possibly easier modification would be to add the ability to display the y
> labels on the right side.  Then you could use 2 widget instances, properly
> aligned, to display the data.  The first series in an instance with the
> left labels and the second in the one with right labels.
>
> Another option, depending on how much data is being displayed (and if you
> need the ability to select a point on the graph and display the value -
> which would probably require the first solution), would be to fake it  .
> You could take the data for the first y scale and then map the next series
> to those values for graphing.  Then you would just need to display another
> scale on the right side of the chart to show the values.
>
> So for s1 = 1, 2, 3; s2 = 30, 20, 10
> You would graph s1 = 1, 2, 3; s2 = 3, 2, 1 (but have a label on the right
> going from 10 to 30)
>
> Thanks,
> Brian
>
> On Sun, May 27, 2018 at 2:21 PM, Glen Bojsza via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Hello,
> >
> > I am trying to find a graphing solution that will support dual y - axis
> > line plots.
> >
> > Both sets of data need to be plotted on the same graph so the left Y
> scale
> > is used for one set of data that is plotted and the right Y scale is for
> > the other set of data.
> >
> > From what I have found neither ChartMaker or ChartsEngine support this
> type
> > of plot.
> >
> > Does anyone have any suggestions?
> >
> > thanks,
> >
> > Glen
> > ___
> > 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

Re: Windows 10 and LC9.0

[Monte Goulding via use-livecode]

Hi Folks

I just wanted to chime in here on a couple of things.

Regarding the windows day I am trying to do as much as I can on Windows now. 
It’s a bit easier now that 8.x has been EOLd there’s only one toolchain to deal 
with. Having said that though the way we work on LiveCode and the way you work 
with LiveCode are completely different so good bug reports are essential to 
getting what you are seeing fixed.

I currently have a couple of PRs open that should resolve some of the issues 
people are seeing so hopefully in 9.0.1 people won’t see the slow typing in the 
SE and when nudging lots of controls.

Regarding other issues here it would be really helpful if people could quote 
bug numbers when discussing problems they are having so that we can get them 
sorted.

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

Is anyone using tsNet external with LCserver?

[Matthias Rebbe via use-livecode]

Hi,
is anyone already using tsNet external with Livecode server? If so, is there 
something i should take care of when trying to “install” / copy the external to 
my custom installation?

Unfortunately the commercial LC server builds still do not contain the external.

Regards,

Matthias Rebbe




___
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: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

[Monte Goulding via use-livecode]

> On 28 May 2018, at 2:40 am, Pi Digital via use-livecode 
>  wrote:
> 
> Thanks for the clarification, Monte. 
> 
> But just to clarify in return (respectfully), when I spoke of IDE changes I 
> was specifically referring to the Project Browser (omitted from your quote). 
> As the greatest extent of items within the IDE that need fixing are GUI with 
> the majority of their code within their respective stacks. I’d started on the 
> project browser back n it’s early days but quickly got shut down by two of 
> LCs former coders. I even created a stack comparator but they weren’t 
> interested (surprisingly).

OK well this may or may not have been before my time with the company so I’m 
not sure what as involved. If you find your patch needs to touch scripts in 
binary stacks then I would recommend the following:

- ensure there is a bug/enhancement report for what you want to do
- open up a report requesting the scripts you want to edit be turned into 
script only stacks and mention you will fix the original report if this is 
done. This will need to be done by someone on the team but as it doesn’t take 
long, we want to do it anyway and we like to help out people that are 
contributing we should be able to do it fairly quickly.
- wait for the scriptification then make your patch to that.

If your patch involves changes to the controls on binary stacks then the best 
we can offer at the moment is asking you to write a script that makes the 
changes. That will actually help us if we have a merge conflict and is a 
process we have used once or twice even within the team. For example when 
legacy inks were removed I wrote a script to fix them and we applied it to 
multiple branches die to a merge conflict.

The best thing you can do is communicate with the team what you would like to 
work on and we will help in whatever way we can. Gitter is a good venue for 
such discussions.

> 
> I appreciate, though, that google had been a bit rubbish at notifying, mainly 
> because they relied mostly on notifying when people logged in but our API had 
> silent mode on so we never heard. In my defence however, oAuth and similar 
> have been under review by every provider for the last three years due to 
> security, so perhaps having looked during those years for anything that uses 
> oAuth or similar to ensure they are up to date. Now is probably a good 
> opportunity to check all of the other ones. 

Yes I have opened a report to update the oauth2 library as soon as we can.
> 
> I hope this doesn’t touch a nerve, but why hasn’t the mergext stuff been set 
> as open source also. This would be useful to the community with regards 
> building extensions for LiveCode (similar to the new sockets library). 

There are some mergExt externals that were always open source and still are. 
The rest of it fit into Indy and Business to add product differentiation.
> 
>> All we need is a decent bug report for anything that isn’t open source
> 
> And then we just need to wait several months potentially before that fix sees 
> the light of day. Not helpful!

Not necessarily true either. There are a number of factors that are involved in 
determining what makes it into our fortnightly sprint. Ali is probably the one 
to discuss that 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: Windows 10 and LC9.0

[J. Landman Gay via use-livecode]

On 5/26/18 7:20 PM, Sean Cole (Pi) via use-livecode wrote:

When I wrote the list of things that were broken I was writing specifically
about Mac.


I haven't responded so far because I thought the issues were 
Windows-related and I do development on Mac. There is something going on 
that apparently doesn't affect my setup because the only issue in your 
report I've seen (and it's minor) is the property inspector not resizing 
correctly when you change panes.


I can drag-drop controls from the palette, resize the message box 
whenever I like, and the script editor works fine for me. I haven't had 
a crash recently until yesterday when I was implementing RSA encryption 
and I did something wrong in my handler. So I'm trying to think what I 
do differently that doesn't cause the problems you're seeing.


I suspect what it boils down to is that I don't use the project browser 
because the app browser is better suited to my workflow. And some of the 
new scripting options are disabled, the only ones I use are Bracket 
Completion, Control Structure Completion, and Autoformatting.


It would be interesting to see if those who are having issues still have 
the same problems if the Project Browser is closed and some of the 
scripting options are turned off. While it's true that users shouldn't 
have to do that, it would at least give the team an idea of why some 
people have trouble while others don't. Once identified, they could 
address the issues.


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

Graphing Solution...

[Glen Bojsza via use-livecode]

Hello,

I am trying to find a graphing solution that will support dual y - axis
line plots.

Both sets of data need to be plotted on the same graph so the left Y scale
is used for one set of data that is plotted and the right Y scale is for
the other set of data.

>From what I have found neither ChartMaker or ChartsEngine support this type
of plot.

Does anyone have any suggestions?

thanks,

Glen
___
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: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

[Stephen Barncard via use-livecode]

Sean, with all due respect, Monte probably has a deal with livecode that
enables him to retain ownership of his rights to his code that he wrote in
return for whatever deal he has with livecode.

Wouldn’t you?

On Sun, May 27, 2018 at 09:41 Pi Digital via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks for the clarification, Monte.
>
> But just to clarify in return (respectfully), when I spoke of IDE changes
> I was specifically referring to the Project Browser (omitted from your
> quote). As the greatest extent of items within the IDE that need fixing are
> GUI with the majority of their code within their respective stacks. I’d
> started on the project browser back n it’s early days but quickly got shut
> down by two of LCs former coders. I even created a stack comparator but
> they weren’t interested (surprisingly).
>
> I appreciate, though, that google had been a bit rubbish at notifying,
> mainly because they relied mostly on notifying when people logged in but
> our API had silent mode on so we never heard. In my defence however, oAuth
> and similar have been under review by every provider for the last three
> years due to security, so perhaps having looked during those years for
> anything that uses oAuth or similar to ensure they are up to date. Now is
> probably a good opportunity to check all of the other ones.
>
> I hope this doesn’t touch a nerve, but why hasn’t the mergext stuff been
> set as open source also. This would be useful to the community with regards
> building extensions for LiveCode (similar to the new sockets library).
>
> > All we need is a decent bug report for anything that isn’t open source
>
> And then we just need to wait several months potentially before that fix
> sees the light of day. Not helpful!
>
> Cheers.
>
> Sean Cole
> Pi Digital
>
> > On 27 May 2018, at 02:11, Monte Goulding via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Hi Sean
> >
> > It is a relief to hear from you. I’m sorry if you were weirded out by
> the help offered. I have struggled in the past to swallow my pride and just
> accept help when I need it. Last year dealing with Rebecca’s cancer was a
> humbling experience for me in this regard.
> >
> > Anyway, there’s a few points I thought it might be helpful to clarify
> for yourself and others below.
> >
> >> Due to various security risks,
> >> Google had decided to deprecate the use of webviews for authenticating
> >> oAuth entry.
> >
> > Although this may appear to be blame shifting I’d like to point out that
> when Dropbox dropped API v1 they sent a number of emails allowing us to get
> prepared to offer something for v2. Google’s little note at the bottom of a
> page you don’t really look for little notes on really didn’t help that much
> clearly.
> >
> >> Despite being distributed as part of LC, mergext is
> >> not open source so can’t be repaired by any of us.
> >
> > All we need is a decent bug report for anything that isn’t open source.
> >
> >> which
> >> we can’t fix easily because it’s part of the ide and they won’t accept
> ide
> >> amendments due to the fact it can’t be checked and compared using
> >> GitHub!!!
> >
> > If the issue is in a script only stack which most things are in the IDE
> then we do accept contributions.
> >
> >> Looking at the latest LC8 release, the ‘fix’ Monte did for mergGoogle
> >> hasn’t been added in. It’s hardly working let alone ‘Stable’ then, is
> it!!
> >
> > This is the main point I wanted to clarify. When I heard of your
> situation I stopped doing the work I had been assigned and started working
> on a fix for you. Doing it as quick as I could meant breaking the mac cross
> compilation so I built for iOS, ensured it worked and posted a link for you
> (or anyone else to access it). So that leaves on the todo list before it
> becomes part of the main distribution for me to fix the mac build, have it
> reviewed by another member of the team and included in the main bundle of
> mergExt builds we include in the distribution. In the meantime we have a
> build that works for those that need it.
> >
> > Regards
> >
> > 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
> ___
> 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

-- 
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
___
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: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

[Pi Digital via use-livecode]

Thanks for the clarification, Monte. 

But just to clarify in return (respectfully), when I spoke of IDE changes I was 
specifically referring to the Project Browser (omitted from your quote). As the 
greatest extent of items within the IDE that need fixing are GUI with the 
majority of their code within their respective stacks. I’d started on the 
project browser back n it’s early days but quickly got shut down by two of LCs 
former coders. I even created a stack comparator but they weren’t interested 
(surprisingly).

I appreciate, though, that google had been a bit rubbish at notifying, mainly 
because they relied mostly on notifying when people logged in but our API had 
silent mode on so we never heard. In my defence however, oAuth and similar have 
been under review by every provider for the last three years due to security, 
so perhaps having looked during those years for anything that uses oAuth or 
similar to ensure they are up to date. Now is probably a good opportunity to 
check all of the other ones. 

I hope this doesn’t touch a nerve, but why hasn’t the mergext stuff been set as 
open source also. This would be useful to the community with regards building 
extensions for LiveCode (similar to the new sockets library). 

> All we need is a decent bug report for anything that isn’t open source

And then we just need to wait several months potentially before that fix sees 
the light of day. Not helpful!

Cheers. 

Sean Cole
Pi Digital

> On 27 May 2018, at 02:11, Monte Goulding via use-livecode 
>  wrote:
> 
> Hi Sean
> 
> It is a relief to hear from you. I’m sorry if you were weirded out by the 
> help offered. I have struggled in the past to swallow my pride and just 
> accept help when I need it. Last year dealing with Rebecca’s cancer was a 
> humbling experience for me in this regard. 
> 
> Anyway, there’s a few points I thought it might be helpful to clarify for 
> yourself and others below.
> 
>> Due to various security risks,
>> Google had decided to deprecate the use of webviews for authenticating
>> oAuth entry.
> 
> Although this may appear to be blame shifting I’d like to point out that when 
> Dropbox dropped API v1 they sent a number of emails allowing us to get 
> prepared to offer something for v2. Google’s little note at the bottom of a 
> page you don’t really look for little notes on really didn’t help that much 
> clearly.
> 
>> Despite being distributed as part of LC, mergext is
>> not open source so can’t be repaired by any of us.
> 
> All we need is a decent bug report for anything that isn’t open source.
> 
>> which
>> we can’t fix easily because it’s part of the ide and they won’t accept ide
>> amendments due to the fact it can’t be checked and compared using
>> GitHub!!!
> 
> If the issue is in a script only stack which most things are in the IDE then 
> we do accept contributions.
> 
>> Looking at the latest LC8 release, the ‘fix’ Monte did for mergGoogle
>> hasn’t been added in. It’s hardly working let alone ‘Stable’ then, is it!!
> 
> This is the main point I wanted to clarify. When I heard of your situation I 
> stopped doing the work I had been assigned and started working on a fix for 
> you. Doing it as quick as I could meant breaking the mac cross compilation so 
> I built for iOS, ensured it worked and posted a link for you (or anyone else 
> to access it). So that leaves on the todo list before it becomes part of the 
> main distribution for me to fix the mac build, have it reviewed by another 
> member of the team and included in the main bundle of mergExt builds we 
> include in the distribution. In the meantime we have a build that works for 
> those that need it.
> 
> Regards
> 
> 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
___
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: Windows 10 and LC9.0

[Erik Beugelaar via use-livecode]

Maybe an idea for the mothership to setup an survey like they did with the 
HTML5 campaign.

Survey containing for example questions about:

1. Percentage of total LiveCode developers mainly using LiveCode on Windows 
platform against Mac OSX platform;
2. Percentage of total LiveCode developers mainly targeting Android on Windows 
platform against Mac OSX platform targeting Android;
3. Suggestions of making the IDE working solid under Windows platform;
5. Priority list of issues;
5. Etc etc

It has no use to look backward dealing with technical issues you couldn’t fixed 
by yourself, my wise father always told me (senior engineer Electronics) to put 
all strength together so you all can move forward, in this case to make a 
stable working version 9.x of LiveCode IDE under Windows/OSX.

Just my 2cents,
Erik Beugelaar



On 27/05/18 02:20, "use-livecode on behalf of Sean Cole (Pi) via use-livecode" 
 wrote:

>On Sat, 26 May 2018 at 22:09, AndyP via use-livecode <
>use-livecode@lists.runrev.com> wrote:
>
>
>> If for example you are using LC on Mac which I have used in the past and
>> was a pleasure to behold.. it just works!
>>
>When I wrote the list of things that were broken I was writing specifically
>about Mac. I very rarely code on Windoze. The Mac ‘just works’, true. But
>LC on a Mac is ‘just flawed’. And from the catalogue of faults I’ve binge
>read from the last couple of weeks posts it seems it’s a cross platform
>issue.
>
>LC 9 is simply not ready, is still Beta and is an embarrassment. Any new
>customer that would come their way would immediately abandon LC based on
>frustration and limitation. There seems no sense to it. Did they not
>actually test it for real before they released it? I have a feeling they
>put far too much trust in their automated tests and don’t do nearly enough
>manual real world testing to see how their dev env works. Especially the
>script editor for goodness sake, the very heart of the coding environment!
>
>
>-- 
>Sean Cole
>*Pi Digital Productions Ltd*
>www.pidigital.co.uk
>+44(1634)402193
>+44(7702)116447
>'Don't try to think outside the box. Just remember the truth: There is no
>box!'
>'For then you realise it is not the box you are trying to look outside of,
>but it is yourself!'
>
>eMail Ts & Cs    Pi Digital
>Productions Ltd is a UK registered limited company, no. 5255609
>___
>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