> Now seriously. I think it's a pity that the scarce human resources TG > has are being diverted in almost parallel directions, but something good > will surely come out of the competition :)
I agree, but it seems like the learning curve to get more developers involved in rum is pretty high. Keeping all the generic function stuff in your head can be difficult, and the error messages that peak-rules generates can be a bit opaque. On the other hand the use of generic functions provides a huge amount of flexibility, and when everything just works, it is a thing of beauty. Alberto did a great job on Rum this summer, and we were all totally impressed with the results. As better django admin than django it's a great step forward, and we all jumped on the bandwaggon right away. And I understand that sprox includes catwalk2 which is a lot like rum, but missing all the restfullnes, the JSON interface, and much of the high level design goodness of Rum, which is unfortunate. But to me it makes sense to separate out form generation tools form the wsgi-app-admin thing, because lots of people need help with form generation too. And it's unfortunate that the form-generation stuff lead to an admin interface redo - but I can see the desire to use the same tools for form generation that you use for admin interface building. I wonder if there's some way we can figure out to work together more.... --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
