Re: xAPI in LiveCode with xAPI Cohort Meeting #2 2/10/21 1:30 EST to 4 PM EST

[Brian K. Duck via use-livecode]

I’m hopeful that you will be able to attend part, or all, of this meeting time.

Please continue to mark your availability in When2Meet, url below. 
> https://www.when2meet.com/?10983382-E3NWh 
> 
There is another opportunity tomorrow for meeting time from 1:30 PM to 4 PM 
EST. The times are broken into 1/2 hour blocks within When2Meet, and there is a 
maximum of 2 people that have conflicts. Based on the information in When2Meet, 
I have blocked time in zoom starting 2/10 at 1:30 PM EST.

As I am in possession of a free Zoom account, the meeting scheduling is limited 
to 30 minute blocks. I will update the xAPI Cohort Slack for 
Team-xAPI-in-LiveCode with zoom credentials during the event.

I will also paste the follow on Zoom meetings into the chat during the meeting.

The FIRST block of Zoom meeting is here:

Topic: xAPI in LiveCode #2 Zoom Meeting, Part 1 
Time: Feb 10, 2021 01:30 PM America/Detroit

Join Zoom Meeting
https://us04web.zoom.us/j/71113499164?pwd=OE9ERTMwZ09iZityTlVPOS9JVVl2Zz09

Meeting ID: 711 1349 9164
Passcode: m465Fz

During this time, we'll recap what we covered in Meeting #1, ask for 
introductions, and look at the strategy of using LiveCode as a Learning Record 
Provider.  With the added time, we may be able to open the LiveCode project and 
discuss how LiveCode is sending a statement to the LRS.

This meeting will be recorded for those who cannot attend, or will be offline 
for part of the meeting.

Brian

Bduck a t Mac do t 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

Re: Close Stack Cleanup

[Curry Kenworthy via use-livecode]

Jacque:

> I did a test before answering and the message was sent to the card
> of my otherwise blank stack, after dismissing the IDE dialog.

Same here!

Bob:

> there have been at least 2 versions that were unstable that crash
> to desktops were not uncommon, and after losing so much data, I
> save frequently, and auto save whenever I close a sub stack.

I agree, saving carefully/saving "big-league" is a must for LC IDE! :)
Got in the constant-save habit way back with version 1.1.1.
(Which had a tendency to vanish in the middle of a coding session.)

Here's what I do (and it all works, no message problems, no bugs):

1. If I edit any script, I manually save when I apply changes.
(I don't write more than 3 lines of code before saving.)

2. If I edit any UI or properties, I manually save.
(I save every 5 minutes or less, and before leaving a dirty card.)

3. Before I close any stack I've edited, I MANUALLY save.
And if I use auto-clean, it's hooked up to saveStackRequest. Reliable.
No message difficulties. And I know it's saved.*
(If I forget to save, it warns me. That's my backup if habit fails.)

4. *For each of the above, #1-#3, I look for the dialog while saving.

5. *And every session (and before closing an edited stack) I look at the
stack in the Finder/Desktop to check the Mod date. I also make a copy.
("Sorta trust, but verify the heck out of it." There can be the known
disassociated-SE, or other bugs, that prevent IDE from really saving.)

6. *If in step #4 or #5 I find that it wasn't really saved,
I can save again or take any other necessary steps I deem appropriate,
because ... I have NOT closed the stack yet! That's why.
I intentionally save, then double check, then intentionally close.

IOW, If you and I don't trust the IDE enough to let it decide when we
should save (which is a big part of the reason this thread exists) ...

... then why should I trust it to SAVE FOR ME when I close a stack?
To me, that seems risky, plus it's not building on the same premise.

Even if the IDE did NOT have a known bug (or complication) and even if
the close message DID usually work, I would still save manually,
each and every time before closing a stack. That way I know.

(LC IDE should be more reliable, yet there is a silver lining:
it has taught me to save more carefully in EVERY app!
Because the idea of a completely reliable app instance is fantasy;
the computer itself could have a hardware or OS failure at any moment.
My manic LC save habits have "saved" me in other apps, more than once.)

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

Re: xAPI in LiveCode with xAPI Cohort

[Martin Koob via use-livecode]

Hi Brian

I can jump in just for a half hour today.  I have other work meetings all day.

see you then.

Martin

> On Feb 9, 2021, at 2:15 AM, Brian K. Duck via use-livecode 
>  wrote:
> 
> Please continue to mark your availability in When2Meet, url above. Based on 
> early responses, our first opportunity to meet will be today at 12:30 EST.  
> Here is a zoom link: Topic: xAPI in LiveCode Cohort #1 - Zoom Meeting
> Time: Feb 9, 2021 12:30 PM America/Detroit
> 
> Join Zoom Meeting
> https://us04web.zoom.us/j/75593825050?pwd=Wklta3FhckZGU213OEtoUFVwTzNGZz09
> 
> Meeting ID: 755 9382 5050
> Passcode: 2CQm0k
> 
>> On Feb 8, 2021, at 3:26 PM, Brian K. Duck  wrote:
>> 
>> The xAPI Cohort has launched, we’re preparing to meet live over the next 
>> week.
>> 
>> Please use this link to register your availability:
>> 
>> https://www.when2meet.com/?10983382-E3NWh
>> 
>> Brian Duck
>> Bduck at Mac do t 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