|
|
Re: Code Recommenders specialized for Scout [message #1282611 is a reply to message #1282066] |
Wed, 02 April 2014 15:24 |
|
Hi Jeremie,
Hi Matthias,
thanks for moving this discussion into your forum. We put together a short installation guide [1] that shows how to install and configure our crowdsourced code completion for Eclipse Scout.
Matthias,
your question regarding proposal order: I *think* (maybe I'm wrong) you expected the getConf* methods to be on top - but they aren't, right? This is because public methods get a much higher relevance by JDT than protected methods. This is built-in behavior of JDT and we did not change this behavior.
Scout users,
if you have any questions, please post them here.
Thank you,
Marcel
[1] http://goo.gl/7ytglC
[Updated on: Wed, 02 April 2014 21:34] Report message to a moderator
|
|
|
|
Re: Code Recommenders specialized for Scout [message #1282861 is a reply to message #1282844] |
Wed, 02 April 2014 21:33 |
|
> If i understood correctly [...]
You do.
> As the configuration and behaviour of Scout elements are consistently modeled with the protected getConf*
> and exec* methods of the abstract field classes this is somewhat unfortunate. do you think that there is a
> chance in the future to more closely match the design of the Scout application model?
We are able to implement any ordering, labeling and highlighting scheme you'd like to see for Scout
What else do you have in mind?
|
|
|
|
|
|
Re: Code Recommenders specialized for Scout [message #1289181 is a reply to message #1288695] |
Wed, 09 April 2014 05:31 |
|
> Should I worry about the Info messages in the Error Log?
No. It's more a debug message saying that there is yet no model in the repository for this jar. As soon as you share data for that, the miner will create models and these messages will disappear.
Having said this, I think we simply should hide those messages.
Thanks for the feedback,
Marcel
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05234 seconds