Community
Participate
Working Groups
Using the most excellent CPath mechanism to designate source folders results in a source folder being decorated with a "C". This is useful as it helps distinguish source folders from non-source folders. If you select the top level project - which makes all of the contained folders source folders - you don't get any source folder decorations. To avoid confusion to the user, we should be consistent in our source folder decoration...
> Using the most excellent CPath mechanism to designate source folders [[laughs]] Are you looking for Boston Cream with Coffee ? ... It will not happen ... 8-) > you don't get any source folder decorations. Correct, if there is no source folder or the source folder is explicetly the project, we do not show any source folder. This is done because: - To be consistent with JDT - To be backward compatible - To be consitent. Even if we create a Source folder(SourcRoot) it is collapse by the CView so it is less confusing to the user. Since the folders underneath are ICContainer but not ISourceRoot I think what you are saying is that we should have another icons to indicate that a folder is part of the model. For example in JDT they have 2 icons: IPackageFragmentRoot --> source folders IPackageFragment --> folders under package folders: (can be collapse, depending on the layout) IFolder --> normal non Java folders. So C should do the same ISourceRoot --> source folder ICContainer --> folder underneath source folders IFolder --> non CElement folder
PR was not targeted to any particular release. Changing target milestone to 2.1
Returning to the pool.
Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'.
