Re: native scroller cuts off parts of last line in a field

2021-04-20 Thread e.beugelaar--- via use-livecode
I am still wondering why layout issues anno 2021 has to be programmed manually 
for all devices. It is nonsense and don't make sense.
I started programming with Clipper 5.x in text base environments and even in 
that period we had ClipDAS, i was co-writer of it, to draw virtual screens.
Is it really so hard to add a general page designer to deal with positioning 
objects anno 2021! I dont want to spent my time on this stupid rect issues but 
instead focus on the business logic etc. Jesus.

Met vriendelijke groet,

Erik Beugelaar



From: use-livecode  on behalf of Klaus 
major-k via use-livecode 
Sent: Tuesday, April 20, 2021 1:56:37 PM
To: How to use LiveCode 
Cc: Klaus major-k 
Subject: Re: native scroller cuts off parts of last line in a field

Hi Brian,

> Am 20.04.2021 um 13:48 schrieb Brian Milby via use-livecode 
> :
>
> I think that is just a bug.

wonderful! :-(

> See here for workaround idea:
> https://github.com/Himalayan-Academy/Siva-Siva-App/blob/nightly/behaviors/behavior_mobileScroller.livecodescript
> Basic idea is to add 60 or so px to content region and then adjust a bit when 
> not at the top.  Requires adjustments in scrollerDidScroll handler.

I even added a line of WHITE text (field has white background) at the end, but 
obviously LC does not see this!?
Will try the workaround thank you!

> Thanks,

no, I thank YOU! 8-)

> Brian

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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: LC Bug: Copying an Image fails

2021-03-20 Thread e.beugelaar--- via use-livecode
Hi Curry,

It's always fun to read your comments and conclusions that can be somethimes  
interpreted in Dutch as: "de redding is nabij".
So, a solution is near to come!

Nice weekend,
Erik

Met vriendelijke groet,

Erik Beugelaar



From: use-livecode  on behalf of Curry 
Kenworthy via use-livecode 
Sent: Saturday, March 20, 2021 5:55:19 AM
To: use-livecode@lists.runrev.com 
Cc: Curry Kenworthy 
Subject: Re: LC Bug: Copying an Image fails


Bob:

 > MS Office copy operations are notoriously problematic.
 > Microsoft maintains their own clipboard format, so that when
 > switching to another product the clipboard must be translated.
 > Other apps may do the same.
 > The translation does not always go to plan.

Eh ... I think this is a more useful current summary:

1. The Windows blank pasted image bug was about a data stream pointer.
Thanks to the LC Team for looking into that; hope it's merged sooner.

2. There's a crash for some copied image data. Not just MS Office.

3. Mac has image copy/paste troubles too. Also not just MS Office.
I'll report that soon, and we'll probably see improvement.

4. There are dozens of issues with copied content being converted in LC.
I'm crushing many of those with workarounds, so improvement there too!

Is copy/paste between apps effortless? No.
Do users expect it? Yes.
Even with the most popular apps? Of course!
There are problems, but also progress

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.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: LC Roadmap

2021-02-14 Thread e.beugelaar--- via use-livecode
https://www.b4x.com if u dont want headaches.

Get Outlook for Android


From: use-livecode  on behalf of Curry 
Kenworthy via use-livecode 
Sent: Sunday, February 14, 2021 11:31:47 AM
To: use-livecode@lists.runrev.com 
Cc: Curry Kenworthy 
Subject: Re: LC Roadmap


JeeJeeStudio:

 > I like Livecode a lot, but it has it's limitations,
 > lot of bugs are not solved.

True. Would be more accurate with "yet" added; solving bugs is ongoing!
We could also say that many bugs HAVE been solved. Moderate progress.
(I know, having been on the front lines of the bug-reporting battle.)

I attribute bug density to dev strategy during the "Great Refactoring."
Good: Kickstarter project threw money/man-hours at LC to achieve a lot.
Bad: Code quality was mediocre; lots of bugs introduced at that time.
(We are STILL finding and reporting LC 7 and 8 bugs.)

Problem: Digging out from under myriad bugs takes big money/man-hours.
Meanwhile: Platforms, especially Apple and Mobile, are moving targets.

Traditional solution: Use a new campaign, like FM, for cashflow.
Underlying philosophy: Quality = energy/money/time.
Potential weakness: History could repeat itself. New code quality??

My proposed solution: Decrease net bugs with more careful coding.
Underlying philosophy: New code should be good code. (Almost zero-sum.)
Potential weakness: Too late for the Refactoring; only useful from now.

 > Livecode is great! Don't misunderstand and it learns a lot of
 > people to program. But it runs behind future facts.

Some truth there too, but it misses a (gigantic) point. In fact, two:

A. A good IDE is not ONLY about features, bugs, and platforms.
B. LC's benefit is not ONLY about being easy to learn. (When it is.)

If that's the only reason you're here, you don't understand LC!

And you're not the only one. Even those at the top have missed it.
Raney failed to see it: He considered MC a stepping stone to C.
LC Ltd also missed part of it: many unique benefits under-promoted.
And the way some features are added CONTRADICTS the LC paradigm.

