[...] >> Please keep me uptodate, I will introduce the new developer to this list >> in about 3 weeks or so. At that time we will have design sessions, since >> in that concept we want to have also chainable commands (operations?). >> Glad if someone wants to partecipate with good ideas :) >> >> Regarding to that I want to ask (so I can already do some prototypes) if >> anyone has an idea on how to deal with this. Operations have their >> extension point, but we need to implement the openmi interfaces. >> Should we create new types of operations or create a new concept of >> chainableoperation? >> > Yes! > > If we go back to the origional uDig design documents for DataAccess you > can see some thoughts for chained operations (but that was with Features > in mind).
Where can I see that? > Quickly: I had thought of a simple "Map" of settings (to build a UI > from), a declaration of the inputs (ie Type) and the output. (ie Type). > Build it all as a straight up domain model, use GEF to make a simple > graphic editor for the chaining part and then ... start running data > through. This sound exactly the way I want it to be. :) > So please use your recent operations experience (even if just as a > simple example) and your experience actually chaining stuff and see what > pops out. Jody, I guess it is a problem of language (both English and development :)) of mine, but I don't understand exactly what you mean. I mean, I think I got what you are saying, but you talk about things I never saw and heard and there are no references towards somewhere to look, whereas you usually give them. So could you please repeat the "quickly" part a bit slower? Andrea _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
