Community
Participate
Working Groups
I was wondering if the field editors currently available should be extended with more OOTB funcitonality, especially a flexible field editor with regexp field validation and automatic error messages would be helpful for many purposes. This could e.g. be subclassed to allow URL validation, mailto- validation etc?
I think many of the building blocks are there (field editors, content proposal adapter, etc.). Even if we did not offer API, a sample that ties this together might be interesting. But this won't happen in the 3.3 timeframe, as we are past API and function freeze...
No interest in revisiting this for 3.4? Even platform could already make use of such editors?
No arguments on the usefulness of this idea, everything typically becomes a matter of available time. We would always entertain a patch. ;-) However even a proposed implementation would need to be done before M6 API freeze in order to make 3.4.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.
