On Thu, Dec 18, 2008 at 4:12 PM, Julio Napurà Carlos <[email protected]> wrote: > > Uhmm > what about rum [1] and RumAlchemy ? > > Some cool things you might overlook http://rumdemo.toscawidgets.org/ > > [1]http://toscawidgets.org/documentation/rum/ >
As Iain pointed out Rum is a, admin tool build on top of TW, it's a reinvention of Catwalk which was TG's original admin-like application, on that front Chris Perkins (who is the author of dbsprockets) has two initiatives of the same type: one is called DBMechanic, which is a table centered admin. And he has been working (in the last 2 weeks I believe) on Catwalk2 which is also a reinvention of Catwalk but works on top of dbsprockets and is a "model" centric admin. As for history this is how things evolved, and their stability Catwalk is unusable outside of TG1, code is unmaintained and the original author is long gone. So stay away from that. DBsprockets is a toolkit to build forms out of your tables, the basic sprocket could be described as "go look for table X exclude fields a,b,c and give me a insert form", it's stable and works nice DBMechanic then is "do everything DBSprockets does but for all tables" , it's less stable and may get confused with complex models Rum is a SOC project from this year by the author of TW, which is designed to build a totally pluggable admin, in theory you could make a Rumjango, and get it running on django's ORM. although noone has written it, or you could strip out the tw rendering and plug your own. it's still in development and UI isn't customizable, at least not in a simple documented way. DBsprockets declaratives, is a new module of dbsprockets that lets you work directly with classes (it is an analogy to SA declarative syntax, although as declarative you can use it with plain SA), it's very new less than 2 weeks Catwalk2 is DBMechanic for SA classes. It is also very new, but it's a nice POC. and Chris hopes to get it out by tg2.0 final which should be in the first days of Jan. As for the difference between Rum and DBsprockets, it's architectural and you will have to understand at least one to know what is going on different on the other, but they serve the same task. If you want to look at it as a blackbox, it's like templating X and templating Y, they both solve the problem but each has it's advantages and disadvantages. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
