[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-core-dev] Flexible Resource Model use case
|
I think that the scenario in which people typically think of using
exclusion in a link directory is related to difficulty of including
files to begin with.
For example, because traditional C/C++ IDE (Visual Studio, CodeWarrior,
etc...) lack an automatic inclusion folder link mechanism, the user has
to explicitly include which files in a directory should be included in
the project.
Because in eclipse it is currently so awkward to *include* files (i.e. a
linked resource has to be manually created for each single file), the
users typically resort to create a folder linked resource for the
parent, and then run into problems with excluding new siblings that are
created.
My opinion is that if eclipse provided better UI to create linked
resource in the first place (such as creating a linked resource tree by
drag and drop from Windows Explorer, from an "Add Files..." menu when
right clicking on a container resource in the navigator, etc...), the
users wouldn't need a complex mechanism to attempt to exclude resources,
they would simply include the needed resources explicitly.
Serge Beauchamp.
Software Engineer
Freescale Semiconductor
Oberhuber, Martin wrote:
Linked Resources can mask stuff on a case by case basis.
Do you think that exclusion based on Patterns would be possible in 3.5
as well?
Cheers,
--
*Martin Oberhuber*, Senior Member of Technical Staff, *Wind River*
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
------------------------------------------------------------------------
*From:* platform-core-dev-bounces@xxxxxxxxxxx
[mailto:platform-core-dev-bounces@xxxxxxxxxxx] *On Behalf Of *John
Arthorne
*Sent:* Dienstag, 20. Mai 2008 20:02
*To:* Eclipse Platform Core component developers list.
*Subject:* Re: [platform-core-dev] Flexible Resource Model use case
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.
John
*"Terence Parker" <eclipse.tparker@xxxxxxxxx>*
Sent by: platform-core-dev-bounces@xxxxxxxxxxx
05/20/2008 01:20 PM
Please respond to
"Eclipse Platform Core component developers list."
<platform-core-dev@xxxxxxxxxxx>
To
platform-core-dev@xxxxxxxxxxx
cc
Subject
[platform-core-dev] Flexible Resource Model use case
I haven't seen the following use case yet so I want to add it to
the discussion.
* A project needs to pull in code that is rooted in folder "A1"
* A1 is outside the user's workspace
* A1 contains many subfolders
* Only a handful of A1's subfolders are a part of the project
* IFolder.createLink() is called, linking the project to
folder A1
* IFolder.createLink() starts a refresh that traverses
_everything_ under A1
* The cost of traversing all of A1's subfolders is too
high--IResource.setHidden() can only be called on subfolders
after they have been pulled into the workspace
We need a way to hook into the resource delta creation so that any
nested subfolder can be hidden _before_ that subfolder is traversed.
--Terry Parker_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev
------------------------------------------------------------------------
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev