> Maybe the problem was that you tried to make Catwalk SA compatible. I > would probably try a complete rewrite for SA instead, and only get some > inspiration from the original Catwalk.
Well not really. Myself and one other developer (Robin Dunn) tried in vain for 2 days to get catwalk to work with SA. We did re-writes where we thought we could and tried to use what we could of Catwalk. Having worked with the code for 2 days straight, I think it is fair for me to call it spaghetti code. (I did more than just a cursory glance). Certainly the code is not well tested, and there are definitely some bugs that I came across as a user back when I was using SO over a year ago. DBMech/Sprox is a complete re-write. I just need a JS/CSS developer to step up and help me add some glitz. > Since I'm not using SO, I don't know. But I noticed that the SQL > designer code that ModelDesigner is based upon, has experienced some > heavy updates in the last time and looks even cooler. So it would be > probably a good idea to rewrite ModelDesigner based on the latest SQL > designer, and only get some inspiration from the old ModelDesigner. > > -- Christoph What I would really like to do is merge ModelDesigner into DBMechanic so that you can do on-the-fly database changes (this is going to require reflection and sqlalchemy.migrate to work). This was the plan for DBMechanic v0.4. Now, who do I have to convince to join my team (ie, who is writing the model designer)? -chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
