Re: Lasso Digest, Vol 61, Issue 6

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lasso Digest, Vol 61, Issue 6

Yescas, Alejandro
Will Lasso ever be Open-Source ?….it currently seems abandoned.








On Jul 25, 2016, at 2:00 AM, [hidden email]<mailto:[hidden email]> wrote:

Send Lasso mailing list submissions to
[hidden email]<mailto:[hidden email]>

To subscribe or unsubscribe via the World Wide Web, visit
http://newlists.lassosoft.com/cgi-bin/mailman/listinfo/lasso
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lasso digest..."


Today's Topics:

  1. Re: Mailchimp API v3.0 (Black Night Lists)
  2. Converting Classic L8 Inline to L9 & DS - Return Key Value?
     (Marc Pinnell)
  3. Re: Converting Classic L8 Inline to L9 & DS - Return Key
     Value? (Steve Piercy - Website Builder)
  4. Re: Converting Classic L8 Inline to L9 & DS - Return Key
     Value? (Marc Pinnell)
  5. Looking to move up from LP 8.5.6 (Jerad Hoff)
  6. Re: Looking to move up from LP 8.5.6 (Tom Parker)
  7. Ping (Rick Draper)


----------------------------------------------------------------------

Message: 1
Date: Tue, 19 Jul 2016 11:27:51 +0100
From: Black Night Lists <[hidden email]>
To: [hidden email]
Subject: Re: Mailchimp API v3.0
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Nice one, I have downloaded it and will check it out.

On 18 Jul 2016, at 19:31, Jason Huck <[hidden email]> wrote:

For anyone who needs it, I put together a very simple Mailchimp wrapper for
Lasso 8.x, based on a PHP implementation I found. It's not a drop-in
replacement for the previous version, but it was a reasonable way to wrap
the bulk of the API (everything except batch operations and webhooks)
without writing a ton of code.

The way it works is very simple: there are methods for each kind of HTTP
verb required by the API. Each of these accepts a "method" param, which is
the API endpoint you need to access, and an "args" param, which is a map of
options. It returns the full, decoded response, and stores the headers in
an instance variable in case you need to inspect them. I thought I would
have to use curl via [os_process] for the more exotic verbs, but MailChimp
allows you to simulate PUT, PATCH, and DELETE calls via POST with an extra
MIME header, so it just uses plain old [include_url] for everything.

The custom type and a few examples are on GitHub:
https://gist.github.com/jasonhuck/a6d8f5d96d812dd9af29ebe8efec4ce9

I've verified that it works with a number of different CRUD operations for
campaigns, lists, and reports, and have ironed out a handful of minor
issues along the way. It seems to be working pretty well, but hasn't been
extensively battle tested yet.


Regards

Stephen Thirlwell
Black Night Software
http://www.blacknight.co.uk









------------------------------

Message: 2
Date: Sun, 24 Jul 2016 11:22:49 -0700
From: Marc Pinnell <[hidden email]>
To: Lasso Talk <[hidden email]>
Subject: Converting Classic L8 Inline to L9 & DS - Return Key Value?
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Working to convert some really old code. Inserting a new value into a table that uses an auto-increment key value. Stuck on how to get the key value (#innum in L8 code below).

Old L8 code (truncated a little for display):
inline(
$authInfo_db,
#subDB, //override default db
-table = 'subs',
-add,
-keyfield = 'innum',
'cname' = #fromForm->find('fname')->first->second,
'adcost' = #cost,
'fld1' = 'WandW Subscription',
'date' = date_format(date, -format='%D'),
'time' = date_format(date, -format='%T')
);
#innum = field('innum'); //Pickup auto increment value
/inline;

New L9 code using DS (truncated a little for display):
subs_ds->keycolumn('innum') //innum is auto increment
->addrow(::subs,
   map(
::cName = postparam('fname') + ' ' + postparam('lname'),
::address = postparam('sadd'),
::city = postparam('city'),
::time = date_format(date, -format='%T'),
::adcost = $cost,
::fld1 = 'WandW Subscription'
   )
   $innum = ::innum->asstring //Pickup auto increment value - doesn't work :(
)

Is this possible? Do I need completely rethink the process (trying to convert, not reinvent!)

Marc

====================
Marc Pinnell
Director of Web Services
[hidden email]
www.shasta.com
833 Mistletoe Lane, Suite A1
Redding, CA  96002
530-224-6866  Ext. 100
530-224-2035 Fax



------------------------------

Message: 3
Date: Sun, 24 Jul 2016 11:33:48 -0700
From: Steve Piercy - Website Builder <[hidden email]>
To: [hidden email]
Subject: Re: Converting Classic L8 Inline to L9 & DS - Return Key
Value?
Message-ID:
<[hidden email]>
Content-Type: text/plain; charset=UTF-8; format=flowed

$innum is nested within ->addrow.  That makes it a pair, not an
assignment, that you pass into ->addrow.

Try this:

    // attempt to add a new user and grab the record's keyvalue
    local(kv) = #create_record_ds
        -> addrow(
            ::column = value,
        ) -> keyvalue

--steve


On 7/24/16 at 11:22 AM, [hidden email] (Marc
Pinnell) pronounced:

Working to convert some really old code. Inserting a new value
into a table that uses an auto-increment key value. Stuck on
how to get the key value (#innum in L8 code below).

Old L8 code (truncated a little for display):
inline(
$authInfo_db,
#subDB,         //override default db
-table      =   'subs',
-add,
-keyfield   =   'innum',
'cname'     =   #fromForm->find('fname')->first->second,
'adcost'    =   #cost,
'fld1'      =   'WandW Subscription',
'date'      =   date_format(date, -format='%D'),
'time'      =   date_format(date, -format='%T')
);
#innum = field('innum');        //Pickup auto increment value
/inline;

New L9 code using DS (truncated a little for display):
subs_ds->keycolumn('innum')     //innum is auto increment
->addrow(::subs,
map(
::cName     =   postparam('fname') + ' ' + postparam('lname'),
::address   =   postparam('sadd'),
::city      =   postparam('city'),
::time      =   date_format(date, -format='%T'),
::adcost    =   $cost,
::fld1      =   'WandW Subscription'
)
$innum = ::innum->asstring  //Pickup auto increment value - doesn't work :(
)

Is this possible? Do I need completely rethink the process
(trying to convert, not reinvent!)

Marc

====================
Marc Pinnell
Director of Web Services
[hidden email]
www.shasta.com                                     833
Mistletoe Lane, Suite A1
Redding, CA  96002
530-224-6866  Ext. 100
530-224-2035 Fax


#############################################################

This message is sent to you because you are subscribed to
the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy              Website Builder              Soquel, CA
<[hidden email]>               <http://www.stevepiercy.com/>



------------------------------

Message: 4
Date: Sun, 24 Jul 2016 12:15:15 -0700
From: Marc Pinnell <[hidden email]>
To: [hidden email]
Subject: Re: Converting Classic L8 Inline to L9 & DS - Return Key
Value?
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Brillant! Worked perfect.

Looking ahead, can you return other fields with the same technique?

marc


On Jul 24, 2016, at 11:33 AM, Steve Piercy - Website Builder <[hidden email]> wrote:

$innum is nested within ->addrow.  That makes it a pair, not an assignment, that you pass into ->addrow.

Try this:

  // attempt to add a new user and grab the record's keyvalue
  local(kv) = #create_record_ds
      -> addrow(
          ::column = value,
      ) -> keyvalue

--steve


On 7/24/16 at 11:22 AM, [hidden email] (Marc Pinnell) pronounced:

Working to convert some really old code. Inserting a new value into a table that uses an auto-increment key value. Stuck on how to get the key value (#innum in L8 code below).

Old L8 code (truncated a little for display):
inline(
$authInfo_db,
#subDB,         //override default db
-table      =   'subs',
-add,
-keyfield   =   'innum',
'cname'     =   #fromForm->find('fname')->first->second,
'adcost'    =   #cost,
'fld1'      =   'WandW Subscription',
'date'      =   date_format(date, -format='%D'),
'time'      =   date_format(date, -format='%T')
);
#innum = field('innum');        //Pickup auto increment value
/inline;

New L9 code using DS (truncated a little for display):
subs_ds->keycolumn('innum')     //innum is auto increment
->addrow(::subs,
map(
::cName     =   postparam('fname') + ' ' + postparam('lname'),
::address   =   postparam('sadd'),
::city      =   postparam('city'),
::time      =   date_format(date, -format='%T'),
::adcost    =   $cost,
::fld1      =   'WandW Subscription'
)
$innum = ::innum->asstring  //Pickup auto increment value - doesn't work :(
)

Is this possible? Do I need completely rethink the process (trying to convert, not reinvent!)

Marc

====================
Marc Pinnell
Director of Web Services
[hidden email]
www.shasta.com                                     833 Mistletoe Lane, Suite A1
Redding, CA  96002
530-224-6866  Ext. 100
530-224-2035 Fax


#############################################################

This message is sent to you because you are subscribed to
the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy              Website Builder              Soquel, CA
<[hidden email]>               <http://www.stevepiercy.com/>


#############################################################

This message is sent to you because you are subscribed to
the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>


====================
Marc Pinnell
Director of Web Services
[hidden email]
www.shasta.com
833 Mistletoe Lane, Suite A1
Redding, CA  96002
530-224-6866  Ext. 100
530-224-2035 Fax



------------------------------

Message: 5
Date: Sun, 24 Jul 2016 19:49:51 -0700
From: Jerad Hoff <[hidden email]>
To: [hidden email]
Subject: Looking to move up from LP 8.5.6
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8

Greetings,

I have helping a non-profit out for the past 5-6 years writing little solutions here and there in Lasso 8.5.6 running on a old mac mini of mine. We?ve decided it?s time for them to get their own server to partially reduce the ?hit by a bus? scenario if I disappear and my server goes with me (there?s also the issue where I?m using software nobody has heard of, but at least it will run until they can find a volunteer to re-write it in php or whatever). I?m worried about trying to get 8.5 running in the latest linux or Mac OS (not sure yet on the server type).

I started with Tango, moving over to Lasso 2.5 back in the day. Anyway, I never advanced to the LassoScript stuff, I?m still an old-school put everything in brackets kind of guy. I mention this because I?m trying to figure out why Lasso 8.6 is still for sale when 9.3 is out in the wild. Are there issues moving to 9.x when upgrading 8.x sites that 8.6 needs to remain available? I?m a little confused by 8.6 and 9.3 both being available and both costing the same.

Also I see now that the licenses include ?instances? of the software. Does this mean if I get three instances with my license, I can run one of the instances on a completely different server as a backup? Or do all of the instances need to remain one one computer?

That said, is this worrying for nothing? Can I simply move my 8.5 license to a newer server running the latest linux or Mac OS and will it still work? I?m almost done ditching FMP as a datasource, so that won?t be a worry any longer.

Thanks for the advice guys!

  - Jerad



------------------------------

Message: 6
Date: Sun, 24 Jul 2016 21:56:14 -0600
From: Tom Parker <[hidden email]>
To: [hidden email]
Subject: Re: Looking to move up from LP 8.5.6
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi Jerad,

I do not often post here, but I am replying to you because I am probably
more in your situation than others who post frequently on this list.

(Preface: I remain forever grateful to the Treefrog/ new LassoSoft folks
who have kept Lasso alive as long as they have, and these suggestions
are not in any way intended to disrespect what you have done for Lasso.)

I have a large web-based commercial software application that has been
Lasso-based since 2001.  It is currently running on Lasso 8.6 because it
would have taken too much time to convert it to Lasso 9.x.  When/if it
needs a new cycle of development, we will rewrite it in a different
language such as Python or php.  Lasso 8.6 and 9.3 are (in my mind)
essentially different languages because it takes significant work to get
a complex 8.6 site to work completely in 9.3 (I have never accomplished
it despite having succeeded at developing several complete applications
in previous versions of Lasso), so when we considered the next language,
we evaluated 9.3 as if it was a completely different language and chose
not to pursue it.

I also have two internal applications I use to run my business--both are
running on 8.6.  I joined the Certified Lasso Developer (CLD) program (I
think that is what it is called) whenever Treefrog took over Lasso, and
that costs $49/month and you get three instances of whichever Lasso
version you prefer and you can use those instances on different
servers--which I think is more flexible than the normal subscription.
The "test" to become a CLD is fairly trivial, easy to pass, if you have
built anything in Lasso and can Google for obscure questions.

However, I will be having a college student convert these internal
applications to python or php later this summer as I am worried about
future server operating systems supporting Lasso 8.6.

I taught my son how to program using Lasso when he was 11, and he has
built a few applications since then.  This summer, he used Lasso and
other tools to build an interactive spatial database cataloguing music
composers in Paris during the 1920's and accounting for how history and
geography influenced their compositions.  I was letting him use one of
my servers which had Lasso 8.6 running on it, but the University where
he is interning was not interested in supporting a subscription-based
software to run their interactive web site so he rewrote the Lasso
portions in php, which was fairly painless apparently.  I'd advise you
to go this route.

You should contact LassoSoft directly (not via this list) and ask them
about their plans for Lasso, if you are considering trying to stay with
Lasso as your language.

Good luck,

--Tom Parker




On 7/24/2016 8:49 PM, Jerad Hoff wrote:
Greetings,

I have helping a non-profit out for the past 5-6 years writing little solutions here and there in Lasso 8.5.6 running on a old mac mini of mine. We?ve decided it?s time for them to get their own server to partially reduce the ?hit by a bus? scenario if I disappear and my server goes with me (there?s also the issue where I?m using software nobody has heard of, but at least it will run until they can find a volunteer to re-write it in php or whatever). I?m worried about trying to get 8.5 running in the latest linux or Mac OS (not sure yet on the server type).

I started with Tango, moving over to Lasso 2.5 back in the day. Anyway, I never advanced to the LassoScript stuff, I?m still an old-school put everything in brackets kind of guy. I mention this because I?m trying to figure out why Lasso 8.6 is still for sale when 9.3 is out in the wild. Are there issues moving to 9.x when upgrading 8.x sites that 8.6 needs to remain available? I?m a little confused by 8.6 and 9.3 both being available and both costing the same.

Also I see now that the licenses include ?instances? of the software. Does this mean if I get three instances with my license, I can run one of the instances on a completely different server as a backup? Or do all of the instances need to remain one one computer?

That said, is this worrying for nothing? Can I simply move my 8.5 license to a newer server running the latest linux or Mac OS and will it still work? I?m almost done ditching FMP as a datasource, so that won?t be a worry any longer.

Thanks for the advice guys!

   - Jerad


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>




------------------------------

Message: 7
Date: Mon, 25 Jul 2016 19:00:00 +1000
From: Rick Draper <[hidden email]>
To: [hidden email]
Subject: Ping
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Does my email to this list still work?

Very best regards

Rick Draper



------------------------------

#############################################################
This message is sent to you because you are subscribed to
 the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>


End of Lasso Digest, Vol 61, Issue 6
************************************


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lasso Digest, Vol 61, Issue 6

Rachel Guthrie

> On Jul 26, 2016, at 12:52 PM, Yescas, Alejandro <[hidden email]> wrote:
>
> Will Lasso ever be Open-Source ?….it currently seems abandoned.

Hi Alejandro, not, it is not abandoned as you can see there is still active development going on around the world. A lot of the discussion has moved to real-time chat on gitter, however the great thing about gitter is that you can readup on what was discussed even while you were not logged in. I know many developers are loving that feature.

Lasso 9.3.2 has a new beta out at the moment, and should be a full release shortly.

Lasso going open source is something that has been discussed every couple of years. There is thinking about the potential positive and negative impacts this would have, and no defined position change at this time. We value our security, and Lasso was not designed with open source in mind.

Happy coding!

Rachel Guthrie
LassoSoft

>
> On Jul 25, 2016, at 2:00 AM, [hidden email]<mailto:[hidden email]> wrote:
>
> Send Lasso mailing list submissions to
> [hidden email]<mailto:[hidden email]>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://newlists.lassosoft.com/cgi-bin/mailman/listinfo/lasso
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lasso digest..."
>
>
> Today's Topics:
>
>  1. Re: Mailchimp API v3.0 (Black Night Lists)
>  2. Converting Classic L8 Inline to L9 & DS - Return Key Value?
>     (Marc Pinnell)
>  3. Re: Converting Classic L8 Inline to L9 & DS - Return Key
>     Value? (Steve Piercy - Website Builder)
>  4. Re: Converting Classic L8 Inline to L9 & DS - Return Key
>     Value? (Marc Pinnell)
>  5. Looking to move up from LP 8.5.6 (Jerad Hoff)
>  6. Re: Looking to move up from LP 8.5.6 (Tom Parker)
>  7. Ping (Rick Draper)
>


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lasso Digest, Vol 61, Issue 6

Jonathan Guthrie
I’d also like to point out that Kyle is still around, I’m still around (although I don’t post from a lassosoft.com <http://lassosoft.com/> address anymore…). Eric’s still here - however he’s as quiet as a mouse.
And of course, Sean’s still got wildly coloured hair.

If you pop onto the Gitter channel Rachel mentioned, you might be surprised at what you find!

Thanks
Jono

> On Jul 29, 2016, at 1:23 PM, Rachel Guthrie <[hidden email]> wrote:
>
>> Will Lasso ever be Open-Source ?….it currently seems abandoned.
>
> Hi Alejandro, not, it is not abandoned as you can see there is still active development going on around the world. A lot of the discussion has moved to real-time chat on gitter, however the great thing about gitter is that you can readup on what was discussed even while you were not logged in. I know many developers are loving that feature.


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lasso Digest, Vol 61, Issue 6

John May-2
Do you have a link to said Gitter channel?  All I found was some
Javascript thing named Lasso (trademark infringement?).

        - John


On 7/29/16 2:32 PM, Jonathan Guthrie wrote:

> I’d also like to point out that Kyle is still around, I’m still
> around (although I don’t post from a lassosoft.com
> <http://lassosoft.com/> address anymore…). Eric’s still here -
> however he’s as quiet as a mouse. And of course, Sean’s still got
> wildly coloured hair.
>
> If you pop onto the Gitter channel Rachel mentioned, you might be
> surprised at what you find!
>
> Thanks Jono
>
>> On Jul 29, 2016, at 1:23 PM, Rachel Guthrie <[hidden email]>
>> wrote:
>>
>>> Will Lasso ever be Open-Source ?….it currently seems abandoned.
>>
>> Hi Alejandro, not, it is not abandoned as you can see there is
>> still active development going on around the world. A lot of the
>> discussion has moved to real-time chat on gitter, however the great
>> thing about gitter is that you can readup on what was discussed
>> even while you were not logged in. I know many developers are
>> loving that feature.
>

--

-------------------------------------------------------------------
John May : President                   http://www.pointinspace.com/
Point In Space Internet Solutions         800.664.8610 919.338.8198

         Professional FileMaker Pro, MySQL, PHP & Lasso Hosting
           on shared, virtual and hardware dedicated servers


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lasso Digest, Vol 61, Issue 6

Jonathan Guthrie
https://gitter.im/LassoSoft/LassoChat <https://gitter.im/LassoSoft/LassoChat>

Note that Gitter works in closely with GitHub repos - we use it for chats based on certain other repos…

Jono

> On Jul 29, 2016, at 2:39 PM, John May <[hidden email]> wrote:
>
> Do you have a link to said Gitter channel?  All I found was some Javascript thing named Lasso (trademark infringement?).


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Loading...