> > I find the "procedures" about normal for an open source project, but I > > think we could cut down on the description to make them easier to follow. > > I have had different experiences and find them a bit oversized. But I > understand your point. > The problem is that we are creating a "how to develop uDig" book and lack a > decent developer manpower in the community. > > >
Ah okay I get you. Yeah documentation priority is user-docs, admin docs (release/devel environment/build). Notes on how to develop using uDig is very much a lower priority. > > I am hesitant to add functionality without documentation (or video?) > > providing a clue on how to use it. > > > > I am ok with adding docs with new functionality, which I think is what I have > been doing. > > > Okay - we are on the same page here. > We have usual problem of uDig having this double face of framework and user > GIS. It disperses our force :) > > I will most probably try to nail down the editor part and missing doc/code > this weekend. If you are hacking, we can do some together. Everyone is > invited obviously, let's hope in some bad weather :) I will look for you then. Jody
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
