[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] [GSoC] Support generic script keywords
|
On 03/21/2016 09:37 AM, Vidura Mudalige wrote:
Don't we have to do any change to the event creation? So the
refactoring part is just pushing existing events into the event bus
and creating separate event streams for each keyword?
Currently we have a method called fireEvent() or something like this. It
pushes events to previously registered listeners. Fist task is that this
method additionally pushes events to the event bus. So existing
functionality stays intact while we already have event bus messages
available. Then we will look at listeners that react on already existing
keywords. Instead of the current listener interface we change their
implementation to use the event bus.
Refactoring of the given functionality is really simple and should only
take a few days or even less.
Regarding the UI implementation, when we editing script keywords using
properties view, what should happen to the actual script files? Should
they change as well?
Scripts already provide 2 storages for keywords: a) within the file ->
in that case you have to alter the source of script files. b) in a
metadata storage. Here you just need to set those keywords using a given
API. Somehow the user needs to define where he wants to store properties
to. We also need to visualize if a property is part of the script or
overridden by the local user.
Christian
