| Re: [ease-dev] Shell autocompletion |
Hi Martin, just tried it out, looks really promising. I agree, parsing the text is the most critical problem. For auto completion in general we need to distinguish following cases: 1) you have a call chain with a parent Java object in this case it resolves to use reflection for java fields and methods At a later stage it would be interesting to try to extract the java doc comments that the java editor displays for its methods. Maybe we find a way to reuse their tooltips. This is something to be evaluated together with Vidura. 2) parent object coming from javascript If we have a javascript class, we could try to parse for its properties and display them to the user. This one has low priority from my point of view and could be a nice to have target for GSoC. I guess it will only work for the script shell anyway. 2) no parent available Here we should display functions available for the script interpreter. We can do this by a) looking for loaded modules and their functions and b) looking for user defined functions and variables. For the first ones, we can reuse the help text provided by Vidura. Did you both already start to align with each other? -- Christian
Attachment:
smime.p7s
Description: S/MIME cryptographic signature