On Sep 7, 3:08 pm, "Angelo Gladding" <[EMAIL PROTECTED]> wrote: > I truly believe the organic approach is best for now. In other words, we > need a reliable wiki and related discussion. Optimally they would coexist on > the same website even though we already have conversations on this list. > Aaron has mentioned this from the beginning but we've yet to realize any > such solution. That said, and part of the reason I've withheld responding > thus far, I'm going to begin a hosted solution to this problem. I'll > probably post back by Sunday with my progress. I may or may not make use of > Seddit's code considering it uses Prototype and Postgre and I've yet to see > it in action.
I'm not sure if Seddit is really the tool to solve the "documenting process." When I set out to create it, I had the idea of something more like a mailing list. You'll search the archives if you have a question, but usually the first place to find your answer will be in the documentation. And for documentation, a wiki is certainly the best tool for the job. I believe seddit will work well for your "related discussion" aspect of the wiki. I'm interested to see how your hosted solution is coming. I'd be interested to talk with you, and see if maybe we can't get seddit integrated when it's ready to go live. I think it can solve atleast half of the problem. As for seddit's progress. I don't plan to drop the ball on this one. I'll continue to work on it throughout the school year, and get it deployed. The summer just wasn't enough time to get specs written up, and write a fully function application. Also, just curious. Is there anything wrong with prototype and postgresql? > I don't think less is ever more when it comes to good documentation. When > coding, absolutely. When looking for help, not so much. Great documentation > = python.org. I believe the current one-pager documentation is actually > quite useful but it could always grow and expand and that's where it's > lacking -- depth. Where do we outline design idioms, the concept of REST, an > HTTP roundup (headers, seeother, redirect) etc. I agree. I came into writing seddit without ever using web.py. One of the most daunting pieces of writing code for web.py is that I had no clue where to start. I think some documentation with "best practices" would be very helpful. I know one of the neat things about web.py is the freedom you have to develop your own application, but it's still very helpful to give newcomer's somewhere to start. Let them get their feet wet before letting them loose. Drew. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
