Create example for running the converter client side instead of from node.
bafolts opened this issue · comments
Since the code base is in javascript the code should run just fine from any browser. This will allow applications to convert code on the client side as well as the server side. The code shouldn't have to be re-factored much. Most likely just some controller class created to run the conversion and retrieve the results.
I think that is a great idea, but I would hope that the command line interface does not change. I will need to keep running it from the server using my node.js server wrapper so I can log and run other related code on the server that will not run be able to run directly in a browser.
Server side wont change, the client side api will just enable more use cases. It will really just be a glorified wrapper of what you can do on the command line, but through some javascript module that can be accessed like any other module.
Sounds good.