> On 17 Jul 2015, at 17:21, Sean P. DeNigris <s...@clipperadams.com> wrote: > > Noury Bouraqadi-2 wrote >> The main difference is that with PharoJS we develop and test in Pharo, >> with the confort of all cool tools such as the GT inspector, spotter :-) > > Wow!!! That is my main pain point with Amber. Unless one is very disciplined > with TDD, the linkage between the app loaded in the browser, and Helios > loaded in a separate window, introduces a run-compile-like cycle where after > every change, one has to reload the app which reloads the IDE, and you lose > all current state e.g. workspaces, etc. > > How mature is PharoJS? Is anyone using it in production? Who are the core > developers? What are the intentions e.g. toy? experiment? > production-quality? next big thing? > PharoJS is a side project I started early May this year as an experiment. But, after few weeks I noticed that it can cover a significant subset of Pharo. As I showed at ESUG (we missed you BTW), it allows building a simple form app for smartphones using PhoneGap.
So, I shifted my goal, and decided to make it clean and usable for production-quality app. Fortunately, I won't be alone. Torsten Bergmann and Dave Mason kindly offered their help and joined the project since few days. Regarding the status, PharoJS is usable, but I don't recommend to use it for production right now. It is not polished and parts are likely to dramatically change in the forthcoming weeks. We also need to expand the documentation. Lot of stuff to do, but I'm very excited about it :-) Still, you can give it a try. There is a first tutorial that gives a quick overview. More to come. Noury
