[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ease-dev] [GSoC Proposal] Support generic script keywords
|
This is a proposal for GSoC 2016, to add generic script keywords to EASE.
EASE allows to register script locations. Such scripts get their own
Explorer view and typically hold macros that users need on a daily
basis. Such scripts are simple scripts files, augmented with a special
comment header, that may contain keywords. When a script location is
parsed, the keywords are extracted and actions are performed upon them.
Currently we use a publisher/subscriber pattern to push these keywords
to interested listeners which then implement actions. As of today we
support actions to bind scripts to toolbars and menus.
In the future we want to support generic keywords and provide a simple
way to listen for them. The idea is to use the event bus of Eclipse
instead of the publisher/subscriber pattern. So new scripts will promote
their keywords on the event bus. Clients may listen for such events and
react on them accordingly.
want to add some security to them.
Your task would be to change the current implementation to use the event
bus. Therefore you need to change the current listener mechanism so that
existing functionality does not break.
Further we need a page in the Properties view to display and change
script keywords without touching the script file content.
Finally a new keyword handler should be implemented that allows scripts
to be run on certain timed events, like a cron job. The cron syntax [1]
should be supported. Furthermore the special entries @Startup, @Shutdown
should be supported.
Skills required for this task:
You should have experience in UI programming best already with e4.
Experience with the event bus will help you in solving this GSoC assignment
and of course you need to get acquainted to EASE.
If you think of applying for this task you should introduce yourself on
this mailing list. Further you should do a sample commit to EASE. This
could be a small donation to a JavaDoc comment in one of the source
files, so you do not need to fix code already. It will prove that you
are able to set up your development environment and that you are
familiar with the contributor workflow.
looking forward for your applications
cheers
Christian
