I just want to throw my hat in and say that there's no reason to re-author this in PHP. It's a great excuse to learn Python if you haven't already, getting it running is pretty simple, and the Django/Python docs are free and online. It would be one thing if we intended people to deploy this thing (like the Depender app), but that's not its purpose. Reauthoring it in another language so that we don't have to learn a new one isn't a great reason to double our work and essentially split the project.
2009/10/27 Fábio M. Costa <[email protected]> > The installation instructions are to make it run locally. If you want to > run it on a server you will need to install mod_python or use wsgi, it can > be tricky. But you dont need to install it on a server if you just want to > contribute anyway. > > > -- > Fábio Miranda Costa > Solucione Sistemas > Engenheiro de interface > > > On Tue, Oct 27, 2009 at 10:26 AM, Ryan Florence <[email protected]>wrote: > >> >> I just don't feel that it is anywhere near as simple as you might >>> think to somebody who has no experience in: python, Django or server >>> administration. >>> >> >> Django and similar frameworks do have an enormous hump for many. >> >> Believe me, it's worth it. >> >> Again, I don't do anything in Django but I know it's really similar to >> Rails. I can do stuff in rails in 10 minutes what took me 10 days in php. >> It'll be worth your time to figure it out. >> >> >> Ryan Florence >> >> [Writing TextMate Snippets] ( http://blog.flobro.com/ ) >> >> On Oct 27, 2009, at 6:22 AM, cbolson wrote: >> >> >>> So far the only reason behind having mooshell in PHP is that it is >>>> easier to >>>> >>> code with. >>> And that is why it makes sense to me :) >>> >>> 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. >>>> >>> Absolutely, I wasn't trying to suggest that it *should* be programed >>> in php, only that it would be possible. >>> The only reason *I* would like it in php is that *I* could jump in and >>> take a look at it easily without having to learn a new language. >>> >>> 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. >>>> >>> Of course not, I don't think that anyone was suggesting that you >>> did :) >>> >>> Installation is now a step by step process: >>>> http://wiki.github.com/zalun/mooshell/installation >>>> >>> I have taken a look at that and must admit to not having understood >>> pretty much any of it :( >>> It all looks like server-admin stuff to me, an area which I have >>> absolutely no knowledge in. >>> I don't have adminstrator rights to my hosting server and I wouldn't >>> know where to start if I did. >>> >>> Let it be said that I realise that all these factors are MY short >>> comings, this is not a problem with mooshell (in any way), Django or >>> Python. >>> I just don't feel that it is anywhere near as simple as you might >>> think to somebody who has no experience in: python, Django or server >>> administration. >>> >>> Thanks for you time and for your comments :) >>> >>> Chris >>> >>> >>> On 27 oct, 12:58, Piotr Zalewa <[email protected]> wrote: >>> >>>> 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. Raccoonhttp:// >>>> 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<http://wiki.github.com/zalun/mooshell/html-js-css%28please> >>>> do) >>>> >>>> Installation is now a step by step process: >>>> http://wiki.github.com/zalun/mooshell/installation >>>> >>>> Regards >>>> zalun >>>> -- >>>> >>> >> >
