On Fri, Jan 6, 2017 at 2:49 AM, Heather Laine via use-livecode <
use-livecode@lists.runrev.com> wrote:
> "A bit like devs are being milked" seems a somewhat extraordinary
> statement. LiveCode is a business, with expenses and a stable of highly
> skilled and valuable developers. Which of them
: Friday, January 06, 2017 8:10 AM
To: How to use LiveCode
Cc: Bob Sneidar
Subject: Re: TS Net for Indy vs Business
Exactly what I was thinking when I read it. My greatest aprehension in using
Livecode is that one day it will be gone, and I will have to learn to use
C++ or Objective C, which
I totally agree with you and could not have said it better.
> Am 06.01.2017 um 17:09 schrieb Bob Sneidar via use-livecode
> >:
>
> Exactly what I was thinking when I read it. My greatest aprehension in using
> Livecode is
Exactly what I was thinking when I read it. My greatest aprehension in using
Livecode is that one day it will be gone, and I will have to learn to use C++
or Objective C, which is to say I will have to give up software development.
I'm not really sure how they stay afloat as is, but as I
On 6 Jan 2017, at 12:49, Heather Laine via use-livecode wrote:
"A bit like devs are being milked" seems a somewhat extraordinary
statement. LiveCode is a business, with expenses and a stable of
highly skilled and valuable developers.
I meant this in the traditional 'online pushy chatty'
"A bit like devs are being milked" seems a somewhat extraordinary statement.
LiveCode is a business, with expenses and a stable of highly skilled and
valuable developers. Which of them would you like us to fire? We need to pay
for LiveCode's development so that all of the users in the community
On 30 Dec 2016, at 12:41, Skip Kimpel wrote:
+1
LC needs to reconsider breaking up functionality based upon licensing.
Indeed! I haven't looked in depth at the differences, but I thought it
was more (or even entirely) about support, which makes sense for
high-level business requirements,
Hi Bill and others,
I appreciate the feedback regarding the feature breakdown between the
different licenses.
The decision to split the features (and how they were split) across
Business and Indy was decided on by the LiveCode team.
I expect that some of them may have seen this thread,
Charles:
It also seems to me like this is a vital feature that could cripple some
applications. I agree with the other posters that the Indy version will
probably be purchased by the great majority of those who purchase licenses. It
“should” be a big market.
Best,
Bill
> Skip Kimpel wrote:
SFTP var content only?
Wow… Strange strategy… Indy should/could be LC's bread and butter.. a product
that works may be a better strategy in the long run than providing a crippled
option. Reserve business only feature for true enterprise features, not for a
simple options that come with any
Charles,
Thanks a lot for the quick reply! Things are much clearer now. I have some
comments below.
On Fri, Dec 30, 2016 at 12:13 AM, Charles Warwick <
char...@techstrategies.com.au> wrote:
> 2. For Indy users, SFTP and SMTP can only be performed to/from a variable
> - not directly using a
+1
On 30/12/2016, 11:40, "use-livecode on behalf of Roger Eller"
wrote:
I am really disappointed that SFTP (for Indy) is limited to a variable
(RAM) -vs- writing directly to a file. Moving large files
+1
LC needs to reconsider breaking up functionality based upon licensing.
SKIP
> On Dec 30, 2016, at 6:40 AM, Roger Eller wrote:
>
> I am really disappointed that SFTP (for Indy) is limited to a variable
> (RAM) -vs- writing directly to a file. Moving large files
I am really disappointed that SFTP (for Indy) is limited to a variable
(RAM) -vs- writing directly to a file. Moving large files that exceed
system RAM is very common.
~Roger
On Dec 30, 2016 5:13 AM, "Charles Warwick"
wrote:
> Hi Andre,
>
> I will be adding a
Hi Andre,
I will be adding a fair amount of documentation for tsNet over the
coming weeks that I hope will better answer a number of the questions
that are being asked on the list.
In the mean time, I hope that the following two points will explain what
is happening for you.
1. For Indy
Hey,
Yes, we found that page as well. The problem is that even though the page
lists features available to each license, there is no list of commands and
functions per license. For example, it says that public key authentication
is only available to business license holders, so we'd assume that
Sannyasin Brahmanathaswami wrote:
> We need some help.
>
> We know that we can do SFTP with TS-Net external
>
> but
>
> functions that we try to use from an Indy LC return "unlicensed" even
> when, the documentation make not indication that they should fail
> without the business license.
>
>
I agree but I am also about to launch a product that uses the SFTP
functionality and am curious about what feature you are getting that message
for so I don't have any surprises.
SKIP
> On Dec 27, 2016, at 8:58 AM, Sannyasin Brahmanathaswami
> wrote:
>
> Would rather not
Would rather not piece-meal this:
For the sake of the product (to keep new developers from cursing LC)
Let's get documentation: simple:
All commands/methods that will work with Indy and any standalone built with Indy
All commands/methods that are business license only
+ ideally: sample
What features are you getting "unlicensed" for?
SKIP
> On Dec 26, 2016, at 9:03 PM, Sannyasin Brahmanathaswami
> wrote:
>
> We need some help.
>
> We know that we can do SFTP with TS-Net external
>
> but
>
> functions that we try to use from an Indy LC return "unlicensed"
We need some help.
We know that we can do SFTP with TS-Net external
but
functions that we try to use from an Indy LC return "unlicensed" even when, the
documentation make not indication that they should fail without the business
license.
What we need is
Documention on what functions and
21 matches
Mail list logo