Re: [Qgis-developer] Building plugin for Print Composer

2015-08-14 Thread Nyall Dawson 
On 14 Aug 2015 23:41, "Vincent Mora"  wrote:
>
> Le 08/08/2015 11:19, Nyall Dawson a écrit :
>>
>>
>> On 7 Aug 2015 6:58 pm, "Vincent Mora"  wrote:
>> >
>> > Hi all,
>> >
>> > I need to add graphs generated by a plugin to compositions. I'm
considering to develop a PluginComposerItem in the same spirit as
PluginLayers, adding/removing a button in the toolbar when the plugin is
registered/removed.
>
> Hi Nyall,
>
>> Just a warning that similar work is already underway - adding a composer
item type registry so that plugins can register their own custom item types.
>
> Thanks for the warning.
>
> Are you referring to QEP#9 or to something else ?
>
> What is the status of the work that is "underway" ?
>
> What is the planned time-frame ?
>
> Is there a branch somewhere that I can base my work on / contribute to ?
>
> We need a composer plugin item for a customer project with a deadline in
November. We have planned a few days of dev to contribute that and we'd
rather put those efforts in a long term solution.

Sorry Vincent, I've been a bit swamped over the last week and haven't had a
chance to respond yet. I'll put down a detailed email sometime over the
next couple of days outlining the situation.

Nyall

>>
>> It's an extensive work though, because composer has a lot of hard coded
handling of all the existing item types (checkout all the item specific
methods in QgsComposition/QgsComposerView). That's why this work is tied up
with the layouts/reporting framework refactor.
>
> I've seen that, and I'm not sure I see why it prevents the introduction
of a plugin item (+registry) that would be used as a base class for python
objects to draw in a frame that is part of a composition.
>
> V.
>
>
>> Nyall
>>
>> >
>> > Is that what was needed in your cases, or was a more general approach
required (like the qgis plugin mechanism, being able to access the
interface) ?
>> >
>> > V.
>> >
>> >
>> > Le 22/06/2015 18:05, G. Allegri a écrit :
>> >>
>> >> The suggestion from John is exactly what we did too. And we also
built a chart composer...
>> >>
>> >> It would be great to have the means to know what other teams are
working to. It would save a lor of time and money and, probably, get better
software from a shared effort ;)
>> >>
>> >> giovanni
>> >>
>> >> Il 22/giu/2015 19:31, "John Gitau"  ha scritto:
>> >>>
>> >>> Hi Jakob,
>> >>>
>> >>> A workaround would be to have a plugin that creates a new composer
view object:
>> >>>
>> >>> custom_composer = self.iface.createNewComposer("My Composer")
>> >>>
>> >>> Then get a reference to the main window in the composer view:
>> >>>
>> >>> main_window = custom_composer.composerWindow()
>> >>>
>> >>> Then you can either add a new toolbar (and required actions) or
append an action to the main toolbar. Have a look at the ComposerWrapper
class for something similar we implemented for designing charts in the
composer: https://gist.github.com/gkahiu/06a43a589f9441736397
>> >>>
>> >>> Hope this is helpful.
>> >>>
>> >>> Cheers,
>> >>>
>> >>> John
>> >>>
>> >>> On Mon, Jun 22, 2015 at 2:07 PM, G. Allegri 
wrote:
>> 
>>  You can act on it but you can't custom gui widgets to the Composer
interface.
>>  I cannot check the code right know. I listen to a specific
(existing) composition opening but if I remember correctly you can watch
the Composer opening too.
>> 
>>  Il 22/giu/2015 17:19, "Jakob Lanstorp"  ha
scritto:
>> >
>> > Hi Giovanni, thanks for the update. Another solution would be to
catch the
>> > event when a user starts an existing print composer. Cannot in doc
for the
>> > pyqgis API find anything for this. Anyone who know is one can
listens for a
>> > print composer to startup by the user and act on it.
>> >
>> >
>> >
>> > -
>> > Jakob Lanstorp
>> > --
>> > View this message in context:
http://osgeo-org.1560.x6.nabble.com/Building-plugin-for-Print-Composer-tp5212187p5212221.html
>> > Sent from the Quantum GIS - Developer mailing list archive at
Nabble.com.
>> > ___
>> > Qgis-developer mailing list
>> > Qgis-developer@lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> 
>> 
>>  ___
>>  Qgis-developer mailing list
>>  Qgis-developer@lists.osgeo.org
>>  http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >>>
>> >>>
>> >>>
>> >>> ___
>> >>> Qgis-developer mailing list
>> >>> Qgis-developer@lists.osgeo.org
>> >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >>
>> >>
>> >>
>> >> ___
>> >> Qgis-developer mailing list
>> >> Qgis-developer@lists.osgeo.org
>> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >
>> >
>> >
>> > ___
>> > Qgis-developer mailing list
>> > Qgis-developer@lists.osgeo.org
>> > http

