| Re: [ease-dev] Help Tutorials |
Martin, Vidura,
you could already start to align fort he shell autocompletion:
in case we display functions/constants exported from modules we should display the same help content used for the modules explorer. So Martin you need an interface to extract this data from and Vidura, you could point Martin to the right code locations to pick the data from and how to display those browser tooltips.
Christian
From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Martin Klösch
Sent: Friday, June 19, 2015 11:52 AM
To: ease developer discussions
Subject: Re: [ease-dev] Help Tutorials
Hi,
I've been busy refining and refactoring the shell autocompletion. It is almost at a point where I am satisfied, the only thing left is constructor detection, but that should be finished some time this weekend. I moved most of the code to the base class, so the autocompletion works for both _javascript_ and Python (haven't tried any other language yet). Different languages can then customize the suggestions even further. The mentioned constructor detection will be the first of these language specific features and at first I will only implement this for _javascript_.
After that I will also move on to the editor features. This will be the first time it would be good to really align, because it will be rather difficult to get the typedetection right. I am not sure how you would like to proceed, I suggest we both play around with it for 1-2 weeks just to get a feeling and then merge our prototypes to get a first base for further implementation. Do you agree?
Best regards,
MartinAm 19.06.2015 10:41 vorm. schrieb "Vidura Mudalige" <vbmudalige@xxxxxxxxx>:
Hi Christian,
I abandoned the latter one.
I thought that the fully detailed tooltip on modules will be more user friendly. But I will change it as you said.
I will try to add a style sheet to the rendered content. After that I hope to move to the next part of the project, that is "Bug 468359 Help hovers over editor content".
Thank you.
On Fri, Jun 19, 2015 at 12:34 PM, <Christian.Pontesegger@xxxxxxxxxxxx> wrote:
Hi Vidura,
looks very promising. So you already use the browser widget and render the according information for methods.
· On modules it would be great to extract only the module information (everything before the constants/method overview).
· Can you add a style sheet to the rendered content? Put it into some root folder “resources” and add a sample styling, eg color the title, just to make sure it works
We can then start customizing the look and feel to get closer to the look of the java tooltips. This is something that can be done at the end of this GSoC, if there is still time.
So just have a proof of concept for CSS would be enough so far.
Regarding your change topics on gerrit: please try to use “amend previous commit”
Currently we have 2 open topics for the same thing:
https://git.eclipse.org/r/#/c/50406/
https://git.eclipse.org/r/#/c/50339/
I guess the latter is obsolete? If so, please abandon the topic, then I will push
Keep up the good work!
Christian
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev
--
Vidura Mudalige
Undergraduate
Computer Science & Engineering
University of Moratuwa.
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev