Community
Participate
Working Groups
Created attachment 256717 [details] Screenshot of the improved completion for AQL In this new step in my quest to improve the AQL code completion in Sirius, it is time to improve more advanced areas that are a bit lacking compared to the JDT including: 1 - camel case support for the proposals "self.eAlCo" should propose eAllContents() and eAllContents(type). 2 - camel case filtering "self.e" should propose things like eContents() and eAllContents() but while keeping the proposals open, typing "AC" to have "self.eAC" should filter the proposals to only show things like eAllContents(). This feature would have to be supported, for the interpreters that want it in the Sirius/JFace integration. 3 - styled string support This should be done without any dependency to the UI for the AQL runtime or the Sirius completion proposals. This work should also simplify the integration for other interpreter whiteout any dependency to AQL directly. The styled string support should be visible both in the proposals and their documentation. 4 - better documentation viewer Using a custom IInformationControl Sirius could control advanced features like a hyperlink detector or even additional actions, in the JDT there is the Open Declaration action for example. We could also control the text wrapping, the scrollbar etc. Those improvements may not be available in Sirius 3.1 since I have to clean things a bit and the deadline maybe a bit to close to integrate this work (unless you want it NOW!) but I will try to contribute it soon. Of course, those new behaviors should degrade nicely with proposals that do not support them for other interpreters. As usual, I have attached an image to this issue as a teasing of things to come :)
(In reply to Stephane Begaudeau from comment #0) > Those improvements may not be available in Sirius 3.1 since I have to clean > things a bit and the deadline maybe a bit to close to integrate this work > (unless you want it NOW!) but I will try to contribute it soon. All of these sound (and look) good, but we're approaching the final freeze for 3.1, so I'm putting this for 4.0 (may happen in a milestone). No hurry to finish your patches.
Additional task The analysis of the proposal start typed by the specifier (VSM editor) or by a user (interpreter view) should not be case sensitive, the completion should allow (like the MTL completion) . to type aql:self.NA to retrieve aql:self.name . to type aql:self.eallco to retrieve aql:self.eAllContents()
Moving out of the 4.0 scope for now, along with all the other issues which were there "by default". This does not mean some of these will not be re-integrated at some point, but for now these issues are not part of the roadmap for 4.0. If you feel strongly about this removal from 4.0 and/or are ready to sponsor the corresponding work, feel free to comment.
*** Bug 484851 has been marked as a duplicate of this bug. ***
