Good shout. Although, having the gui available helps when things go wrong
like the PDF font rendering issues and being able to see the templates
build as it goes for each page/card. But thanks for the heads up.
Sean
On Thu, 17 Dec 2020 at 05:40, Richard Gaskin via use-livecode <
LC Server had graphics capabilities added a few versions back. You can
lay out objects on cards and export images with it now.
I'm not sure if those extend to the PDF external, but if you happen to
try it please let me know.
If nothing else, being able to run faceless should save quite a
Hi Richard,
My case scenario is maybe a little unique, I don't know. The server app
needs to build from MySQL data and other resources (csv's and images)
downloaded from emails received from a vendor a PDF report that it 'prints'
out and uploads to a web hosted site for downloading by the clients
Hi all,
Continuing my study, I've just tried installing LC9.6.2RC onto the latest
Debian 10 build (clean install in Parallels from its add VM page). However,
it comes up with an error when installing LC right after double-clicking
the installer: "Failed to load library 'gdk' (tried
On 12/16/20 1:39 AM, Pi Digital via use-livecode wrote:
Back to my OP.
- What system build of Linux should I best install in Parallels virtual and
Server Remote Host for deployment should I run with? Given the choices of
potentially having LC IDE running as the ‘live’ software stack on the
Pi Digital wrote:
> Ah, i see your POV now. You distinguish a difference between ‘runs on’
> and ‘deploys on’. Where as I infer that there is no difference and
> that ‘supports’ is as ‘system requirements’ or ‘supported systems’.
To me "runs on" and "deploys on" can only be the same thing when
Ah, i see your POV now. You distinguish a difference between ‘runs on’ and
‘deploys on’. Where as I infer that there is no difference and that ‘supports’
is as ‘system requirements’ or ‘supported systems’.
The document is aimed at users of Livecode who, of course are developers but,
are also
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
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
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
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,
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.
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
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
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
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
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
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
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
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
> 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
Sean Cole wrote:
> You're probably right. However, with security issues constantly
> needing keeping up to date with, it's probably worth working out
> if it is worth supporting Linux at all, then. If they, LC, feel
> it 'is' worth supporting Linux, it is surely, then, essential
> to keep up
Hi Richmond,
You're probably right. However, with security issues constantly needing
keeping up to date with, it's probably worth working out if it is worth
supporting Linux at all, then. If they, LC, feel it 'is' worth supporting
Linux, it is surely, then, essential to keep up with these latest
On 12/14/20 3:17 PM, Sean Cole (Pi) via use-livecode wrote:
Hi Mark,
Are you able to say what particular bits were broken so I know what to be
on the lookout for and assess if these might affect our project?
Sure. Here's the PR
https://github.com/livecode/livecode/pull/7127
But note that you
Hi Mark,
Are you able to say what particular bits were broken so I know what to be
on the lookout for and assess if these might affect our project?
Thanks
Sean Cole
*Pi Digital *
On Mon, 14 Dec 2020 at 01:15, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 12/13/20
"I wonder why LC don’t state support for later Ubuntu, Fedora or Debian
builds?"
I suspect that LiveCode believes that the uptake of the Linux version is
insufficient to justify the effort of testing LC on those platforms.
Richmond.
On 14.12.20 2:20, Pi Digital via use-livecode wrote:
On 12/13/20 4:20 PM, Pi Digital via use-livecode wrote:
Thanks all. These insights are useful. Hery’s explanation of their choice to
move to Debian provides a good argument. I had just tried Ubuntu 20.04 in a
parallels virtual machine and my server app worked ok. I will try a Debian
build
Thanks all. These insights are useful. Hery’s explanation of their choice to
move to Debian provides a good argument. I had just tried Ubuntu 20.04 in a
parallels virtual machine and my server app worked ok. I will try a Debian
build too. I wonder why LC don’t state support for later Ubuntu,
Hi Sean,
I've been using LiveCode on Ubuntu 16.04 and 18.04 for years (Servers
and Desktops) and it worked fine. A years ago we migrated everything to
CentOS / RedHat and Fedora (development machines and servers). However,
we are going to migrate everything to Debian.
Debian is very stable
I personally use Neon, it's based upon Ubuntu and is the development base
platform for KDE.
I find that it is better integrated between the tools as they are
specializing upon one desktop and ensuring everything is properly supported.
I have used livecode on it over the past year without issue.
Well, I am running LC 9.6.1 on Xubuntu (Ubuntu with XFCE) 20.10 without
a backward glance: Rocks!
Richmond.
On 13.12.20 19:40, Sean Cole (Pi) via use-livecode wrote:
Hi all,
I just heard the news that RedHat is going to be dropping support for
CentOS. With my recent issues with PDF Printing
Hi all,
I just heard the news that RedHat is going to be dropping support for
CentOS. With my recent issues with PDF Printing in CentOS, I was already
looking to perhaps try out CentOS8 or another Dist. but now we have this
news I'm thinking of going to Ubuntu.
The release notes for LC says it
34 matches
Mail list logo
