So far the only reason behind having mooshell in PHP is that it is easier to code with.
> I can't see any reason why it couldn't equally be developed with php I also can't see any reason why it couldn't equally be developed in Haskell.... or Java, RoR, Keppler, Perl, Fortran (eeeh no - take it back- no Fortran), name it. But I see the reason why it was done in Django. I like it that way. Well you know - I've been there (in the PHP world) for like 6 years (was it 8?) and since a year I'm using Django (day to day). I may tell you - I think PHP is to backend as jQuery is to JS - easy to learn, hard to really master. I actually found learning mootools and Django very similar - They both are more complicated on the beginning, but after a bit of learning (few days of fun) they are just awesome. When I have to go back to support old PHP sites with jQuery or Prototype I have a headache. Django/Python is very well documented, language is well structured, code is way cleaner just because it is thought out properly. Well what can I say more? Aaah there is a Python to Mootools class translator (not that it was used in MooShell). I'm not here to convince anyone to Django, but I see no point in rewriting the whole tool to a different language just because it is easier to someone. If you want to contribute to MooShell you may take it as a good excuse to learn another language - there's never enough of them once you start. MooShell is written as a Django application and may be added to an existing Django project pretty easily. It works like a plugin. Integrating it takes minutes. Regardless the database behind. There is only one framework into which I would consider to rewrite MooShell just to proove the point it can be done. Raccoon http://raccoon.keetology.com/ If you want to contribute to front end you don't have to know Django/Python: http://wiki.github.com/zalun/mooshell/html-js-css (please do) Installation is now a step by step process: http://wiki.github.com/zalun/mooshell/installation Regards zalun --