Re: [Qgis-developer] CI testing for OSX

2015-08-14 Thread Nyall Dawson 
On 15 Aug 2015 13:17, "Larry Shaffer"  wrote:
>
> Hi Nyall, all,
>
> On Thu, Aug 13, 2015 at 11:31 PM, Nyall Dawson 
wrote:
>>
>> On 13 August 2015 at 04:32, Tim Sutton  wrote:
>>
>> >
>> > Awesome stuff Nyall - can you give any notes on what specifically you
had to do to enable OS X testing?
>>
>> Not much really... all the ground work was already in place and were
>> just waiting on Travis to open up multi OS builds again. Whoever setup
>> the homebrew install package (Larry?) made it super easy to install
>> the dependencies, and we already had 99% of the tests passing without
>> error on OSX. Michael Kirk had also already given this a shot so I was
>> able to borrow parts of his attempts which also helped a lot.
>
>
> Yes, I set up the QGIS Homebrew formulae in the osgeo/osgeo4mac tap.
>
> For example, to set up a dev environ on Mac:
>
https://github.com/OSGeo/homebrew-osgeo4mac/wiki/Developing-on-QGIS-using-OSGeo4Mac
>
> I haven't had time recently to update the work there, so some of the
notes may be outdated.

Thanks Larry, this made it really easy to implement this.

I'm wondering- is there a way to prevent the installation of
postgres/postgis when installing the dependencies? It slows the build down
a lot and conflicts with the existing preinstalled postgis available on
Travis.

Nyall
>
> Regards,
>
> Larry Shaffer
> Dakota Cartography
> Black Hills, South Dakota
>
>
>>
>> Nyall
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] CI testing for OSX

2015-08-14 Thread Larry Shaffer 
Hi Nyall, all,

On Thu, Aug 13, 2015 at 11:31 PM, Nyall Dawson 
wrote:

> On 13 August 2015 at 04:32, Tim Sutton  wrote:
>
> >
> > Awesome stuff Nyall - can you give any notes on what specifically you
> had to do to enable OS X testing?
>
> Not much really... all the ground work was already in place and were
> just waiting on Travis to open up multi OS builds again. Whoever setup
> the homebrew install package (Larry?) made it super easy to install
> the dependencies, and we already had 99% of the tests passing without
> error on OSX. Michael Kirk had also already given this a shot so I was
> able to borrow parts of his attempts which also helped a lot.
>

Yes, I set up the QGIS Homebrew formulae in the osgeo/osgeo4mac tap.

For example, to set up a dev environ on Mac:
https://github.com/OSGeo/homebrew-osgeo4mac/wiki/Developing-on-QGIS-using-OSGeo4Mac

I haven't had time recently to update the work there, so some of the notes
may be outdated.

Regards,

Larry Shaffer
Dakota Cartography
Black Hills, South Dakota



> Nyall
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Building plugin for Print Composer

