-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from p0nce/master
Merging has it has received 3 votes for, 0 votes against.
- Loading branch information
Showing
1 changed file
with
42 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,51 @@ | ||
# documents | ||
# Dlang Graphics Workgroup | ||
|
||
|
||
The output of the Dlang Graphics Workgroup: a technical recommendation for an Image abstraction library, suitable to implement further graphics works. | ||
|
||
**Stage: requirements gathering.** | ||
|
||
**Step 1: requirements gathering.** | ||
|
||
Please vote on proposals here: https://github.com/DlangGraphicsWG/documents/pulls | ||
|
||
Current list of unsolved disagreements: https://github.com/DlangGraphicsWG/documents/wiki | ||
|
||
Current requirements gathered: [requirements.md](requirements.md) | ||
|
||
Current decision process: [decision-process.md](decision-process.md) | ||
|
||
|
||
# Goals | ||
|
||
|
||
The Dlang Graphics Workgroup is a collective of D library writers who want to | ||
make libraries together with a collegial design. | ||
|
||
|
||
|
||
We feel that Phobos leads the path towards building reusable, expressive abstractions; | ||
and that there is no reason a GUI Toolkit can't be unopinionated to the same degree std.range or std.allocator is. | ||
|
||
We acknowledge that working on our own graphics libraries (like we currently do), may not yield | ||
the best possible result for everyone; and that discussion and arguing are called | ||
for if we are to keep the D community engaged. | ||
|
||
Because this task is essentially about defining graphical interfaces, and those interfaces exchanges "images", | ||
**our first line of work is the design of an Image library**. | ||
|
||
Because this task is essentially about (dis)agreement, we **talk about pain points** (pros/cons) | ||
and give them existence. | ||
|
||
|
||
## Step 1: | ||
|
||
Find out what we actually need in an Image library. | ||
|
||
## Step 2: | ||
|
||
Figure out what we already got that matches it. | ||
|
||
## Step 3: | ||
|
||
Figure out what do we need to do to make it fully match our needs. | ||
|