On mercredi 21 juin 2017 11:32:49 CEST DelazJ wrote:
> 2017-06-21 11:22 GMT+02:00 matteo :
> > Hi Harrissou and Yves,
> >
> > ok so no webhooks or some automatic tasks that is "aware" of new
> > algorithms of Processing to put them in the docs.
> >
> > There's. IF the committer adds the [feature]
2017-06-21 11:22 GMT+02:00 matteo :
> Hi Harrissou and Yves,
>
> ok so no webhooks or some automatic tasks that is "aware" of new
> algorithms of Processing to put them in the docs.
>
> There's. IF the committer adds the [feature] tag to the commit, then an
issue is created in the Documentation, s
Hi Harrissou and Yves,
ok so no webhooks or some automatic tasks that is "aware" of new
algorithms of Processing to put them in the docs.
Yves, as soon as Nyall is finished with the Processing armageddon I will
make some checks, open tickets and add the missing algorithms.
BTW isn't it possible
Matteo,
On mercredi 21 juin 2017 09:43:39 CEST matteo wrote:
> Is the documentation of he Processing providers (in the website) build
> according to the algorithm number of the UI?
Probably for the first import but now this is a manual task. Could you open
ticket(s) on missing alogrithmes?
Than
Hi Matteo,
As far as I know there is no automatic process to generate/fill a section
in the online documentation for each algorithm added to Processing. Someone
has to be aware of this new algorithm and write its description. And I'm
not sure it has often be the case untill the webhook (which curr
Hi all,
Processing is now in big reorganization but also before its porting in
C++ I noticed some differences between the number of algorithm in the UI
and those in the website.
For example, I remember that there were some algorithm in the Database
menu that involves also SpatiaLite while in the d
