Open davehodg opened 5 years ago
Thanks for the suggestion, the web
directory is indeed starting to get a little cluttered - I will think about how to best reorganize things. Maybe one directory per example... we'll see.
There are a few tests... https://github.com/haukex/emperl5/blob/emperl_v5.28.0/ext/WebPerl/WebPerl.t, plus the tests from Perl's core test suite that I've been able to run manually. It's not easy to do, since a significant number of the core tests use features like signals or qx//
that WebPerl doesn't support. I definitely want to get a fair number of those tests passing before I take WebPerl out of "beta". Selenium or similar tests are a good idea too. I've been keeping a To-Do list with some notes on testing here: https://webperl.zero-g.net/notes.html#todos
As for the other suggestions, WebPerl isn't on CPAN and isn't really like other dists... the build process is quite complex, I'm not sure how EUMM could really help? As for installation, people would be putting the build products into their webservers, I don't think the regular Perl install tools can really help there...
Can we structure things to look like other dists?
A lib/ directory for modules html/ for HTML js/ for JavaScript css/ for CSS. .psgi in the root or a bin/ directory t/ for tests. We do have tests, right? Maybe we could work in some Selenium tests?
Use ExtUtils::MakeMaker to tie everything together. Perhaps in the hope we might one day install things. And run tests.