Community
Participate
Working Groups
It would be nice to provide a dialog for testing and verifying regular expresions. It should work the following way: next to fields in which user can enter a regular expression there is a "Check" button. After clicking it there should appear a dialog containing: * an editable field for regex (with initial expression) * a text to which the regex will be matched (editable) * the same text with highlighted regex matches * buttons: OK (replaces initial expression with the one from the field) and Cancel (closes the dialog)
Hmm. I'm really not sure where to put this. This certainly does feel like a useful thing across all languages, but at the same time doesn't fit nicely into the platform at all. I'm not sure what we should do with this Paul...
The intention is to create a reusable UI component which could be used wherever a regular expression is needed. Similar to the one for Working Set (see bug 199904). It's true that regular expressions are not very popular in the UI, but I'm sure there is couple of places where the new component can be used. The other thing that came to my mind is that we could use two versions of the regex validation: * full-blown regular expressions * simple patterns with "*" and "?", which are also quite common And finally, I guess Aleksandra is willing to provide a patch, so you can then decide whether and where you want to use it. It's supposed to be a warm-up task before starting with her bugs for GSOC[1] [1] http://wiki.eclipse.org/The_%22Compare_with%22_dialog
Two ideas where this kind of validation could be used: * Preferences: Team > Ignored Resources > "Add Pattern..." dialog for the *? case * "Fix Copyrights" dialog if we decide to use regular expressions there, which would be quite useful imo I'm pretty sure there is more...
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.
