On Tue, Aug 7, 2012 at 12:39 PM, jjg <j.j.gr...@gmx.fr> wrote: > > Paolo Cavallini wrote >> >> IMHO with such high numbers, appropriate tagging & filtering is the way to >> go. >> > > With 6000+ gradients that is easier said than done. > > The site has, presently, a set of "selections" (blues, topo, bath and so on) > which myself and Etienne have discussed as forming the basis for such > QGIS sets (outline - XML file of gradient paths used to generate the > cpt-city > pages and also to be downloadable, these could then be used to filter the > GUI, or to make specialist sub-sets of zipfiles on the QGIS side). That we > will have a look at after the zip download is tested and working.
We need to establish is which directories (sets) have licences that allow us to distribute with QGis (Apache, GPL, CC3, etc.). Some code can assist but in the end it's safer to read each directory's copyright information. I was thinking of an interface to make zip files from selection lists. The plugin would probably be suited for that, because it's not really part of the core and it's much easier to write this sort of thing in python. Ideally, we should have a point-n-click interface for generating these selections, but I think it would be too costly to implement. So a manual solution would probably be easiest on the short-term. Unless we feel it's necessary to have users make their own selections (by selecting favourites), and use that. Perhaps a first step would be using the cpt-city selections which can be distributed and generate a list from that. Do people feel that the existing cpt-city "selection" would be sufficient, or are there too many? My feeling is that we could aim for parity between the cpt-city selections and qgis selections (and excluding files for license issues). It would be nice if people could help out in 1) determining which directories we can ship with QGis - this would be passed to Jim who would add this to each directory's metadata 2) build a list of core gradients 3) testing the rendering of the gradients (I have a solution that compares the preview to the png's on the cpt-city website) 4) general testing and anything I might be forgetting Anybody interested please advise! > > As to the GUI navigation of such a large number of gradients, that is a > challenge. I personally use the site itself as a selector, then when I find > the one I want, I copy-paste the path (which is listed under the preview > on each individual gradient's page, for exactly this purpose) into my > script. It might be better to present all of the gradients in a given directory in a single page, instead of the tree view? The tree view would remain, but only for browsing by theme / author / whatever. > > eg on > > > http://soliton.vm.bytemark.co.uk/pub/cpt-city/bhw/bhw4/tn/bhw4_003.png.index.html > > the path is > > cpt-city/bhw/bhw4/bhw4_003 > > I've not had time to look at the QGIS selecter, if it does not have a > "gradient path" input (ie, no extension, no base directory) then perhaps > it would be an idea to add one. > > Jim > > > > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/color-ramp-manager-tp4993619p4993698.html > Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