LiveCode - and the legacy of HyperCard - is not Just Another IDE.
People have usually failed miserably at explaining the magic.
("Easy English-like language?" Way too vague! Also missing the point.)
Too few good analyses, too much parroting weak/transient slogans.

I intend to do a bit myself in that area soon, explaining what HC/LC is.
(I had health/energy problems, thus some detractors, but they'll see!)
The unique strengths of LC paradigm -yes, paradigm- deserve attention.
That's why I'm making it a point to be more active on this list.

That paradigm is why many of us are here: not just a handy-dandy tool.
It's a worldview of how to code - which should be updated not discarded.
This paradigm has extreme value; likely more than even LC Ltd realizes.
That's why I'm making it a point to be more active on this list!

Growing the audience again requires understanding/promoting that value.
You can't just swap in any XYZ tool/language for LC. It ain't the same!
Nor is success ONLY about winning the feature and platform arms race.
That, but so much more. Paradigm is key. It has been neglected too long.

We must MAKE THE CASE for LC. Some have tried (thanks!) but not enough.
I feel paradigm is equally important to explain to LC Ltd, as to users.

 > HTML5 is a drag in LC, unusable, to play ok, to really use no way..

Not much argument there! Hopefully good things coming.

 > And next to it I'm learning Flutter platform with Dart
 > as main language, it's free, it's the future

Thanks for sharing that. It looks pretty good.
However, really the future? Maybe not!
End of LC? "Hell no!" :D

(At least, if LC Ltd play their hand well.)

Again, there's #1. Paradigm - more on that soon, when I have time.
But also several other factors in play:

2. Current and future tech changes; you ain't seen nothing yet!
3. Mega corp competition; Apple & others will frequently reinvent.
4. Tech giant control; Silicon Valley oversteps, people will push back.
5. Corporations are good at innovation, also good at screwing up.

The control factor might bite Google and Apple soon:
should I build there, when Powers That Be can pull the plug anytime?
Increasingly, the big guys don't follow their own rules; it's arbitrary.

Tip: they just love control, whether visual fashion trends or ideology.
What they encourage one year may become a "sin" the next. (Hi, Apple!)
Very often it's simply dollars and cents; more control means more fees.

Meanwhile, you're at the mercy of their tech whims.
Whatever they think should be the new trend, you must do.
Modern corporate strategy is to reinvent for profit; relentless change.

Factor #5 is also big for me. Remember how Google would "fix" search?
They "fixed" it alright! They killed it; try searching a non-trend.

So do I want to leap into Google's IDE?

Trust them to "fix" software development? To decide what I should do?
To reinvent every 5 

Re: open secure socket... using certificate

2021-01-29 Thread e.beugelaar--- via use-livecode
Xojo is not multi platform.
If you want to move, which i regret, I strongly advise you to go for the B4X 
platform.

Get Outlook for Android


From: use-livecode  on behalf of Bernard 
Devlin via use-livecode 
Sent: Friday, January 29, 2021 7:19:58 PM
To: How to use LiveCode 
Cc: Bernard Devlin 
Subject: Re: open secure socket... using certificate

Hi Richard

The idea of client certificates was why I was looking for this feature for
the past 15 years. I know that PKI is complex but it is important (which is
why browsers implemented it decades ago).  Even tsNet behaves very
differently on Windows and OS X when it comes to server certificates (looks
to me that Microsoft is mis-implementing their libcurl/schannel interface,
but I guess it stung them 20 years ago when they hadn't implemented
Certificate Revocation Lists).

Without LC having client certificates the only option I face is moving to
another tool. Even the idea of implementing real secure sockets in a FFI
external would be a huge amount of work for any of us users (as there is
not even a single lower level language which we could rely on in each
platform, so we'd be implementing a complex security layer and learning how
to do it in several different languages).

I'm going to look at moving to Xojo. Their docs say they implemented secure
sockets with certificates in 2006.  Their Android deployment platform is
close to completion. It really would have been better for LC to have
removed those claims from the Dictionary back in 2014, as then I'd have
seen in recent years it still hadn't been implemented and would have looked
at another tool months ago rather than get to this point and realise I'd
wasted a lot of time. I've spent an entire week now just pondering on the
options on how I can move forward.

Regards, Bernard


On Fri, Jan 29, 2021 at 4:12 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
>
> Thank you, Bernard.  In bringing myself up to speed on this, once I
> stumbled across the phrase "two-way SSL" I was able to find much good
> reading about it.
>
> I just added Comment #11 to the bug report on this:
>
>  The range of services requiring two-way SSL is increasing,
>  and with IoT the scope of use cases is multiplying.
>
>  Where required, I don't see an opportunity for a scripted
>  workaround, so in those cases the only alternative is to
>  leave LC for a tool that supports two-way SSL.
>
>  This would seem a good time to bite the bullet on this
>  implementation. What would be required to make it happen?
>
> https://quality.livecode.com/show_bug.cgi?id=13410#c11
>
>
___
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