<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 08/08/2015 11:19, Nyall Dawson a
écrit :<br>
</div>
<blockquote
cite="mid:CAB28AsgSjS=Xcyr-bEsY0Vs+NRLk5BQfw8A-=SoQfLU4Mxi5LA@mail.gmail.com"
type="cite">
<p dir="ltr"><br>
On 7 Aug 2015 6:58 pm, "Vincent Mora" <<a
moz-do-not-send="true" href="mailto:vincent.mora@oslandia.com">vincent.mora@oslandia.com</a>>
wrote:<br>
><br>
> Hi all,<br>
><br>
> 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.</p>
</blockquote>
Hi Nyall,<br>
<blockquote
cite="mid:CAB28AsgSjS=Xcyr-bEsY0Vs+NRLk5BQfw8A-=SoQfLU4Mxi5LA@mail.gmail.com"
type="cite">
<p dir="ltr">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. </p>
</blockquote>
Thanks for the warning.<br>
<br>
Are you referring to QEP#9 or to something else ? <br>
<br>
What is the status of the work that is "underway" ? <br>
<br>
What is the planned time-frame ?<br>
<br>
Is there a branch somewhere that I can base my work on / contribute
to ? <br>
<br>
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.
<blockquote
cite="mid:CAB28AsgSjS=Xcyr-bEsY0Vs+NRLk5BQfw8A-=SoQfLU4Mxi5LA@mail.gmail.com"
type="cite">
<p dir="ltr">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.</p>
</blockquote>
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.<br>
<br>
V.<br>
<br>
<blockquote
cite="mid:CAB28AsgSjS=Xcyr-bEsY0Vs+NRLk5BQfw8A-=SoQfLU4Mxi5LA@mail.gmail.com"
type="cite">
<p dir="ltr">Nyall<br>
</p>
<p dir="ltr">><br>
> 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) ?<br>
><br>
> V.<br>
><br>
><br>
> Le 22/06/2015 18:05, G. Allegri a écrit :<br>
>><br>
>> The suggestion from John is exactly what we did too.
And we also built a chart composer...<br>
>><br>
>> 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 ;)<br>
>><br>
>> giovanni<br>
>><br>
>> Il 22/giu/2015 19:31, "John Gitau" <<a
moz-do-not-send="true" href="mailto:gkahiu@gmail.com">gkahiu@gmail.com</a>>
ha scritto:<br>
>>><br>
>>> Hi Jakob,<br>
>>><br>
>>> A workaround would be to have a plugin that creates
a new composer view object: <br>
>>><br>
>>> custom_composer = self.iface.createNewComposer("My
Composer")<br>
>>><br>
>>> Then get a reference to the main window in the
composer view:<br>
>>><br>
>>> main_window = custom_composer.composerWindow()<br>
>>><br>
>>> 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: <a moz-do-not-send="true"
href="https://gist.github.com/gkahiu/06a43a589f9441736397">https://gist.github.com/gkahiu/06a43a589f9441736397</a><br>
>>><br>
>>> Hope this is helpful.<br>
>>><br>
>>> Cheers,<br>
>>><br>
>>> John<br>
>>><br>
>>> On Mon, Jun 22, 2015 at 2:07 PM, G. Allegri <<a
moz-do-not-send="true" href="mailto:giohappy@gmail.com">giohappy@gmail.com</a>>
wrote:<br>
>>>><br>
>>>> You can act on it but you can't custom gui
widgets to the Composer interface.<br>
>>>> 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.<br>
>>>><br>
>>>> Il 22/giu/2015 17:19, "Jakob Lanstorp" <<a
moz-do-not-send="true" href="mailto:jlanstorp@gmail.com">jlanstorp@gmail.com</a>>
ha scritto:<br>
>>>>><br>
>>>>> Hi Giovanni, thanks for the update. Another
solution would be to catch the<br>
>>>>> event when a user starts an existing print
composer. Cannot in doc for the<br>
>>>>> pyqgis API find anything for this. Anyone
who know is one can listens for a<br>
>>>>> print composer to startup by the user and
act on it.<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> -----<br>
>>>>> Jakob Lanstorp<br>
>>>>> --<br>
>>>>> View this message in context: <a
moz-do-not-send="true"
href="http://osgeo-org.1560.x6.nabble.com/Building-plugin-for-Print-Composer-tp5212187p5212221.html">http://osgeo-org.1560.x6.nabble.com/Building-plugin-for-Print-Composer-tp5212187p5212221.html</a><br>
>>>>> Sent from the Quantum GIS - Developer
mailing list archive at Nabble.com.<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">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>>>><br>
>>>><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">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>>><br>
>>><br>
>>><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">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>><br>
>><br>
>><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">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
><br>
><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">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</p>
</blockquote>
<br>
</body>
</html>