Thanks, Sergey. This is burried in the extensible mechanism for
maintaining project lists. We could provide a standard services for this
mechanism to do filtering.
Cheers,
Doug.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sergey
Prigogin
Sent: Thursday, October 02, 2008 8:31 PM
To: Eclipse Platform Core component developers list.
Cc: E4 developer list
Subject: Re: [platform-core-dev] Straw man proposal
Doug,
The requirement to have filters associated with folder resources
is missing in the Strawman. It is important that the filters can be
associated with folder resources at creation time to avoid reading files
that are not intended to be a part of the project. This requirement is
critical for scalability.
-sergey
On Thu, Oct 2, 2008 at 5:18 PM, Schaefer, Doug
<[EMAIL PROTECTED]> wrote:
Hey gang,
To feed the discussion for tomorrow's resource meeting,
I have put together a straw man proposal for the e4 resource system
architecture. I'm sure it has a lot of holes and I'm hoping you'll help
me fill them. I could also be totally on the wrong track and maybe
there's better answers we can put on the table. But let's discuss.
The proposal is here:
http://wiki.eclipse.org/E4/Resources/Strawman
<http://wiki.eclipse.org/E4/Resources/Strawman>
Also at tomorrow's meeting we should discuss if we want
to continue our discussions on the platform-core-dev list, or move them
to the e4-dev list. My opinion is changing on this. I'd like to get
concensus from the team on how we want to do this.
Cheers,
Doug.
_______________________________________________
platform-core-dev mailing list
[EMAIL PROTECTED]
https://dev.eclipse.org/mailman/listinfo/platform-core-dev
_______________________________________________
eclipse-incubator-e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
