On Saturday 08 April 2006 19:14, Lourens Veen wrote: > I'm currently trying to figure out who uses the site, what they want to > do, and what kind of data is needed for that and in what formats.
How about on-demand? Opensource tends to be an evolutionary process, why not let the web follow that too. It seems to be like it'd be a bit foolish to try anticipate all the needs and usage patterns of a website in advance, and then set that in stone. Go with the flow, be one with the stream. Afterall, what people don't really need from a website, is design. > Second, which kinds of documents are typically created in a hardware > project, and what formats are used? Where should these documents be > stored, in a source code version management system, or is it just > binary data that might as well be stored in a file system? Are there > open standard formats in this arena, or do we need to standardise on a > single application and its file format? Do we want to? I'd love a web interface to it, with any revision control information available, as well as trouble-free download of arbitrary versions. The more fileformats that can be parsed into www and displayed, the better, even better if they can be highlighted and diffed. Downloadables for each format would be nice too. Copy&paste from websites gets tedious in the long run. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
