Catwalk2 is much more integrated with TG2 than Rum is. There are some features built into Rum that are not yet in Catwalk, but I am sure Alberto/Michael can comment on that more than I can. Catwalk is built with Sprox, and TW and some dojo if you have tw.dojo installed. Rum is currently only running as HTML, but I know Alberto has plans to expand on his JavaScript support. Rum is more configurable than Catwalk, but I believe it takes a small amount more effort to install.
As for configurability, big things are coming to Catwalk. Catwalk is to become a tg-quickstart-specific configuration of tgext.admin. tgext.admin is a completely configurable admin system. You give it your models, and it provides a complete crud system, where every part of it is overridable. Everything from the main template to the validators for each field. Also, tgext.admin uses your default genshi templates by default, so the look-and-feel of your admin will match that of your site. tgext.admin already supports dojo tables, which means you get sortable, orderable fields, and infinite record numbers in the same table. Beyond that, since tgext.admin and Catwalk are both based on sprox, it is easy to re-use your knowledge using components of sprox directly in your application. This is akin to django newforms being used in django admin. Sprox also provides a new FillerBase class which helps you create reasonable jsonification, which has been a challenge with TurboJson, which can sometimes have idiosyncrasies. Lastly, the documentation for Sprox, tgext.admin, and tgext.crud (which tgext.admin uses) is intended to be world-class. I believe the docs at www.sprox.org are coming along, and I am currently in development of tgext.admin docs. Here is a sneak preview: http://tgtools.googlecode.com/svn/projects/tgext.admin/trunk/docs/source/images/class_diagram.png I believe there is a place for both technologies in the TG stack. We have made the decision to work independently for the time being, as the goals of our projects are a little different. Sprox is intended to be a little more tg-oriented (although it can be used completely outside the TG stack with no problems), and therefore drive the development process of TG a little bit. We already have RestController, @with_trailing_slash and a couple of other decorators that I just havn't had time yet to integrate into the tg source. Sprox is also user-friendly, relies on standard pythonic ways of manipulating widgets. Concepts such as extension and encapsulation are all that is needed to create your own stand alone forms using Sprox. I'm not going to state the goals of Rum, only that they are different than Sprox's for these things. Hope this helps you. cheers. -chris On Jan 20, 7:53 pm, Lukasz Szybalski <[email protected]> wrote: > Hello, > So I was wondering what are some differences in catwalk2 admin > interface vs rum admin interface. > > The reason I'm asking is that both seem to do the same, provide admin > interface for add/edit/view/delete of the identity stuff. I like rum > better because it can take the master template and bland in the admin > interface into the original template. Since this is not that > scientific I was wondering if you guys could shade some light at what > other differences are there? > > 1. How can I expend the admin interface to users, and manage who can > edit what catwalk2 vs rum? > 2. What are some use cases? Differences in use depending on type of > application? When would I use catwalk2 vs rum? Are they both > interchangeable without differences? > > Thanks, > Lucas > > -- > How to create python package?http://lucasmanual.com/mywiki/PythonPaste > Bazaar and Launchpadhttp://lucasmanual.com/mywiki/Bazaar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
