Tuesday, December 13, 2005

Scan through the web?

Rodolfo raised a question about UMIT going web. This project was developed with the MVC aproach predicting the development of new interfaces for the UMIT engine. So, UMIT can have a web or even a text based interface (maybe with ncurses?).

I'm not sure if it is time to develop these interfaces for the next release. If someone wants to apply for the job, it would be great!

I think that now it's time to discuss what web development tools we have to make this interface, and which one is better for case. Would be Zope? Turbo Gears? Django? or just Mod Python? What do you think it's better? Leave me a comment!

Fyodor sent me some suggestions and thoughts about what he wanted to see on and some issues found on the interface. I´m working on his suggestions also.


  1. Hey Adriano,

    I'm biased, as a Django core developer, but I'd say Django is your best bet. It makes things simple and gives you all sorts of convenient niceties for free.

    Feel free to e-mail me directly if you have any questions.


  2. Depends on how much you want decided for you. I've found Myghty gives you an incredible amount of flexibility and makes very few decisions for you.

    For example, Myghty lets you design page-driven sites, or MVC sites. You can use any ORM you want or none at all, you have full control over the flow, etc.

    I'm working on whats essentially a highly customized Myghty setup, called Pylons that makes a few more decisions for you. It dispatches to a Controller using my Routes port, includes useful helper functions, great functional testing (using Ian Bickings Paste Fixture and Eval Exception projects), and emphasizes easy deployment (Using Python Paste).

    Pylons is still a few weeks a way from an initial release, though since its just a slight customization of Myghty I'd consider it rather stable right now.

    I'm obviously biased of course, Django and TurboGears are both great choices too and make different trade-offs as they're full-stack frameworks. In Pylons we tried to focus on good defaults for a full-stack framework, but exposing all the hooks to make it easy for a developer to tweak it out however they want it to work.

  3. Hoooowwwddddyyyy-Hoooo!!!!