Andrea Aime wrote: > Hi, > in our current new data tree we have no visible way to > show which resources and datastores are in trouble, > meaning they are in a state that cannot be used. > > The simple example is the misconfigured datastore, > or the proper configured one that cannot connect > to its backend (dbms down for example). > > How do you think we should handle that? Talking with > Rolando we considered a few possibilities: > * red mark decorators on the icons, a la Eclipse. > Nice effect, implementation is not exactly trivial, > but doable. Would also call for an icon explosion > unless we do add the decoration by dong some > image ops using the base icons and one that does > contain only the red marker) > * a separate ajax pageable list below the tree table > that explicitly list the resources that are failing, > maybe collapsed under a link saying "xxx nodes in error" > and expanding when you click on it > * same as above, but instead of expanding in place, > pop up a dialog with the same table
I think I like the icon decorator. Its the same deal as eclipse does errors and I think it works well. I believe udig does this too. > > One drawback of this kind of error reporting is that > we have to scan the whole catalog in order to provide > it, so it won't scale very well. On the other side, > that's exactly what we're doing nowadays anyways, > scannign the whole catalog in order to build the > green/red/gray status bars. The StoreInfo interface has a getError()/setError(). The point of this method is to track when a store has a problem. Could we use this as an alternativ to scanning the entire catalog. Basically anytime ResourcePool tries to connect to a store using a StoreInfo it would store the error that occurs (if it does) in this property. If no error occurs it clears the property. > > Related to this we have the feedback for the auto > configure button, which should try to auto > configure a resource. Rolando suggested to try to > autoconfigure, and if it fails decorate the nodes > that failed with a marker, not in the icon, but after the > name (aligned right in the same column). > Seems like a good idea to me, and hovering on top of the > icon one would get the error message that prevented > the full auto-configuration. > > Opinions? > Cheers > Andrea > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:4007,48651f4c211821804284693! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
