[Qgis-developer] Vienna hackfest: QGIS Legend discussion

[Régis Haubourg]

Hi Martin, 
thanks a lot for your feedback. I have some questions: 


Martin Dobias wrote
> Hi
> 
> First of all thanks everyone who contributed to this thread - there
> were many interesting ideas that we can discuss further.
> 
> 
> On Mon, Mar 31, 2014 at 10:32 AM, Régis Haubourg
> <

> regis.haubourg@

> > wrote:
>> Some questions here since French users are really interested in that
>> work,
>> and need some info before being able to fund some work :
>>
>> - I saw Lutra Consulting calls for fundings on that item. Is the budget
>> fullfilled or are you still looking for funds? [
> 
> We are still looking for funds for the project (so far we have reached
> ~70% of the goal) - and therefore contributions are welcome!
> 
> 
>> - We previously discussed of legend for size varying symbols and diagrams
>> [0]. Is that also included in that work?
> 
> This is not part of the refactoring work, but it is very interesting
> use case and therefore I will keep it in mind and do the design in a
> manner that adding such functionality should be possible. Advanced
> legend manipulation could be another followup project.

Hi Martin, does that mean that we need to wait that your refactoring is
finished before starting a work on proportionnal legends? What is the target
version for that?
This is a high priority use case here, should we fund a temporary plugin for
current versions ? This is sub-optimal too me, and that requires also we
fund first a plugin, and secondly a core feature. 



Martin Dobias wrote
>> - Can some give us some conclusions of what what said in codesprint
>> legend
>> workgroup on this? (sorry for not being able to come and contribute
>> there)
> 
> While we have discussed various aspects, we have not reached too many
> conclusions :-)
> 
> - legend vs layer manager - there was a good point that we are mixing
> the concept of map legend and layer manager into one tree. While these
> are related, they get into conflicts... while layer manager should be
> a tool for management of the map (and be as powerful as possible), map
> legend should provide mainly the help for the user to identify the map
> elements (and be as simple as possible).

Are you heading to an arcmap like solution with different tabs in layer
registry?


Martin Dobias wrote
> - support for multiple canvases - while it is not the intent to have
> this functionality when the refactoring is complete, the work should
> bring us a bit closer to that. It is still unclear how multiple
> canvases should behave as there are lots of use cases with different
> needs, e.g.:
>   - tabbed vs split screen canvases
>   - same or different map extent
>   - same or different layer styles
>   - same or different set of layers / visibility

after having experienced Mapinfo, Arcmap, and QGIS dockable Mirror map, I
think Multi Canvas is really required for multi map composers, and current
arcmap design is rather good. We still need Dockable mirror map for on
screen visulisation purposes.


Martin Dobias wrote
> - new functionality suggested - we discussed some of the ideas from
> the thread, especially the ones from Olivier. No conclusion was
> reached whether to adopt all of them in the future, but the icons as
> indicators for labeling, diagrams, snapping, actions, editing(?) etc
> were seen as potentially very useful. They could be even used for
> reporting map canvas refresh progress (animated wait icon) or
> errors/warnings (e.g. reprojection failed).
> 
> I am sure there were more things discussed which I have forgotten
> already, other participants please feel free to add your impressions.
> 
> Regards
> Martin
> _______________________________________________
> Qgis-developer mailing list

> Qgis-developer at .osgeo

> http://lists.osgeo.org/mailman/listinfo/qgis-developer

Cheers
Régis




--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Vienna-hackfest-QGIS-Legend-discussion-tp5131063p5132638.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.