2015-08-14 Thread Vincent Mora 
Le 08/08/2015 11:19, Nyall Dawson a écrit :
>
>
> On 7 Aug 2015 6:58 pm, "Vincent Mora"  > wrote:
> >
> > Hi all,
> >
> > I need to add graphs generated by a plugin to compositions. I'm
> considering to develop a PluginComposerItem in the same spirit as
> PluginLayers, adding/removing a button in the toolbar when the plugin
> is registered/removed.
>
Hi Nyall,
>
> Just a warning that similar work is already underway - adding a
> composer item type registry so that plugins can register their own
> custom item types.
>
Thanks for the warning.

Are you referring to QEP#9 or to something else ?

What is the status of the work that is "underway" ?

What is the planned time-frame ?

Is there a branch somewhere that I can base my work on / contribute to ?

We need a composer plugin item for a customer project with a deadline in
November. We have planned a few days of dev to contribute that and we'd
rather put those efforts in a long term solution.
>
> It's an extensive work though, because composer has a lot of hard
> coded handling of all the existing item types (checkout all the item
> specific methods in QgsComposition/QgsComposerView). That's why this
> work is tied up with the layouts/reporting framework refactor.
>
I've seen that, and I'm not sure I see why it prevents the introduction
of a plugin item (+registry) that would be used as a base class for
python objects to draw in a frame that is part of a composition.

V.

> Nyall
>
> >
> > Is that what was needed in your cases, or was a more general
> approach required (like the qgis plugin mechanism, being able to
> access the interface) ?
> >
> > V.
> >
> >
> > Le 22/06/2015 18:05, G. Allegri a écrit :
> >>
> >> The suggestion from John is exactly what we did too. And we also
> built a chart composer...
> >>
> >> It would be great to have the means to know what other teams are
> working to. It would save a lor of time and money and, probably, get
> better software from a shared effort ;)
> >>
> >> giovanni
> >>
> >> Il 22/giu/2015 19:31, "John Gitau"  > ha scritto:
> >>>
> >>> Hi Jakob,
> >>>
> >>> A workaround would be to have a plugin that creates a new composer
> view object: 
> >>>
> >>> custom_composer = self.iface.createNewComposer("My Composer")
> >>>
> >>> Then get a reference to the main window in the composer view:
> >>>
> >>> main_window = custom_composer.composerWindow()
> >>>
> >>> Then you can either add a new toolbar (and required actions) or
> append an action to the main toolbar. Have a look at the
> ComposerWrapper class for something similar we implemented for
> designing charts in the
> composer: https://gist.github.com/gkahiu/06a43a589f9441736397
> >>>
> >>> Hope this is helpful.
> >>>
> >>> Cheers,
> >>>
> >>> John
> >>>
> >>> On Mon, Jun 22, 2015 at 2:07 PM, G. Allegri  > wrote:
> 
>  You can act on it but you can't custom gui widgets to the
> Composer interface.
>  I cannot check the code right know. I listen to a specific
> (existing) composition opening but if I remember correctly you can
> watch the Composer opening too.
> 
>  Il 22/giu/2015 17:19, "Jakob Lanstorp"  > ha scritto:
> >
> > Hi Giovanni, thanks for the update. Another solution would be to
> catch the
> > event when a user starts an existing print composer. Cannot in
> doc for the
> > pyqgis API find anything for this. Anyone who know is one can
> listens for a
> > print composer to startup by the user and act on it.
> >
> >
> >
> > -
> > Jakob Lanstorp
> > --
> > View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Building-plugin-for-Print-Composer-tp5212187p5212221.html
> > Sent from the Quantum GIS - Developer mailing list archive at
> Nabble.com.
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> 
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> 
>  ___
>  Qgis-developer mailing list
>  Qgis-developer@lists.osgeo.org
> 
>  http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >>>
> >>>
> >>>
> >>> ___
> >>> Qgis-developer mailing list
> >>> Qgis-developer@lists.osgeo.org 
> >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >>
> >>
> >>
> >> ___
> >> Qgis-developer mailing list
> >> Qgis-developer@lists.osgeo.org 
> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> >
> >
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org 
> >