Community
Participate
Working Groups
Build 3.1.0 This is a reminder to keep JDT informed if CamelCase support is introduced in the platform. Note that we have defined CharOperation#camelCaseMatch(...) operations, and this is intended to be in JDT/Core as leveraged in search & codeassist which are headless operations. JDT is planning to support CamelCase for 3.2
I'm not sure who on UI should be looking at this.
I've been thinking about this and I'm not sure that it makes as much sense in general as it does for Java.
Actually it's not just Java (certainly a general development issue). We have a number of bugs in other areas requesting CamelCase as well.
Susan, Doug - can we discuss what we might want to provide in a general sense here. NOTE, I'm not necessarily talking about 3.2 just what would we do. Also I believe JDT or others might be willing to provide patches.
I'll be looking at CamelCase from the standpoint of bug #94382 (Open Resource/Open Type sharing code) during this milestone (M4).
We have defined an API in JDT/Core: CharOperation#camelCaseMatch(...). It could be pushed down into the platform, but note that we need it in headless land. Also, our implementation is char[] based for performance reasons, and we would want to preserve that (i.e. there could be several versions of the same method, but one efficient implementation for char[]). Given CamelCase is not well specified, it could be problematic to come up with several implementations, which would likely not be exactly the same.
moving Open Resource related bugs to Szymon. Szymon, please move between you and Krystof as needed. Let me know if you have any questions. These are all the bugs I had related to OpenResource.
Krzysztof is responsible for camel case support in the platform.
JDT/Core implementation for CamelCase is done in org.eclipse.jdt.core.search.SearchPattern class (camelCaseMatch methods)
This support is currently in org.eclipse.ui.dialogs in the workbench rather than in JFace.
CamelCase is done in org.eclipse.ui.workbench inside classes: org.eclipse.ui.dialogs.SearchPattern and org.eclipse.ui.dialogs.CharOperation.
CamelCase works properly for open resource dialog. All functionality for camelCase filtering is inside org.eclipse.ui.dialogs.SearchPattern .
Unfortunately, we were not aware of the fact that Platform/UI just copied and modified JDT/Core's implementation, and now it's too late to fix this bug for 3.3. Reopening, since this needs to be cleaned up for 3.4. The diverging implementations of CamelCase support have already caused a lot of grief (see e.g. bug 176017).
Moreover, if CamelCase support is going to be used in the Platform, you should also support something like JDT/UI's TextFieldNavigationHandler (again, this needs to be coordinated, and the implementation needs to be cleaned up before it is moved, etc.).
Krzysztof left the team some time ago. I'm removing the target milestone.
Reassigning to Susan.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009. Updating title to make it a bit clearer what is requested. This is one of many "look at all the copies of XXX function and try to offer a consolidated class/API for it" bugs. I'm assigning to JFace because that's where similar bugs are assigned, but it's not clear if the API would actually live there.
see also bug 393293 for some more ideas on enhancing this feature
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. -- The automated Eclipse Genie.
