I am working on the team developing the "dbstuff" apply named DBMechanic for the time being. It is intended to be a replacement for FastData.
Please excuse the blurry documentation. The intention is for that to be a place holder for a graphical document which should be available in the next week. The truth is, the code base is in a state of flux at this point, but by mid-end of next WEEK we will need developers in a bad way. We too have a short time-scale and need something up and running ASAP. What we plan to do is finish sorting out the basic API and get SQL Alchemy and ToscaWx support sorted out before unleashing this to the droves of developers gnawing at the bit to get their hands on it. Ha ha! Seriously though, we will need all the help we can get to develop the Widgets to support the API base as soon as we get the general schema worked out. We hope to have this by Wednesday of next week, so if you can hold on till then we could really use some help. In the mean time I am happy to trade email/message board posts about our project. Ask away. -chris On Mar 2, 4:07 pm, "wavydavy" <[EMAIL PROTECTED]> wrote: > Heya all. > > I have used the original fastdata with my older projects a fair bit > with good success. My newer projects are using SA/Elixir, Genshi and > ToscaWidgets (simply awesome!), and I find myself in need of > fastdata's functionality. I am aware things are still emerging in this > area, and I am quite happy to get my hands dirty and work on > something. I'd really rather not role my own :( > > Problem is, I'm not sure what the current approach is, i.e. where's > best to get involved? There are three projects as far as I can see > from the list archive and looking at the svn repo: > > tgcrud: rails-ish scaffold generating tool, not my preferred approach > > fastdata2: looks interesting, and fairly functional, uses the neat > twGrids widgets, but doesn't seem to provide a default controller/view > at all. Is the idea that you write your own? Is it still a going > concern? > > dbstuff: pycon sprint stuff, aimed at replacing FastData2? Looks like > an ambitious project, but not yet close to working, and while blurry > whiteboard photo's are nice, they don't add all that much to my > understanding :) > > I need something working in the next week or so, which is the best bet > to use/get involved with? Where their any discussion/decisions at > pycon that are worth knowing about regards the future e.g. is dbstuff > where its going, or is it still all up in the air? > > Currently leaning towards fastdata2, just didn't want to put in a load > of work in on it to learn that its been deprecated or similar. > > Cheers > > -- > wavy davy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
