From: Cameron S. <ca...@sh...> - 2003-09-13 04:17:12
|
On Friday 12 Sep 2003 3:55 pm, Sean Wheller wrote: > I think that requirements need to be defined that will > address portability. Yes. On Friday 12 Sep 2003 3:55 pm, Sean Wheller wrote: > The track sounds right. But I think that the > requirements etc need to be stable before investing so > much time is developing tools. Once stable, then the > wish list can be attacked. Yes and no. The requirements were reasonably stable until you came along with a pile of great ideas. :) Part of refining requirements involves developing a prototype which will flush out a number of the issues you don't understand of have not thought of. However, I agree we need to capture the ideas from this discussion in the requirements. We also need to update the design as we develop it, as it also explains to ourselves and future developers why we have chosen the design we are using. -- Cameron Shorter http://cameron.shorter.net Open Source Developer http://generguide.sourceforge.net http://mapbuilder.sourceforge.net http://geotools.org Senior Software Engineer http://www.adi-limited.com |