<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Benedict<br>
<br>
It is a good direction to go towards multiple views / dataframes.
This is a frequent feature-wish and it is good to know someone is
working on it.<br>
<br>
The RFC is centered around data frames as layer collections, but I
think it would involve more than just QgsProject and QgsMapLayer.
E.g. every frame could have it's own canvas / layer set / output
crs (maybe even legend, overview map). Therefore, the term data
frame may need to be changed.<br>
<br>
Once you are working on QgsProject, don't forget that layers and
whole groups can be embedded from other projects / frames.<br>
<br>
<br>
Regards,<br>
Marco<br>
<br>
<br>
On 09.01.2013 01:04, Benedict Holland wrote:<br>
</div>
<blockquote
cite="mid:CAD+mzowfN8uFLH5Abm2iSEGQtaJ6RdBug2rnxHn1MWY3JitHMQ@mail.gmail.com"
type="cite">Hi All,
<div><br>
</div>
<div>I don't know if I can actually call this project data frames
as I don't know if that is TMed by ESRI but regardless the
concept is the same. The RFC is located here:</div>
<div><br>
</div>
<div>
<a moz-do-not-send="true"
href="http://hub.qgis.org/wiki/quantum-gis/Data_Frames">http://hub.qgis.org/wiki/quantum-gis/Data_Frames</a></div>
<div><br>
</div>
<div>This would be a substantial change to the
current architecture of QgsProjects and the relationship between
QgsProjects and QgsMapLayers. I have been a professional
developer for about 6 years or so and have worked on projects
much larger than this but not in c++ for quite some time. I do
though use best practices including unit tests and documentation
as part of a standard development procedure and I applaud
your requirements that these be included in this feature. While
I do expect this will change the architecture I do not expect
much will break unless previous releases cannot load a project
file from a future release but honestly, there is little I or
anyone else can do about that now except tell people to upgrade.
If there isn't currently a way to handle future releases then I
will also create a method for doing that and file it under the
same RFC linked above. </div>
<div><br>
</div>
<div>Let me know what you can think. I am eager to get working on
this as it would make life substantialy easier for me in the
direct future. </div>
<div>~Ben Holland</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-psc">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
<a class="moz-txt-link-abbreviated" href="mailto:marco.hugentobler@sourcepole.ch">marco.hugentobler@sourcepole.ch</a> <a class="moz-txt-link-freetext" href="http://www.sourcepole.ch">http://www.sourcepole.ch</a>
Technical Advisor QGIS Project Steering Committee </pre>
</body>
</html>