<div dir="ltr"><div>Hi Raymond,</div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 16 sept. 2019 à 18:47, Raymond Nijssen <<a href="mailto:r.nijssen@terglobo.nl">r.nijssen@terglobo.nl</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Harrissou!<br>
<br>
How are you? Thanks for the reminder.<br>
<br></blockquote><div> I'm fine, thanks. Hope you are fine, too.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
During the hf I've been working quite some time on the cookbook, to be <br>
exactly on the vector-layer page I started with in A Coruna. I'm halfway <br>
now, at the part where "Symbology" starts. Should I put it in a branch <br>
and share it already? I kind of hope that the symbology part will be <br>
easier and faster.<br>
<br></blockquote><div>Thanks for taking care of this. If you think it's in a mergeable state and can be reviewed, I think it could be nice to publish and have pythonista review it. It would result in less outdated information in the Cookbook.</div><div>If I'm not wrong, a part of the symbology section has been recently updated so less to do.</div><div><br></div><div>Greetings,</div><div>Harrissou<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Kind regards,<br>
Raymond<br>
<br>
<br>
On 16-09-19 17:57, DelazJ wrote:<br>
> Hi all,<br>
> <br>
> The hackfest has gone for weeks, but QGIS is still there as well as <br>
> writers and developers. So I wonder if someone had considered the <br>
> opportunity to give a hand on any of the identified issues.<br>
> <br>
> /NB: It could not be for the "Spare Time Inc" since we still have <br>
> unallocated funds (and not "founds" - damn keyboard)./<br>
> <br>
> Regards,<br>
> Harrissou<br>
> <br>
> Le ven. 23 août 2019 à 18:21, DelazJ <<a href="mailto:delazj@gmail.com" target="_blank">delazj@gmail.com</a> <br>
> <mailto:<a href="mailto:delazj@gmail.com" target="_blank">delazj@gmail.com</a>>> a écrit :<br>
> <br>
> Hi all,<br>
> <br>
> With the QGIS Community Meeting beginning, a bunch of developers and<br>
> writers will meet to brainstorm and improve QGIS. Here are some<br>
> suggestions of topics (among many others) some documentation<br>
> contributors would be REALLY interested in having a fix for. We need<br>
> a developer to address and ease our "life" (sounds tragical enough?<br>
> :D ). Well.<br>
> <br>
> In short:<br>
> 1/ *Improve the automatic creation of screenshots* [1]<br>
> 2/ *Redirect docs links *and ensure that changing links in docs does<br>
> *not break the help button* in application [3]<br>
> 3/ *Document/improve the doctest architecture for PyQGIS Cookbook<br>
> *(kind of [4])<br>
> <br>
> For the details:<br>
> 1/ QGIS is moving fast. Dialogs are changing at every release,<br>
> making screenshots in the docs obsolete. There was a plan to avoid<br>
> writers manually take each screenshot, and instead generate them in<br>
> series, browsing tabs of a specified dialog eg. A work had been<br>
> initiated in the QgsAppScreenshots class [1]. It could be nice to<br>
> get more news on it.<br>
> Incidentally, with such a feature, we can expect more translated<br>
> screenshots (which may not be good for our server but helpful for<br>
> non-English readers and translators).<br>
> <br>
> 2/ Because features are getting bigger, we sometimes need to<br>
> reorganize the chapters in documentation in order to match how<br>
> things behave in the application and also avoid very loooong<br>
> chapters. Moving sections or renaming them (to match their actual<br>
> scope) breaks the Help button associated to the feature, for at<br>
> least three releases (the next-to-be LTR and the two previous<br>
> versions since they point to the same doc). To fix that, doc writers<br>
> have to update the links in the code and this change only applies to<br>
> current release(s), not for EOLed one (eg 3.6 could have more not<br>
> working links than 3.8 or master - we have a script for checks [2]).<br>
> We need to find a more viable way to address this issue and redirect<br>
> requested links to their actual place in the corresponding doc.<br>
> This issue is a long standing one that has been reported/discussed a<br>
> couple of times already (eg [3] has some suggestions)<br>
> <br>
> 3/ During the La Coruna hackfest, a doctest infrastructure has been<br>
> set up to ensure code samples provided for PyQGIS Cookbook are still<br>
> working. Months later, it looks to me like it's less used than it<br>
> should:<br>
> - partly, because we did not make it mandatory,<br>
> - partly because it does not apply (or we did not figure out how?)<br>
> in some cases. Eg it seems it does not know about iface [4]. Also<br>
> there are test projects the system should rely on but nobody uses it<br>
> and afaics there's no example someone not used to this could follow.<br>
> It could be nice clarifying the system and help writers adopt it.<br>
> <br>
> [1] <a href="https://github.com/qgis/QGIS/blob/master/src/app/qgsappscreenshots.h" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/blob/master/src/app/qgsappscreenshots.h</a><br>
> [2] <a href="https://github.com/qgis/QGIS/blob/master/scripts/chkdoclink.sh" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/blob/master/scripts/chkdoclink.sh</a><br>
> [3]<br>
> <a href="https://github.com/qgis/QGIS-Documentation/pull/2258#issuecomment-352246124" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/pull/2258#issuecomment-352246124</a><br>
> [4] <a href="https://github.com/qgis/QGIS-Documentation/issues/3776" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/issues/3776</a><br>
> <br>
> Et voilà... Sorry to have been long. Looking forward...<br>
> And for information, docs still have unallocated founds...<br>
> <br>
> Happy hackfest,<br>
> Harrissou<br>
> <br>
> <br>
> _______________________________________________<br>
> Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>
> <a href="mailto:Qgis-community-team@lists.osgeo.org" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
> <br>
_______________________________________________<br>
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></blockquote></div></div>