Quoting Mark Stosberg <suppressed>: > In article <suppressed>, Peter Masiar > wrote: > > > > Which way to go now? > > Twiki sounds good to me. Really, something is better than nothing. The > presonal preference of the person setting it up is also fine with me as > a starting point, too. :) Thank you :) > I don't have much experience with any wiki's, Exactly. Many list members do not, too, so it's hard to advocate one feature or another. Using (any) wiki will build this experience. > but know from database programming experience that's it's a lot easier > to program with data when there is a real database involved. OTOH, long > documents, such as complete web pages have been the exception to that. I am database programmer by trade, too. But if page has 40-60K of text and participants are too lazy to refactor it, and we want to keep change history, in database we need to store all 60K multiple times. In text, only changes are saved (using CVS). But there is heated discussion on Twiki forum about storing page attributes separately, and database should be optional. Those are details, which belong to specofications. Peter Masiar --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.