6.c compatibility

[zaucker]

Most of the examples are not compatible with the christmas release. It would be very helpful to have working examples for supplies and also GTK::Simple.

[jnthn]

They also pre-date the supply/react/whenever syntax, so will want a re-work
for that too in various cases. Anyways, fixing these is on my todo list.

In the meantime, my ongoing blog series on building an async STOMP
Client/Server implementation is also a good source of information and
examples; it's appearing at https://6guts.wordpress.com/.

On Mon, Jan 11, 2016 at 10:56 PM, Fritz Zaucker [email protected]
wrote:

Most of the examples are not compatible with the christmas release It
would be very helpful to have working examples for supplies and also
GTK::Simple

—
Reply to this email directly or view it on GitHub
#2.

[zaucker]

Thanks. I am following your blog on STOMP.
I was mainly interested to get the golf-helper example to work as it would be a good starting point for a first useful Perl6 project I could demonstrate to my co-workers here.
After changing schedule_on() to schedule-on() in the golf-helper code it fails with
Invalid GV status observed; aborting
Something beyond my current abilities to fix, I think. I guess I'll just wait until you get around to this.
Thanks for all your efforts in any case.

[zaucker]

Any chance of a working example with current technologies?

[jnthn]

Updated various of the sample applications today, plus added a README.md for the two larger ones noting how to use them. The GUI one now uses the GTK::Simple module from the ecosystem, plus the NativeCall bundled in Rakudo, rather than containing a local copy of both. :-)

[zaucker]

Cool! Thanks, Fritz

…

Sent from my iPhone

On 25 Sep 2017, at 19:53, Jonathan Worthington ***@***.***> wrote: Updated various of the sample applications today, plus added a README.md for the two larger ones noting how to use them. The GUI one now uses the GTK::Simple module from the ecosystem, plus the NativeCall bundled in Rakudo, rather than containing a local copy of both. :-) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.