Community
Participate
Working Groups
I propose to replace the current hardcoded Expressions used in the Expression Framework to be replaced by an extension based approach. An expression could be represented by an extension and it would allow plugin developers to develop own expressions (like Scripting). It should be easy to do, I could try to supply the initial patch for it. Or is something like that planned for e4 and will not be introduced into the 3.x stream anymore at this stage? Example: <pre> <extension id="core.expression.extensions"> <expression name="ruby" class=org.ruby.eclipse.expression.internal.RubyExpression> </expression> </pre> This would provide a new "tag" with the name "ruby" to the expression XML parser. The RubyExpression class must implement Expression.
Paul, this is you, I'm not sure how to assign something to runtime expressions.
I'd probably suggest we look at this under bug 269698 PW
Ah sorry Paul for filing the same enhancement request twice. So your main concern is the tooling support in PDE for that? I think it would be possible for PDE to know about available extensions. So when you define a new ExpressionConverter in one of the plugin.xml PDE could know about it, and add the tag to its known tags. For adding values to the content assist, I think as with the "with" variable, the PDE does not support very much content assist there either. Also if we add support of extensions to PDEs tag validator we could just transform all currently known default expressions to extensions too.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
