On Thursday, 23 January 2020 at 19:11:19 UTC, Jordan Wilson wrote:
On Thursday, 23 January 2020 at 15:19:34 UTC, bauss wrote:
Novelate is a visual novel engine written in D.
It officially binds to SFML but the engine itself has no
direct dependencies on SFML as there's plans for supporting
On Thursday, 23 January 2020 at 18:00:30 UTC, Cym13 wrote:
On Thursday, 23 January 2020 at 15:19:34 UTC, bauss wrote:
Novelate is a visual novel engine written in D.
It officially binds to SFML but the engine itself has no
direct dependencies on SFML as there's plans for supporting
libraries
On Thursday, 23 January 2020 at 17:05:10 UTC, Robert Schadek
wrote:
DESTROY!
Tried:
---
unittest {
immutable SemVer v1 = SemVer(1,1,1);
immutable SemVer v2 = SemVer(2,2,2);
immutable SemVer v3 = SemVer(3,3,3);
immutable SemVer v4 = SemVer(4,4,4);
immutable VersionRange a =
On Thursday, 23 January 2020 at 15:19:34 UTC, bauss wrote:
Novelate is a visual novel engine written in D.
It officially binds to SFML but the engine itself has no direct
dependencies on SFML as there's plans for supporting libraries
such as SDL etc. in the future too.
It's still a
On Thursday, 23 January 2020 at 15:19:34 UTC, bauss wrote:
Novelate is a visual novel engine written in D.
It officially binds to SFML but the engine itself has no direct
dependencies on SFML as there's plans for supporting libraries
such as SDL etc. in the future too.
It's still a
dud needs your help.
I'm starting work on the dependency resolution and for that I had
to implement proper handling for Semantic Versions, Version
Ranges,
and Version Unions(VersionUnion is basically a VersionRange[]).
The dependency resolution algorithm I want to implement (based on
the
Novelate is a visual novel engine written in D.
It officially binds to SFML but the engine itself has no direct
dependencies on SFML as there's plans for supporting libraries
such as SDL etc. in the future too.
It's still a work-in-progress but the basics are done as of now
and it has
