Hi!
I have been wondering if there any plans of splitting D into a bunch of smaller, replaceable packages that integrate well together.
One of the immediate benefits of this would be a much better extension/modding interface.
I believe this could also increase the number of contributions and contributors, as it would be easier to develop new functionality without knowing all the internals, as long as the extension interfaces are well documented.
Have there been any thoughts on this?
Am 13.07.2015 um 13:38 schrieb Márcio Martins:
Hi!
I have been wondering if there any plans of splitting D into a bunch of smaller, replaceable packages that integrate well together.
One of the immediate benefits of this would be a much better extension/modding interface.
I believe this could also increase the number of contributions and contributors, as it would be easier to develop new functionality without knowing all the internals, as long as the extension interfaces are well documented.
Have there been any thoughts on this?
The first step is basically ready to be merged into master:
https://github.com/rejectedsoftware/vibe.d/blob/subpackages/dub.json
However, there was a bug in DUB 0.9.22 that prevented the sub modules
from working, so I want to make sure that 0.9.23 or up are reasonably
widespread before making the switch.
The next step will probably be to switch to either separate sub folders
or separate repositories. But this still has to be determined.
What this change doesn't add is a way to generally replace sub modules.
However, in many parts this is already supported through the existing
API, so this would be mostly a question of demand.
On Mon, 13 Jul 2015 13:54:15 +0200, Sönke Ludwig wrote:
Am 13.07.2015 um 13:38 schrieb Márcio Martins:
Hi!
I have been wondering if there any plans of splitting D into a bunch of smaller, replaceable packages that integrate well together.
One of the immediate benefits of this would be a much better extension/modding interface.
I believe this could also increase the number of contributions and contributors, as it would be easier to develop new functionality without knowing all the internals, as long as the extension interfaces are well documented.
Have there been any thoughts on this?
The first step is basically ready to be merged into master:
https://github.com/rejectedsoftware/vibe.d/blob/subpackages/dub.jsonHowever, there was a bug in DUB 0.9.22 that prevented the sub modules
from working, so I want to make sure that 0.9.23 or up are reasonably
widespread before making the switch.The next step will probably be to switch to either separate sub folders
or separate repositories. But this still has to be determined.What this change doesn't add is a way to generally replace sub modules.
However, in many parts this is already supported through the existing
API, so this would be mostly a question of demand.
Great! You guys are way ahead! :)
