From 4ef04f461f3bf23838632168de51cd3cc0c59f8f Mon Sep 17 00:00:00 2001 From: Hauke D Date: Sun, 17 Feb 2019 13:09:37 +0100 Subject: [PATCH] Updated Notes with To-Do's and Talks --- notes.md | 30 ++++++++++++++++++++++-------- 1 file changed, 22 insertions(+), 8 deletions(-) diff --git a/notes.md b/notes.md index 78c5648..464fd8f 100644 --- a/notes.md +++ b/notes.md @@ -20,13 +20,17 @@ Other places I've written about WebPerl: - [Embedding WebPerl Code Demos into Other Pages](https://www.perlmonks.org/?node_id=1223812) - [WebPerl now has Experimental Perl 6 Support!](https://www.perlmonks.org/?node_id=1225647) -I also gave a [lightning talk](http://act.perlconference.org/tpc-2018-glasgow/talk/7475) -at YAPC::EU 2018 in Glasgow: [Video Link](https://youtu.be/KrGSg7uVZj0?t=29520) +Talks: + +- YAPC::EU 2018 in Glasgow - [lightning talk](http://act.perlconference.org/tpc-2018-glasgow/talk/7475), [Video Link](https://youtu.be/KrGSg7uVZj0?t=29520) +- *(planned)* German Perl Workshop 2019 - [talk](http://act.yapc.eu/gpw2019/talk/7616) (in German 🇩🇪) +- *(hopefully)* YAPC::EU 2019 ([PerlCon](https://perlcon.eu/)) in Rīga [![DOI 10.5281/zenodo.1400490](https://zenodo.org/badge/DOI/10.5281/zenodo.1400490.svg)](https://doi.org/10.5281/zenodo.1400490) -### In the Press +### "In the Press" +- WebPerl gets a mention in Will Braswell's talk ["Perl 11 - The Future of Saint Larry's Language"](https://fosdem.org/2019/schedule/event/perl11/) - [Perl Advent Calendar 2018, Day 2](http://www.perladvent.org/2018/2018-12-02.html) (by Mark Fowler) - [Reddit: Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should (2018-10-22)](https://www.reddit.com/r/programmingcirclejerk/comments/9qerw5/your_scientists_were_so_preoccupied_with_whether/) 😉 - [Hacker News (2018-10-21)](https://news.ycombinator.com/item?id=18269071) @@ -40,34 +44,44 @@ TODOs 1. Testing + - How to best disable individual tests that we know won't work? (qx etc.) + - How to handle the many tests that call an external Perl? + - patching t/test.pl's runperl() seems easiest at the moment, and we can use the iframe method from the IDE - Continue work on `WebPerl.t` - More tests for Unicode support (Perl/JS interface, Perl.eval(), plus Emscripten's virtual FS) - Focus on getting the tests running in the browser instead of node.js - How to best package tests? - If possible, a separate bundle, so that it can be loaded optionally and we don't need to rebuild - How does `make test` find and handle all the various modules' `t`s? - - How to best disable individual tests that we know won't work? (qx etc.) - - How to handle the many tests that call an external Perl? - - patching t/test.pl's runperl() seems easiest at the moment, and we can use the iframe method from the IDE 2. Misc - Write up a full RPC example + - Add `Future` to the WebPerl build for a little more async niceness? + - Would `Future::AsyncAwait` work in WebPerl? (Or maybe with a JS backend?) + - `Future::HTTP` (probably just as a frontend to XHR?) + - Improve Perl 6 integration + - Build a packaged Rakudo.js ourselves instead of borrowing from + - Perhaps get an API change or two into Rakudo.js: `STDOUT` currently gets output with HTML escapes + - See also notes in [Perl 6 Support 🦋](perl6.html) - Investigate Emscripten's main loop concept for handling nonblocking sockets? - Turn some patches from emperl5 into patches for P5P - Submit some patches to Emscripten - - - Would we need to patch Perl's signal functions if Emscripten's stubs weren't noisy? - - Add Perl.Util functions for making file uploads and downloads easier + - Add `Perl.Util` functions for making file uploads and downloads easier - Plus an example showing how to use it to run a "legacy" Perl script with inputs and output - - Perhaps create a CPAN Bundle:: module or similar for `build.pl` deps? - There is some potential for restructuring: - `Perl.glue()` and `Perl.dispatch()` could go into `WebPerl.xs` (?) - Parts of `webperl.js` could go into `common_preamble.js` or `WebPerl.xs`, so that `emperl.js` is runnable on its own in a Web Worker (?) (see notes in `perlrunner.html` / `e12f1aa25a000`) - `nodeperl_dev_prerun.js` could probably be merged into that as well + - Could put a `WebPerl` stub on CPAN + - In theory could write a `WebPerl::Local` that contains the `WebPerl` API, and + have various drivers such as `WebPerl::WebDriver` or `WebPerl::JSAny` that + runs the code given to WebPerl's `js()`... - Regarding the funky syntax highlighting on GitHub: 3. See Also