Looks like work was started for adding encoding functions to LCB:
https://github.com/livecode/livecode/blob/develop/libscript/src/encoding.lcb
https://github.com/livecode/livecode/blob/develop/libscript/src/module-encoding.cpp
Looking at the C source, looks like error reporting is needed along
On Sat, Oct 20, 2018 at 5:26 AM AndyP via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Also for the bug fix note, you can also create one directly in GitHub,
> using
> the 'Create new file' button. Just make sure that you are in the *correct
> branch* on your *own fork of LiveCode*.
>
On Fri, Oct 19, 2018 at 4:01 PM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Something to remember, everyone, is even if you have no idea what you're
> doing, you probably can still help. Fixing something in docs is a great
> way to start.
> • There are a bunch of
On Fri, Oct 19, 2018 at 10:52 AM AndyP via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I was just about to add notes on adding the bugfix note from my experience
> as
> a first time contributor, and then what! you've already made a video about
> this.
>
> Excellent.
>
> It would be
> Malte P. wrote:
> Hey HH!
Hey Malte!
> 1) This is amazingly fast!
The judgement of the master of animations ...
The speed too blew me away the first time it worked.
Everything is done by computing and applying an
affine transform for the canvas.
> 2) Where do I put the money for the help
Hey HH!
1) This is amazingly fast!
2) Where do I put the money for the help fund?
3) How does LCB compare to JS speed wise?
4) Thanks so much for all your contributions!!!
Cheers!
Malte!
___
use-livecode mailing list
use-livecode@lists.runrev.com
Yes, the docs are a great introduction way in for contributing to LiveCode
and for using GitHub.
I've learned a lot from the experience so far with some gentle but
instructive nudges from Panos.
Also for the bug fix note, you can also create one directly in GitHub, using
the 'Create new file'
