Hi all,<div><br></div><div>I just modified the wiki page and replaced the absolute links ( <a href="http://hub.qgis.org/issues/issue_number">http://hub.qgis.org/issues/issue_number</a> ) by redmine syntax for links to issues ( #issue_number ).</div>
<div><br></div><div>This way we will be able to see wich issues are closed.</div><div><br></div><div>Michael<br><br><div class="gmail_quote">2012/8/16 Etienne Tourigny <span dir="ltr"><<a href="mailto:etourigny.dev@gmail.com" target="_blank">etourigny.dev@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Martin, Arun and others<br>
<br>
I think this is great! My work on cpt-city color ramps is still<br>
evolving, and I was wondering in which ways it could benefit from your<br>
work.<br>
<br>
As far as I see it, here is how ramps would work:<br>
<br>
1) an interface to browse a number of available gradients and import<br>
them into user's gradients.<br>
<br>
The entire cpt-city archive holds about 6000 gradients. I have<br>
prepared a reduced set (about 800) that we could provide optionally<br>
for qgis users, based on licenses and a broad selection (the one from<br>
cpt-city). The goal is to have a minimal set (about 100) that would be<br>
distributed with qgis.<br>
<br>
The current interface to browse these gradients needs an overhaul, and<br>
I was thinking of adopting a layout similar to the one you adopted for<br>
the style manager: a tree to the left with various ways to organize<br>
the gradients, a search feature, and a box to the right with the<br>
matching ramps. Because there are a number of ramps available, it<br>
might not fit well inside the style manager because it would add<br>
clutter. On the other hand, it could be useful to have it integrated<br>
directly, with a specific category in the tree and perhaps a specific<br>
tab page for the matching ramps. My preference is to use a dedicated<br>
dialog for this, very similar to the style manager, but I would<br>
appreciate feedback and of course a thumbs up/down to reuse your work.<br>
<br>
2) once ramps are chosen they reside in the color ramps tab like other ramps.<br>
<br>
3) import/export: cpt-city ramps are stored in standard svg<br>
"linearGradient" format. It would be nice to be able to import/export<br>
these from the style manager, and perhaps change the internal xml<br>
representation of color ramps to that format - or at least export in<br>
svg linearGradient.<br>
<br>
cheers,<br>
Etienne<br>
<br>
<br>
On Tue, Aug 14, 2012 at 5:25 PM, Martin Dobias <<a href="mailto:wonder.sk@gmail.com">wonder.sk@gmail.com</a>> wrote:<br>
> Hi all<br>
><br>
> I am happy to announce that I have just merged Arun's work on<br>
> symbology. He has done a great job and after some testing I think the<br>
> code is ready for prime time.<br>
><br>
> What to expect?<br>
> - style manager has been greatly improved:<br>
> - grouping of symbols (including child groups of groups)<br>
> - tagging<br>
> - "smart" groups (showing only symbols matching some criteria).<br>
> - search<br>
> - symbol selector and properties dialogs have been integrated to just<br>
> one dialog, improving the usability a lot<br>
> - style database is now stored in a SQLite database rather than an XML<br>
> file for better scalability<br>
> - style import improvements: load style directly from given URL,<br>
> saving imported symbols into a group<br>
> - SVG fill: shows directories for easier traversal through the SVG directories<br>
> - surely some more goodies I've forgotten to mention!<br>
><br>
> Please note that with the transition of styles to SQLite database you<br>
> will find your style empty - but don't worry! You can import all your<br>
> saved symbols and color ramps from ~/.qgis/symbology-ng-style.xml -<br>
> from now they will be stored in ~/.qgis/symbology-ng-style.db.<br>
><br>
> Arun: thanks for your hard work and I hope you will continue to<br>
> contribute to QGIS! :-)<br>
> Also many thanks to Nathan for co-mentoring and lots of great ideas<br>
> for the GUI improvements that landed in the code.<br>
><br>
> Regards<br>
> Martin<br>
<div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br></div>