Richmond wrote:
>On 16.12.20 2:14, Richard Gaskin via use-livecode wrote:
>> Richmond wrote:
>> > Well . . . they could install a later version of Ubuntu (takes
>> > about 30-120 minutes) and build and test on that version.
>> >
>> > Surely not that arduous.
>>...
>> How familiar are you with the
Sean -
This thread began with a concern over how Linux compatibility is
described in the Release Notes.
I proposed a solution, but it didn't resonate. Perhaps a different
approach may work:
The audience for the Release Notes is developers, and what developers
need to know is where LiveCode
I had my client try it. Adding "wait 0 milliseconds" after a "go card" didn't make any
difference really. The first four card changes were pretty fast, and after that it got slower
and slower with each subsequent card change. I was watching her screen remotely but I couldn't
see it due to how re
I am not familiar at all.
But, having built an LC version for Linux it can then be tested on
a recent Linux distro.
On 16.12.20 2:14, Richard Gaskin via use-livecode wrote:
Richmond wrote:
> Well . . . they could install a later version of Ubuntu (takes about
> 30-120 minutes) and build and tes
It’s this kind of rhetoric that drive me to madness and then getting a used of
being abusive as I defend what I’ve said. Richard, there is no need as you
have clearly misinterpreted practically everything I said in an effort to get
some kind of oneupmanship.
>> On 16 Dec 2020, at 01:00, Richa
Pi Digital wrote:
> But that does not seem to correlate to the way it is for MacOS or Win.
> Are you saying they compile from all of those versions of MacOS and
> Win they reference to supporting.
Mac and Windows are each made by a single organization, with specs
defining compatibility.
"Linu
A little while ago in this forum we were alerted to the fact that LC direct
connection to a remote database not using SSL was a security hole. This also
applies to managing Mailman lists on a remote server.
After a steep (re-)learning curve with the various technologies, I now have a
working me
Richmond wrote:
> Well . . . they could install a later version of Ubuntu (takes about
> 30-120 minutes) and build and test on that version.
>
> Surely not that arduous.
Exactly how sure are you?
What they need to do is more than what customers need to do.
How familiar are you with the LC build
Well . . . they could install a later version of Ubuntu (takes about
30-120 minutes) and build
and test on that version.
Surely not that arduous.
Best, Richmond.
On 15.12.20 19:38, Mark Wieder via use-livecode wrote:
On 12/15/20 3:48 AM, Richmond via use-livecode wrote:
2. Stir up trouble.
Thanks Panos.
My main concern of late has been the PDF output font rendering in CentOS and I
am hoping that it will be better in Ubuntu or another distro. But I’m guessing
I’m going to have to do a whole heap of testing to find out.
Sean Cole
Pi Digital
> On 15 Dec 2020, at 09:24, merakosp
But that does not seem to correlate to the way it is for MacOS or Win. Are you
saying they compile from all of those versions of MacOS and Win they reference
to supporting.
This is a very odd use of semantics.
When reading about LiveCode support, to me it doesn’t matter if it is LC Ltd or
th
On 12/15/20 3:48 AM, Richmond via use-livecode wrote:
2. Stir up trouble.
Personally I think that LiveCode central are being a bit @#$%^&*
claiming that LiveCode
is cross-platform and not saying they support more recent versions than
Ubuntu 16.04 and so on.
And stirring up trouble means tha
Hi Sean & Richmond,
I think it is best to only support LTS versions and just one desktop
(Gnome). This will standardize the platform a bit (Hey, I don't want to
start a flame, I'm just saying that Gnome and Ubuntu / Debian are the
most used).
The problem with LINUX is the sheer number of diff
Sean Cole wrote:
> On 15 Dec 2020, at 02:52, Richard Gaskin wrote:
>
>> As Mark Weider noted, the "official" support is merely a reflection
>> of their build system, and it relies on a version of Ubuntu still
>> actively getting security updates.
>
> That doesn’t seem to be stated or inferred in t
I would pick a small fight here.
On 15.12.20 11:24, merakosp via use-livecode wrote:
Hello Sean,
Off the top of my head, the main Linux issues that are currently unresolved
are:
1. The player object is broken on all Linux distros. You might be able to
workaround this by using shell commands wi
1. I have never, ever experienced any problems at all with any versions
of LiveCode on
any versions of Xubuntu that are more 'modern' than 16.04.
2. Stir up trouble.
Personally I think that LiveCode central are being a bit @#$%^&*
claiming that LiveCode
is cross-platform and not saying they su
Hello Sean,
Off the top of my head, the main Linux issues that are currently unresolved
are:
1. The player object is broken on all Linux distros. You might be able to
workaround this by using shell commands with mplayer.
2. The browser widget is broken in most Linux distros. It might work for
ju
> On 15 Dec 2020, at 02:52, Richard Gaskin via use-livecode
> wrote:
>
> As Mark Weider noted, the "official" support is merely a reflection of their
> build system, and it relies on a version of Ubuntu still actively getting
> security updates.
That doesn’t seem to be stated or inferred in
18 matches
Mail list logo
