<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I fully agree. Porting the analysis code of fTools to the analysis
    lib would be a great gsoc project. <br>
    <br>
    Regards,<br>
    Marco&nbsp; <br>
    <br>
    On 24.02.2012 08:55, Nathan Woodrow wrote:
    <blockquote
cite="mid:CAAi8Yg-1Qn0zhmeciGYrwemep2VKnJ5X=9Lve_-KoLkZBRgodw@mail.gmail.com"
      type="cite">I'm a +1 to Alisters ideas. &nbsp;I think it would be good
      to have a full suite of tools for manipulating vector objects and
      layers. &nbsp;These tools should be ports of fTools to C++ and live in
      the&nbsp;analysis lib so that they can be used in C++, Python and UI
      (Carson and I have talked about this before).
      <div>
        <br>
      </div>
      <div>I think this project would be good as it is tightly scoped
        and would be easy to mange in chunks. Merging would also be
        easy, even merging as the project moves along as each tool
        is&nbsp;independent.</div>
      <div><br>
      </div>
      <div>Would should be careful not to start a GSoC project that is
        too large, has wide scope, vague goals, or is to hard to mange
        in a summer. &nbsp;</div>
      <div><br>
      </div>
      <div>
        <div>
          <div>- Nathan</div>
          <div><br>
            <br>
            <div class="gmail_quote">
              On Fri, Feb 24, 2012 at 10:15 AM, Alister Hood <span
                dir="ltr">&lt;<a moz-do-not-send="true"
                  href="mailto:Alister.Hood@synergine.com">Alister.Hood@synergine.com</a>&gt;</span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                Something that has been mentioned by a few people, and
                would probably be very popular, I described like this:<br>
                <br>
                "Vector editing/geoprocessing tools or whatever they are
                called, like the ones found in the Mapinfo 'Object' menu
                - i.e. similar to ftools, but taking sets of selected
                features as inputs, instead of whole layers."<br>
                <a moz-do-not-send="true"
href="http://woostuff.wordpress.com/2011/05/17/the-things-i-would-like-to-see-in-qgis-what-are-yours/"
                  target="_blank">http://woostuff.wordpress.com/2011/05/17/the-things-i-would-like-to-see-in-qgis-what-are-yours/</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.osgeo.org/pipermail/qgis-user/2011-May/012041.html"
                  target="_blank">http://lists.osgeo.org/pipermail/qgis-user/2011-May/012041.html</a><br>
                <br>
                Later in that second thread someone also mentioned the
                following; I think other people have also made similar
                requests/suggestions:<br>
                <br>
                "I guess implementing topology rules and visualizing the
                existing errors would be a way to identify and correct
                problems like polygon overlapping. &nbsp;It might already
                exist some code."<br>
                <br>
                This second idea would probably require more research
                and thinking about exactly what to do.<br>
                <br>
                I think both these ideas are complementary, and could
                perhaps be done in a single project. &nbsp;But I guess they
                are also features that might be able to attract other
                sponsors - you might think it is better to use Google
                money to do something which is unlikely to get
                sponsorship otherwise.<br>
                <br>
                Regards,<br>
                Alister<br>
                <br>
                <br>
                Somebody started working on a plugin similar to this
                (early last year I think), but it didn't get very far.<br>
                <br>
                &gt; Date: Thu, 23 Feb 2012 15:31:02 +0100<br>
                &gt; From: <a moz-do-not-send="true"
                  href="mailto:jr.morreale@enoreth.net">jr.morreale@enoreth.net</a><br>
                &gt; Subject: Re: [Qgis-developer] GSoC ideas<br>
                &gt; To: &lt;<a moz-do-not-send="true"
                  href="mailto:qgis-developer@lists.osgeo.org">qgis-developer@lists.osgeo.org</a>&gt;<br>
                &gt; Message-ID: &lt;<a moz-do-not-send="true"
                  href="mailto:ee204f37fdb370744d28a4c105369f70@enoreth.net">ee204f37fdb370744d28a4c105369f70@enoreth.net</a>&gt;<br>
                &gt; Content-Type: text/plain; charset=UTF-8;
                format=flowed<br>
                <div class="HOEnZb">
                  <div class="h5">&gt;<br>
                    &gt; On Tue, 21 Feb 2012 17:03:15 +0200, Alexander
                    Bruy wrote:<br>
                    &gt; &gt; Hi all,<br>
                    &gt; &gt;<br>
                    &gt; &gt; Google Summer of Code 2012 is announced
                    few weeks ago and as far as<br>
                    &gt; &gt; I know OSGeo will participate. Hope QGIS
                    will participate too. I<br>
                    &gt; &gt; started<br>
                    &gt; &gt; wiki page for collecting ideas [0]<br>
                    &gt; &gt;<br>
                    &gt; &gt; Maybe we should announce also to the user
                    list asking for ideas too<br>
                    &gt; &gt;<br>
                    &gt; &gt; [0] <a moz-do-not-send="true"
                      href="http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2012"
                      target="_blank">http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2012</a><br>
                    &gt;<br>
                    &gt; Hi,<br>
                    &gt;<br>
                    &gt; how about these projects :<br>
                    &gt;<br>
                    &gt; 1. Update and merge the multithread branch<br>
                    &gt;<br>
                    &gt; 2. QGIS, Valgrind &amp; Co<br>
                    &gt;<br>
                    &gt; Both would get the student to put its hand in
                    all the dark corners of<br>
                    &gt; QGIS and both would produce a positive and
                    visible impact.<br>
                    &gt;<br>
                    &gt; Regards,<br>
                    &gt; Jean-Roc<br>
                    _______________________________________________<br>
                    Qgis-developer mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
                    <a moz-do-not-send="true"
                      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>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Dr. Marco Hugentobler
Sourcepole -  Linux &amp; Open Source Solutions
Churerstrasse 22, CH-8808 Pf&auml;ffikon SZ, 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>