Should the projector be split off?

[hampelm]

Datasources require nodetiles-core just for the projector. It seems that it would be cleaner to split the projector off and require it in both datasources and core? That way we're not requiring the whole core for each datasource.

[bensheldon]

Makes sense to me.
—
Sent from Mailbox for iPad

On Thu, May 23, 2013 at 11:36 AM, Matt Hampel [email protected]
wrote:

Datasources require nodetiles-core just for the projector. It seems that it would be cleaner to split the projector off and require it in both datasources and core? That way we're not requiring the whole core for each datasource.

Reply to this email directly or view it on GitHub:
#53

[Mr0grog]

That way we're not requiring the whole core for each datasource.

But you aren't ever going to use a datasource without core around anyway, right? Pulling this out might be nice and tidy, but I don't really see any actual benefit to it.

[bensheldon]

@rob you may be right. Would there ever be the case in which either scenario would set up a crazy dependency graph, eg: a data source requires a different version of core/projector than the project/core is using. 

​It makes my head hurt to think about, but I'll look at some other projects that do these types of "many small parts that make up a larger system" and see how they deal with dependency issues like this.

On Thu, May 23, 2013 at 4:28 PM, Rob Brackett [email protected]
wrote:

That way we're not requiring the whole core for each datasource.

But you aren't ever going to use a datasource without core around anyway, right? Pulling this out might be nice and tidy, but I don't really see any actual benefit to it.

Reply to this email directly or view it on GitHub:
#53 (comment)

[bensheldon]

I poked around RailwayJS (now apparently Compound) and they seem to have everything pretty well separated.

I'm on the fence because:

• the projector has some exposed interfaces that other packages (the datasources) are using, which makes me think it would be good to package/version it separately.
• BUT, I don't know what the result would be if there were version conflicts between what the package is using and core is using.

Alternative proposal: rather than datasources including core as a dependency, we inject the projector (or all of core?) into the datasource.

Edits: Ruby on the brain.