[udig-devel] Re: homework for udiggers Part 3

Jesse Eichar jeichar at refractions.net
Tue Oct 3 10:12:06 PDT 2006


>
> 5)Feature editor.
>
> We are implementing feature editor based on new  
> TabbedPropertySheetPage and
> its framework. IGeoSelection can wrap just one feature and editor  
> can create
> UI for attibutes editing like it is now. Also IGeoSelection can  
> wrap just a
> filter of the layer and the editor will create UI to set values for
> appropriate attribute types and then perform batch updating through
> FetaureStore.modifyFeatures(AttributeType[], Object[], Filter).
>
> We have selection tools that provide IGeoSelection to  
> GeoSelectionService.
> We have editor that listens GeoSelectionService and creates  
> necessary UI for
> the particular contents of IGeoSelection.
>

Great!  The existing implementation was not supposed to last as long  
as it did.  It is a demonstration of the how the FeatureEditor  
framework can be used.  You will probably want to modify the Feature  
Editor framework a bit so that it uses you IGeoSelection.

> 6) Editing tools
>
> We know the situation. bunch of work is needed. There should be  
> capability
> to switch off all animations. Seems a lot of work was devoted to  
> create and
> fix animation when the core functionality of editing tools is so  
> raw. The
> question of priorities for users: what is more important -  
> animation or  how
> to create a line with good UI response time.

That seems like a fair request.  I'll add that option.

>
> 7)Catalog
>
> Catalog is not friendly at lot. It is simple and brutal. But is a  
> core thing
> like ArcCatalog.. all resources are coming into application through  
> catalog
> - a kind of central geographical resources repository. Resources  
> must be
> lazily activated. Is IService interface good enough to be a kind of
> lightweight descriptor for the data source? Seems, yes, but if to  
> switch on
> all logs, when UDIG is opening, a lot of warnings appear like
>
> WARNING: projection (.prj) for shapefile:
> file:/D:/eclipse/kuviogis-workspace/db2shp/2006_09_13/18_03_58/ 
> MHGIS_GISA1_K
> UVIO.shp is not available
>
> for shapefiles contained in Catalog. Seems   something tries to  
> load data
> source to create label, whatever, not lazy now.. (debugging has  
> shown that
> CatalogPlugin.title() methods causes loading resources in Catalog  
> during
> opening the application when there is no opened editors..


I think everyone agrees that the catalog needs to be extended most  
likely it will even be able to have a full perspective for searching/ 
viewing and browsing the catalog.

With regards to the lazy loading.  We have 2 conflicting  
requirements.  In the catalog we want to know the Titles of the  
IService/not the URL but we want them to be lazy loading.  What I do  
now is cache the titles when an IService is added to the catalog and  
use that until the IService is opened.  I will write a test-case to  
ensure that is still the case.

Also tell me what you think of UDIG-881

>
> 8) Copy/paste
>
> If this is not ready and buggy, I would like to hide that  
> functionality
> until it starts to work properly. I copied layer in Layers view and  
> pasted
> to another map. The application starts to be crazy, rendering has  
> broken,
> etc.
>
> Refactor all places where copying/pasting is available, test, fix  
> or hide
> for the time being.

Yes.  no more to say.




More information about the udig-devel mailing list