| Re: [ease-dev] Definition of org.eclipse.ease.module.platform.Selector lost? |
|
On 25.08.2014 17:55, GAUFILLET, PIERRE
wrote:
Hi, when checking out the projects from org.eclipse.ease.core in your workspace you will experience quite some plugins showing errors: org.eclipse.ease.integration.modeling.* o.e.ease.ui.e4 o.e.ease.ui._expression_.* These plugins are not part of the current maven build. Reason for this is that we have restructured the project and split it up in 3 repos: core, modules and scripts So all the integration plugins should move to modules, while the examples should go to scripts. During refactorings I must have deleted the extension point by accident. So we should rescue it (http://git.eclipse.org/c/e4/org.eclipse.e4.scripting.git/tree/Plugins/modules/org.eclipse.ease.module.platform/schema/Selector.exsd) and move it to some location in the modules repo. While looking at the code of the plugins I would suggest to clean them up, add documentation and ev. use some new features of the engine like optional parameters. Named parameters are sometimes inconsistent and would need some cleanup, too. Besides that we changed the way scripts can hook code into the UI thread which is a bit safer now than it was when we started last year. But without Arthur around who knows what the methods should do and what they are used for I have quite a hard time to implement this. When reworking those modules we should also consider their focus. Do they target a broad community of eclipse users or are they tailored for a dedicated project? Personally I cannot tell as I've never seen the use cases. regards Christian |