[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-core-dev] Flexible Resource Model use case
|
On Tue, May 20, 2008 at 11:01 AM, John Arthorne <
John_Arthorne@xxxxxxxxxx> wrote:
Exclusion is definitely an interesting
area to explore. Note that IResource#setHidden is not the best mechanism
for implementing this though. setHidden will hide the resource from the
UI, but under the covers it will still create the entire subtree and much
of the cost will be the same. You can actually exclude subtrees today
using a linked resource pointing to the null file system, but there is
no UI for doing it. I think with a bit of UI work, exclusion support could
be added with very little effort even in 3.5 if there was interest in doing
it.
I hadn't known that about setHidden. For performance on large code bases an alternative that doesn't create the subtree is needed.
Setting up linked resources to null file systems doesn't address a scenario where you want the direct contents of parent folder A1 and of its child subfolder B1, but not of other subfolders of A1. In that case you can link to individual files in A1 and the folder B1, but then the refresh behavior is different for A1 and B1. You could create all links at the file level rather than the folder level, but that doesn't scale well for large projects. It also ties you to a view of a folder that doesn't update when you refresh it. Or was your suggestion to hide a subfolder by creating a null file system link with the same name?
--Terry
