[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A unified project root interface

From: Jorgen Schaefer
Subject: Re: A unified project root interface
Date: Sat, 23 Mar 2013 18:26:48 +0100

On Sat, 23 Mar 2013 13:10:20 -0400
"Eric M. Ludlam" <address@hidden> wrote:

> If this project concept is created as a simple thing, that's fine,
> but EDE won't be able to use it, though it could contribute.   If
> that's the overall story where simple uses need the simple project,
> and EDE is used when you need more, that seems like a fine
> compromise, but it won't simplify the plethora of project projects.

Let's say we create two primary API functions

- (project-root)
- (project-set-root DIR)

so that PROJECT-ROOT returns the current project root if set, and if
not, sets it to something a simple hook returns. Then, if EDE's project
system simply calls (project-set-root DIR) when it loads, we end up
with a upwards-compatible system so that some extensions can just use
P-R to find the project root, and will continue to work when EDE is in
use. If they need more functionality than P-R, they can simply
transition over to using EDE.

Am I missing something?

        -- Jorgen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]