search

asmblah / uniter

🎉 PHP in the browser and Node.js => Docs: https://phptojs.com/
https://asmblah.github.io/uniter/
Other
446 stars 42 forks source link

Beta #46

Open phpengine opened 7 years ago

phpengine commented 7 years ago

Uniter is described as being in beta state. Is there anything I can do to help bring it into what you'd call beta, alpha, RC, 1.0, etc. ?

asmblah commented 7 years ago

That's a good question - I had been holding off on removing the "alpha" label on https://asmblah.github.io/uniter/demo/interactive.html until a few more language features had been implemented, but perhaps that doesn't make sense anymore.

The main thing I'd like is to have better documentation/examples for how people can get set up and start building web apps with Uniter - eg. an example Browserify/Webpack config, etc. Perhaps as a first step, some better content for https://github.com/asmblah/uniter/blob/master/README.md?

[For a bit of background] I've been looking at improving the language and standard library support to the point where it can be used for "real-world" applications - for a project I'm working on at the moment, I've needed support for some of the Symfony components (config, dependency injection, event dispatcher, translator etc.) so I've been focusing on adding some of the language features and standard library functions that those need. A lot of these changes haven't been published to NPM yet, but you can see some of them in the commits for PHPCore (https://github.com/uniter/phpcore/commits/master), eg. https://github.com/uniter/phpcore/commit/122f96f63beb68e8678254c23e020aa512dd5cb2. I still need to pull all of these into the main Uniter project and rebuild the prebuilt .js bundle that's there, it's getting a little out of date now.

Thanks!

asmblah commented 7 years ago

I've just been reading through the GH issues that are still outstanding - does anybody think that condensing all the various repositories for the different packages (phpcommon, phptoast, phpcore, phpruntime, phpify, dotphp etc.) down into a monorepo, as Babel do, is not a good idea? I'm planning on doing exactly that in the very near future, which (along with some better documentation) will hopefully make it easier for people to contribute, eg. adding support for some missing standard library functions like metaphone() (as an example).

/cc @IngwiePhoenix @systemovich