Re: [ease-dev] [GSoC] Support generic script keywords

[Christian Pontesegger <christian.pontesegger@xxxxxx>]

Hi Vidura,

plan is to exchange the existing functionality with the new keyword mechanism. So your code should go into o.e.e.ui.scripts. No need to start a new plugin there.
As a first step you may leave existing functionality in there. Currently there exists a service checking for scripts. It then uses a publisher/subscriber pattern to promote events.
You should additionally push script events to the event bus. The bus allows to filter events and to subscribe to dedicated streams. If each keyword creates its own event stream, listeners might filter only on events they are interested in. Once events work next step is to replace the existing toolbar/menu, ... keyword listener mechanism with the new event system. Its functionality could remain the same, so no need to implement something here.
Then you should add some new event listeners. I gave some examples on the topic description on this list but would also be very interested in your ideas.

So question 1 should be clear by now.
Question 2: o.e.e.ui.scripts handles registration of script locations and provides services for script parsing (read out those keywords) and event creation. Additionally the listener for script binding to the UI is located there.

cheers
Christian

On 03/19/2016 12:29 PM, Vidura Mudalige wrote:

Hi Christian,

I went through the references and tried to outline the refactoring step.

I am planning to create a separate plugin which can extract all the available scripts and the keywords of these scripts(For this the existing functionalities of o.e.e.ui.scripts can be used). Using these scripts some suitable events should be created. These events should be posted to Eclipse event bus by using the keywords as the topics. All the possible keywords should be implemented as separate listeners(We can add new keywords here in future). Each of these listener should subscribe to the event bus by using their keywords as the topics. Also each of these listener should have a event handler method which deals with the corresponding component(For this the existing functionalities of UIIntegrationJob class in o.e.e.ui.script plugin can be used). Am I following the correct path?

Now I have few questions.

1. After implementing this new plugin what should happen to the current pub/sub mechanism of o.e.e.ui.scripts plugin?

2. What are the other main functionalities in o.e.e.ui.script plugin which can be affected from this new mechanism?

Thank you.    

--

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