[Qgis-developer] Re: [Qgis-user] Atlas plugin - create map books
Nathan Woodrow
madmanwoo at gmail.com
Thu Jan 26 02:50:09 EST 2012
-1 to mixing Python and C++ to me. If we only targeted one platform with
one version of Python I would be a +1 but the amount of emails we get about
Python not working, conflicts with Python version, conflicts of Python
plugin libs etc, would lower the user experience not increase it.
There is also the issue of API binding.
I would love to see the composer improved to handle map book making as a
core built in function, however I am happy for it to stay as a plugin at
the moment because it will be easy to work out and fix all the logic bugs,
has a larger spread of users, and quicker to develop and distribute.
- Nathan
On Thu, Jan 26, 2012 at 5:43 PM, Marco Hugentobler <
marco.hugentobler at sourcepole.ch> wrote:
> Hi
>
> I also think that it is not necessary to port the atlas plugin to C++.
>
>
> It would be interesting to see what other devs think about opening
>> qgis to python code.
>>
>
> -1
>
> I like the clear distinction between C++ and Python parts as it is now.
> For me, it is still very important to have the possibility to build QGIS
> without Python if necessary (e.g. doing a quick test with a Windows or Mac
> build of a branch).
>
> Regards,
> Marco
>
>
>
>
>
>
>
>
>
> On 25.01.2012 23:37, Martin Dobias wrote:
>
>> [moving the discussion to qgis-dev list]
>>
>> On Wed, Jan 25, 2012 at 7:53 PM, Vincent Picavet
>> <vincent.ml at oslandia.com> wrote:
>>
>>> Hi,
>>>
>>> As for having Atlas a QGis core part, I could do the C++ port, but this
>>>>> project would need funding. If anyone interested, get in touch.
>>>>>
>>>> Do you think a porting to C++ is really necessary? Wouldn't it be
>>>> sufficient to move the py code to master once ready for production and
>>>> well tested?
>>>>
>>> That's something to ask to qgis devs at large :)
>>> If we keep it in Python, I'd be glad to move it to qgis master.
>>> We'd want to wait for test and consolidation before that.
>>> What do other think ?
>>>
>> It is really tempting to move forward from being pure c++ application
>> to a hybrid of c++ and python code - and I am not talking about python
>> plugins shipped by default with qgis - I mean that python would be a
>> required dependency since some parts of the GUI would be in python. I
>> tend to be in favor of that (to some degree).
>>
>> There are some advantages (many python developers, lots of working
>> python code in plugins) and some disadvantages (code maintenance). At
>> the same time we should have a vision what should and what should not
>> go into qgis app - not many plugins are really for general purpose,
>> with good gui+code quality and without further dependencies.
>>
>> It would be interesting to see what other devs think about opening
>> qgis to python code.
>>
>> Regards
>> Martin
>> ______________________________**_________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/**mailman/listinfo/qgis-**developer<http://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>
>
>
> --
> Dr. Marco Hugentobler
> Sourcepole - Linux& Open Source Solutions
> Churerstrasse 22, CH-8808 Pfäffikon SZ, Switzerland
> marco.hugentobler at sourcepole.**ch <marco.hugentobler at sourcepole.ch>
> http://www.sourcepole.ch
> Technical Advisor QGIS Project Steering Committee
>
>
> ______________________________**_________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/qgis-**developer<http://lists.osgeo.org/mailman/listinfo/qgis-developer>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/qgis-developer/attachments/20120126/082857a0/attachment.html
More information about the Qgis-developer
mailing list