Hello Vincent, For now, the Recommendation Engine from the application (easyrec) can't read data, we have to send data to it through its Rest API. And it can't deal with raw data, we would have to count the number of uses of each API and send that data to the Recommendation engine, but if we have such data I don't think we'd need a Recommendation Engine since we would already know the most used APIs. The Recommendation Engine would then be more appropriate if we use it to recommend APIs based on what happened in the wiki and not what can be found on Github. We could also train the engine with the APIs used by the users of the Auto Completion Extension, and it would be easier to implement, but it would require a "training" period with bad recommendations. Thanks, Yann On Wed, Aug 5, 2015 at 12:14 PM, [email protected] <[email protected]> wrote:

Hi devs and especially Caleb,

This is a wild idea of how to combine a Recommendation Engine and the Auto Completion Extension we have.

See https://blogs.oracle.com/geertjan/entry/eclipse_recommenders_for_netbeans_id... for the details.

In short, it’s about listing the most used APIs at the top of the suggestion box when hitting the auto completion shortcut key.

WDYT? Would the Recommendation Engine used by http://extensions.xwiki.org/xwiki/bin/view/Extension/RecommendationsApplicat... work for this?

I’m mostly curious at this stage since I don’t know how much work it would require. The idea would be that the recommendation engine would read all extension code found on github xwiki and xwiki-contrib repos to generate a usage list. This would need to run regularly and the result would need to find its way into the Auto Completion Extension somehow.

Just a wild idea… :)

Thanks -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs